Freeze the packet at a named cutoff
The board packet is not finished when the last slide arrives. It is finished when the packet owner freezes a version, checks the page order, and confirms that every appendix referenced in the agenda is present. Set the cutoff in the board calendar and tell contributors what happens to anything received after it: it goes into a late-addendum queue with an owner and an approval path.
Name the version on the cover, in the file name, and in the board portal entry. A label such as “v3 final” is not enough when two people each created a file called final. Use a date-time stamp and a short change note so the board secretary can tell which packet was distributed and which one was replaced.
Separate working, review, and board-ready copies
The finance team may need a working copy with commentary, the CEO may need a review copy with unresolved questions, and the board needs a clean copy with decisions and source notes. Keep those artifacts separate. Moving a review copy into the distribution folder because it is the newest file is how confidential commentary reaches the wrong audience.
Use a permission model that follows the copy's purpose. Working files belong in the staff drive, review files in a restricted folder, and board-ready files in the portal with download logging. When a reviewer requests a change, return a marked copy to the owner rather than editing the board-ready file in place. The board-ready version should only change through the freeze and reissue process.
Control distribution by role and board member
Build the distribution list from the board roster and the staff roles that need access, not from last year's email chain. Check for departed directors, changed addresses, assistants who receive on behalf of a director, and external advisers who should receive only a specific section. Each recipient should have a role and an access level, not just an email address.
Some packets contain an executive session appendix, a legal memo, or a compensation schedule that should not go to the full distribution list. Split those materials into separate, labeled files and give them a narrower audience. Record who received the full packet, who received a section, and when access was granted.
Track acknowledgements and late changes
A sent packet is not a received packet. The portal should show a download or acknowledgement event, and the assistant should follow up with anyone who has not accessed the material by the stated deadline. For a director traveling internationally, confirm the time zone and the device before the meeting, not during the opening minutes.
Late changes need a change note: what changed, why, who approved it, and which pages were affected. Reissue the whole packet only when the board secretary decides that a partial addendum would create confusion. A page-level correction that is not logged will surface as a contradiction in the meeting record later.
Handle corrections without erasing history
If an error is found after distribution, preserve the original file and issue a corrected version with a visible change note. Do not overwrite the file in the portal and hope nobody notices. Directors who annotated the earlier copy need to know which pages changed and whether their questions are still relevant.
For a sensitive correction, the board secretary or general counsel decides how to communicate it. The assistant prepares the corrected page, the comparison, and the recipient list. The correction message should say what changed and what action, if any, the director should take. It should not speculate about the cause or assign blame in writing.
Reconcile the record after the meeting
After the meeting, compare the packet index with the minutes, the decisions, and the requested follow-up. Note which packet version was discussed, which materials were tabled, and which questions were deferred. That reconciliation makes the next packet easier to assemble and gives the board secretary a clean record for the minute book.
Store the board-ready packet, the correction notes, and the distribution log according to the governance retention schedule. Do not keep personal annotations or draft commentary in the permanent record. At the next cycle, review the late additions and the sections that generated the most questions, then adjust the contributor deadlines rather than the board's reading time.