Multi-Community Operations
How can senior living operators double their portfolio size without doubling corporate overhead?
Last reviewed
Direct answer
Overhead grows with the work each community adds at corporate: reports to assemble, numbers to reconcile, exceptions to chase. Reduce that per-community work before growing. Set portfolio-wide definitions, name the source of each key figure, build rollups into the data rather than spreadsheets, and track corporate hours per community so the effect is measured, not assumed.
Why this happens
If every new community adds its own reporting quirks, corporate staff grow in step with the portfolio. The cost is not the software; it is the repeated hand reconciliation.
Communities managed per corporate employee is a useful measure only with a dated baseline and a consistent definition of corporate roles. Any claimed improvement should show both.
Hypothetical example: three communities, one kpi
Community A
Occupancy 94%
Residents ÷ licensed beds.
Community B
Occupancy 89%
Occupied units ÷ units in service.
Community C
Occupancy 91%
Billable days ÷ available days.
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Ranking these communities compares definitions, not performance.
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.