Governance practice · Practical guide
Board Meeting Papers: Version Control and Late Changes
Prevent conflicting agenda packs by controlling versions, approvals, circulation and post-meeting retention.
Create a single controlled pack
Give the meeting pack an identifier, meeting date, owner and version. Establish one authorised location rather than circulating competing attachments. Label each paper with its agenda item, author, decision request, sensitivity classification and revision date. A late change should never make a previously approved paper silently disappear.
Set submission and review gates
Agree deadlines for paper submission, quality review, accessibility checks and final circulation. The secretary can check completeness, but the sponsoring officer remains responsible for accuracy. If an item asks for approval, the paper should state the precise decision sought, implications, options and supporting evidence; do not disguise a decision as an information item.
Handle last-minute corrections explicitly
When a material fact changes, issue a numbered replacement or addendum with the change described. Tell recipients which version is current and whether earlier copies should be disregarded. If members cannot review the revised evidence adequately, the chair should consider deferral under the governing rules. Do not backdate the revised document.
Limit disclosure and preserve access
Restrict confidential papers to authorised recipients, use accessible formats and avoid forwarding private links through unapproved channels. Check that external guests see only the items relevant to them. Record access or circulation where policy requires it; a general email delivery receipt is not proof that a member read a paper.
Fictional worked example
A fictional board receives pack v1 on Monday. On Wednesday the finance lead corrects an arithmetic error in paper 6, changing the recommended amount. The secretary publishes pack v2 with a dated change note and notifies authorised members. The chair confirms whether the revised item can proceed. The minutes cite the version considered, not the superseded proposal.
Archive the decision context
After the meeting, retain the final circulated pack and any material addenda alongside the approved minutes under the organisation’s retention rules. Link the decision record to the version actually considered. Keep a short exception log for late papers and access issues to improve the next cycle.
Scope: General operational guidance, not jurisdiction-specific legal advice. Check the applicable constitution, bylaws, policies and law. Worked examples are fictional; SecretAIry's public demo does not retrieve customer records.