Loading...
SeniorCRE deploys as an Operator-Controlled Operating Record above the systems you already run. You keep your EHR, your GL, and your payroll. What changes is who controls the reconciled record above them. Sequencing below is a design target from validation-environment runs — not customer evidence: there is no operator-production deployment today, first deployment dates remain to be determined.
Short answer
Deployment starts with a tenant foundation and a written data-mapping dictionary, then moves community-by-community in waves with a parallel run at every wave. Nothing is switched off in your existing stack; the operating record is reconciled against it until your finance and clinical leadership sign the variance report. Progress is measured by milestone state — Authority Workshop Complete, First Source Connected, First Governed Metric, First Community Production, First Governed Board Record, Portfolio Wave Complete — and no day counts are published. Sequencing is bounded, in practice, by decisions only the operator can make.
Status definition. BUILT (the label formerly printed as LIVE; renamed September 7, 2026 because the word worked against its own definition) means the capability exists in a controlled SeniorCRE environment. It does NOT mean an operator is running it in production. As of July 30, 2026 there is no completed operator-production deployment and no operator production deployment, and "live with operators today" is a prohibited claim. A subset of built surfaces remains built only and is being disabled or labeled accordingly; BUILT is therefore not a representation of operator-production readiness.
Two coordinated workstreams
Governance and technical work advance in parallel. A state closes when its written gate closes — never on a calendar date.
Who is permitted to declare a number true.
BASELINE
Record the systems in use, the entity hierarchy, and where the same number is produced more than once.
NAME
Name the authority for each contested metric: who defines it, who approves it, who may override it.
RECONCILE
Run the operating record against the source systems and adjudicate every variance in writing.
GOVERN
Move the reconciled metric under the authority matrix, with lineage and approval retained.
INSTITUTIONALIZE
Make the governed metric the version used in the board record and the operating meeting.
SCALE
Repeat the sequence by wave across the remaining portfolio.
How the data arrives, and how it is proven.
DISCOVER
Inventory sources, extract paths, access owners, and contractual limits.
CONNECT
Establish the read path — connector or scheduled extract, labeled as which.
MAP
Write the data dictionary: field, source of record, transformation, owner.
VALIDATE
Compare against source output until the variance report is signed.
PRODUCTIONIZE
Promote only after the production readiness gate states are satisfied for that scope.
Milestone states
Authority Workshop Complete
The authority matrix is signed: every contested metric has a named definer, approver, and override path.
First Source Connected
One source system delivers data on a repeatable schedule with the read path documented.
First Governed Metric
One metric is reconciled to source, variance-adjudicated in writing, and published with lineage.
First Community Production
One community operates on the governed record under the readiness gate, with rollback defined.
First Governed Board Record
A board-facing package is produced from the governed record, with lineage attached to each figure.
Portfolio Wave Complete
A defined wave of communities is reconciled, governed, and signed by operator leadership.
Milestones advance on written gates, not on dates. No day counts are published: timing is a design target, not customer evidence.
States, not claims
Each domain below is a state the operator can inspect. PENDING is the default; a domain moves to PASS only when an evidenced record exists for the scope in question.
States as of 2026-08-29. PENDING is the default until an evidenced record exists.
Infrastructure
Tenant isolation, environment separation, and capacity plan documented.
Security
Access model, encryption posture, and logging reviewed for the deployment scope.
Incident response
Named on-call path, severity ladder, and notification commitments in writing.
BC/DR
Backup, restore, and continuity procedures exercised and recorded.
BAA and subprocessors
Executed BAA and a current subprocessor list provided to the operator.
Contract
Order form, term, and support model executed for the deployment scope.
Data
Data dictionary, retention terms, and export/portability path defined.
Governance
Authority matrix signed and override logging enabled.
Clinical
Clinical configuration elected, one authoritative MAR named, and clinical sign-off seat filled.
Evidence
Variance report and lineage artifacts produced for the scope being promoted.
Support
Support hours, escalation contacts, and response commitments documented.
Illustrative example
Infrastructure
Tenant provisioned, environments separated.
Security
Access model and logging reviewed.
BAA
Executed and countersigned.
Authority Matrix
Contested metrics assigned an authority.
Connector A
Read path established and documented.
Connector B
Read path established and documented.
Baseline
System and metric inventory recorded.
First governed metric
Reconciled, adjudicated, published with lineage.
Production authorization
Operator signs the readiness gate for scope.
Illustrative example. The states above are a display of how the readiness gate is presented during a deployment; they are not a status report for any operator or environment.
Design targets, evidence class D
Waves overlap by design. Nothing advances on a status deck — each wave closes on a written gate, and the existing stack keeps running until your leadership signs.
Tenant, entity hierarchy, roles, and the written data-mapping dictionary.
Operator owns
SeniorCRE performs
Parallel run
None yet — no operating decisions are taken from SeniorCRE in this wave.
Exit gate
Finance and clinical leadership sign the mapping dictionary. Unsigned fields are excluded, not guessed.
One community. Census, labor, and revenue reconciled end to end.
Operator owns
SeniorCRE performs
Parallel run
Full parallel run: the existing stack remains the operating infrastructure of record for decisions.
Exit gate
Variance report is accepted in writing, or the wave does not advance. Unexplained variance blocks Wave 2.
A contiguous cohort of communities sharing one payer and staffing model.
Operator owns
SeniorCRE performs
Parallel run
Parallel run continues through two full close cycles before any legacy report is retired.
Exit gate
Two consecutive closes reconcile within the operator-agreed tolerance, with a written owner on every exception.
Remaining communities, board-level reporting, and audit posture.
Operator owns
SeniorCRE performs
Parallel run
Parallel run ends only where the operator signs a specific report as reconciled; everything else stays dual-run.
Exit gate
Signed governance charter naming the operator as controller of the reconciled record and its exports.
Design targets, evidence class D
Design target — not customer evidence. No day counts are published for SeniorCRE deployment. The Operator-Reported column is what operators told us their legacy rollouts actually took.
| Portfolio band | Communities | SeniorCRE design sequence | Operator-reported legacy | Dominant driver |
|---|---|---|---|---|
| Single community / pilot | 1 | Provisioning, then Authority Workshop → First Governed Metric in a single wave | 2–4 months | Source-system export latency and the incumbent’s extract fee schedule |
| Small portfolio | 2–9 | 2 waves to Portfolio Wave Complete | 4–9 months | Chart-of-accounts normalization across entities acquired at different times |
| Mid portfolio | 10–24 | 3–5 waves to Portfolio Wave Complete | 6–12 months | Number of distinct payroll and GL instances, not number of buildings |
| Large portfolio | 25–49 | 5–8 waves to Portfolio Wave Complete | 9–18 months | State-specific clinical and Medicaid billing variation across the footprint |
| Enterprise / multi-state | 50+ | Wave cadence set by regional clinical leadership capacity | 12–24 months | Change-management bandwidth of regional directors, which is a fixed human constraint |
Gate criteria — not customer evidence. SeniorCRE columns are evidence class D and publish no day counts: modeled from SeniorCRE validation-environment runs, not from operator production. SeniorCRE has no completed operator-production deployment as of September 17, 2026; Founding Operator deployment dates are not yet scheduled and remain to be determined. Operator-Reported columns are evidence class C: unaudited ranges from discovery interviews, useful for scoping questions and not for underwriting.
Diligence artifacts
Verifiable today
The resident, property, encounter, employee, and ledger entities are documented with field-level source mappings for the common incumbent systems. Reviewable under NDA by your CIO or a third-party advisor before you sign anything.
Verifiable on request
We will run a de-identified extract from your incumbent through the migration path and return a reconciliation report: record counts in, record counts out, rejected rows, and the reason for each rejection. You keep the report whether or not you buy.
Verifiable today
The parallel-run design — what runs in both systems, for how long, and which variances block sign-off — is a written artifact, not a promise made on a call.
Verifiable today
Contractual export of your operating record in a standard format at any time, including after termination. Ask every vendor on your shortlist for the same clause and compare the answers.
Not yet verifiable
There is none. SeniorCRE has no operator-production deployment as of September 17, 2026. First deployment dates remain to be determined. If a named production reference is a hard gate for your committee, we are not yet a fit and we will say so early rather than late.
Not yet verifiable
Integration surfaces are built. No integration is running in an operator production environment today.
Use this against every vendor on your shortlist, including us. Each step names an owner and a gate that has to close before the next wave starts.
Catalogue each clinical, billing, payroll, scheduling, GL, and reporting system in scope, with its contract end date, its export format, and the fee to extract full history.
Exit gate. A written inventory in which every system has a named owner and a documented export cost. Any unknown extract fee is an open financial risk, not a detail.
Rebuild HoldCo, OpCo, PropCo, property, and unit relationships, then reconcile against state licensure records rather than against the incumbent system alone.
Exit gate. Hierarchy signed off by finance and compliance, with licensure discrepancies logged.
Resolve account collisions between entities acquired at different times, and confirm the crosswalk preserves year-over-year comparability.
Exit gate. Finance leadership signs the crosswalk. In the rehearsal above this step, not the technology, caused the largest slip.
Org hierarchy, role-based access control, tenant isolation, audit logging, SSO, and module enablement.
Exit gate. A provisioned validation tenant you watched on a screen share, with acceptance criteria written down.
Push a de-identified extract through the migration path and produce a reconciliation report: records in, records out, rejected rows, reason per rejection.
Exit gate. You hold the variance report, whether or not you buy. A vendor unwilling to produce one before contract is asking you to underwrite their mapping.
Specify what runs in both systems, the acceptance boundary, and which clinical, billing, and labor variances are disqualifying.
Exit gate. A written parallel-review test plan naming a variance tolerance per domain. "We will validate carefully" is not a tolerance.
Validate residents, charts, medication-administration history, care plans, leases, AR/AP, and GL balances for one community under the parallel-review plan; move writes only where the operator elects migration.
Exit gate. Property-level sign-off from the clinical and business-office leads at that community.
Confirm assessment submission, staffing-data submission, and billing classification continuity for every community in scope, and name who absorbs remediation if a regulatory item set changes during the engagement.
Exit gate. A written clause naming who pays for regulatory change, plus a submission calendar mapped against the accepted sequence.
Sequence each wave only after the prior wave clears the same variance tolerance as the acceptance boundary; terminate a legacy contract only where the operator separately chooses replacement.
Exit gate. A wave log with contracted gates, accepted gates, and variance for each community. The gap between promised and accepted gates is the only implementation benchmark that survives scrutiny.
Produce the same metric in clinical, labor, and financial views simultaneously and reconcile any variance to a documented convention.
Exit gate. Matching values, or a written convention explaining the difference. Nothing in between.
Written support across clinical, financial, and workforce workflows, then runbook handoff to operator IT with an escalation path per domain.
Exit gate. A signed runbook handoff, not a training deck.
Execute an export of the operating record in the contracted format and document the result.
Exit gate. A completed export in your possession during the agreed review period. An untested exit clause is a promise, not a control.
Buyer-side instrument
Ten weighted questions drawn from where senior housing deployments actually slip. Score each vendor on your shortlist and export the sheet for your committee packet.
Weighted score
0.0 / 25
Not scored yet
Answer the ten questions below for any vendor. Weights reflect deployment risk, not vendor preference.
1. Will the vendor publish a written data-mapping dictionary before any load?
Unwritten mapping is where migration schedules and variance disputes go to die.
2. Is a parallel run required at every wave, with a named exit gate?
Cutover without a parallel run transfers migration risk from the vendor to your close.
3. Does the vendor produce a variance report your CFO signs, not a status deck?
A signature on reconciled numbers is the only implementation milestone that survives audit.
4. Can you keep your EHR, GL, and payroll as domain systems of record?
Rip-and-replace multiplies clinical and payroll risk in the same quarter.
5. Do you get a contractual export of the reconciled record, in a documented schema?
Control of the Operator-Controlled Operating Record is meaningless if you cannot leave with the record.
6. Is every integration labeled by real status — production, validation, or extract?
Ambiguous integration language is the single most common source of implementation slip.
7. Is there a named production reference at your portfolio size and setting mix?
Ask us this one too. As of September 29, 2026, Pre-production. No operator runs SeniorCRE in an operator production environment; no operator workflow has been validated; no measured operator outcome or independently validated result is published; no third-party integration is live in operator production; and no PHI is processed in operator production.
8. Does the plan name an owner per step on your side, not just the vendor side?
Most slipped deployments slip on operator decisions nobody was assigned.
9. Will the vendor show you what went wrong in prior rollouts?
A rollout log without failures is marketing, not evidence.
10. Is access default-deny, with per-tenant capability gating and access review?
Clinical and payroll data in one record raises the bar on entitlement governance.
Answers stay in your browser. Nothing is submitted to SeniorCRE, and no contact information is required to export the sheet.
First-party rehearsal log
Anonymized validation rehearsal — multi-community, multi-state, de-identified structure with two clinical systems of record and two payroll instances inherited from a 2025 acquisition.
This is a rehearsal, not a customer outcome. The portfolio structure, entity hierarchy, chart of accounts, and de-identified record volumes come from a design-partner discovery engagement; the run itself executed. Evidence class D. No resident data and no operator production system was involved, and no operator is named because none has completed a production deployment as of September 17, 2026. We publish the failures below because a rehearsal log without failures is a brochure.
—
What was proven
Nine distinct systems catalogued across two operating companies; entity hierarchy reconstructed to unit level; 41 GL account collisions identified between the two charts of accounts.
What went wrong
Two communities had licensure records that disagreed between the state portal and the incumbent system. Resolution required an operator authority decision and moved those communities to a later validation gate.
—
What was proven
Org hierarchy, role-based access control, tenant isolation, audit logging, and SSO exercised via the operator onboarding wizard.
What went wrong
Nothing at this step. This is also the step most vendors can do quickly, so it should carry the least weight in your evaluation.
Wave 1 · 1 community
What was proven
Resident, chart, medication-administration history, lease, and AR/AP migration pattern tested with a bounded parallel review. Reconciliation report produced: records in, records out, rejected rows with a reason per row.
What went wrong
2.7% of medication-administration history rows rejected on first pass because of a free-text dosage field in the source system. Mapping rule added, re-run clean; the rule is now part of the mapping dictionary.
Wave 2 · 4 communities
What was proven
The account collisions resolved into an operator-approved chart crosswalk; validation communities reached financial parity inside the parallel review.
What went wrong
Finance leadership rejected the first crosswalk because two expense categories had been reconciled in a way that broke year-over-year comparability. Rebuilt after operator review. This is a human agreement problem, not a software problem, and it is a common reason a wave slips.
Wave 3 · 5 communities
What was proven
State-scoped access control and state-specific assessment variation exercised across three states in one wave.
What went wrong
Medicaid billing rules in the third state required a rule set that had not been built for the rehearsal. Scoped as a written build item. In a real engagement this is a contractual change-order conversation, and you should ask who pays for it before signing.
Wave 4 · 4 communities
What was proven
Two payroll instances reconciled into one labor record with staffing-hour attribution by community and shift, preserving submission-ready labor reporting continuity.
What went wrong
The two payroll instances used different pay-period boundaries. Reconciliation required a documented convention decision from the operator; until that decision was made, labor cost per resident day was not comparable across the two OpCos.
All 14
What was proven
The same metric produced identical values in clinical, labor, and financial views in one session — the test we ask operators to run on every vendor, including us.
What went wrong
Occupancy differed by 3 residents against the incumbent on first pass, traced to mid-month move-out timing convention. Convention documented, variance closed.
Validation rehearsal from discovery through portfolio reporting parity across de-identified communities. Operator decisions — crosswalk agreement, pay-period convention, licensure discrepancy — controlled the sequence. Treat the log as gate evidence, not a deployment-duration claim.
Deployment doctrine
Road 1 retains the systems the operator chooses and governs what they produce. Road 2 assigns selected system-of-record functions to SeniorCRE. Either road establishes operator-controlled authority for census, labor, compliance, and NOI decisions.
Selecting SeniorCRE as the core operating infrastructure, or retiring a legacy system onto it, is a supported path — but it is an explicit, governed migration decision with its own exit gates, not the starting posture.
Answered directly
The eight questions that decide enterprise deployments, answered without hedging — including the ones where the honest answer is no.
Deployment advances on gates, not on dates, and no day counts are published. A single community moves through Authority Workshop Complete, First Source Connected, First Governed Metric and First Community Production in one wave; larger portfolios repeat the sequence by wave. Any sequencing shown is a design target — not customer evidence. The binding constraint is almost always operator decisions — entity hierarchy, chart-of-accounts alignment, and variance adjudication — not software configuration.
Only if you decide they should be. The default posture is to keep them: in a parallel configuration your incumbent eMAR keeps medication administration and SeniorCRE reads one direction only, your GL remains the ledger, and your payroll remains the pay run. SeniorCRE has built clinical record surfaces; medication administration and eMAR remain roadmap — not built. Any future clinical system-of-record function must clear its own Production-Entry Gates and receive operator acceptance. SeniorCRE reconciles those through governed definitions, source authority, reconciliation, and lineage that the operator controls. Selecting SeniorCRE as the core operating infrastructure, or retiring a legacy system onto it, is a supported but explicit migration decision with its own exit gates.
No. Integration surfaces are built. As of September 29, 2026, no integration is running in an operator production environment; Founding Operator deployment dates are not yet scheduled and remain to be determined. Partner enablement, contracts, and rate limits are conditions we do not control and will not represent as complete.
Not yet, and we will tell you that in the first meeting rather than the last. There is no completed operator-production deployment. What we can give you is a 71-day, 14-community rehearsal log with the failures included, the written mapping dictionary, the exit-gate structure, and an access-control review. If your committee requires a named production reference to proceed, you should defer us until we have one.
The wave does not advance. Every variance line gets a named cause and a named owner, and unsigned fields are excluded from the record rather than estimated. A parallel run stays in force until your finance and clinical leadership accept the variance report in writing. There is no scenario in which an unreconciled figure silently becomes the number your board sees.
The operator controls the reconciled operating record, including exports, in a documented schema. That is the point of the architecture: the Operator-Controlled Operating Record sits above your systems and belongs to you, so switching costs are not used as leverage. Retention, access review, and audit cadence are set in the governance charter signed at the end of the rollout.
Access is default-deny with per-tenant capability gating, role-to-permission mapping signed at Wave 0, and an access-review cadence set in the governance charter. Entitlement changes are logged in the audit trail. Because clinical and workforce data sit in one reconciled record, entitlement governance is treated as a deployment gate rather than a post-launch cleanup item.
Chart-of-accounts and entity-hierarchy disagreement inside the operator, usually surfaced by a prior acquisition. If two legacy structures have never been reconciled, that reconciliation is the project, and no vendor can compress it. We would rather name that in diligence than discover it in Wave 1.
Different rooms need different evidence. Each path opens with the artifacts your function actually has to defend.
CIO / CTO
Integration surface inventory by real status, tenancy and entitlement model, export schema, and the access-review posture. Bring your security questionnaire.
COO / SVP Operations
A scoped review of where census, labor, revenue, and compliance stop agreeing across your existing systems — and which of those breaks are decisions only you can make.
CFO / Board / Capital
What is verifiable today, what is not, the gate structure that protects your close, and the current production-evidence boundary as of September 29, 2026.
SeniorCRE does not publish clinical outcome percentages, model accuracy percentages, or per-module annualized dollar values. Figures of that kind were withdrawn on August 5, 2026 because capability is not outcome: the platform implements the workflow, but no outcome has been validated at a named operator community. Nothing on this platform should be read as a predicted clinical or financial result.
Trademarks referenced elsewhere on this site (PointClickCare®, MatrixCare®, Yardi®) belong to their respective owners and are used nominatively for identification only. Statuses on this page are stated as of September 17, 2026 and are subject to change.
Bring your system inventory, your entity hierarchy, and your two charts of accounts. We will walk the gates, name the decisions only you can make, and tell you early if you need a named production reference we do not yet have.
Deployment sequencing describes how the platform is designed and demonstrated to be stood up. It is not a report of completed operator-production rollouts.