The board packet leaves the assistant's hands long before the meeting starts, and the chair can still change the agenda the night before. A handoff that depends on one person remembering the latest version will fail under that pressure. The fix is a short sequence that makes ownership, version, and approval visible at every step. It should work even when the chair's office sends a change after the printer has run.
Documentation
Build a board packet handoff that survives the chair's last-minute change
A practical handoff sequence for board packets that keeps ownership, version control, and approval visible when the chair changes the agenda late.
Table of contents
Why a late chair change exposes the handoff
A late agenda change is not only a content problem. It moves the packet from a finished product into a live production queue with a new deadline, new approvers, and a higher chance of distribution to the wrong list. Most teams plan the original packet carefully and treat the revision as an exception. The exception is where the handoff either holds or breaks.
The failure is usually invisible until the meeting. A section is replaced in the shared drive, but the printed binder keeps the old page. A director receives the revised note without the corrected appendix. The chair then has to reconcile two documents in front of the full board. A handoff design should prevent that scene, not explain it afterward.
Name one packet owner and one deputy
Every packet needs one named owner who can say which version is current. The owner does not have to write every section, but they must control the assembly order, the approval list, and the release time. A deputy should hold the same information so a sick day does not stop the revision. Put both names on the cover sheet where the chair can see them.
The owner also needs authority to reject a late change that has no approver. That sounds rigid during a board week, but it gives the chair's office a clear next step instead of an argument. The deputy can cover the production work while the owner resolves the approval question. Two roles, one decision path, and no shared assumption that someone else is watching.
Keep a change log with time, source, and approver
A change log is the difference between a revision and a rumor. Record the time the request arrived, the person who sent it, the section affected, and the approver who accepted it. Add a short reason so the next reader knows whether the change was legal, editorial, or scheduling related. The log can live at the front of the packet or in a linked sheet, but it must be visible to the owner and deputy.
The log should also show what was removed. A replacement page often hides the fact that an old appendix is still in the room. Mark superseded material as retired and name the person who confirmed the removal. At the close of the packet, the log becomes the distribution record and the first place to look when a director asks which version they received. For a broader evidence review, see our research on where board packet revisions consume support hours.
Separate content approval from production changes
The person who approves the wording is not always the person who rebuilds the PDF. Keep those two decisions separate so a production fix does not quietly change the substance. The content approver signs off on the revised section, and the production owner confirms pagination, bookmarks, and distribution. If the same person holds both roles, add a second reader for the final check.
This separation matters most when the chair's office sends a verbal change. The owner writes the change down, reads it back, and asks for an explicit approval on the written version. Only then does production touch the file. That extra step feels slow for five minutes and prevents a much slower correction in the meeting.
Rehearse the late-change window
Run one short rehearsal before each board cycle. Give the team a fictional change at the same hour the chair's office usually calls, then time how long it takes to approve, rebuild, and distribute. Note where the team waits, because waiting is the real cost in a late revision. The rehearsal should include the deputy and the distribution contact, not only the packet owner.
The rehearsal also tests the tools. A shared drive that locks during export, a print queue with no backup, or a distribution list that requires one person's laptop will all surface in the exercise. Fix the weakest link before the live packet arrives. A written handoff is only useful when the people named in it can actually perform their part under time pressure.
Close the packet with a distribution record
The handoff is not complete when the file is sent. Record who received which version, when it was sent, and whether the recipient confirmed access. Keep the confirmation separate from the read receipt, because a receipt proves delivery and not comprehension. If a director joins late, the record shows exactly what they missed and which correction they need.
At the next cycle, review one late change and one ordinary packet against the same checklist. Ask whether the owner, deputy, log, and approver were obvious without a conversation. Update the cover sheet or the log if the answer is no. The goal is not a perfect packet but a handoff that still works when the chair changes the plan. Set the next review date before the team leaves the room, and background is available from the GAO corporate governance resources.
Key takeaways
- Name a packet owner and a deputy on the cover sheet, with authority to reject an unapproved late change.
- Log the time, source, section, approver, and reason for every revision, and mark superseded material as retired.
- Keep content approval separate from PDF production so a formatting fix cannot alter the substance.
- Rehearse one late change before each board cycle and record who received each final version.
Frequently asked questions
Who should own a board packet revision?
What belongs in a board packet change log?
How do you handle a verbal change from the chair's office?
Keep reading
Related executive support guides.
Set a document naming standard the whole executive office can follow
A four-field document naming standard that improves search, version control, and handoffs without adding friction to daily work.
Write the board packet intake note that survives a later review
An executive support operations control for executives, chiefs of staff, and executive assistants, focused on board packet with a source, owner, exception path, and close.
Write the inbox intake note that survives a later review
An executive support operations control for executives, chiefs of staff, and executive assistants, focused on inbox with a source, owner, exception path, and close.