Your systems disagree. Who decides which number governs?

What depends on the number

The decision doesn't wait for your systems to agree.

1. Occupancy

   Which census definition governs the board, lender, operating, and forecasting view?

2. Labor

   Which hours, agency costs, overtime, and staffing assumptions are authoritative?

3. Care

   Which operating information should leadership rely upon when clinical and operational context intersects?

4. Compliance

   Can leadership reconstruct what was known, what governed, who decided, and why?

5. NOI

   Are capital and operating decisions being made from numbers whose definitions and lineage are understood?

II/The scoreboard is NOI

Nobody loses an assignment over an inconsistent definition. They lose it over NOI.

So the question is not whether two screens disagree. It is what the disagreement is costing you while it stands. Ungoverned numbers leak money in forms that never show up as a variance line, because each system did exactly the job it was given.

Every leak below happens between systems that are individually correct. That is why no single system catches it.

1. Leak 01

   Care delivered at one level, billed at another

   A resident is reassessed to a higher acuity in the clinical system. The billing system keeps charging the prior level until someone notices and rebills.

   Why nobody catches it: Clinical did its job and billing did its job. The gap sits between them, so neither system reports an exception.

   Illustrative: one resident moved up a level at a $600 monthly differential, caught three months late, is roughly $1,800 of revenue that is never billed. Assumption-based, not a measured outcome.

2. Leak 02

   Deposits counted as occupancy, care hours staffed against empty beds

   The CRM treats a signed deposit as occupied. The executive director staffs from the CRM. The resident moves in two weeks later.

   Why nobody catches it: The CRM is right about the deposit and the census system is right about the bed. Nothing reconciles the two before the schedule is published.

   Illustrative: care hours scheduled against beds nobody is in are paid in full and produce no revenue. The exposure scales with how many move-ins are in flight in any week.

3. Leak 03

   Three points of occupancy treated as a rounding error

   Two definitions of occupancy sit three points apart, and the pack that gets used depends on who assembled it.

   Why nobody catches it: Both figures are defensible, so the variance is argued rather than resolved, and it survives from month to month.

   Illustrative: at a 100-unit assisted living community at $5,000 per month, three points is three units — roughly $180,000 of annual revenue. Arithmetic on stated assumptions, not a SeniorCRE result.

Govern the systems you have. Or choose SeniorCRE as the system.

Two roads, one principle: the operator decides what governs. Choose the starting scope that fits your community — keeping a working stack or establishing a first system of record. Neither choice commits you to the other.

Either way, the operator determines what is authoritative. Govern first. Replace only by choice. Two forms of operator authority: data authority — who decides what is true? — and architecture authority — who decides what systems remain or are replaced? Both answers are the operator.