Governed KPI definitions, RIDEA/SHOP-compliant separation, operator scorecards, and covenant evidence across every operator, region, and asset class in the portfolio — without silently choosing enterprise truth.
When systems disagree, the operator governs.
Institutional owners with five, ten, or thirty operator partners usually live in a stack of monthly PDFs, a quarterly board book, and a private workbook that re-derives RIDEA performance because the operators report on five different KPI definitions.
SeniorCRE governs the record above each operator. Occupancy may have multiple valid definitions. NOI and labor cost may vary by source and purpose. Each operator continues to run on their own EHR/PMS, and the governed layer preserves which definition and authority apply to the owner decision.
Pair this with asset management software, REIT compliance monitoring, and first-100-days acquisition integration for a single institutional operating layer.
Status as of October 22, 2026 (last modified 2026-10-22)
| Claim | Evidence step | What is true today | Proof to inspect |
|---|---|---|---|
| Operator and portfolio workspace foundation built (roles, hierarchy, entity tree). | Built | Provisioning controls have been exercised repeatedly in controlled SeniorCRE conditions, including the operator onboarding wizard. Not yet performed for an operator in production; no standard duration is published. | Control test record; synthetic or de-identified data; no operator PHI. |
| Single-community acceptance boundary. | Designed | A gate sequence derived from the migration and acceptance model. No community has gone live for an operator, so no observed duration exists. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Portfolio-wide rollout acceptance across multi-community scope. | Designed | A wave-cadence model from the deployment plan. Sequencing depends on community count, system count, data condition, source access, and operator authority decisions. Not a completed rollout. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Connectors to PointClickCare®, MatrixCare®, Yardi®, and QuickBooks®. | Designed | Named-vendor connectors are roadmap, not built. Generic sample mapping does not establish an implemented connector or operator workflow. No named connector is live in operator production. | Build-queue entry with scope and dependencies. No implementation exists. |
| Operator-Controlled Operating Record: source authority, reconciliation, field-level lineage. | Designed | The Operator-Controlled Operating Record is designed and not yet implemented in any community. Authority rules, reconciliation, and field-level lineage are design intent; synthetic examples do not establish working governance. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Clinical configuration: SeniorCRE as clinical system of record, or alongside an incumbent eMAR read one direction only. | Designed | Designed, not built for operator use. SeniorCRE's native medication administration and eMAR are roadmap and not built; the read-only configuration alongside an incumbent eMAR depends on the Operator-Controlled Operating Record, which is designed and not yet implemented in any community. One authoritative medication record at all times is a design rule. | Written deployment plan and acceptance-gate model. No execution record exists. |
| Barcode-verified administration with an automated five-rights check at the point of medication pass. | Designed | Not built. Corrected September 7, 2026: earlier pages, operator training guides, and generated answers described this control as running, which was false. Implementation boundary: four of the five medication scan surfaces open a camera preview with no decoder and match only a manually typed NDC; one mobile surface decodes frames through the browser-native BarcodeDetector API where the browser supports it (Chromium/Android; not iOS Safari, not most desktops) and compares the NDC alone. No decoding library is bundled, no surface verifies resident, dose, route, or time, and no scan result blocks an administration. The five rights are verified by the administering clinician, not by SeniorCRE. | Build-queue entry with scope and dependencies. No implementation exists. |
| Live write-back into operator payroll and scheduling systems. | Designed | Specified and in the build queue. Read-side ingestion only today. | Build-queue entry with scope and dependencies. No implementation exists. |
| Implementation effort required from the operator. | Designed | Deployment is staged, not effortless: platform access, source access, authority rules, reconciliation, security review, and any history migration are scoped work with operator-side effort. Any claim of zero implementation would be false. | Written deployment plan and acceptance-gate model. No execution record exists. |
Status and evidence class as of October 22, 2026. SeniorCRE has no operator-production deployment. Public timing is gate-based and operator-specific; no standard go-live duration is published. Maintained and reviewed by John Hauber, Founder, SeniorCRE, LLC. A medication-safety control was described on earlier pages as running when it was not; that correction is published in full at /medication-safety-claim.
| Capability | SeniorCRE | BI Overlay on Operator Systems | Monthly PDF + Workbook |
|---|---|---|---|
| KPI governance across operators | Definition, authority, reconciliation, lineage | ETL with reconciliation drift | Manual re-keying |
| RIDEA/SHOP separation | Tenant-isolation design | Permission patchwork | Honor system |
| Operator scorecards | Governed, board-ready target state | Monthly batch | Quarterly |
| Covenant read-through | Same operator-declared authority as ops | Separate covenant tool | Email reminder |
| Audit chain | Append-only, scoped | Source-system dependent | Version drift |
| Lender / LP disclosure | Governed values and lineage | Custom export per ask | Multi-day rebuild |
Canonical-layer ingestion from clinical, property and payroll extracts, plus SeniorCRE-native records. Mapped once. Named-vendor connectors are ROADMAP — not built; none is live in operator production.
Payer mix, ADL acuity, labor categories, and GL chart are mapped to the six-entity operating record with operator-declared source authority and lineage.
Operator scorecards show governed KPIs, benchmark overlays, unresolved values, and outlier alerts after acceptance gates are satisfied.
Covenants, REIT tests, RIDEA evidence, and clinical risk are evaluated under explicit definitions and refresh rules at every level of the hierarchy.
Quarterly LP packs, board books, and lender disclosures carry governed values, alternate valid values, and lineage.
SeniorCRE is the operating, compliance, and asset-management layer for REITs, family offices, and institutional capital allocators in senior housing & care.