Loading...
Most senior housing & care software holds together at one to three communities. The real pain begins at ten, twenty, regional expansion, and multi-state operations — when the operating model, not the portfolio, is what actually breaks.
When systems disagree, the operator governs.
Institutional trust markers
Multi-community operators, REITs, private equity, lenders, and multi-state portfolios evaluate the same nine markers before they sign. Each one is documented, enforced in the platform, and reviewable in the Trust-by-Design procurement package.
HIPAA-safeguarded controls; no SOC 2 certification or report claimed. No completed independent penetration-test report claimed.
HIPAA-safeguarded controls today: encryption at rest and in transit, BAA execution, PHI segregation, and signed-URL access to PHI buckets.
Operator-controlled definitions, source authority, reconciliation, and lineage across clinical, financial, workforce, compliance, and capital surfaces. Multi-tenant with database-enforced isolation.
A documented ingestion path for operator-supplied clinical, property, and accounting exports. Named-vendor connectors are ROADMAP; no third-party integration is live in operator production today. AI reads only the fields the operator declared readable.
SOC 2 in progress (underlying AWS infrastructure maintains its own SOC 2 reports), MFA required, session timeout, concurrent-session limits, continuous automated vulnerability scanning.
Immutable, append-only logs with UTC-millisecond timestamps, full user/session context, and 7-year retention.
33-role RBAC hierarchy. Property-level tenant and role gates enforced at the API layer (Fastify + tRPC on AWS) with WorkOS-authenticated sessions and defense-in-depth checks in PostgreSQL.
Holding Co → Operator → Region → Property → Unit hierarchy. Portfolio rollups computed from the Operator-Controlled Operating Record at request time. Designed for multi-state, multi-payer, multi-entity ownership.
Full detail on each marker, evidence inventory, and the Trust-by-Design procurement package live on the Trust Center.
Grounded on the SeniorCRE platform knowledge base. Ask anything about portfolio operations visibility, labor, clinical, financial close, or stabilizing newly acquired communities.
Grounded on the SeniorCRE platform knowledge base. Not clinical advice.
Try one of these, or ask your own question:
Buyers usually evaluate platforms at the size they are today. Then they grow into the problem the platform was never designed to solve. By the time the cracks are obvious, the cost of replacement is highest and the team has the least bandwidth to absorb it.
SeniorCRE is built for what happens after the third community — when the operating model is what determines whether scale creates operational alpha or operational drag.
Where the operating model actually fractures as the portfolio grows:
Founder-led operations
Spreadsheets work. Workflows live in someone's head. The ED and CEO are usually in the same room.
First cracks appear
Reporting starts slipping. Regional roles emerge. Decisions begin waiting on month-end.
The operating model breaks
Spreadsheets explode. Standards drift across communities. Ownership starts asking questions the team can't answer in real time.
Fragmentation tax
Every region runs slightly differently. Survey risk concentrates in the weakest community. Investor reporting is a quarterly heroics exercise.
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. | Architecture 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. | 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.
| Failure mode at scale | SeniorCRE portfolio operations | Single-building software | Spreadsheets + point tools |
|---|---|---|---|
| Numbers reconcile across communities | One Operator-Controlled Operating Record | Per-community only | Manual reconciliation, version drift |
| Regional real-time visibility | Built across staffing, census, compliance, labor, performance | Not regional-aware | Reports emailed weekly |
| Workflow standardization | Portfolio-wide definitions and KPIs | Each community configures independently | "How we do it here" varies by site |
| Compliance posture | Continuous, audit-grade documentation | Community-by-community | Survey-cycle scrambles |
| Ownership & investor reporting | Portfolio operations, built | Not designed for ownership view | Quarterly heroics from twelve sources |
Identify where the current stack already breaks — reporting, staffing, compliance, ownership reporting.
Govern resident, ledger, shift, unit, and entity evidence with source authority and lineage — without a big-bang cutover.
Mirror workflows, validate data, and accept each community boundary without pausing operations on day one.
Regional and ownership views use governed staffing, census, compliance, labor, and performance context across each accepted community boundary.
SeniorCRE is the operating, compliance, and asset-management layer for REITs, family offices, and institutional capital allocators in senior housing & care.
Start at Why Operators Switch — this page adds: The breakpoint: where reporting quietly stops reconciling.
The seat: census, labor, care, compliance, revenue, and NOI under operator authority.
The moment the existing stack stops answering the question.
What scaling looks like when the record governs.