· I'mBoard Team · governance · 16 min read
What Is a Board Packet? The Nonprofit Board Packet Guide (+ Template)
A board packet is what your directors read before the meeting. What goes in one, the order that works, how long it should be, when to send it, and a copy-and-adapt outline.
What Is a Board Packet?
A board packet is the single set of materials your directors read before a board meeting: the agenda, the minutes awaiting approval, the treasurer’s report, the executive director’s report, committee reports, and the background behind every decision the board is being asked to make. Some organizations call it the board book. It exists so that fifteen volunteers with day jobs can walk into a room — or a Zoom — already knowing enough to discuss and decide, instead of being briefed from zero for the first forty minutes.
That is the whole test. If your directors could not vote responsibly on any item without someone reading a report aloud to them, the packet did not do its job. British and Australian boards use a different name for the same document; here is what that term covers if you are working from a template written on the other side of the Atlantic.
Most nonprofit board packets fail in one of two directions. They are too thin — an agenda and a financial statement emailed the night before, so the meeting becomes a staff briefing. Or they are too thick — a hundred pages of appendices nobody opens, which produces exactly the same meeting, because a packet that is impossible to read and a packet that was never sent are functionally identical.
Part of our Nonprofit Board Portal resources — pricing, the honest comparison including the free options, and how the verified-nonprofit half price works.
What Goes in a Nonprofit Board Packet
There is no legally required table of contents. Your bylaws may name a few items that must be circulated in advance; beyond that, the contents are a governance choice. The list below is the working standard for a 501(c)(3) board, in the order most boards find works.
1. The agenda, with a time and an ask per item
The agenda is the packet’s spine and the first page directors see. Every line should carry three things: how long it gets, who owns it, and what the board is being asked to do — approve, discuss, or receive for information. An agenda that reads “Finance — Treasurer” tells a director nothing. “Approve FY27 budget — Treasurer — 20 min — motion” tells them to read the budget before they arrive.
2. The consent agenda bundle
Routine, non-controversial approvals go into one bundle passed with a single motion: minutes of the last meeting, standard committee reports, a policy renewal that changes nothing, a grant acceptance already inside board policy. Any director may pull an item out for discussion, no reason required. That single mechanism is the difference between a meeting that spends its first half hour on housekeeping and one that spends it on the organization. If it is new to your board, start with what a consent agenda is and then how to run one.
Everything in the consent bundle must be in the packet in full. That is the deal: the board approves without discussion because it read the material in advance, not because it trusts staff to have handled it.
3. The treasurer’s report with budget-to-actual
Not a raw export from the accounting system. A nonprofit board’s finance section wants:
- Budget to actual for the year to date, with variances flagged and briefly explained — a column of numbers is data, a sentence saying why the program line is 18 percent under is governance.
- Statement of financial position — assets, liabilities, net assets split restricted and unrestricted.
- Cash position and operating reserves in months, which is the number a director will actually remember.
- Anything a director should be worried about, stated plainly by the treasurer rather than buried in a footnote.
Directors have a fiduciary duty of care, and financial oversight is where it is most often tested. Give them something they can exercise it on.
4. The executive director’s report
The ED report is the narrative layer: program delivery against plan, staffing and any changes, development progress, partnerships, risks emerging, and decisions the ED wants the board’s air cover on. Two to four pages. The discipline here is separating governance from management — the report should surface what the board needs to govern, not everything that happened. Operational detail belongs in an appendix or nowhere.
5. Committee reports and committee minutes
Finance, governance, development, executive — whichever committees carry the work between meetings. Each report should be short and end with a clear statement: nothing to bring forward, or a specific recommendation with a motion attached. Committee minutes attached behind the report give the full board the record without spending meeting time on it.
6. Decision items, each with its background
This is the part most packets get wrong. Every item the board will act on needs, in one place: the proposed motion in its final wording, the background that led to it, the options considered and why this one, the financial impact, and any conflict-of-interest disclosures. If a director has to ask “wait, what are we actually approving?” in the room, that item was under-documented and should probably be tabled.
Keep the standing reference material — bylaws, conflict-of-interest policy, board roster and terms, meeting calendar, strategic plan, latest audit and Form 990 — permanently available and linked rather than reprinted in every packet.
Order and Length: The Hundred-Page Packet Nobody Reads
Length is a governance decision disguised as a formatting one. Every page you add lowers the probability that any page gets read.
A workable target for a nonprofit board meeting is 20 to 30 pages of core packet, with everything else in a clearly labeled appendix that carries no expectation of being read. The core packet is the material a director must have absorbed to participate. The appendix is the material a director might want to check.
Three habits keep it there:
- Lead with the summary. Each section opens with a short “what you need to know” paragraph. A director who reads only the first page of every section should still be able to hold up their end of the discussion.
- Push detail down, not out. Do not delete the full grant report — move it behind the two-paragraph summary, so the diligent director can go deeper and the rushed one is not blocked.
- Cap the ED report and each committee report. A page limit is a crude tool that works. Nobody has ever complained that a board report was too short.
Order matters as much as length. Put the items needing the board’s best thinking early, while attention is high: consent agenda, then the strategic discussion or significant decision, then finance, then reports. Boards that put the strategic conversation last discover it never happens.
A Copy-and-Adapt Board Packet Outline
Adapt the sections and the page targets to your board’s size and cadence. The point is the shape, not the numbers.
BOARD PACKET — [Organization] — Board Meeting, [Date]
COVER PAGE
Meeting date, time, location and video link
Quorum requirement (from bylaws) and current board size
Packet sent [date] — questions to [staff contact] by [date]
1. AGENDA 1 page
Each item: owner, minutes allotted, action type
(approve / discuss / receive)
2. CONSENT AGENDA 1 page + attachments
a. Minutes of [prior meeting date] attached in full
b. Committee reports accepted as submitted attached in full
c. [Routine approval within board policy] attached in full
Note: any director may pull any item, no reason needed
3. STRATEGIC DISCUSSION / DECISION ITEMS 3-6 pages
For each item:
- Proposed motion, final wording
- Background and how we got here
- Options considered and why this recommendation
- Financial and program impact
- Conflict-of-interest disclosures, if any
- What we need from the board today
4. TREASURER'S REPORT 4-6 pages
Budget to actual, year to date, with variance notes
Statement of financial position
Cash and operating reserves, stated in months
Restricted vs unrestricted net assets
Treasurer's plain-language summary and concerns
5. EXECUTIVE DIRECTOR'S REPORT 2-4 pages
Programs against plan
Staffing
Development and funder relationships
Risks and issues emerging
Where the ED needs the board
6. COMMITTEE REPORTS 1 page each
Governance / Finance / Development / [other]
Each ends with: nothing to bring forward, OR
a specific recommendation with motion wording
7. APPENDIX (reference only, no reading expected)
Full grant and program reports
Detailed financial statements
Policy documents under revision
STANDING REFERENCE (linked, not reprinted every meeting)
Bylaws | Conflict-of-interest policy | Board roster and terms
Annual meeting calendar | Strategic plan | Latest audit and Form 990
For the agenda itself, our nonprofit board agenda guidance goes deeper on sequencing, and the board meeting preparation checklist covers the staff-side production run.
When to Send the Board Packet
A week before the meeting. Seven days is the working standard for a volunteer board, and the reasoning is entirely practical: your directors have jobs. A packet that lands Thursday night for a Saturday morning meeting gets skimmed in the parking lot — and an unread packet is one of the quieter reasons directors stop showing up, which is where missed quorum comes from.
Sending late is a governance failure with a scheduling cause. Directors who did not read cannot discuss, so they defer to staff — the opposite of oversight. It also compounds: once the board learns the packet always arrives late, they stop looking for it early, and even an on-time packet goes unread.
The way to hit the date is to work backwards from it and put the internal deadlines on staff calendars, not in someone’s head:
| When | What happens | Who |
|---|---|---|
| 3 weeks out | Chair and ED set the agenda; decision items identified | Chair + ED |
| 2 weeks out | Committee reports and treasurer’s report due to staff | Committee chairs, treasurer |
| 10 days out | ED report drafted; decision-item backgrounds written | ED |
| 8 days out | Packet assembled, proofed, page count checked | Staff / operations |
| 7 days out | Packet distributed to the board | Staff |
| 3 days out | Reminder with the direct link; RSVPs confirmed for quorum | Staff |
| Day before | Final reminder, any late addendum flagged explicitly | Staff |
If something is not ready at the 8-day mark, send the packet without it and follow with a clearly labeled addendum. A complete packet that arrives too late to read is worth less than an incomplete one that arrives in time.
How to Distribute It So Directors Actually Open It
The delivery mechanism decides the read rate more than the content does.
Email attachments are the default and they fail in predictable ways. They break on phones, they get buried under the reply-all thread that follows, and when you send a correction you have created a second version living in fifteen inboxes with no way to know who is reading which one. Six months later, when someone needs last March’s packet, it is in whoever’s mailbox still has it.
A shared drive folder solves versioning and creates a permissions problem instead: it inherits whoever set it up, and when that volunteer’s account is deleted the bylaws go with it. Most nonprofits that have been around a decade have a story like that.
A link that opens the current packet is the arrangement that works — one address, always pointing at the latest version, with the appendix a click away rather than 60 pages of attachment. The critical detail for a volunteer board is what happens when the least technical director taps that link. If the answer is a login screen and a password reset, you will get the adoption rate everyone in this sector describes the same way: about half the board. If it opens, they read it.
The Packet, the Meeting, the Minutes, the Archive
The packet is one stage of a loop, and boards that treat it as a standalone deliverable pay for it later.
Packet → meeting. The packet sets the agenda, so it determines what gets discussed. Items with no written background become items with no real decision.
Meeting → minutes. The minutes record what the board decided against what the packet asked. When the packet contains the final motion wording, the secretary is transcribing rather than reconstructing — which is most of why some boards’ minutes take an hour and others take a week. If minutes are the bottleneck at your board, how to write minutes and the minutes template are the place to start, and the secretary’s duties guide covers who owns what.
Minutes → archive. Approved minutes are a permanent legal record, and Form 990 Part VI asks how your board documents its decisions. Approving them promptly — the IRS Form 990 instructions’ benchmark for contemporaneous minutes is the later of the next meeting or 60 days after the meeting — is the practical answer. Minutes sitting unapproved for three meetings is a finding waiting to happen.
Archive → next packet. The next packet needs the last minutes for the consent agenda, plus whatever prior decision an item builds on. A searchable archive turns that into thirty seconds; a folder named “Board Stuff (new)” turns it into an afternoon.
Where Board Packets Go Wrong
The packet goes out late, every time. Usually because one committee report is always missing. Fix the process, not the deadline: ship on time with a gap and a labeled addendum, and the late report becomes visible to the board rather than absorbed by staff.
Version confusion. Two treasurer’s reports, one corrected, both in the thread, and three directors looking at different numbers in the meeting. It is the strongest argument for one link over attachments: there is only ever one current version.
Abridging that quietly creates work. A director asks for a two-page summary, so staff now produce a summary and the full packet — the work doubled and the summary became the only thing anyone reads, unaudited. Better to restructure the packet once, with the summary at the top of each section, than to maintain two documents forever.
No background on decision items. The board is asked to approve something it is learning about in the room, and either rubber-stamps it — a fiduciary problem — or tables it, wasting a meeting.
Nobody knows who read it. Knowing who has opened the packet three days out is what lets the chair make a phone call before the meeting instead of discovering the gap during it.
How a Board Portal Helps
You can run a perfectly good board on email and a shared folder — plenty of organizations do, and the honest comparison is on our nonprofit board portal page alongside the free options. What a board portal changes is the staff hours the packet consumes and the read rate at the other end.
With I’mBoard specifically, the shipped surface is: build the packet from the agenda and the uploaded reports, with AI narrative drafting to turn a set of documents into readable section summaries; distribute it as a link every director opens without a login or a password; see who has opened it before the meeting rather than after; schedule the meeting and send the reminders from the same place; capture decisions and action items as they happen; and file everything into a searchable archive you can export in full, free, forever. It is $149/month flat per board, $74/month for EIN-verified 501(c)(3)s, every director and every committee included.
There is a live demo with no signup if you want to see a packet before you decide anything.
Ready to see what your next packet looks like? Try I’mBoard free → — free until after your next board meeting (up to 60 days), no card, no contract.
FAQ
What is a board packet?
A board packet is the compiled set of materials sent to directors before a board meeting: agenda, minutes for approval, treasurer’s report with budget-to-actual, executive director’s report, committee reports, and the background behind every item the board will decide. In a nonprofit it is assembled by the ED or an operations manager, usually with the board chair setting the agenda alongside them.
What should be included in a nonprofit board packet?
At minimum: a timed agenda showing what the board is asked to do on each item; the consent agenda with all its attachments in full; a treasurer’s report showing budget to actual, cash, and reserves in months; the executive director’s report; committee reports; and, for every decision item, the proposed motion with its background, options, and financial impact. Bylaws, the conflict-of-interest policy, and the board roster should be permanently available rather than reprinted every time.
How long should a board packet be?
Aim for 20 to 30 pages of core material, with everything else in a labeled appendix nobody is expected to read. The hundred-page packet is not more thorough — it is less likely to be read at all, which produces the same meeting as sending nothing. Summarize at the top of each section and push the detail behind it.
When should the board packet be sent?
A week before the meeting. Volunteer directors need a weekend to get through it. Sending the night before all but guarantees an unread packet, a meeting spent on briefing instead of governance, and a board that defers to staff on decisions it is supposed to be overseeing.
What is the difference between a board packet and a board book?
None, in practice — they are two names for the same document, and American boards use both. “Board book” tends to show up at larger organizations and in older governance writing. British and Australian boards use a third term for it, which is worth knowing if you are adapting a template from overseas.
Who prepares the board packet?
At most 501(c)(3)s the executive director assembles it, often with the board chair co-owning the agenda and the treasurer and committee chairs supplying their sections. Above roughly $1M in budget, an operations manager or executive assistant usually takes over production. The secretary owns the minutes inside it, not the packet as a whole.
Glossary
Board Packet: The compiled set of materials distributed to directors before a board meeting so they arrive prepared to discuss and decide. Also called a board book.
Consent Agenda: A bundle of routine approvals passed with a single motion. Any director may “pull” an item out for discussion without giving a reason, which is what makes bundling safe.
Budget to Actual: A comparison of what the organization planned to spend and receive against what it actually did, year to date, with the variances explained. The core of a nonprofit treasurer’s report.
Operating Reserves: Unrestricted net assets available to cover operations, usually expressed in months of expenses. The number directors remember and the one funders ask about.
Restricted vs Unrestricted: Funds a donor has limited to a specific purpose or period versus funds the board may direct. Confusing the two is how a board approves spending it does not actually have.
Decision Item: An agenda item on which the board will take formal action, requiring the proposed motion, its background, the options considered, and the financial impact — all in the packet, before the meeting.
Addendum: Material distributed after the packet but before the meeting, clearly labeled. Better than delaying the whole packet for one late report.
Form 990 Part VI: The section of the annual IRS return that asks about governance practices, including how the board documents its decisions. Prompt minutes approval is the practical answer to it.