Multi-Community Operations
How can senior living operators standardize workforce, occupancy, and financial reporting across newly acquired communities?
Clicks …Last reviewed
Direct answer
Map each acquired community to the portfolio’s definitions for each domain — worked and paid hours and agency labor for workforce; units, residents and billed days for occupancy; chart of accounts and NOI treatment for finance. Report the acquired communities in a labelled transitional tier until each mapping is approved, then fold them into portfolio totals.
The executive view
Leaders need to know whether a change in the combined numbers is performance or counting. Domain-by-domain mapping and a transitional tier keep that distinction visible during the months when it matters most.
Why this happens
Workforce, occupancy and finance each have their own definitions, and acquired communities rarely match on all three at once.
Mapping one domain while leaving the others unmapped produces ratios — labor per resident day, revenue per occupied unit — that mix standards.
Hypothetical example: mapping status for an acquired community
Workforce
Mapped week 2
Agency pay codes reclassified
Occupancy
Mapped week 3
Deposit units moved to pending
Finance
Mapped week 5
42 GL accounts mapped
Portfolio totals
Included week 5
Transitional tier until all three approved
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Hypothetical timeline. Ratios were held out of portfolio totals until every input followed the same standard.
The governance question
Portfolio governance means one approved operating vocabulary applied across communities that may keep different systems. The definition and authority rules are set centrally; each community’s sources are mapped to them.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- One enterprise register of operating definitions.
- Per-community mapping from local systems to those definitions.
- Comparable KPIs that declare their definition.
- A defined onboarding path for acquired communities.
- Enforcement through visible exceptions, not mandates alone.
SeniorCRE perspective
SeniorCRE is designed so communities can keep different systems under one governance architecture: the operator sets the definitions and authority rules once, and each community’s sources are governed against them. The operator decides where replacement makes sense; governance does not require it. 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.