The packet's job is decisions, not archives
A board packet exists to help a group of busy volunteers make good decisions in a limited amount of time — not to serve as a complete historical record of the organization's activity. When a packet tries to do both, it usually fails at the first job: board members either skip the reading entirely or skim it minutes before the meeting starts.
What belongs at the front
The items requiring an actual vote or decision should be the first thing a board member sees, with a one-paragraph summary of what's being asked and why. Financial reports, committee updates, and informational items belong after the decision items, not before them — a board member who reads only the first page should still know exactly what's up for a vote.
Consistency matters more than polish
A packet that follows the same structure every month — same section order, same summary format — gets read faster over time, because board members learn where to look for what they need. A beautifully designed packet that reorganizes itself every meeting actually slows a board down, even if each individual page looks great.
The consent agenda, done right
Routine, non-controversial items — approving last month's minutes, ratifying a small expenditure already within budget — don't need individual discussion time. Grouping them into a single "consent agenda" that gets approved with one vote (unless a board member specifically pulls an item out for discussion) frees up meeting time for the decisions that actually need debate. Boards that skip this step often spend as much time on routine approvals as they do on the decisions that matter.
How often to revisit the format
A packet format that works well doesn't need to change often — but it's worth a real review at least once a year, usually when board turnover brings in new members who didn't help design the current structure. Asking new board members what was confusing about their first packet is one of the more reliable ways to catch a format that's become comfortable for veterans but genuinely unclear for anyone new.
What a new board member's first packet should feel like
A useful test for any board packet is imagining it in the hands of someone who joined the board a week ago, with no institutional memory of past decisions or ongoing initiatives. If that new member can identify what's being voted on and why within the first two pages, the format is working. If they need a phone call to a longer-tenured board member just to understand what the packet is asking of them, the structure — not the new member's unfamiliarity — is usually the actual problem worth fixing before the next meeting rolls around, since the same confusion will just repeat itself with the next new member who joins, and the one after that, until the format itself changes.
Why length and quality pull in opposite directions here
It's tempting to think a more thorough packet — more detail, more supporting documents, more context — automatically makes for a better-informed board. In practice, the opposite is often true: the longer and more exhaustive a packet gets, the less of it any individual board member actually reads before the meeting. A shorter packet that surfaces exactly what needs a decision, with supporting detail available on request rather than included by default, tends to produce more informed discussion than a comprehensive one nobody finished reading.
What board members say when asked directly
Boards that survey their own members about packet quality tend to hear a consistent complaint: not that the content is wrong, but that they can't find what they need in time to prepare. That single piece of feedback — findability over content — is usually the clearest signal that a format problem, not an information problem, is what's slowing the board down. Fixing structure and consistency addresses this directly; adding more detail to an already-hard-to-navigate packet does not.
Where this breaks down in practice
Most nonprofits build packets by hand each month, pulling reports from different systems and pasting them into a shared document — a process that eats hours of staff or volunteer time and produces a slightly different format every cycle. Boards that move to a shared system for packets, agendas, minutes, and votes tend to see both problems improve at once: less prep time, and a packet board members can actually navigate without relearning the layout, month after month, regardless of who's putting it together.