Article
Board Pack Numbers Keep Changing: What to Check First
Board pack numbers can change for good reasons.
Late invoices arrive. Credits are processed. Sales stages move. Finance applies month-end adjustments. A data refresh catches records that were missing yesterday.
The problem is not that numbers ever change.
The problem is when nobody can quickly explain why they changed, which version is final, and whether the decision should wait.
That is a reporting trust problem.
Why board pack numbers change
Board packs often sit at the collision point between operational reporting and formal reporting.
The operating team may want the latest view. Finance may want the approved view. Sales may want the forecast view. The board may need the decision-ready view.
Those views are not always the same.
If the pack does not explain which view is being used, a normal timing difference can look like a mistake.
That is why board pack changes often reveal a semantic gap: the same metric label is being used for different meanings or moments in the business process.
The first question is not “what changed?”
The first question is:
Was the previous number wrong, provisional, or just built for a different purpose?
Those are different situations.
If the previous number was wrong, the business needs a correction and a source-path check.
If the previous number was provisional, the business needs visible status and caveats.
If the previous number was built for a different purpose, the business needs clearer definitions and labels.
Treating all three as “data quality issues” makes the conversation too vague.
Check the metric definition
Start with the label in the board pack.
If it says revenue, does it mean booked revenue, invoiced revenue, recognised revenue, net revenue, recurring revenue, cash collected, or forecast revenue?
If it says customers, does it mean contracted customers, active customers, paying customers, accounts, users, or logos?
If it says pipeline, does it include all opportunities, weighted opportunities, qualified opportunities, renewals, expansions, or expected value?
A board pack does not need to include a long definition under every number. But priority metrics need enough context that readers know what they are looking at.
For disputed numbers, a lightweight KPI definition can prevent the same debate from returning every month.
Check timing and approval status
Many changing board pack numbers are timing issues.
The pack may be pulled before finance close. The dashboard may refresh daily. The spreadsheet may include a late manual adjustment. The warehouse may lag behind the source system.
None of that is automatically wrong.
But the status should be visible.
Useful labels include:
- Draft
- Provisional
- Finance reviewed
- Board final
- Updated after close
- Excludes late adjustments
The business does not need every technical detail. It needs to know whether the number is safe for the decision.
Check ownership
Changing board pack numbers become more damaging when nobody owns the explanation.
There should be a clear business owner for the meaning and a clear technical owner for the reporting path.
Without that, changes create a scramble. People ask finance, sales, operations, data, and whoever built the original spreadsheet. The answer becomes a coordination problem rather than a reporting process.
A reporting contract can help when a metric keeps returning to leadership conversations. It makes the definition, owner, source, caveats, and safe-use context explicit.
Check whether the change is tolerable
Not every difference needs to be eliminated.
A forecast number and a finance-close number may be allowed to differ. A sales pipeline view and a board-ready revenue view may be allowed to differ. A live dashboard and a monthly pack may be allowed to differ.
The important thing is whether the difference is agreed and explainable.
That is tolerable divergence: a difference that is visible, understood, and safe in context.
If the difference is not visible, people experience it as broken reporting even when both numbers are defensible.
What to do next
Choose one board pack number that changed recently and run a first-pass check.
Ask whether it has a clear definition, named owner, visible source path, visible caveats, controlled duplicate versions, and enough context for automation or summaries.
The Reporting Trust Scorecard gives you a simple way to do that without turning the board pack into a full implementation project.
If the issue is part of a wider reporting pattern, read why your business numbers don’t match next. If the hidden cost is already showing up in repeated meetings and manual reconciliation, read the Invisible Data Tax.