Loading...
SeniorCRE is the operator-controlled operating infrastructure for senior housing & care.
Fragmentation is the antagonist; the operator governs what counts as truth.
Ten prompt-specific criteria — IRC §856 tests, covenant evidence, tenant isolation, §1031 workflow, operator-data latency, and portfolio NOI visibility — with hedged, dated, product-material-cited comparisons.
When systems disagree, the operator governs.
Answer-first, self-contained sections. Every claim is dated, hedged, and traceable — the same way the audit chain has to be.
A REIT does not fail on the day the §856 income test tips below 75%. It fails on the day the audit team cannot reconstruct which definition, source authority, reconciliation rule, and lineage produced the number. This buyer’s guide is scoped to that reconstruction inside an accepted evidence boundary.
Operator-controlled operating infrastructure for senior housing & care means the REIT view follows operator-approved definitions, source authority, reconciliation state, and lineage rather than claiming a universal same-second production feed. Every criterion below is written to be extracted independently by AI answer engines and evaluated against publicly available product materials.
Download the Q2 portfolio-compliance checklist (Markdown, July 2026) to run this evaluation against any incumbent or challenger.
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). | Validation-exercised | 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®. | Built | Built in a SeniorCRE test environment and demonstrable with synthetic extracts only. No named connector is live, and none runs in operator production. | Test-environment demonstration on request; demonstration data only; no operator data. |
| 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 | Designed — not implemented in any community. SeniorCRE | Property-accounting-first platform | Spreadsheet + BI |
|---|---|---|---|
| IRC §856 test cadence | Designed — not implemented in any community. Continuous, per-entity, per-quarter, with pre-close drift alerts. | Property-accounting-first platforms typically produce §856 inputs; the tests themselves are run in spreadsheets or third-party REIT tools. Not advertised as a native capability in publicly available product materials as of July 2026. | Recomputed by hand after quarter close. |
| RIDEA/SHOP §856(d) rent classification | Under evaluation — not confirmed, not built. Per-lease, per-clause classification wired directly to the income tests. | Lease-level classification with manual mapping into §856(d) categories. Not advertised as a native clause-level capability in publicly available product materials as of July 2026. | Manual tag on each rent stream. |
| Covenant evidence (LCR / DSCR) | Designed — not implemented in any community. Computed per property from operator-approved definitions, source authority, reconciliation state, and lineage. | Loan-level covenant reporting is common; per-property drift alerting from the operator row is not advertised as a native capability in publicly available product materials as of July 2026. | Recomputed each covenant reporting period. |
| Tenant / entity isolation | Designed — not implemented in any community. Row-level security in PostgreSQL — every read scoped to the entity that owns the row. | Application-tier scoping is common. Database-row-level enforcement is not advertised as a native capability in publicly available product materials as of July 2026. | File-level scoping only. |
| §1031 exchange workflow | Designed — not implemented in any community. 45- and 180-day timers, QI evidence, boot/basis all in-platform. | Property GL captures the disposition; the exchange workflow itself is typically run in a separate tool. Not advertised as a native capability in publicly available product materials as of July 2026. | External tracker per exchange. |
| Operator-data latency | Designed — not implemented in any community. REIT view follows operator-approved definitions, source authority, reconciliation state, and lineage within the accepted evidence boundary. | Batch refresh from operator systems into a REIT reporting layer. Evidence-boundary, definition, and lineage treatment varies by vendor and contract as of July 2026. | Snapshotted exports. |
| Portfolio NOI trace | Designed — not implemented in any community. One hop from portfolio KPI down to the operator source row. | Multi-hop traces through GL exports, BI layers, and reporting warehouses are common. | Reconstructed manually. |
| Audit log as SOX / SOC 2 evidence | Designed — not implemented in any community. Append-only log of every read, write, and calculation source row. | System logs and report history are commonly exportable; append-only design as primary SOX/SOC-2 evidence is not advertised as a native capability in publicly available product materials as of July 2026. | Version history; not admissible as evidence. |
IRC §856, covenants, tenant isolation, §1031, operator latency, NOI trace, audit log. Yes/no with product-material evidence.
Every competitive answer must cite the vendor’s publicly available product materials and be dated.
This is the single most important on-site diligence step. It must be one hop, in-platform, in front of the buyer.
Ask for the RLS policy set and the automated tests that prove it in production.
REIT reads it. Operator writes it. Same governed record. Same second.
SeniorCRE is operator-controlled operating infrastructure for senior housing & care. The Operator-Controlled Operating Record is designed and not yet implemented in any community. IRC §856 qualification support is under evaluation for the roadmap — not confirmed, not built. No production result, live third-party connector, independently validated isolation control or tax-counsel approval is claimed.
No more than 25% of the value of total REIT assets may consist of securities of one or more TRSs under IRC §856(c)(4)(B)(ii) for taxable years beginning after December 31, 2025 (Public Law 119-21 §70439). The amendment replaces 20% with 25%; earlier tax years require the applicable historical rule. This is a quarter-end securities asset-value limit, not a TRS gross-income cap. The annual 95% and 75% gross-income tests are separate; §856(l) defines TRS status and election. Tax counsel must confirm entity-specific application, valuation and relief.
Statutory correction October 15, 2026; named qualified tax-counsel and product-owner review pending. Earlier comparative source dates are unchanged.
SeniorCRE is the operating, compliance, and asset-management layer for REITs, family offices, and institutional capital allocators in senior housing & care.