What to include in a board book

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.

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.

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.

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.

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.

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.