Executive Reporting
Why do executive dashboards disagree with departmental reports?
Last reviewed
Direct answer
Executive dashboards and departmental reports usually draw from different systems or data warehouse loads, apply different definitions and refresh at different times. Departments read their own systems directly, while executive views read combined data. Unless definitions and lineage are governed, the two will drift apart and both will look authoritative.
Why this happens
Every handoff between systems adds a chance for definitions or filters to change.
Showing the definition and refresh time on every view makes most of these disagreements easy to explain.
Hypothetical 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.
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
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 → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
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 Operator-Controlled Operating Record is designed and not yet implemented in any community. Current capability states and production-entry gates are published in the Evidence Record at the Trust Center; nothing here should be read as a production result.
