Executive Reporting
How do large senior living operators standardize executive reporting during rapid portfolio acquisition?
Clicks …Last reviewed
Direct answer
Fix the executive report’s definitions first and map each acquired community to them, rather than waiting until every community is on the same software. Report acquired communities in a separate, labelled tier until their mapping is approved, so leadership can tell a performance change from a definition change.
The executive view
During fast acquisition, the executive report changes for two reasons at once: the portfolio is performing differently, and the numbers are being counted differently. Unless those are separated, leaders cannot read their own report. A short, written onboarding standard keeps the report comparable from the day a community joins.
Why this happens
Software conversions take months, and acquisitions do not wait. Acquired communities often keep their prior EHR, payroll and chart of accounts for a year or more.
Rolling those figures straight into portfolio totals mixes definitions. Occupancy, labor ratios and margin all appear to move, and some of the movement is only a change in counting.
Hypothetical example: portfolio margin in the month of acquisition
Existing 40 communities
27.2% margin
Management fee below NOI under the portfolio rule
Acquired 8, as reported
31.0% margin
Management fee not yet allocated
Acquired 8, mapped
26.4% margin
Fee allocated under the portfolio rule
Executive report
27.0% combined
Acquired tier shown separately until mapping approved
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Hypothetical figures. Adding the unmapped communities would have shown margin improving. The mapped figure shows it slightly lower, which is the decision-relevant fact.
The governance question
A defensible executive number has an approved definition, a known source authority, a recorded resolution of any disagreement, and lineage back to source. Disputed numbers should be shown as disputed, not smoothed.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- Governance checks before a number reaches an executive view.
- Visible dispute status for unresolved numbers.
- Drill-through from a KPI to its original source values.
- An audit trail of determinations behind each KPI.
- Clear labeling of calculated versus governed numbers.
SeniorCRE perspective
SeniorCRE is designed so an executive can open any governing number and see its definition, sources, disagreements and the determination that settled them. The aim is a defensible operating record, not a more attractive dashboard. 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.