How to Build a Board Package Directors Can Actually Use
A package is not a pile of attachments. It is the document set your Board governs from.
By A.C. Lynch, GPC Desig. · Governance practitioner

The test a package has to pass
A good Board package answers three questions without anyone having to ask you: what are we deciding, what do we need to know to decide it, and what happened since we last met. If a director has to email you for context, the package has not done its job.
That standard is achievable with structure alone. It rarely requires more content — usually less, better organized.
A reliable running order
Order matters because it signals priority. This sequence works for most Boards:
- Cover page: organization, meeting type, date, time, location or link.
- Table of contents with page numbers, marking each item as decision, discussion or information.
- Agenda.
- Minutes of the previous meeting for approval.
- Business arising and the action item register.
- Financial report for the period, with any variance notes.
- Senior staff or Executive Director report.
- Committee reports.
- Decision items, each with its own briefing note.
- Information items and correspondence.
- Appendices: policies under review, contracts, background material.
Briefing notes do the heavy lifting
Every decision item deserves a one-page briefing note: the issue, relevant background, options considered, the recommendation, the financial and risk implications, and the proposed motion wording. Drafting the motion in advance is not presumptuous — it saves the meeting from wordsmithing under time pressure, and the Board is free to amend it.
Where a decision has policy implications, name the policy and the section. Directors should not have to guess which rules they are working inside.
Version control is the whole discipline
Most package failures are version failures: two financial summaries with different totals, a policy draft that was superseded, an agenda that says one thing while the covering email says another. Adopt one naming convention, use it every cycle, and keep a single source folder per meeting.
Keep a short pre-distribution checklist and run it every time, even when you are certain.
- One agenda version, matching the table of contents.
- Every decision item has an attached document and a proposed motion.
- Figures reconcile across the financial report, briefing notes and appendices.
- Confidential material is separated and labelled, not buried mid-package.
- Pagination is continuous and the file opens cleanly on a phone.
Distribution and afterwards
Distribute within your notice period, record when and to whom, and keep the distributed version untouched. If something must be added afterwards, send it as a clearly labelled supplementary item rather than reissuing the package — a reissued package leaves directors unsure which one is real.
After the meeting, file the distributed package alongside the approved minutes. Together they show what the Board decided and what it had in front of it when it decided.
The short version
- Structure beats volume: a table of contents, a consistent order and page numbers solve most package problems.
- Give every decision item a one-page briefing note with a proposed motion.
- Keep one source folder and one naming convention per meeting.
- Never reissue a distributed package — send labelled supplementary items instead.
- File the distributed package with the approved minutes.
Stay connected
Practitioner-led governance resources, new publications, and directory news — delivered occasionally, never sold.
Want to choose specific interests? Use the full sign-up form.