Run a Board Pack Version Register for Executive Meetings

Run a Board Pack Version Register for Executive Meetings

by ExecutiveAssistantAgency Editorial Team · 5 min read

A practical version register for board packs, covering file naming, freeze points, controlled distribution, late corrections, and audit-ready archive handoff.

In this article
  1. A board pack changes more often than the meeting
  2. Name files for reading, not for pride
  3. Set a freeze point and defend it
  4. Distribute through one controlled path
  5. Handle late corrections with a short paper trail
  6. Keep the register readable at a glance
  7. Brief the chair before the pack lands
  8. Close the cycle with a clean archive

A board pack changes more often than the meeting

The first draft of a board pack leaves the assistant's desk weeks before the meeting. Finance adds a revised forecast, legal rewrites a resolution, and the CEO edits the opening letter after a late flight. Each change creates a new file with a slightly different name. Without a register, the assistant has to remember which file went to which director and which version the chair will open on the morning of the meeting.

A version register solves that problem with a short, boring record. It lists each released file, the time it was sent, the recipients, and the reason for the release. It also names the one file that is currently authoritative. The register does not replace the document management system. It gives the assistant a single place to answer the question that arrives at the worst possible moment: which copy is final.

Name files for reading, not for pride

Use a naming pattern that a director can read without a decoder. Start with the meeting name, then the section, then the version marker. A file called strategy-review-v3 is more useful than a file called final-final-approved. Keep the version marker short and numeric, and avoid words such as final or latest because they stop being true within a day.

Reserve a separate marker for drafts that have not been reviewed. A simple draft prefix prevents an early file from being mistaken for a released pack. When a section owner sends a replacement, do not overwrite the earlier file. Save it under the next number and note the change in the register. The NARA guidance on electronic records explains why keeping the earlier version matters when someone later questions what the board saw.

Set a freeze point and defend it

Pick a freeze time that gives the chair and the board enough time to read. Two business days before the meeting is common for a full pack, with a shorter window for late-breaking items. Publish the freeze time in the cover note and in the calendar invitation. Then treat every change after that point as an exception with a named approver.

The freeze is not a wall. It is a decision point that forces a conversation about materiality. If a number changes in a way that could affect a vote, the chair needs to know before the meeting starts. If a typo changes nothing, the assistant can correct it in the meeting copy and note the correction in the register. The point is to make the choice visible rather than silent.

Distribute through one controlled path

Send the pack through a single distribution method, preferably a permissions-controlled folder or board portal. Avoid mixing email attachments, shared drives, and printed binders unless the register records each channel. Directors who receive a file by email may forward it, and the assistant may never learn that a second copy exists. A controlled path reduces the number of places where an outdated file can survive.

Generate a recipient list from the board roster rather than from memory. Check the list against the chair's office before each release. If a director's assistant receives the pack on their behalf, record that person as a delegate in the register. The CISA physical security guidance is written for facilities, but its principle of controlled access applies equally to a sensitive board file.

Handle late corrections with a short paper trail

When a section owner sends a correction after the freeze, ask for three things: the changed page, the reason for the change, and the approver's name. Save the corrected file as a new version and send a short notice to the recipients who received the earlier copy. The notice should identify the section and the version, not repeat the sensitive content in the subject line. This keeps the correction traceable without turning email into a second copy of the pack.

If the correction arrives during the meeting, give the chair a printed change sheet and record the time it was distributed. Do not silently swap a file in the portal while directors are reading. A visible change sheet protects the assistant and gives the board a clean record of what was discussed. After the meeting, attach the change sheet to the minutes file.

Keep the register readable at a glance

Limit the register to six columns: meeting, section, version, released to, released at, and note. Use plain text rather than a color-coded spreadsheet that only its creator understands. Add one row per release, even when the release covers several sections. If a section did not change, say so in the note instead of creating a new row for every file.

Review the register at the end of each board cycle. Mark the authoritative file and close the older rows. A short closing note such as "superseded by v4" is enough. The NIST control catalog treats configuration control as a lifecycle activity, and a board pack deserves the same discipline.

Brief the chair before the pack lands

The chair does not need every file, but the chair does need to know what changed. Prepare a one-page cover note that names the sections with material updates and the sections that are unchanged. Send it to the chair's assistant before the full pack goes out. This gives the chair's office a chance to ask for a briefing or flag a conflict before the directors begin reading.

Keep the cover note factual and short. Avoid adjectives that imply a recommendation the chair has not made. If a section owner wants to frame a change, let that language live in the section itself. The cover note should help the chair navigate, not campaign for an outcome.

Close the cycle with a clean archive

After the meeting, collect the approved minutes, the final pack, the change sheet, and the register in one folder. Name the folder for the meeting and the year, not for the assistant who prepared it. Record the location in the team's index so a successor can find it without asking around. Retain the folder according to the organization's records schedule.

Do not delete the working drafts immediately. Keep them for the period the legal or compliance team requires, then dispose of them on schedule. If a director asks for a copy months later, the archive should answer the request in minutes. For teams that need steady coverage across board cycles, contact us to discuss assistant support. The meeting room release rule is a useful companion practice for keeping the meeting itself under control.