Census & Occupancy
How can senior living executives resolve disagreements between census
Clicks …Last reviewed
Direct answer
When census disagrees between the EHR, billing, the CRM and payroll, resolve it by purpose, not by picking a system. Write which census governs each use — clinical, staffing, billing and owner reporting — compare the systems resident by resident each day, classify each difference as timing, definition or error, and have the accountable executive approve the governing figure while every source value stays visible.
The executive view
Census disagreements reach executives as competing reports, but they are usually settled one level down by a written rule. The executive role is to decide who owns each census purpose and to insist that every difference is explained, assigned and closed before month-end rather than argued about after it.
Why this happens
Each system counts census for its own job: the EHR counts residents physically present, billing counts billable days including bed holds, the CRM counts signed move-ins, and payroll staffing models often use last week’s figure.
Without a rule per purpose, each department reports the census that suits its own work, and executive meetings spend time reconciling instead of deciding.
Hypothetical example: census for one community on the same day
EHR
96 residents
Two on hospital leave excluded
Billing
98 residents
Bed holds billed
CRM
100 residents
Two signed move-ins not yet arrived
Governing census
96 staffing · 98 revenue
Rules approved by the COO and CFO; CRM shown as pipeline
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Hypothetical figures. Every system was right for its own purpose. The disagreement was resolved by deciding which census answers which question and recording who approved it.
The governance question
Before reconciling census, an operator has to decide which census governs which decision: staffing, billing, investor reporting and sales availability can legitimately use different definitions. The governance step is to approve those definitions, assign source authority for each, and record the determination when sources disagree.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- Hold an approved, written definition for each census and occupancy measure.
- Compare census across systems daily, not only at month-end.
- Show the specific residents or units behind a census difference.
- Record which source governs each census measure and why.
- Keep the original system values alongside the governing number.
SeniorCRE perspective
In SeniorCRE’s architecture, census is a governed measure: each definition is approved by the operator, each source’s value is preserved, and daily differences are surfaced with the residents behind them before month-end. The operator’s determination, not a model, sets the census that staffing, finance and reporting read. 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.