The standard sections
01
Most board books follow a fairly consistent structure, even though the specific content varies by company stage and industry.
The board book should mirror the agenda. Directors should be able to move from an agenda item to the relevant memo, metric, report, or proposed resolution without guessing where it lives.
- Agenda for the upcoming meeting
- Minutes from the previous meeting, pending approval
- CEO or executive summary covering the period since the last meeting
- Financial reports and key operating metrics
- Committee reports, if applicable
- Decision items with supporting context and a clear recommendation
- Supporting documents referenced by agenda items
- Outstanding actions and upcoming milestones — reporting dates, AGMs, filing deadlines — due before the next meeting
Where BoardKite helps
BoardKite assembles this list from live records instead of a manual copy-paste: the standard sections pull current financials, open decisions, and outstanding actions automatically, and a board calendar surfaces upcoming fiscal, governance, and disclosure dates so nothing forces an emergency agenda item.
Decision items need extra context
02
Decision items are the highest-value part of the board book. A director should not have to infer what is being requested from a long memo or a slide deck. The board book should state the decision, the recommendation, the options considered, and the implications of approving or rejecting it.
This is where many board books become too presentation-heavy. Slides may explain background, but the decision context should be explicit and easy to scan before the meeting starts.
- Decision requested: the exact approval, vote, or direction needed
- Recommendation: what management or the committee proposes
- Alternatives: realistic options considered and rejected
- Risks: financial, operational, legal, or strategic tradeoffs
- Follow-up: owner and next action if approved
Where BoardKite helps
BoardKite structures each decision item the same way — the ask, recommendation, and options stay attached to the agenda item, and once approved, the follow-up becomes a tracked action linked back to that decision instead of a line in a memo.
Financial and KPI sections should be board-ready
03
Financial reports and operating metrics should help directors exercise judgment, not simply archive every dashboard. Put the most important trend, variance, or question up front, then link to detail for directors who want to inspect the underlying numbers.
For early-stage companies, that often means runway, burn, revenue, pipeline, hiring, product delivery, and key risks. For nonprofits, it may mean budget-to-actuals, program metrics, fundraising, compliance, and mission impact.
- Current period results and trend against plan
- Material changes since the last board meeting
- Cash, runway, budget, or liquidity view where relevant
- Key operating metrics and risks requiring board attention
- Management commentary explaining variance, not just raw numbers
Common mistakes
04
The most frequent problem is staleness — a board book assembled a week early with financial screenshots that are already out of date by meeting day. A close second is inconsistency: every meeting's board book looking different in structure, which forces directors to hunt for what they need instead of knowing where to look.
Another common mistake is volume. A large board book can look thorough while making preparation harder. Directors need enough detail to make good decisions, but the main packet should separate essential material from appendices and reference documents.
- Sending a new PDF every time one number changes
- Mixing routine updates with decision-critical materials
- Using inconsistent section names from meeting to meeting
- Including long appendices without a summary or recommendation
- Failing to mark what changed after the first circulation
Why static PDFs cause problems
05
A board book emailed as one large PDF is hard to update, hard to search, and impossible to version cleanly — if a number changes two days before the meeting, someone has to rebuild and resend the whole document. It also makes access control an afterthought; once a PDF is sent, there's no way to control who forwards it or for how long it stays accessible.
Static PDFs also disconnect materials from the decisions they support. Months later, the team may have the minutes in one place, the old PDF in another, and the follow-up action somewhere else entirely.
- Version control becomes a manual naming convention
- Search depends on local files and email archives
- Access cannot be reliably revoked after distribution
- Directors may review different versions before the same meeting
- Supporting documents are separated from minutes and decisions
Where BoardKite helps
BoardKite avoids this by keeping one current version behind a permissioned link instead of a distributed file — access can be changed or revoked by role at any time, and every past board book stays searchable by meeting instead of scattered across email threads.
A better approach: a living board book
06
Tools that build the board book from the same live agenda items, metrics, and documents your team already works in solve the staleness problem directly — directors always open the current version, and updates propagate without anyone re-sending an attachment.
A living board book also preserves context after the meeting. The agenda, supporting documents, decisions, minutes, signatures, and follow-up actions can stay connected as one governance record instead of becoming a set of disconnected files.
- Agenda items and supporting materials stay connected
- Updates can be made without recirculating a whole PDF
- Directors open the current version from one secure link
- Access can be role-based and revoked when needed
- Past board books remain searchable with meeting history
Where BoardKite helps
A living board book is only as trustworthy as its security model. In BoardKite, the underlying agendas, minutes, decisions, and attachments are encrypted at rest with a per-organization key, and the AI drafting that pulls the book together runs on a provider your organization configures, whether that's the hosted default or your own key.