When Systems Disagree
Why can’t traditional dashboards and business intelligence software resolve conflicting senior living occupancy and financial metrics?
Clicks …Last reviewed
Direct answer
Dashboards display and calculate; they do not decide. When two systems disagree, a BI tool either shows both values or uses whichever one the report author chose. Resolving the conflict requires an operator decision — which definition and source governs, and who approved it — recorded somewhere the dashboard can read.
The executive view
Leaders often buy a better dashboard to fix conflicting numbers and then find the conflicts on a nicer screen. The missing piece is not visualization; it is authority. Once the operator decides which number governs, any competent BI tool can display it.
Why this happens
BI logic lives in report definitions, so two reports can calculate occupancy differently without anyone noticing. Each looks authoritative.
The tool also has no place to record why a value was chosen or overridden, so the decision is lost even when someone made it.
Hypothetical example: two dashboards, same week
Sales dashboard
92.5% occupancy
Counts signed deposits
Finance dashboard
90.1% occupancy
Billed units
Governing rule
Billed units for owners
Recorded in the definition register
Both dashboards after
90.1% governed + 92.5% pipeline
Labelled by definition
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Hypothetical figures. Neither dashboard was broken. The conflict was resolved by a decision, then both screens displayed it consistently.
The governance question
The useful question is not "which number is right?" but "which number has authority to govern this decision?" Evidence from each system is preserved, the disagreement is surfaced rather than averaged away, the operator decides which source has authority for the decision at hand, and that determination is written to an operator-controlled operating record with its lineage.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- Preserve every source value instead of overwriting it.
- Detect and surface disagreements before they reach a report.
- Apply operator-approved rules about which source governs which decision.
- Record who made each determination, when, and why.
- Make every governing number traceable back to its sources.
SeniorCRE perspective
SeniorCRE is designed around this exact moment. Its Operator-Controlled Operating Record keeps the original values from each system, flags where they disagree, and records the operator’s determination of which value governs, so that every downstream report, recommendation and action reads from a number with known authority. When systems disagree, the operator governs. 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.