Board reporting cadence is the schedule a company uses to report results and forecasts to its board: how often each report goes out, what it covers, and how far ahead of each meeting it lands. A common pattern for growing companies is a quarterly meeting plus a written monthly update. Timing matters more than frequency. Updated November 2026: added a sample cadence table, a seasonal pacing example, and board trust rules from ORM's COO.
What is reporting cadence?
Reporting cadence is the fixed rhythm on which results get shared: what is reported, to whom, and how often. Board reporting cadence is the version built for directors, who meet a few times a year and need to act between meetings.
That second part is where most cadences fall short. In the What Directors Think 2026 survey from Diligent Institute and Corporate Board Member, only 47% of directors said they receive real-time data between meetings often or always, as Diligent reports. The monthly update exists to close that gap. The investor update vs board deck entry covers how the monthly note differs from the meeting package.
A sample board reporting cadence
Each report in the cadence should map to a decision someone makes at that frequency. Pete Furseth, ORM's COO, applies the same test to any reporting tool: which decision does it support each week, each month and each year?
| Report | How often | Who sees it | What it carries | Decision it supports |
|---|---|---|---|---|
| Forecast call | Weekly | Revenue team only | Deal-level changes, commit, slipped close dates | Where selling time goes this week |
| CEO stand-up | Weekly | CEO and leadership | What changed since last week, forecast range | Whether anything needs escalating |
| Monthly board update | Monthly, fixed send date | All directors | Bookings against seasonal pace, forecast range and direction of travel, cash, top risks, asks | Hiring and spend adjustments, early warning |
| Quarterly board package | Quarterly, sent as a pre-read | Directors and observers | Quarter result; next-quarter forecast split into carry-over, in-quarter and pull-forward revenue; monthly ARR waterfall; decisions requested | Votes, approvals, plan changes |
| Annual plan | Yearly | Full board | Targets, capacity plan, documented assumptions (ramp by role and region, addressable market, average sales price, win rate, days to close) | Plan approval |
| Off-cycle update | When an assumption breaks | Directors | What broke, the effect on the range, the response | Whether to act before the next meeting |
On lead time, published guidance does not agree. Rework recommends sending materials 48 to 72 hours before the meeting. I'mBoard says a week. Pick one fixed send date inside that range and hold it every cycle.
Illustrative example: report against seasonal pace
The first monthly update of a quarter is where boards most often get a false alarm. Pete's observation across ORM customers is that within a quarter the third month is always the largest and the first month is always the smallest. A straight-line pace ignores that.
Illustrative numbers: a company with a $3.0M quarterly bookings target closes $450K in month one.
- Straight-line pace expects one third of the target by the end of month one: $3.0M ÷ 3 = $1.0M. Against that, $450K looks $550K behind. - Suppose the company's own history puts 15% of a quarter's bookings in month one, 30% in month two and 55% in month three (15 + 30 + 55 = 100). The seasonal pace for month one is $3.0M × 15% = $450K. - On seasonal pace, the company is exactly on plan. The board note should say so, show both lines, and save the alarm for a real gap.
The same logic runs at the weekly level. ORM breaks each quarter into a 13-week seasonality curve for every customer, because without it you cannot tell whether you are ahead or behind.
Two clocks run at once
The governance clock is slow. It handles the annual plan approval, the quarterly review, and the decisions that require a board vote. The operating clock is fast. It handles the weekly forecast call, the monthly close, and the pipeline reviews that adjust the quarter while it is still running. The revenue operating cadence guide lays out the operating side meeting by meeting.
Board reporting summarizes the operating clock. It should never be a separate build. When a different team assembles the board package from scratch using different definitions, two problems follow. The package arrives late, and its numbers disagree with the ones the revenue team has operated against all quarter.
Early beats precise
Pete puts the timing problem plainly: getting the forecast right in the last week of the quarter does not help anyone, because by then the quarter has already happened. The value sits in knowing the likely shape of the quarter on day one, early enough to do something about it.
Board reporting inherits that logic. A quarterly package that explains a miss in detail after the fact is worth less than a monthly note that flagged the risk in week three. ORM targets 95% forecast accuracy and builds its forecast to stay solid from day 1 through day 90 of the quarter, which is what makes a day-one read worth reporting instead of a placeholder the board is asked to ignore.
So the first monthly update of a quarter carries a real position: how the quarter is expected to land, what has to be created inside the quarter to get there, and where the risk sits. A daily pipeline snapshot is what lets the team show how that position moved since the last update.
When the read is bad, send it. Pete's rule for a target the team cannot support is to communicate early, and sometimes to call down the number with the board instead of carrying it to the quarterly meeting. "Bad news doesn't get better with time."
What makes a board trust the numbers each cycle
"Credibility is won in the detail," Pete says. A board trusts a forecast that passes three tests every cycle:
1. Consistent. The number on one slide shows up on the next, and the number in the monthly note matches the quarterly package, or the change is explained. The forecast rolls up cleanly from region to total business. 2. Traceable. Anyone presenting a number can drill down and explain how it came together. 3. A range. Show a low case, an on-target case and an upper bound, so directors see the risk around the expected outcome.
Do that every cycle and the board stops interrogating every line. For which metrics belong in the package, see sales metrics for a board deck; for the pipeline page itself, see the board deck pipeline slide.
Match the cadence to the decision
Report at the frequency the board can act on. A pipeline coverage figure that moves weekly is an operating metric, and pushing it into board reporting invites deal-level questions the board is not positioned to answer. A forecast reported monthly with its direction of travel gives directors what they need for hiring and cash decisions. How often the forecast itself should be rebuilt is a separate question, covered in monthly vs quarterly forecast cadence.
Off-cycle updates go out when an assumption breaks, on no schedule. The test is simple. If the board would want to know before the next scheduled update, it goes out now.
Who builds the package
Automate the assembly and keep the accountability. Pete sees board slides as a good use of AI: gathering the data, organizing it, and flagging what changed. ORM automates board slides for one of its customers today. The line he draws is that the sales leader still has to be able to speak to every number on the page.
Traceability is the catch. If a language model builds the deck and nobody can point back to the source that drove each number, checking it takes as long as building it by hand. The reporting habits that keep this cadence sustainable are covered in sales forecasting best practices, and most of them come down to producing the numbers once and reusing them everywhere.
Frequently Asked Questions
What is meant by reporting cadence?
Reporting cadence is the fixed rhythm on which a team shares results: what gets reported, to whom, and how often. For a board, it usually means a quarterly meeting package, a written monthly update in between, an annual plan, and off-cycle notes when something breaks. A good cadence matches each report to the decision its audience makes at that frequency.
How often should you report revenue to your board?
A quarterly board meeting with a written monthly update in between is a common pattern; Rework calls quarterly meetings the norm for mid-market companies and recommends monthly written updates. The quarterly meeting handles decisions and approvals. The monthly note carries the numbers, so nothing in the quarterly package is a surprise. A company in a turnaround may meet monthly, trading board time for tighter oversight.
How far in advance should the board package go out?
Published guidance ranges from 48 to 72 hours (Rework) to a full week (I'mBoard). Pick a fixed send date inside that range and hold it every cycle. The package is a pre-read, and the meeting is for the questions it raises. A fixed date also forces the close and the forecast to finish on schedule instead of running until the last hour.
Should the board see the weekly forecast?
Keep the weekly forecast out of board reporting. It is an operating instrument that moves with normal deal noise, and showing it invites directors into deal-level management. Report the forecast monthly at most, as a range with its direction of travel, and explain any change from the last number the board saw.
When do you send an off-cycle update?
When an assumption underneath the committed number breaks and waiting for the next scheduled update would leave the board uninformed about something it would want to act on. A large deal disqualifying, a pricing shift that resets deal sizes, or the loss of a top account all qualify. Ordinary forecast movement does not.
What is the 40/20/40 rule for meetings?
It is a time-management guideline from Think Productive that puts 40% of the attention for a meeting on preparation, 20% on the meeting itself and 40% on follow-through. For a board, the preparation is the pre-read and the follow-through is the action list and the next monthly update. Building the package from the numbers the team already operates on keeps the preparation share manageable.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like board reporting cadence into prescriptive action for your team.
Schedule a Demo