Board & Management Packs

The board pack is the most scrutinized document most companies produce. It arrives on a fixed date, it carries the numbers the board will be asked to approve, and it is read by people whose time is measured in minutes. A pack that is late, inconsistent with the last one, or unclear about what the reader is being asked to decide costs credibility that is hard to recover.

This playbook covers how to prepare a board or management pack reliably: what it must contain, how to build the cycle around the meeting date, where the numbers come from, and how to keep it consistent from quarter to quarter. It sits across Recurring Report Production and Report Structure & Standards.

The board asks two questions of every pack: is this consistent with last quarter, and what am I being asked to decide? A pack that answers both is doing its job.

What a board or management pack is

A board pack is a recurring report prepared for a board or executive committee ahead of a scheduled meeting. A management pack is the same document aimed inward at an executive team, usually with more operational detail and a shorter cycle.

Both share the defining features of a recurring report: a fixed cadence tied to meeting dates, a defined audience, and a deadline the producer does not set. The board date is the anchor, and everything else schedules backward from it.

Because the pack is governed by the meeting calendar rather than the reporting calendar, the production cycle is shorter and less forgiving than for most reports. There is no option to issue next week.

What it must contain

A board pack has a predictable shape, whatever the business.

The decisions page is the one most often missing, and the one the board most needs. A pack that presents performance without stating what is being asked of the reader leaves the meeting to reconstruct its own purpose.

Building the cycle around the meeting date

The single most useful discipline in board-pack production is to schedule backward from the meeting date, not forward from the data close.

• Meeting date minus 10 working days: data freeze. All figures for the pack are fixed.
• Minus 8: first draft assembled from the standard structure.
• Minus 6: variance commentary drafted against the frozen numbers.
• Minus 4: internal review, including the finance lead and the executive sponsor.
• Minus 2: final approval and sign-off, logged with a version.
• Minus 1: distribution to the board.
• Meeting day: the pack is presented, with any late change handled as an exception.

Scheduling backward is what makes the deadline real. Where the cycle is scheduled forward from the close, a late close silently consumes the review time, and the pack is finalized in the final hours before the meeting.

The preparation process

Within that calendar, the work itself follows a repeatable sequence.

• Intake last cycle’s pack as the starting point. Reuse the structure, the definitions and the exhibit formats.
• Freeze the data and record the snapshot. The pack must be reproducible after the meeting.
• Refresh the standard exhibits. Most exhibits change only in their numbers.
• Write the commentary against the numbers, not before them.
• Reconcile to the management accounts before the pack is circulated, so no figure is a surprise.
• Run the pre-issue checks – totals, completeness, period alignment, units.
• Get the approvals, and record who approved which version.

Most of the effort in a poor pack goes into rebuilding what already existed. The intake step is where that effort is recovered. See The Reporting Workflow for the sequence in full.

Where the numbers come from

Board packs fail most often on data, not on prose.

Figures arrive from the finance system, the CRM, operational systems and manual inputs, and they are assembled under time pressure. Two of the most common defects are a figure that cannot be traced and a figure that disagrees with another report to the same audience.

The scale of the underlying problem is documented. In a 2026 Intuit survey of 2,000 finance leaders, 51% of the finance week went to manual work such as reconciliation and report stitching, and 70% reported no single source of truth for critical data. A 2026 study of analytics teams found 78% of analyst time going to preparation and validation rather than insight. In board-pack terms, that effort sits between the close and the meeting.

The controls that address it are covered in the data pillar: a single agreed source per metric, a data-quality checklist run before issue, and a reconciliation to the management accounts. See Data Quality for Reporting and Data-Quality Checks for Report Production.

Keeping it consistent

Consistency is what makes a board pack readable across cycles, and it is what allows the board to focus on the change rather than the format.

• Keep the structure stable across cycles, so readers re-orient in seconds.
• Keep the definitions stable, so a metric means the same thing each quarter.
• Keep the exhibits stable, so a chart is comparable to its predecessor.
• Version the report, so a corrected pack does not circulate alongside the original.

A pack that changes shape every quarter forces the reader to relearn it, and hides genuine change among cosmetic change. Structure and definitions belong in a style guide, applied every cycle. See Report Style Guide and Report Approval & Sign-off.

Common failure modes

• Late close consumes the review. The cycle is scheduled forward, and review happens in the final hours.
• No data freeze. The numbers move after the draft is written.
• Untraceable figures. A number appears in the pack and no one can say where it came from.
• Inconsistent definitions. A KPI means something different from last quarter.
• No decisions page. The board is presented with performance but not with a question.
• Uncontrolled versions. A corrected pack circulates alongside the original.

What good looks like

A well-run board pack cycle has a small number of visible properties.

• The pack issues on schedule, every cycle, without a scramble.
• The figures reconcile to the management accounts, and any difference is explained.
• The structure is familiar, so the board reads the change, not the format.
• The decisions are explicit, and the board knows what is being asked.
• The pack is reproducible, from a retained snapshot and a version record.

None of these require a new system. They require a calendar, a frozen snapshot, a standard structure and a controlled approval.

What a pilot looks like

Most organizations can see the gap between their current board-pack cycle and the one described here. Closing it is usually a matter of weeks, not a transformation program.

A pilot typically covers two cycles of one report – the board pack is the most common starting point. We take the existing pack, standardize the structure and exhibits, install the data freeze and the checks, and run the cycle with your team observing. At the end, you have a pack that issues on schedule, a template and checklist you own, and a measured before-and-after of the time the cycle consumes.

If the pilot does not demonstrate a measurable reduction in production time, there is no obligation to continue. See book a pilot call to scope one against your calendar.

Frequently asked questions

What goes in a board pack?

Cover and contents, an executive summary, performance against plan, variance analysis, risks and issues, a decisions and approvals page, and supporting appendices. The decisions page is the most commonly missing and the most important.

How long should a board pack be?

Long enough to support the decisions and no longer. Most are 15-30 pages including appendices, with the substantive content in the first ten. The board’s time is the constraint, not the page count.

How far in advance should a board pack be prepared?

Work backward from the meeting: data freeze at ten working days, draft at eight, review at four, final approval at two, distribution at one. The exact figures vary, but the backward schedule is what makes the deadline real.

What is the difference between a board pack and a management pack?

Audience and detail. A board pack is written for non-executive directors and focuses on decisions and governance; a management pack is written for the executive team and carries more operational detail on a shorter cycle.

How do you stop the board pack numbers disagreeing with other reports?

Agree one source and one definition per metric, freeze the data, and reconcile the pack to the management accounts before issue. Most disagreements are a difference of source or basis, which a metric dictionary resolves. See Building a KPI & Metric Dictionary.

Who should prepare the board pack?

Usually the finance team, with contributions from the executive team for their sections. What matters is one named owner for the pack as a whole and a defined cut-off for contributions.

How do you handle a late change after the pack is distributed?

Treat it as an exception: assess materiality, and if the change matters, reissue through the controlled distribution list with a new version. Immaterial changes are noted at the meeting. See Data Refresh & Versioning.

How much time should a board pack take to produce?

It varies, but a well-run cycle concentrates effort in the four days after the freeze. Where production sprawls across two weeks, the cause is usually rework – rebuilding exhibits and chasing inputs – rather than the writing itself.

Can a board pack be produced with AI?

Parts of it can – first-draft commentary, structure and formatting – provided a human verifies every figure and every claim. The risk is a fluent narrative that is subtly wrong. See Using AI to Draft Reports.

Next step

Build the cycle backward from the meeting date, freeze the data, and keep the structure and definitions stable across cycles. See How to Produce Recurring Reports on Schedule for the production method, or book a pilot call to have the next two cycles run with you.

Sources

• Intuit Enterprise Suite, Future of Finance 2026 Report (survey of 2,000 CFOs, controllers and VPs of Finance at US businesses over $2.5M revenue, May 2026): 51% of the finance week spent on manual work such as reconciliation and report stitching; 70% report no single source of truth.
• dbt Labs and Quietly, “The Analyst Revolution” (Harris Poll, 2026): 78% of analysts’ time goes to data preparation, validation and tool navigation.

Figures are cited from their sources and dated. Where a source is a vendor benchmark, the sample size is stated.