Board reporting cadence is how often revenue reporting reaches the board and how far ahead of each meeting it lands. Most venture-backed SaaS companies settle on a quarterly meeting with a written monthly update between sessions. The frequency matters less than the timing. Reporting that arrives after the period it describes has closed is a record, not a management tool.
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 the quarter is still running.
Board reporting summarizes the operating clock. It should never be a separate build. When the board package gets assembled from scratch by a different team using different definitions, two problems follow. The package arrives late, and its numbers disagree with the ones the revenue team has been operating against all quarter.
Early beats precise
ORM's Pete Furseth 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's forecast holds accuracy from day 1 through day 90 of the quarter, which makes the day-one read reportable rather than a placeholder the board is asked to ignore.
That changes what the first monthly update of a quarter should contain. Instead of a token pipeline snapshot, it carries a real position on how the quarter is expected to land, what has to be created inside the quarter to get there, and where the risk sits.
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.
Off-cycle updates get sent when an assumption breaks rather than on a schedule. The test is simple. If the board would want to know before the next scheduled update, it goes out now. 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
How often should you report revenue to your board?
Most venture-backed SaaS companies hold a quarterly board meeting with a written monthly update in between. The quarterly meeting handles decisions and approvals. The monthly note handles the numbers, so nothing in the quarterly package is a surprise. Companies at earlier stages or in a turnaround often move to monthly meetings, which trades board time for tighter oversight.
How far in advance should the board package go out?
Several days ahead, on a fixed schedule. The package is a pre-read, and the meeting is for the questions it raises. Material that arrives the night before guarantees the session gets spent narrating slides. A fixed send date also forces the internal close and forecast cycle to finish on schedule instead of running until the last hour.
Should the board see the weekly forecast?
No. The weekly forecast is an operating instrument that moves with normal deal noise, and exposing it invites the board into deal-level management. Report the forecast at the cadence the board acts on, which is monthly at most, and summarize the direction of travel rather than the weekly swings.
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.
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