Executive Reporting
How should disputed numbers be displayed to executives?
Last reviewed
Direct answer
Show disputed numbers as disputed: the competing values, their sources, the reason for the difference, who owns the resolution and when it is due. Do not average them, and do not quietly pick one. Executives can make good decisions with known uncertainty. They make poor ones with false precision.
Why this happens
Hiding disputes moves the risk upward without telling the people who carry it.
Showing disputes also speeds up resolution, because owners know leadership can see them.
Example: board packet occupancy
Executive dashboard
91.0%
Built from a nightly data warehouse load.
Regional report
90.2%
Built from accounting after month-end adjustments.
Community report
92.1%
Built from the clinical census.
- Which number governs?
- Operator Authority
- Governing Record
- SeniorCRE Intelligence
- Execution
Illustrative figures. Governance first. Intelligence second. Execution last.
Leadership sees one number. The question is whether anyone can show which definition, sources and decisions stand behind it.
The governance question
A defensible executive number has an approved definition, a known source authority, a recorded resolution of any disagreement, and lineage back to source. Disputed numbers should be shown as disputed, not smoothed.
Evidence → Disagreement → Authority → Governing Record
What good operating infrastructure should do
- Governance checks before a number reaches an executive view.
- Visible dispute status for unresolved numbers.
- Drill-through from a KPI to its original source values.
- An audit trail of determinations behind each KPI.
- Clear labeling of calculated versus governed numbers.
SeniorCRE perspective
SeniorCRE is designed so an executive can open any governing number and see its definition, sources, disagreements and the determination that settled them. The aim is a defensible operating record, not a more attractive dashboard. Status: the Governed Operating Record is designed and not yet implemented in any community. What has been built, validated and deployed is published on the evidence page, and nothing here should be read as a production result.