Board Pack Review Checklist: What to Check Before the Meeting
A board pack is a decision instrument, not a report. Review it by asking whether a director who missed the pre-read could vote from it, and whether every number can be traced.
What the pack is for
Board packs often grow by accretion: each meeting adds a section, and nobody removes anything. The result is a thick document that describes activity but does not frame a decision. Before reviewing content, check the purpose stated for this meeting. If the pack does not contain a decision, an approval, or a specific oversight question, it is a status report and should be labelled as one.
A useful test is the absent director. Someone who joins remotely, has read the pack once, and has twenty minutes before the vote should be able to identify the ask, the options, the recommendation, and the main risk. If that takes more than twenty minutes, the pack is not ready, regardless of how complete the appendices are.
The decision page
The first page should state the decision in one sentence, name the accountable executive, give the date, and list the options considered. “Approve the proposed supplier agreement and the associated three-year commitment” is a decision. “Note the supplier update” is not. If the ask is conditional, state the conditions and who confirms them.
Check that the recommendation is explicit. A pack that presents analysis without a recommendation pushes the synthesis onto the board, which is the opposite of what a board needs. Where management is genuinely divided, say so and describe the disagreement rather than averaging it into a compromise nobody owns.
Check a board pack against twelve sections
Mark the sections the pack contains. The tool lists what is missing and the question each missing section is supposed to answer.
Financial discipline
Every financial table needs three labels: period, currency, and basis. A revenue figure without a period is not information. A comparison against budget needs the budget version and the date it was approved. Where numbers are restated, explain the restatement rather than presenting the new figure as if it had always existed.
Check that totals tie to the underlying schedules. A summary table that does not reconcile to the detail is either a rounding problem or a control problem, and the reviewer cannot tell which without asking. Look for reconciling items, one-off adjustments, and anything described as “below the line”; these are where the story usually hides.
Variance commentary should explain the cause and the durability. “Costs were higher than plan” is not commentary. “Costs were higher because the migration ran two months longer, and the remaining spend ends in Q2” tells a director what to expect next period.
Assumptions, sensitivities, and risk
Identify the two or three assumptions that carry the recommendation. For an investment case, that might be conversion, churn, or the timing of a regulatory approval. For a cost programme, it might be headcount timing or a supplier commitment. Then check whether the pack shows what happens if those assumptions are wrong by a plausible margin.
A sensitivity table is only useful if the range is realistic. Ranges that vary by two percent do not test the decision. Ask what would have to be true for the recommendation to reverse, and whether that scenario is described anywhere in the pack.
Risks should have owners, dates, and mitigations. A risk register that lists “regulatory change” with no owner is an observation, not a control. Check that the top risks match the ones discussed in the narrative; a mismatch between the register and the prose is a signal that the pack was assembled from different drafts.
Alternatives and dissent
A recommendation without alternatives is hard to approve, because the board cannot see what was rejected or why. The alternatives section should describe the rejected option fairly enough that its supporters would recognise it, and state the reason for rejection in terms of the decision criteria rather than preference.
If a function or a director has expressed a concern, record it. A pack that presents unanimous support where there was disagreement creates a governance problem later. Minutes should reflect the actual discussion, including the questions that were not fully answered.
Operational capacity and people
Approval is not delivery. Check who will do the work, whether they have capacity, and what will stop as a result. Programmes often fail because the same small team is named in three concurrent initiatives, and the board approved all three without seeing the capacity constraint in one place.
People and communication matter in any decision that changes roles, suppliers, or customer commitments. The pack should say who is told first, internally and externally, and what the fallback is if the announcement leaks or the counterparty reacts badly.
Appendix, version control, and the one-hour pass
Appendices should be traceable: each figure linked to a dated source, each source labelled with a version, and each page numbered. If the pack was revised after circulation, the revision should be marked and the changed sections highlighted. Directors who read an early version and vote on a later one need to know what moved.
A practical reviewer pass takes about an hour. Read the decision page and the recommendation. Check the three largest numbers against their schedules. Read the risk section for owners. Read the alternatives section for fairness. Then read the executive summary again and ask whether it still describes the pack you just read. If not, the summary needs rewriting, not the reader.
When the pack is late, thin, or still moving
Packs arrive late for predictable reasons: the numbers were not final, a function did not submit its section, or the recommendation changed after the first draft. The review response should be proportionate. If the decision can wait, ask for the missing section and a revised circulation date. If it cannot, run the meeting on the material available and record explicitly which decisions are deferred and why.
A thin pack is a signal about the decision, not only about the document. If management cannot answer the core question in a page, the work behind the recommendation may not be finished. That is worth saying in the meeting, in neutral terms, because it changes what the board can responsibly approve.
Watch for material that is still moving during the meeting. A revised financial slide presented live, or a legal position described verbally as “being finalised”, should be recorded as an open item rather than treated as approved content. The minutes are the control that keeps the decision tied to the version the board actually saw.
Limits of a pack review
A reviewer can check internal consistency, traceability, and completeness. A reviewer cannot confirm that the strategy is right, that the market data is accurate, or that the legal position is sound without the underlying advice. Say which of those you verified and which you did not.
This checklist is a structure for review, not a substitute for directors’ judgement or professional advice. Use it to make the pack easier to decide from, and to make the gaps visible before the meeting rather than during it.
Scope a private review by email
Send the matter, file volume, formats, deadline, and decision question. A person confirms fit, handling, and timing before files move.