Handling a Same-Day Board Paper Revision Request

Freeze the version that entered the room

Identify the exact version that was distributed and the time it was sent. Save a copy in the board file before anyone edits the working document. The frozen copy is the reference for every later change. Without it, the team cannot tell whether a correction reached the board or only the internal folder.

Check whether the paper was sent as a PDF, a link, or a printed pack. Each format has a different update path. A printed pack may need a replacement page at the meeting, while a link may update silently for everyone. Record the distribution method and the person who controls it.

Tell the paper owner that a same-day revision is being considered. The owner may be the CFO, the general counsel, or a committee chair. The assistant should not edit a board paper without that owner's direction. The freeze protects the owner as much as the board.

Label the frozen copy with the distribution time and the channel. Do not overwrite it when the revised version is created. A separate frozen file is the only reliable way to answer what the board actually received. Keep it with the meeting record, not in a personal folder.

Separate a factual correction from a rewrite

Ask what specifically is wrong. A wrong number, a stale date, or a misnamed entity is a factual correction. A change in recommendation, a new risk, or a different ask is a substantive revision. The two require different approvals and different communication.

Write the change in one sentence and attach the source that supports it. If the source is not available, the correction is not ready. A verbal instruction from a board member may be the reason for the change, but the paper owner still needs to verify the fact. The note should show what changed and why.

Do not use a same-day revision to reopen a debate that was settled before distribution. If the change is substantive, the paper owner and the board liaison should decide whether the item can be handled at the meeting or must wait. The assistant can prepare the options, but the decision belongs to the authorized owner. Record the owner's answer before any replacement page is produced.

Ask the requester to identify the page and the sentence, not just the topic. A vague request can expand into a rewrite during the conversation. If the requester cannot point to the text, the paper owner should review the request before any edit. Precision at intake saves time later.

Route the change through the paper owner

Send the proposed change to the paper owner with the frozen version, the source, and the requested deadline. Ask for an explicit approval rather than a general acknowledgement. Record the approval time and the approver. A quick reply that says looks fine is weaker than a clear instruction to issue the revision.

If the owner is unavailable, follow the board's escalation rule. Do not approve a substantive change on the owner's behalf. A factual correction may have a delegated path, but that path should be written before the meeting day. The assistant should know the difference and act within it.

Keep the board liaison informed at the same time as the owner. The liaison needs to know whether the board will receive a replacement, a verbal correction, or no change. A late surprise at the meeting is worse than an early, honest update. The message should state the status, not promise a final version that is not approved.

Give the owner a deadline that leaves time for distribution before the meeting. A request that arrives after the meeting starts is a verbal correction, not a paper revision. Record the time the owner received the request and the time the answer came back. The gap is useful for the next board cycle.

Reissue with a change log

Create a new version with a clear label, the date, and a short change log. The log should state the page, the old text, the new text, and the reason. Do not rely on tracked changes alone, because the board may receive a clean PDF. A reader should be able to see what changed without comparing two documents side by side.

Replace the distributed file through the approved channel and confirm that the old version is no longer the active link. If a printed pack was used, prepare the replacement pages and a covering note. Check that the page numbers still align. A revision that leaves the old page in the room creates confusion.

Send the change log to the board liaison and the paper owner. Keep the frozen version and the revised version in the board file. If the meeting already started, record the time the correction was delivered and who received it. The record should show the sequence, not just the final document.

Use a clear file name that includes the version and the date. Do not send a file called final-final or revised-new. The recipient should be able to tell which version is current from the name alone. A consistent naming rule prevents the old file from being opened by mistake.

Tell the board liaison what changed

Write a short message that states the change, the reason, and the action the board needs to take. Avoid a long explanation that repeats the paper. The liaison should be able to brief the chair in a minute. If the change affects a recommendation, say so plainly.

Ask the liaison whether the board needs a verbal update at the table. A factual correction may be handled by a replacement page, while a substantive change may need the paper owner to speak. The assistant should not decide the meeting protocol alone. Record the liaison's answer and the time.

Close the revision with a note in the board file: what changed, who approved it, when it was distributed, and what remains open. Review the event after the meeting. If the same paper needed a late change twice, the preparation process may need a earlier freeze. The goal is fewer same-day revisions, not a faster scramble.

Ask the liaison whether the chair needs a separate note or a verbal briefing. A short note to the full board may be unnecessary for a minor correction. The liaison knows the meeting dynamics. Record the answer so the paper owner knows what was communicated.

Related resources

• Building a Board Committee Calendar That Prevents Packet Collisions
• Auditing board packet version control before distribution
• Setting Up a Confidential Document Room for a Sensitive Project

Frequently asked questions