Loading...
Built for senior housing REIT Investor Relations, Asset Management, Internal Audit, and Treasury — so the number in the supplemental, the number on the earnings call, and the number in the lender pack are the same number the operator wrote.
When systems disagree, the operator governs.
Public REITs reporting on senior housing carry a disclosure problem that best-of-breed operator stacks don’t solve: every metric in MD&A traces through three vendors before it reaches the supplemental. SeniorCRE is built so the operator’s row, the asset manager’s row, and the IR team’s row are the same governed record.
| Role | Question | How it’s answered |
|---|---|---|
| Investor Relations | Can I defend portfolio metrics on the next earnings call? | Target state: census, RevPOR, NOI margin, agency labor %, and quality measures roll up to an Operator-Controlled Operating Record per property after source authority and acceptance gates are complete. The number disclosed should trace to the operator-approved record. |
| Asset Management | Can I see operator performance without the BI overlay my team hates? | Capital-layer access reads the operator’s operator-controlled operating record directly. No nightly extract, no late-arriving numbers, no re-reconciliation against a warehouse copy. Property-level tenant isolation lets joint-venture stakes see only their entities. |
| Internal Audit / SOX | Is the operator data SOX 404(b) defensible? | Immutable, append-only audit design captures reads, role grants, and exports. The Operator-Controlled Operating Record preserves source authority and reconciliation lineage to the GL. |
| Treasury / Debt Capital Markets | Can we evidence covenant compliance without a 10-day scramble? | EBITDARM coverage, DSCR, occupancy thresholds, and PPD labor are designed to pull from the governed record the operator accepts. Evidence-pack timing is acceptance-gated, not claimed as an operator-production outcome. |
| ESG / Sustainability | Where does workforce, quality, and resident-outcomes data come from? | ESG metrics are designed to aggregate from accepted operating-record evidence — not a hand-rolled annual survey — and export with provenance to your sustainability report. |
| Strategy / M&A | Can we run sell-side or buy-side diligence on this operator without a 6-week scramble? | The Operating Record is designed to produce audit-grade diligence evidence under NDA after source authority and access rules are approved. |
Most procurement teams start here. The SeniorCRE mutual NDA is a standard two-year, Texas-governed instrument that covers the Trust-by-Design package (SIG Lite, CAIQ, architecture diagrams, control narrative, incident response plan, and pen-test scope). Reasonable redlines are returned by counsel within one business day.
SeniorCRE Mutual Non-Disclosure Agreement
PDF · 4 pages · Texas governing law · 2-year term
Return signed copy to support@seniorcre.com
Prefer your paper? Email your standard mutual NDA to support@seniorcre.com and we’ll return redlines within one business day.
For IR, Asset Management, Internal Audit, and Treasury teams who have already reviewed the Trust Center package — send a direct line to support@seniorcre.com and we will respond within one business day.
Status as of September 29, 2026 (last modified 2026-09-29)
| Claim | Evidence step | What is true today | Proof to inspect |
|---|---|---|---|
| Operator and portfolio workspace foundation built (roles, hierarchy, entity tree). | Validated | 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. | Architecture 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. | Architecture 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®. | Validated | Ingestion and normalization exercised against synthetic and de-identified extracts in controlled SeniorCRE conditions. No third-party integration is live in operator production. | Control test record; synthetic or de-identified data; no operator PHI. |
| Operator-Controlled Operating Record: source authority, reconciliation, field-level lineage. | Architecture 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. | Validated | Both configurations are built and exercised in controlled SeniorCRE conditions, with one authoritative MAR at all times. No PHI workload runs in operator production. | Control test record; synthetic or de-identified data; no operator PHI. |
| Barcode-verified administration with an automated five-rights check at the point of medication pass. | Architecture 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. | Architecture 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. | Architecture 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 September 29, 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 | Operator EHR + warehouse + BI | Manual REIT reporting |
|---|---|---|---|
| Source of operator NOI | Operator-controlled operating record | Stitched extract | Hand-keyed |
| Same-store metric latency | Acceptance-gated | T+1 to T+5 | T+10 to T+30 |
| Audit log on every read | Target-state audit evidence | Per-product | None |
| Covenant evidence assembly | Acceptance-gated | Days | 10+ days |
| Property-level capital multi-layer tenant isolation | Designed in data model | Middleware | None |
| SOX 404(b) walkthrough source | Governed evidence | 3–6 systems | Out of scope |
| ESG provenance to source row | Target state | Varies | Survey-based |
| Buy-side / sell-side diligence export | Acceptance-gated export | Multi-vendor scramble | Multi-week |
60-minute briefing for the IR / Asset-Management / Internal Audit triad.
Vendor-risk delivery within 2 business days. SIG Lite, CAIQ, BAA, sub-processor list.
90-minute session with engineering: operator-controlled operating record, audit log, tenant isolation, capital-layer access.
Explicit terms, source-system owners, definitions, measures, exit conditions, dependencies, and timing.
Run against approved historical records before any production acceptance decision.
Rollout remains gated by source access, reconciliation, security review, and operator acceptance.
SeniorCRE is the operating, compliance, and asset-management layer for REITs, family offices, and institutional capital allocators in senior housing & care.