Skip to main contentSkip to navigation
SeniorCRE Logo

When Systems Disagree

Why do our senior living systems show different numbers?

Last reviewed

Direct answer

Your systems show different numbers because each one records a different event, on a different schedule, under a different definition. The clinical system counts residents in care, accounting counts billable days, and the CRM counts signed move-ins. Each can be correct for its own purpose and still disagree with the others. The disagreement usually comes from definitions and timing, not broken software.

Why this happens

Systems in senior housing & care were bought to run separate functions: clinical documentation, billing, payroll, sales. Each was designed around the events that matter to its own users, so each one draws its own lines around words like "resident," "occupied" and "active."

Timing makes it worse. A move-out recorded on the floor at 4 p.m. may reach billing the next morning and the CRM only when someone updates it. Without one agreed definition and a rule for which source governs, those gaps show up as conflicting numbers.

Hypothetical example: one community, one day, three numbers

  • Clinical system

    92 residents

    Counts everyone admitted and not discharged, including a resident on hospital leave.

  • Accounting

    90 residents

    Counts billable resident days; the hospital leave and a same-day move-in are excluded until the period closes.

  • CRM

    91 residents

    Counts the signed move-in but has not yet received the move-out recorded on the floor.

  1. Evidence
  2. Disagreement
  3. Authority
  4. Operator-Controlled Operating Record
  5. Intelligence
  6. Execution

Illustrative figures. Coherence before Intelligence.

None of these systems is malfunctioning. Each records a different event, on a different clock, under a different definition. The disagreement is information, not noise.

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.

See the evidence record

All When Systems Disagree questions

Request a 30-Minute AssessmentReview the Evidence Record

Stay up to date

The Senior Housing Journal, in your inbox

Perspectives on operator-governed operating information, capital and operating developments across senior housing & care, and platform updates from SeniorCRE.

By subscribing, you agree to receive the Senior Housing Journal newsletter. Unsubscribe at any time. See our Privacy Policy.