A board revenue reporting package is the fixed set of revenue exhibits a company delivers ahead of every board meeting. It covers results against the operating plan, the forecast for the open period, retention movement, and pipeline health. The value comes from the format staying the same. When the layout repeats quarter after quarter, the board spends its attention on what moved rather than on what each chart means.
What belongs in the package
Five exhibits carry most of the weight.
- Results against plan for the closed period, with the variance broken down by segment and by driver. - The current forecast for the open period, stated with its assumptions and its range. - An ARR reconciliation that walks beginning ARR to ending ARR through new business, expansion, contraction, and churn. - Pipeline entering the period, shown with coverage, age, and stage mix rather than a single total. - Efficiency, showing what the growth cost to acquire.
Anything past those five goes in an appendix. Directors read a five-exhibit package. They skim a twenty-slide one.
Every number traces to one source
The fastest way to lose a board is to have two slides disagree. Bookings on the sales page and ARR on the finance page get built from separate exports, and the meeting turns into a reconciliation exercise instead of a decision. Fix it upstream by defining each metric once and generating every exhibit from the same layer.
Traceability matters as much as consistency. When a director asks where a figure came from, the answer should be a query someone can run in the room. ORM's Pete Furseth makes the point about AI-assisted decks specifically: if the output cannot point back to the point of truth that drove the numbers, validating them takes as long as building the deck by hand. ORM built Radar, its MCP and in-app AI, to hold the semantic and analytics layer that raw CRM data lacks, so a board figure traces to a query rather than to a spreadsheet someone saved last Thursday.
Where packages lose credibility
Packages fail on optimism, not on formatting. A sales forecast that lands above plan for three quarters and then misses badly costs more trust than a lower number delivered consistently. Two habits protect against that.
Report forecast accuracy as a standing metric, grading what you told the board last quarter against what actually happened. And stop presenting pipeline coverage as proof the number is safe. Coverage is an input to the forecast, never the conclusion. A company can hold 4x coverage and still miss when the pipeline is aged, concentrated in a handful of large deals, or carrying values well above what deals close for. The 3x coverage rule breaks down exactly when the board most needs a real read on the quarter.
Frequently Asked Questions
What goes in a board revenue reporting package?
Results against the approved plan for the closed period, the current forecast for the open period with its assumptions, an ARR reconciliation from beginning to ending balance, pipeline entering the period with age and stage mix, and an efficiency measure showing what the growth cost. Everything else belongs in an appendix. A package that grows every quarter trains directors to skim it.
How far before the meeting should the package go out?
Far enough ahead that directors read it before they arrive, which in practice means several days rather than the night before. Material that lands late guarantees the meeting is spent narrating slides rather than debating decisions. The package is pre-read, and the meeting is for the questions the pre-read raises.
Should the board package show the plan or the forecast?
Both, held separately. The plan is the approved commitment for the year and does not move. The forecast is the current expectation and moves as the period progresses. Restating the plan to match a weaker forecast erases the baseline the board approved and removes the ability to see whether the year is on track.
How do you keep numbers consistent across slides?
Define each metric once, generate every exhibit from the same data layer, and lock the definitions for the full fiscal year. Most board credibility problems start when the sales page and the finance page are built from different exports by different teams. If a definition has to change mid-year, restate prior periods on the new basis and show both.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like board revenue reporting package into prescriptive action for your team.
Schedule a Demo