Guide
The board packet
Practitioner-written governance guidance
A board packet is the complete set of documents a board receives before a meeting: the agenda, the minutes awaiting approval, the financial statements, the chief executive's report, committee reports, and anything requiring a vote. It is distributed five to seven days ahead so directors can read it before they arrive. A good packet is 15 to 40 pages, leads with what needs a decision, and separates what the board must act on from what it only needs to know.
Also called a board pack, board book, or board materials. "Board packet" is the most common term in US nonprofits; "board pack" is standard in the UK and Australia; "board book" tends to appear in corporate and enterprise contexts.
Last reviewed 12 September 2026.
What goes in a board packet
In this order. The order is not cosmetic: it is the difference between a board that decides and a board that receives updates.
1. The agenda, annotated. Not a list of topics. Each item marked with the time allotted, who is leading it, and one of three labels: Decision, Discussion, or Information. That labelling alone changes meeting behavior more than any other single thing on this list, because a director reading a packet knows which four pages they must actually understand.
2. The consent agenda. Everything routine, bundled and approved in a single motion without discussion: previous minutes, routine committee reports, standard staff reports, gift acceptances within policy. Any director can pull an item out for discussion. This is the highest-leverage structural change available to most nonprofit boards, because it reclaims the first thirty minutes of every meeting.
3. Minutes awaiting approval. The draft minutes from the previous meeting. Sent in advance, approved on the consent agenda, never read aloud.
4. Financial statements. Statement of activities and statement of financial position, actual against budget, with a variance column and a narrative. The narrative is the part that matters. A board cannot read a variance column cold; a treasurer or CFO explaining the three variances that matter in four sentences is worth more than twenty pages of detail. Include cash position and months of operating reserve.
5. The chief executive's report. Two to four pages. What changed since last meeting, what is going well, what is not, what the board needs to know, and what the chief executive needs from the board. That last section is the one most often missing and most often needed.
6. Committee reports. Short, and only from committees that met. A committee with nothing to report should say so in one line rather than filling a page.
7. Decision items, each with a cover memo. One page per decision: the question, the background, the options considered, the recommendation, the financial impact, and the proposed motion language written out. Writing the motion in advance is a small discipline that saves real time and produces much better minutes.
8. Dashboard or scorecard. One page of organizational health. Program outcomes, membership or client retention, campaign progress, board participation. This is the page that lets a board ask whether the mission is working rather than only whether the budget is on track.
9. Appendix. Everything supporting but not required reading. Full committee minutes, detailed program data, background documents. Clearly labelled as appendix so nobody feels obliged.
A worked example: the 24-page packet
A real structure for a 15-person board of a $3M nonprofit meeting six times a year.
| Pages | Section | Label |
|---|---|---|
| 1 | Annotated agenda with times and labels | — |
| 2 | Consent agenda cover sheet | Decision, one motion |
| 3–5 | Draft minutes, previous meeting | On consent |
| 6–7 | Routine committee reports | On consent |
| 8–11 | Financials: activities, position, budget variance, cash and reserves | Information, with narrative |
| 12 | Treasurer's narrative, four paragraphs | Information |
| 13–15 | Chief executive's report, including "what I need from the board" | Discussion |
| 16 | Decision memo 1: approve revised investment policy | Decision, motion drafted |
| 17 | Decision memo 2: approve new committee charter | Decision, motion drafted |
| 18 | Governance committee: proposed slate of officers | Decision, motion drafted |
| 19 | Dashboard: program outcomes, retention, campaign, board participation | Discussion |
| 20 | Strategic plan progress, one page, traffic-light | Discussion |
| 21 | Risk register, top five, with owner and status | Information |
| 22–24 | Appendix | Reference only |
Three decisions, clearly flagged, each with a memo and drafted motion. Everything routine handled in one vote. That is a two-hour meeting that accomplishes something, rather than a two-hour meeting of reports.
The timeline
Working backward from a meeting on day zero.
| When | What |
|---|---|
| Day −21 | Agenda drafted by chief executive and board chair together |
| Day −14 | Content requests sent to committee chairs and staff, with a deadline and a template |
| Day −10 | Financials closed and drafted |
| Day −8 | All content due. This deadline is the one that always slips, and holding it is the entire job. |
| Day −7 | Packet assembled, reviewed by the chair, distributed |
| Day −7 to −1 | Directors read. RSVPs confirmed. Quorum verified before the meeting, not at it. |
| Day 0 | Meeting |
| Day +2 | Draft minutes circulated while memory is fresh |
| Day +7 | Action items assigned with owners and dates, and visible to the board |
Five to seven days is the distribution standard. Fewer than five and directors will not read it. More than ten and the financials are stale. Note that some bylaws set a hard minimum notice period for meetings, and some are surprisingly short: one large YMCA's bylaws require only two business days' notice. Check yours, then ignore the minimum and send seven days out anyway.
The two failure modes
Almost every unread packet fails in one of two ways.
Failure one: the packet is a pile. No labels, no order, no decisions flagged, sixty pages of attachments and a one-line email that says "materials for Thursday." The director opens it, cannot tell what is required of them, closes it, and comes to the meeting cold. Then the meeting becomes the reading session, and staff spend two hours narrating documents out loud.
The fix is entirely editorial: label every item Decision, Discussion or Information, put the decisions first, put everything routine on a consent agenda, and move the bulk to an appendix.
Failure two: the packet is late. Content comes in on the day, someone assembles it at 11pm, it goes out 36 hours before the meeting, two directors never find the email, and one is reading it in the parking lot. This one is not editorial, it is structural, and it is where the evening disappears.
Hand assembly of a packet is commonly three to five hours: chasing reports, converting files, ordering them, generating a table of contents, renaming, uploading, emailing, and re-sending to whoever cannot find it. Six meetings a year plus committees puts that comfortably over 100 hours annually for one person.
The fix is a real deadline plus a system that assembles rather than a person who assembles. Which brings us to the next section.
How to stop building it by hand
Four things, in order of how much time they give back.
1. Templates for contributors, not just for you. Give every committee chair and staff contributor a one-page template with the headings you need. Most late content is late because the contributor did not know what shape it should be.
2. A standing structure that never changes. Same sections, same order, every meeting. Directors learn where things live, and assembly becomes filling slots rather than designing a document.
3. A hard content deadline with a named owner. Day −8, one person chases, and the packet goes out on day −7 with a placeholder if something is missing. A placeholder that says "finance committee report to follow" is better than a packet that is three days late.
4. A system that assembles the packet. This is the step that removes the evening. A board platform takes the uploaded pieces, orders them, versions them, builds the table of contents, publishes one link that is always current, notifies the board, tracks who has opened it, and collects RSVPs against the same meeting. Nobody emails a 40MB PDF, nobody is reading last month's budget by accident, and nobody has to re-send anything.
Two details worth checking before you pick one, because they are where these tools quietly fail:
- Can your board read a real packet on a phone? Load an actual 80-page packet with financial exhibits onto a phone during the trial. Users of several major platforms report large binders becoming slow to scroll, and at least one vendor's mobile app reportedly omits the board book entirely.
- Is the archive searchable? A packet system whose historical minutes are non-text-searchable PDFs has stored your institutional memory without making it retrievable, which is most of the problem you were trying to solve. Test a full-text search for a phrase from three years ago.
Frequently asked questions
How long should a board packet be? 15 to 40 pages of required reading, with everything else in a clearly labelled appendix. If required reading is over 50 pages, the problem is usually that discussion material and reference material have not been separated.
How far in advance should it go out? Five to seven days. Check your bylaws for a minimum notice requirement, then send earlier than that minimum regardless.
What is a consent agenda and do we need one? A bundle of routine items approved in one motion without discussion, with any director able to pull an item out. If your meetings spend their first half hour on minutes and routine reports, yes, you need one.
What is the difference between a board packet and a board book? Nothing substantive. "Board packet" and "board materials" are the common US nonprofit terms, "board pack" is the Commonwealth term, and "board book" is more common in corporate and enterprise settings. Use whichever your board already says.
Should the packet include the full committee minutes? Put a short committee report in the body and the full minutes in the appendix. Directors who want the detail can find it; nobody is required to read it.
Who should write the board report? The chief executive writes theirs, committee chairs write theirs, and the chair and chief executive set the agenda together. When staff write the committee reports, committees stop owning their work.
Should board packets be confidential? Treat them as internal and sensitive. They routinely contain personnel discussion, financial detail, donor information and legal matters. Where your minutes are subject to member inspection rights under your bylaws or state law, know that in advance. This is a good reason not to distribute packets through personal email and consumer file sharing.
How do we handle executive session material? Keep it out of the general packet. Distribute it separately, to the directors entitled to see it, and record in the minutes only that the board entered executive session, the general subject, and any action taken on return.
Related guides
- Board meeting agenda: structure, labels and a template
- Board meeting minutes: what to include and what to leave out
- How to run a board meeting
- Quorum: how to work out yours and what happens without it
- AI-drafted minutes: the governance questions nobody is answering
- Board management software, explained without the sales pitch
Nonprofit Liaison assembles the packet from what your contributors upload, versions it, builds the table of contents, publishes one always-current link, tracks who opened it, and collects RSVPs against the same meeting. $99 a month, flat, unlimited board members. Try the free packet builder or book a walkthrough.
Sources
Real nonprofit board agenda structures reviewed from published board materials, including the Ed Thomas YMCA of McCook common board meeting agenda · YMCA of Metropolitan Milwaukee bylaws, meeting notice requirements · Capterra and G2 verified user reviews on mobile packet performance and minutes searchability · BoardSource guidance on consent agendas and board reporting