Multi-Community Operations
How can regional operators establish one operating vocabulary?
Last reviewed
Direct answer
Start with the ten to twenty terms leadership argues about most, such as census, occupancy, available unit, active employee and hours per resident day. Define each in writing with an owner, publish the definitions, map every report to them, and retire local terms that conflict. Bring in new terms only when a decision needs them.
Why this happens
A long glossary nobody uses is worse than a short one everyone uses.
Shared vocabulary shortens leadership meetings, because time moves from definitions to decisions.
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.
- Which number governs?
- Operator Authority
- Governing Record
- SeniorCRE Intelligence
- Execution
Illustrative figures. Governance first. Intelligence second. Execution last.
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 → Governing Record
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 Governed Operating Record is designed and not yet implemented in any community. What has been built, validated and deployed is published on the evidence page, and nothing here should be read as a production result.