By Nilesh Gadekar, Founder · Last reviewed .
1. Set a source-file standard
Ask contributors for editable originals. Use heading styles, meaningful link text, table headers, and image descriptions. Scanned signatures or attachments may need separate handling. Avoid making the final PDF the first point at which structure is considered.
2. Inventory the packet components
List the agenda, attachments, supplements, and minutes. Identify page counts, scans, forms, and complex tables. Record which components are likely to arrive late so the review scope can be adjusted.
3. Assemble without losing structure
Combining PDFs can disrupt tags, bookmarks, links, and reading order. Review the assembled packet as well as individual files. A correctly structured source is useful, but the final exported version is what families receive.
4. Review the task
Check that a reader can move between agenda sections, identify attachment references, follow links, read tables, and understand important visual content. Record both automated checks and the manual methods used.
5. Verify what was posted
Agree on a version name. After publication, check that the public URL serves the reviewed file. Treat late replacements as a new version that may need another review.
Create an ongoing process
Discuss the Board Packet Service and an agreed schedule. Review the deadline guide or use the deadline estimator.
Assign an owner to each handoff
The packet assembler, document contributor, content approver, accessibility reviewer, and website publisher may be different people. Name those roles before setting the calendar. An unresolved question about a financial table should reach its content owner, while a broken portal link should reach the publishing owner. Both can block completion, but they need different actions.
Create a component list as material arrives. Record the source, filename, owner, type, page count, and expected version. Identify which attachments are scans, which contain forms, and which use complex visual information. That list provides a better basis for a review schedule than the final packet length alone.
| Role | Decision or action |
|---|---|
| Contributors | Provide the best available originals and clarify their content. |
| Packet assembler | Track components, order, references, and the assembled version. |
| Content approver | Confirm substantive information and official wording. |
| Accessibility reviewer | Perform agreed technical and human checks. |
| Publisher | Post the accepted versions and identify live locations. |
Include useful review tasks
A reader should be able to identify the meeting, move between agenda sections, find the related attachment, follow a link, and understand important tables or charts. The review should consider those tasks in the final document. Checking only whether each component opens leaves navigation and assembly issues untested.
Use the PDF checklist for a staff-friendly starting point. For the agreed technical review, record methods and coverage. A tool report, a manual structure review, and a screen-reader task are different kinds of evidence and should be described accurately.
A supplement arrives after the main packet was returned
The board office identifies the new content and decides whether it will be separate or incorporated. The delivery plan records a new version, the additional review scope, and any changed agenda references. After posting, the verification record identifies the files actually available to the public. The earlier packet review does not silently cover the supplement.
Close the loop after the meeting
Minutes and later corrections create another publishing step. Keep them in the same ownership model, with their own sources and versions. A short review of recurring issues can also improve the next packet: ask for editable sources earlier, simplify a difficult table, or update the agenda template.
For recurring delivery, the Board Packet Service can define intake cutoffs, allowances, revision handling, and evidence around your meeting calendar. Turnaround is agreed against the actual workload and required dates. Meeting notice and records decisions remain with the district.