Set a Board Paper Version Control Log for Executive Meetings
by ExecutiveAssistantAgency Editorial Team · 4 min read
A practical version control log that keeps board papers accurate from first draft to the locked pack and the archived minutes.
In this article
A board pack that drifts is a governance problem
The board pack is assembled by many hands: the chief executive, the finance lead, the general counsel, and outside advisers. Each contributor sends a revised file, and the assistant becomes the only person who knows which version is current. When a director opens a stale page during the meeting, the error is visible to the whole board. Version control is how the assistant protects the meeting from that failure.
A version log does not need complicated software. A single table that records the file name, the owner, the date received, and the approval status will cover most board packs. The log gives every contributor a place to see what has been accepted and what is still outstanding. It also gives the assistant a defensible record when a director asks why a page changed.
Open the log before the first draft arrives
Create the log at the same time you open the board folder, not after the first draft appears. List every expected paper, including the minutes, the financial summary, the risk register, and the resolutions. Assign an owner to each item and a due date that sits at least two business days before the pack is released. A blank row is a useful signal that a paper is missing.
Name files with a consistent convention that shows the paper number, the topic, and the version. Avoid names that rely on words like final or latest, because those words lose meaning after the second revision. Put the date and time in the file name so two versions cannot be confused in a download folder. The convention should be simple enough that a new contributor can follow it without a briefing.
Log every revision at the moment it lands
When a revised paper arrives, record it in the log before you open it. Add the sender, the time, and a short note about what changed. Replace the prior version in the working folder but keep the prior version in an archive folder. That archive is what lets you answer a question about what the board saw last quarter.
Use a status column with a small set of values: requested, received, under review, approved, and locked. Anything beyond five values will be applied inconsistently. Change the status only when the owner or the reviewer has confirmed the change in writing. If a paper is approved verbally, send a one-line note that repeats the approval and ask for a reply.
Reconcile the pack against the agenda
Walk the agenda line by line and confirm that each item has a matching paper. A paper without an agenda item may be an orphan that the board does not need. An agenda item without a paper is a gap that will be filled at the last minute unless someone raises it now. Send the reconciliation to the meeting chair and ask for a decision on every mismatch.
Check page numbers and cross-references after each replacement. A revised financial summary can change the page count, which breaks every reference in the chair's notes. Update the table of contents and the page headers in the same pass. A quick read on a tablet catches layout shifts that a desktop view hides.
Lock the pack on a stated schedule
Agree on a lock time with the chair and publish it to every contributor. After the lock, accept only changes that the chair approves in writing. Record the exception in the log with the reason and the approver. The NIST risk management framework treats change control as a repeatable process, and a board pack deserves the same discipline at a smaller scale.
Release the locked pack with a cover note that states the version, the lock time, and the contact for urgent corrections. Send the same file to every director rather than letting each one download a different link. Keep the distribution list with the log so you know who received which version. The confidential document release note offers a useful model for that handoff.
Use the log in the meeting room
Keep a printed copy of the log with the chair's binder during the meeting. Mark the paper that is being discussed and note any correction the chair requests. A printed copy works when the network is slow and gives the assistant a place to write without opening a laptop. Update the digital log after the meeting rather than trying to type during the discussion.
When a director asks whether a page changed, read the version history rather than guessing. Show the prior version only if the chair agrees that it is appropriate. Record the question and the answer in the meeting notes so the context is not lost. A short factual answer is better than a long explanation of the production process.
Close the loop after the meeting
After the meeting, record which papers were discussed and which were deferred. Note any correction that a director requested and whether it was made. Archive the locked pack with the signed minutes so the record is complete. The board meeting preparation routine can share the same folder structure.
A version log is only useful if it survives the next assistant. Store it where the team stores other board records, not on a personal drive. Add a short instruction at the top so a successor can pick it up without a handover call. For teams that need consistent board support, contact us to discuss assistant coverage.
Related Articles
blog
Build a Decision Memo Template for the Executive Approval Queue
A one-page decision memo template that turns a crowded approval queue into clear choices, stated risks, and a recorded outcome the executive can act on quickly.
blog
Build an Executive Reading Folder for Long-Form Briefings
A reading folder structure that gives the executive one place for long-form briefings, a stable naming rule, and a short index that makes the queue easy to enter.
blog
Prepare a Same-Day Visitor Brief for the Executive Suite
A same-day visitor brief that gives the executive the name, purpose, sensitivities, and expected outcome of each visit without exposing unnecessary personal detail.