The wrong PDF in the room starts with the chair’s pre-read

The chair sends the pre-read the week before the meeting. By the time directors gather, one has annotated an attachment from an earlier thread, the finance office has circulated a corrected appendix, and the secretariat is holding three files with the same name. The pack on the table is not the pack anyone marked up — and the minutes will be drafted against a record nobody can identify.

This is not a diligence failure. It is a version-control failure, and it starts earlier than the meeting itself. It starts the moment the chair’s pre-read leaves the board office without a checked version, owner, and distribution list.

One current pack, one named owner

The fix is an operating standard, not a new tool. At any moment there is one current board pack — the file the board works from — and a named owner, usually the board office, who can say which file that is. Nothing reaches directors outside that record. Late material does not travel as a reply-all attachment; it goes to the owner and enters as a new version of the pack, so the record stays whole.

This matters because minutes are drafted against the record. If the record has forked, the minutes inherit the fork — and the correction work lands on the secretary after the meeting, when memories differ about which version was actually discussed.

The checkpoint before the pre-read goes out

Before the chair’s pre-read is released, the board office runs a short version-control checkpoint. It takes minutes, and it catches the fork while it is still cheap to fix.

1. Approved file — the pack being sent is the version that was signed off, not a working draft carrying the same filename.
2. Pack status — open items are closed or visibly marked, so directors are not annotating placeholders.
3. Distribution list — every recipient, including the chair, receives the same file at the same time through the same channel.
4. Release time — anything corrected after release goes back through the owner as a new version, never as a side attachment.

Meeting-day control in the board office

On the day, the board office needs a fast answer to one question: which pack is current. That means a known location for the current file, a visible version marker on the pack itself, and a standing rule that no annotation enters the minutes until it has been reconciled against that version.

When a director arrives with a different file — and someone will — the office identifies the current pack, collects the stray annotations, and folds any real corrections into the record before minutes are drafted. If a correction is material, the pack is re-issued as a new version with the change logged, and the minutes reference the reconciled record. The audit trail follows the pack, not the inbox.

The pre-read is the first version decision

The chair’s pre-read is the first version-control decision of every meeting cycle. Treat it that way, and the wrong PDF never gets into the room. Treat it as a courtesy email, and the board office spends the meeting reconciling files instead of recording decisions.