A Board Pre-Read Distribution Check Before the Meeting

A board pre-read goes out on Friday and a director opens it on Monday to find last month’s numbers. The meeting starts with a correction, the finance lead loses ten minutes, and the board’s confidence in the pack drops. The failure was not the analysis. It was the distribution. A board pre-read distribution check is a short set of confirmations before the pack leaves the building. It verifies the version, the audience, the access, and the acknowledgement. The check takes less time than the correction and protects the work behind the document.

Freeze the version before distributing

Confirm that the pack is the final version and that every section carries the same date. Ask the authors to stop editing before the distribution begins. A file that changes during distribution creates two versions in the board’s hands. Record the version identifier and the time it was frozen. If a late change is necessary, issue a re-release with a clear label rather than editing the original. Directors should never have to guess which file is current.

Check the audience against the access list

Compare the distribution list with the board roster and the approved attendees. Include the directors, the executive participants, and any adviser the board has approved. Exclude anyone whose access has ended or whose attendance is not confirmed. Send the pack through the approved channel rather than a personal email. A personal email can leave the organization’s controls and cannot be recalled. The approved channel also gives you a record of who received the file.

Confirm the format and the links

Open the pack as the directors will open it. Check that the pages render, the tables fit, the links resolve, and the confidential markings are present. A file that works on the author’s laptop may fail on a tablet. Test any link that points to a separate document or a data room. A broken link at 9 p.m. before a board meeting becomes an urgent request. Fix the link or attach the file before distribution.

Send with a short access note

Include a short note that names the meeting, the pack version, the confidential status, and the deadline for questions. State the channel where questions should go. A note that says only “please find attached” leaves the director guessing. Ask for a simple acknowledgement of receipt. The acknowledgement is not a bureaucratic step; it tells you who has the pack and who needs a follow-up. Record the acknowledgements against the distribution list.

Track the acknowledgements

Check the acknowledgements before the meeting preparation window closes. Contact anyone who has not confirmed receipt through the approved route. Do not assume that silence means the pack was received. Record the date and the method of the follow-up. If a director cannot access the pack, offer the approved alternative rather than sending the file to a personal address. The exception should be noted in the distribution record.

Handle a late change honestly

If the pack changes after distribution, issue a replacement with a new version label and a short summary of what changed. Do not quietly replace the file. A director who read the earlier version needs to know which numbers moved. For a material change, notify the board chair before the meeting. The chair can decide whether the meeting needs a short adjustment. The assistant coordinates the communication and records the decision.

Review the distribution after the meeting

After the meeting, note any version confusion, broken link, or access problem. Ask the chair whether the pack arrived in a usable form. Record the issue and the fix for the next cycle. Review the distribution list at the same time. A director who left the board, a new adviser, or a changed role should be reflected before the next pack. The list is a living record, not a one-time export.

Keep the record proportionate

Record the version, the distribution list, the send time, the acknowledgements, and any exception. Do not copy the pack itself into a broad tracker. The board’s documents belong in the governed system that already protects them. Set a retention period with the organization’s records policy. A distribution log kept indefinitely creates risk without adding insight. Keep enough to explain what was sent and when.

Key takeaways

• Freeze the pack version before the first distribution and label any replacement.
• Compare the distribution list with the current board roster and approved attendees.
• Test the format, the links, and the confidential markings as a director would see them.
• Track acknowledgements and record any exception with the route used.

A board pre-read check is a small control around a high-visibility document. It protects the meeting’s first ten minutes and the credibility of the pack behind them. The check is quick when the distribution list and the version record are already in place. Keep both beside the distribution channel so the next pack starts from a known list. A check that begins from scratch every cycle will be skipped under deadline pressure. For related workflows, see the weekly risk scan and the executive support services overview.