Board Packet Distribution Evidence

Abstract

A review protocol for board-support teams that want to test packet control without treating a sent email as proof of distribution.

Methodology

Define the population as every board or committee meeting in a fixed governance cycle, including special meetings and written consents. Record the cycle, the entities, the packet source, and the count of meetings. List the required evidence for each meeting: packet version, freeze time, page index, distribution list, access level, send or portal time, acknowledgement, late addendum, correction, and the version discussed in the meeting. Name the authoritative source for each field. The portal log supports distribution; the board secretary's record supports the version discussed; a director's email does not prove that the packet was received. Sample across meeting types and sensitivity levels. Include an executive session packet, a meeting with a late correction, and a meeting where a director changed after the distribution list was built. Classify defects as missing version label, unlogged distribution, wrong recipient, missing acknowledgement, unresolved correction, or a mismatch between the packet and the minutes. Assign an owner and a correction date. Report the population, sample, defect categories, and limits. Retain the packet index and the distribution log with restricted access. The protocol does not evaluate the quality of the board's decisions.

Freeze and version

The freeze should produce one identifiable packet with a page index and a distribution time. A later addition belongs in an addendum with its own label, even when the board secretary expects everyone to read it before the meeting.

The review should compare the cover label, the file name, and the portal entry. If those three disagree, a director may open a different version than the one the chair references.

Distribution and access

The distribution list should be built from the current roster and the role-based access rule. Record who received the full packet, who received a section, and who received only a notice that the packet was available.

Acknowledgement is a separate event from delivery. A portal download, a read receipt, or a confirmation from the director's assistant can support acknowledgement; a sent email alone does not.

Correction and meeting record

A correction after distribution should preserve the original, label the changed pages, and record the approver. The meeting record should show which version was discussed and whether a tabled item was carried to the next meeting.

After the meeting, reconcile the packet index with the minutes and the action register. The reconciliation is the evidence that the board saw the material the record describes.

Privacy and limitations

Restrict access to executive session and personnel materials. Retain the distribution log and the certificates according to the governance schedule.

The review cannot establish whether a director read the packet or whether the board's decision was sound. It can only show whether the distribution and correction trail is reconstructable.

Key findings

  • A version label without a freeze time is not a control.
  • Distribution to an assistant is not acknowledgement by the director.
  • Corrections need their own version, approver, and reissue date.
  • Executive session materials require a separate access list.
  • The packet discussed in the meeting should be identifiable from the minutes.
  • The review tests evidence, not the substance of governance.

Sources

  1. Standards for Internal Control in the Federal Government, U.S. Government Accountability Office
  2. Privacy Framework, National Institute of Standards and Technology
  3. Records Management Policy and Guidance, National Archives and Records Administration
  4. Cybersecurity Framework, National Institute of Standards and Technology

Return to the Research Content library