When Systems Disagree
What technology helps regional senior living operators identify conflicting operational information before month-end?
Clicks …Last reviewed
Direct answer
Daily comparison of the same figure across systems, against written tolerances, with each difference routed to a named owner. Census, move-ins, care levels, hours and billed days can be checked daily; the month-end close then confirms resolved differences instead of discovering new ones.
The executive view
For a regional operator, month-end is where small daily differences become a reporting delay. Finding them on day 3 costs a phone call; finding them on day 33 costs a restated owner report. The control is simple: compare daily, assign each difference, and close it before the close.
Why this happens
Most reconciliation is scheduled around the close, so differences accumulate for a month before anyone looks. By then, the people who knew why a move-in posted late may not remember.
Regional teams also lack the corporate analysts who would otherwise catch differences, so detection has to be routine rather than heroic.
Hypothetical example: census check on day 6 of the month
EHR
76 residents
Move-in admitted on day 4
Billing
75 residents
Move-in not yet billed
Tolerance
0 residents
Census differences routed same day
Resolution
Billed day 6
Business office confirmed move-in date; recorded
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Hypothetical figures. A one-resident difference caught on day 6 is closed with a note. Caught at month-end, it would have been one of dozens of unexplained variances.
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.