Freeze it. Do not publish it as truth.
- Show the last reconciled value, labelled as such.
- Name one owner and a reconcile-by date.
- Tell leaders which decisions must not use the number yet.
When two sources disagree, what do you say? A quarantine rule, a way to tell real movement from re-categorisation and a register of one source per metric.
I built this control around weekly executive reporting at a venture-backed technology company. The figures here are illustrative.
The situation
One executive dashboard said a small number of sites were live. The source database said a much larger number. Both could not be right, and leaders were about to act on the smaller one. This is the control I put around that moment. The numbers below are illustrative.
Rule one
Drag the gap between the two sources. The rule decides whether the number is published, published with a caveat, or quarantined.
Rule two
After a cleanup day or an import, week-over-week deltas mostly reflect how records are categorised, not what happened in the field. Pick a scenario to see how each delta is flagged and what I would tell the executive team.
| Metric | Last week | This week | Change | Read as |
|---|---|---|---|---|
| Servers | 100 | 180 | +80 | Structural ‡ |
| Records, all types | 200 | 300 | +100 | Structural ‡ |
| Billing flag set | 20 | 60 | +40 | Structural ‡ |
| Vendor blockers | 2 | 40 | +38 | Structural ‡ |
This is structure, not activity. A cleanup day reclassified records and created a new record type. Show every delta as suspect, name the cause and hold the headline until Finance confirms.
One definition each
A dashboard can only be trusted if each number has one source, one written definition and one owner. Illustrative register.
| Metric | Canonical source | Definition fixed in writing | Owner |
|---|---|---|---|
| Live sites | Analytics mart, built from the source records | Installed, activated, reporting data in the last 7 days | Analytics lead |
| Recurring revenue | Reconciled revenue model | Billing now, not contracted, not shipped | Finance lead |
| Open blockers | Delivery tracker | One owner, one next action, one date | Delivery lead |
| Support response | Ticketing system | Priority-tiered clock; alert noise routed separately | Support lead |
| Automation health | Workflow run log | Success rate of critical flows over 7 days | Automation lead |
The notice
Data integrity notice. Figures marked * come from systems still being cleaned. Treat them as directional until Finance confirms them. Deltas marked ‡ reflect re-categorisation, not new activity. The last time billing data was confirmed current was [date].
Four lines, written once and reused. The point is that nobody has to guess how far to trust a number.
Habits
Related tools folded into this page. Each opens in place; tap Close when done.
More in Data, Reporting & Decision Support
See all tools