Multi-Operator KPI Governance for Senior Housing Portfolios
Every operator in a portfolio can report accurately and the portfolio can still disagree with itself. One counts a unit occupied at move-in, another at first billed night. One holds turnover cost above the NOI line, another below it. Rolling those up produces a number that is arithmetically correct and institutionally unusable.
On this page
Across a multi-operator portfolio, most disputes are definitional rather than arithmetic. Governance is what makes the numbers comparable without forcing every operator onto one system.
The fix is not a new dashboard. It is a definition register with named owners, declared source authority per metric per operator, reconciliation performed once under governed rules, and lineage kept attached so a prior period reproduces as published. Operators keep the systems they run today; governance sits above them. Where an operator chooses it, SeniorCRE can also be deployed as the system of record itself.
Key points
- Write one definition per KPI, name its owner, version it, and date it. A metric without an owner cannot be governed.
- For each metric and each operator, state which system governs the value before any disagreement occurs.
- Apply the reconciliation rule, record the approver, and let downstream reports inherit the result instead of re-deriving it.
- Every published KPI traces in one hop to the operating rows and definition version behind it, so a prior period reproduces as published.
- Because each operator applies its own definition, cut-off, and source system, and the roll-up inherits all of them at once. Until definition authority and source authority are declared per metric, the portfolio number is an average of several incompatible measurements.
- No. Deployment is the operator’s choice. Operators can keep the systems they run today while SeniorCRE governs what those systems produce, or deploy SeniorCRE itself as the system of record — including its own EHR and eMAR, scheduling, census, and bed board. Neither road is implied to be the only one.
- The difference between two systems is resolved under a governed rule, with the approver recorded, and every downstream report inherits that resolution. The alternative — reconciling inside each report — is how one figure ends up with several defensible versions.
- Isolation is enforced at the database row level with a written control description available for security review, because a portfolio owner inherits each operator’s confidentiality obligations. Isolation implemented only in application code fails that review.
Frequently asked questions
- Why do multi-operator portfolios report conflicting KPIs?
- Because each operator applies its own definition, cut-off, and source system, and the roll-up inherits all of them at once. Until definition authority and source authority are declared per metric, the portfolio number is an average of several incompatible measurements.
- Do operators have to replace their systems for this to work?
- No. Deployment is the operator’s choice. Operators can keep the systems they run today while SeniorCRE governs what those systems produce, or deploy SeniorCRE itself as the system of record — including its own EHR and eMAR, scheduling, census, and bed board. Neither road is implied to be the only one.
- What does reconciling once actually mean?
- The difference between two systems is resolved under a governed rule, with the approver recorded, and every downstream report inherits that resolution. The alternative — reconciling inside each report — is how one figure ends up with several defensible versions.
- How is one operator’s data kept away from another’s?
- Isolation is enforced at the database row level with a written control description available for security review, because a portfolio owner inherits each operator’s confidentiality obligations. Isolation implemented only in application code fails that review.
https://seniorcre.com/reit-compliance-monitoring/multi-operator-kpi-governance