Board Packets: What to Include and How to Assemble Them

What a board packet is

A board packet is the compiled bundle of everything a member needs to participate in the upcoming meeting: the agenda plus the supporting documents behind each item. Its purpose is to move the reading, review, and preparation out of the meeting and into the days before it, so the meeting itself is spent on discussion and decisions.

Think of the packet as the difference between a board that reacts and a board that governs. When members read the financials, reports, and proposed resolutions in advance, they show up with informed questions and can make real decisions. When there is no packet, the meeting becomes a briefing, and decisions get made on the spot with incomplete information.

Standard contents

Packets vary by organization, but most contain a consistent core set of documents. A typical packet includes the following, usually in agenda order so members can read along.

• The meeting agenda, ideally with time estimates.
• Minutes of the prior meeting for approval.
• The treasurer's or financial report — statements, budget-to-actual, and any variances.
• Committee and staff reports.
• Resolutions, policies, or contracts coming up for approval, in final proposed wording.
• Background memos or briefing notes for major decisions.
• Any consent-agenda items with their supporting documents.
• Relevant correspondence and informational attachments.

Assembly and distribution timing

Assembling a packet is a coordination task: gather each contributor's material by a deadline, compile it in agenda order, add a cover page or table of contents, and confirm every referenced document is actually attached. Set an internal cutoff a few days before distribution so late reports do not derail the schedule.

Distribute the packet with enough lead time for members to read it — many boards send it several days before the meeting, and some bylaws or governing rules set a required notice window. Sending the packet late is one of the most common ways boards undermine their own preparation; if members cannot realistically read it before the meeting, the packet is not doing its job.

Version control

Nothing confuses a board faster than two members looking at two different versions of the same document. Establish clear version control: label each document with a date or version, distribute one authoritative packet, and if something must change after distribution, send a clearly marked update rather than a silent replacement.

Avoid circulating loose attachments across scattered email threads, where it becomes impossible to tell which financial statement or draft resolution is current. A single, dated, authoritative packet — ideally in one place everyone accesses — prevents the "which version are we voting on?" problem that can invalidate or muddy a decision.

Security of confidential materials

Packets often contain sensitive information: personnel matters, legal advice, contracts, financial detail, or items headed for executive session. Treat these with care. Restrict distribution to the board and required staff, mark confidential documents clearly, and prefer secure delivery over forwarding attachments around.

Be deliberate about executive-session materials. Confidential items intended for a closed session should be handled so they do not end up in the general record or in wider circulation. After the meeting, follow your retention and access rules: keep the official packet as part of the record while limiting access to confidential portions.

Making packets easy to build and find later

The last mile is reuse. A packet is not only pre-meeting reading; it is also part of the organization's record of what the board considered when it decided. Keep the packets in one place, organized and searchable, so you can answer later questions like "what did the board have in front of it when it approved that contract?"

Building packets by hand every month is tedious and error-prone — chasing reports, re-ordering documents, checking attachments, and managing versions. This is exactly the kind of recurring work that governance software is designed to take off your plate, pulling the agenda, prior minutes, reports, and resolutions into a consistent packet you can distribute and archive in a few clicks.