The systems provide evidence. The operator establishes authority. The operating record preserves the determination—so leadership can explain which number governed, why it governed, and who approved its use.
Coherence Before Intelligence. Pre-production: complete record designed; operator validation pending.
An Operator-Controlled Operating Record preserves what the organization accepted for a particular decision: the definition, which source governed for that purpose and period, how disagreement was resolved, who approved it, and the evidence that can reconstruct it later.
It is permanent enterprise infrastructure in the class of the general ledger and audit trail—not a claim that one database is right about everything. Source systems keep their domain authority. SeniorCRE’s complete record is designed, not yet implemented in any community.
Fictional 120-unit community · Scripted illustration · No live SI or system connection
September 2026, physical occupancy at month-end. Two totals two units apart can hide four records worth examining.
Clinical census (EHR)
101
Who is physically in residence
Billing ledger
103
Who is being charged rent
Sales CRM
102
Who has signed or is still active
Bed board
100
Which units show as taken
Each count may answer a different question. For physical occupancy at month-end, the clinical census is the designated source. Its 101 still needs evidence and exception review before anyone accepts it.
Executive summary
Status: designed, not yet implemented in any community. Road 1 governs the systems you keep; Road 2 is an operator-chosen replacement of selected functions — each with its own gates.
Capability & evidence status
Component status describes controlled-environment progress only. The Operator-Controlled Operating Record as a whole is designed and not yet implemented in any community as of November 13, 2026; no operator-production deployment or measured operator outcome is claimed.
Coherence Before Intelligence
Morning presence, billed unit-days and portfolio occupied units are different measures. State the numerator, denominator and moment of measurement.
Required artifact: Versioned metric dictionary
Synthetic demonstration · no operator production
Each reading answers a different question. The operator establishes which measure governs a particular purpose; the record is designed to preserve that determination.
Property management
87.4% occupancy
Unit released on move-out day
Clinical record
88.1% occupancy
Unit held until discharge closed
Billing calendar
86.9% occupancy
Billed days, third calendar
Exception unresolved. No governing determination.
Execution denied. Simulation approval never grants live permission.
All original readings remain unchanged: property management 87.4%, clinical 88.1%, billing 86.9%. Definition and rule v1, fictional source timestamps, reviewed exception, designated approver and permitted purpose are retained. Current review: exception open. Context changes reset review and approval.
Residents physically present at 08:00 local time, divided by 1,000 available licensed units. Staffing still requires acuity and skill-mix review. Fictional Monday 08:00 local. Clinical presence governs the morning staffing context; contracts and billed days do not substitute for presence. Approver: Director of nursing / designated census lead. Morning staffing review only; no schedule, clinical order or medication action is executed.
Billable unit-days divided by available unit-days for a fictional 30-day month; this is not a morning resident count. Fictional month close, day 30 at 23:59 local. Accepted billing calendar governs the financial occupancy measure for this closed period; clinical presence serves a different purpose. Approver: Controller / authorized finance approver. Financial reporting review for the defined closed month only; no journal entry or billing write occurs.
Occupied available units at fictional Sunday 23:59 local, divided by 1,000 available licensed units; apply the same dictionary at every included community. Fictional Sunday 23:59 local. Property management governs unit status; if move-out and clinical discharge differ by more than 24 hours, review the clinical discharge date under the retained example rule. Approver: Regional VP of operations / delegated portfolio approver. Portfolio occupancy reporting under this definition and period only; no owner report is transmitted.
Existing percentages are retained from the illustrative governance guide. The 1,000-unit community, counts, 30-day period, timestamps, review evidence and roles are newly invented teaching assumptions—not customer facts. Valid measures may differ by purpose. No averaging, production authority, verified outcome, report transmission or operating-system write is demonstrated.
Rebuilding the same number consumes reconciliation labor and can delay reporting. Different occupancy definitions, workforce measures and acquisition mappings can complicate operating decisions and REIT/owner reporting. The degree of exposure depends on the operator; none of these consequences establishes savings from SeniorCRE.
Annual assumed amounts per community. Leave blank if not estimated. Exclude costs or revenue already counted in another category.
Annual reconciliation labor estimate
$78,000
800 units · $98 labor per unit/year
Optional hypothetical exposure
Not estimated
No exposure assumption included.
Annual reconciliation labor = communities × weekly hours per community × 52 × loaded hourly cost. Optional annual exposure = communities × separately entered annual exposure per community. Units normalize labor cost; they do not multiply it. Combined subtotal includes only identified, confirmed non-overlapping categories.
Fictional teaching assumptions, October 31, 2026: 10 communities, 80 units each, two weekly reconciliation hours and $75 loaded hourly cost. These are not observations, benchmarks or measured losses. Uniform assumptions across communities; 52 weeks per year. Sensitivity changes hours or cost independently, never both at once.
Illustrative scenario analysis only. Not verified customer outcomes, projected SeniorCRE savings, recoverable cash, ROI or a delivery guarantee. Labor may already be budgeted and is not necessarily avoidable expenditure. Optional exposure is hypothetical risk, not an established loss. Blank categories are not estimated; explicit zero is an assumption, not a verified outcome. Exclude reconciliation labor from workforce/reporting exposure and exclude the same revenue or expense from multiple categories. Inputs remain in this browser and are not saved or submitted.
These categories can coexist. A warehouse, dashboard or application may implement governance controls; centralization, presentation and model confidence alone do not establish organizational authority. Evaluate actual controls and evidence, not a category label.
1
An accountable owner approves a versioned metric dictionary.
2
Authorized source access, entity mapping and security review establish the bounded scope.
3
Reconciliation and lineage tests must reproduce the rule and unresolved exceptions.
4
Recorded operator acceptance is required before production reliance.
5
Expand only after source-specific permissions, tests and acceptance clear again.
6
Apply consistent definitions with accountable local exceptions and retained period evidence.
Operators may retain existing systems, or select future SeniorCRE system-of-record functions after their required gates clear. Neither replacement nor immediate production availability is implied. There is no guaranteed timeline or automatic expansion.
Designed Not yet implemented in any community. No operator-production outcome is established by these simulations.
Clinical record surfaces are built; medication administration and eMAR remain roadmap — not built, excluded from Road 2 starting scope and unavailable for production today. The future native clinical configuration requires function-specific build completion, clinical-safety review and clinical sign-off, end-to-end workflow validation, data readiness, operator acceptance before production entry. No community runs SeniorCRE as its clinical system of record.
No operator-production deployment, live named connector, measured portfolio rollout or standard go-live duration is claimed. Replacement of a fixed number of systems within hours is not an available offer or a measured result. Medication administration/eMAR and third-party write-back are excluded from starting scope. Synthetic examples, architecture documents and controlled tests are not operator acceptance. Exactly one medication administration record may be authoritative; a coexistence configuration reads the incumbent MAR one direction only and never writes to it.
Inspect current evidence and assurance status in the Trust CenterWe examine its definition, source authority, recurring disagreement and required decision evidence, then discuss a credible first validation scope—not a promised deployment.
Request a 30-Minute AssessmentExplore the bounded first governed-field phase through the Founding Operator Program.
The retained architecture describes design intent, not deployed governance or production availability. Function-specific evidence and operator acceptance govern reliance; medication administration/eMAR remains roadmap and excluded from starting scope.
In senior living, a single source of truth means an agreed basis for a particular business decision—not one system that is right about everything. The operator defines the number, names which source governs it, sets a rule for disagreements, and names the person who rules on exceptions. An Operator-Controlled Operating Record keeps that determination with the original source values and the evidence explaining why it governs. Valid values remain available for the different questions they answer.
A synthetic community has 98 contracted residents in its commercial register and 96 residents physically present at 8 a.m. in its census register. Both values can be valid: they answer different questions. For morning staffing, the operator defines census as residents physically present at 8 a.m., declares the census register authoritative, and requires a named operations lead to review the two-person difference against the contract and absence records. If the review confirms that two contracted residents are away, 96 governs that staffing decision; 98 remains the contracted-resident count. The record preserves both values, their timestamps, the rule, the evidence and the human ruling. If the evidence does not explain the difference, the conflict stays open for that lead to resolve—it is not averaged away.
Illustrative reconciliation example · synthetic data. This describes a governance method, not a deployed SeniorCRE workflow or an observed operator outcome.
I · The premise
It exists in the census file someone rebuilds each Monday, in the version of the variance a regional trusts, in the corrections a controller remembers making, in the explanation a director gives a surveyor from memory. It is real, it is load-bearing, and it is undocumented.
The question is not whether your organization has an operating record. It is whether the organization governs it — or whether it lives in people, spreadsheets, and habit, and leaves when they do.
II · The definition
The operating record is the record the organization agrees to run from. It shows which number governs, why it governs, and where it came from.
It is not software, and it is not a report. It preserves what happened, which facts were authoritative, how they were reconciled, who approved them, and which decisions they informed — the answer an organization can still give, years later, to the question on what basis did we decide that?
Three of those are already non-negotiable in every serious enterprise. The fourth is the one senior housing & care has been operating without.
III · The structural limit
Each was built for a different purpose and can be authoritative inside its own boundary. None was designed to settle a disagreement that spans care, labor, census, revenue, compliance, NOI, and capital.
Integration connects these systems. Connection is not authority. Something has to sit above them and hold the answer.
IV · What changes
Without a governed record
The first thirty minutes establish which number is real.
Whoever brought the most defensible spreadsheet sets the agenda. The decision happens at the end, if there is time.
With a governed record
The number is settled before the room opens.
The meeting exists to decide and to assign, because definition, source authority, reconciliation, and lineage were governed in advance.
That is the whole reframe. The purpose of leadership time changes from establishing truth to exercising judgment.
V · The smallest undeniable example
In March, leadership approved added agency coverage at one community based on an acuity and census reading. In February of the following year, a lender asks why that quarter missed labor plan. Everyone who was in the room has moved on or moved roles.
The figure that was used
Not today’s recomputed number — the value as it stood when the decision was made.
The definition in force
Which version of “occupied” and “acuity-weighted hours” applied in that period.
The governing source
Which system was authoritative for it, and which conflicting reading was set aside.
The approval
Who accepted the figure as the basis for the decision, and when.
The decision it informed
The coverage approval itself, linked to the record state that supported it.
This is not a cleanup. The same disagreement returns with the next schedule and the next close: whether an on-call hour that was never worked belongs in agency hours is a defensible question with two defensible answers. A governed record does not settle it once — it holds the rule that settles it every time, with the reasoning attached.
A better report can recompute the number. It cannot reconstruct the decision. That gap is not a reporting gap — it is a different layer, and this is the test that proves it.
Illustrative walkthrough of governed decision lineage. It is not a measured operator outcome and does not describe a live production integration.
VI · Why it matters beyond operations
Each unresolved disagreement is small. Their accumulation is not. Teams begin hedging their own figures, leaders discount what they are shown, boards ask for backup instead of recommendations, and lenders price the uncertainty. The cost is not a wrong number. It is diminished confidence in the act of operating.
An Operator-Controlled Operating Record restores that confidence, because it makes truth institutional rather than personal. What the organization remembers no longer depends on who stayed.
A separate synthetic teaching scenario with its own staffing/ownership rule—not a universal authority rule for every reporting purpose.
Demonstration
Illustrative demonstration. The community, residents, roles and figures are invented to show the method; they are not operator data, a deployment or a result.
Property management system
98
Residents with an active lease at 11:59 p.m.
Clinical record
96
Residents in residence at the 11:59 p.m. midnight count
Both systems are correct inside their own boundary. They disagree by 2 because they count different things. The decision at stake: census for next week’s staffing plan and the weekly ownership report.
Proposed use cases · synthetic examples
Five proposed use cases show how the same sequence would govern conflicting information across clinical care, labor, finance and compliance — without requiring an operator to replace the systems it runs today. In every case, SeniorCRE does not decide which system wins. The operator establishes which evidence governs each decision.
EHR census
84
Billing census
85
Synthetic, illustrative figures.
Operator-authorized outcome: Preserve both counts, their definitions and their governing purposes. The billing count may govern contractual revenue calculations while the clinical count governs a different operational measure.
Critical distinction: A billable resident is not necessarily a physically present resident. A single number should not govern revenue, staffing and regulatory reporting unless the definitions genuinely coincide.
Scheduled shift
8 hours
Recorded work
12 hours
Synthetic, illustrative figures.
Operator-authorized outcome: Recognize four additional hours, verify the applicable overtime treatment, and separately document whether the staffing exception was approved.
Important: Missing management approval cannot invalidate legally compensable hours. Four extra hours do not necessarily equal four statutory overtime hours; the applicable overtime rules must be evaluated.
Clinical assessment
Care Level 3
Billing record
Care Level 2
Synthetic, illustrative figures.
Operator-authorized outcome: Reconcile the assessed care level against the resident agreement, effective date, required notices and approved billing change.
Why this matters: The operator can distinguish clinically justified care changes from legally billable changes — preventing both missed legitimate revenue and unsupported charges.
Clinical requirement
120 care hours
Staffing plan
104 care hours
Synthetic, illustrative figures.
Operator-authorized outcome: An illustrative 16-hour variance requiring clinical and operational review. These figures are hypothetical, not established regulatory minimums.
Why this matters: Governance is not simply financial optimization. Clinical safety requirements constrain downstream recommendations.
Approved purchase order
$8,000
Vendor invoice
$10,500
Synthetic, illustrative figures.
Operator-authorized outcome: Flag the $2,500 difference, determine whether it reflects an authorized change, and prevent unsupported payment where the destination system permits enforcement.
Why this matters: The same architecture extends beyond clinical and workforce systems into enterprise financial controls.
Proposed use cases · synthetic, illustrative figures. The Operator-Controlled Operating Record is designed and not yet implemented in any community. Intelligence and execution are downstream capabilities, not claims of currently validated SeniorCRE functionality.
Assess your operating governance — twelve questions, five minutes, immediate ungated results
Operator Executive Edition · October 2026
A 12-page executive brief on conflicting numbers, operator authority, the first governed-field phase and the evidence required before production reliance.
Evidence status dated October 16, 2026. The Operating Record is designed and not yet implemented in any community; examples are synthetic, not measured outcomes.
PDF · 12 pages · 139 KB
Executive Brief · Shift-Level Staffing Governance · October 21, 2026
The six-page companion brief: why the shift is the unit of liability, where four systems disagree, the six-stage governing sequence, decision rights by role and the working checklist for the single-shift test.
Evidence status dated October 21, 2026. The Operating Record is designed and not yet implemented in any community; the worked example is synthetic, not a measured outcome. Discussion document, not legal advice — review any policy built from it with counsel.
PDF · 6 pages · includes the single-shift checklist
Institutional trust markers
Multi-community operators, REITs, private equity, lenders, and multi-state portfolios evaluate the same nine markers before they sign. Their current status, supporting evidence and limitations must be reviewed in the Trust Center; this list is not independent assurance or operator-production evidence.
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.
Governed operator-export ingestion and named-vendor connectors are roadmap, not built. Generic sample mapping does not establish an implemented operator workflow. No third-party integration is live in operator production today.
SOC 2 is planned. SeniorCRE does not claim certification or its own SOC 2 report. AWS’s infrastructure reports are not a SeniorCRE attestation. See the Trust Center for current assurance status.
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.
Contents
Senior housing has many systems but no governed enterprise operating record. SeniorCRE provides operator-controlled operating infrastructure that establishes that record. Operators can govern the systems they already have or run selected domains directly on SeniorCRE. In either case, the operator determines what is authoritative.
Definitions, Authority, Reconciliation and Lineage turn data into governed truth; the Operator Authority Chain™ carries that truth into human decisions and authorized execution. SI comes after governance, not before it.
The operating record is the governed record per resident, care plan, ledger, shift, property/unit, and entity that every surface in senior housing & care reads from and writes to. Canonical here means the representation produced after definitions, source authority, and reconciliation have been applied — not a database that is right about everything. Source systems remain authoritative for their own domains; the record governs what the enterprise accepts as true, with lineage decided once rather than re-argued every month.
How the operating record composes the stack.
Isolation, audit, and access posture behind the record.
How owners, investors, and lenders read the operator’s record.

Definitions · Authority · Reconciliation · Lineage
Illustrative governance diagram. It depicts the governance model and design intent, not operator results, customer deployments, production performance, or verified outcomes.
DALLAS, TX · CATEGORY BRIEF
Epic organized healthcare around the patient record. Every clinician, biller, researcher, and auditor reads the same chart. The chart is the record. Senior Housing & Care never had that primitive. Operators run nine vendors, owners read a different set of numbers, lenders read a third, brokers read a fourth, and the resident exists as a near-duplicate in each. SeniorCRE organizes senior housing & care around the operating record — the governed superset that resolves clinical, financial, workforce, and capital views into one governed representation.
Epic organized healthcare around the patient record. SeniorCRE organizes senior housing & care around the operating record.
| Constituency | What they read from the operating record |
|---|---|
| Operators | Live census, eMAR, shift workload, payer mix, period close — read at request time. |
| Owners & Sponsors | Property-level NOI, occupancy, covenant rollups assembled from the same governed record operators write. |
| Investors & REITs | Portfolio rollups, ESG metrics, threshold alerts — no BI overlay, no nightly ETL. |
| Brokers | Deal-to-ops handoff with audited operating history attached to every transaction. |
| Vendors | Scoped, approval-gated access to the entities they touch — never the whole record. |
| Lenders | Covenant visibility, DSCR, and operating evidence on the same record the operator runs the day on. |
To apply this doctrine across retained systems, use the operator data governance framework with five working documents, explicit acceptance criteria and a synthetic census, labor and revenue exercise.
The operating record maintains one governed representation of each governed object — resident, care plan, ledger, property/unit (bed is a unit-level child of Property, not a seventh entity), shift, entity — while preserving authority and lineage to the systems that originate the underlying events. This is not a claim that SeniorCRE physically owns the only resident row in the operator’s stack.
The operator owns the operating record and declares which source is authoritative for each governed object. SeniorCRE holds only what the operator declared, and preserves it: the definition, the declared source, the reconciliation rule, and the lineage back to the originating rows. The operator exports the record at any time under the data sovereignty standard.
Every write to the operating record is designed to append to an immutable log scoped to the same tenant hierarchy as the read path. Survey, SOC 2, and HIPAA evidence assembly is a future design target, subject to function-specific readiness review — not a current capability. Closed figures are never silently overwritten: a conflict raises a visible notice, and an authorized restatement preserves both the original and the revised value.
The record is governed where it lives, not where it is displayed. Replacement is not required — govern first, replace only by choice. SeniorCRE may govern an incumbent EHR/eMAR or serve as the clinical system of record where the operator selects it.
The operator decides which parts of the record an assistant may read. Answers cite the record directly, and each one is traceable to a row the operator owns — never an inferred schema.
Design intent: one authoritative write path would serve accepted SeniorCRE functions. Clinical record surfaces are built; medication administration and eMAR remain roadmap — not built and excluded from starting scope. Native clinical reliance requires function-specific build, clinical-safety review and sign-off, end-to-end validation, data readiness and operator acceptance; this configuration is not currently deployable.
SeniorCRE ingests the authoritative event with lineage to its origin system and applies operator-approved reconciliation rules to produce the governed enterprise record. The incumbent keeps its authority; the operator declares what the enterprise accepts as truth, and SeniorCRE keeps that declaration with its lineage.
The operator determines the authority topology — which system is authoritative for medication, workforce, ledger, and census — and those decisions can vary by community and by domain. Reconciled once under operator-approved rules rather than reconstructed repeatedly downstream.
Incumbent stacks were assembled the way the industry was bought: clinical here, finance there, CRM elsewhere, workforce somewhere else. Each product owns a different version of the resident, the ledger, and the bed. The architecture is not deliberate — it is inherited. The operating record replaces that inheritance with six entities, each owned exactly once.
The UI is replaceable. The dashboards are replaceable. The SI is replaceable. The operating record is what lasts.
| Entity | Owns | Surfaces it powers |
|---|---|---|
| Resident | Identity, demographics, payer, acuity, consent | Clinical · Billing · CRM · Family · Survey |
| Care Plan | MDS, ADL, IDT goals, PRN reassessments, QAPI flags | Clinical · QM engine · Survey · Family (gated) |
| Ledger | GL, AR, AP, period close, payer postings, accruals | Finance · Investor · Audit · Portfolio rollup |
| Shift | Schedule, clock, acuity-weighted workload, med-pass events | Workforce · Clinical · Payroll · Workload alerts |
| Property / Unit | Bed board, licensure, capacity, capex, occupancy | Operations · Investor · REIT · Asset management |
| Entity | Holding Co → Operator → Region → Property → Unit hierarchy | Permissions · Rollups · Tenant isolation · Reporting |
Hover any entity to trace the surfaces it powers. Click to lock the view. Nothing here is a dashboard — every line is a write path in the operating record.
Every surface — clinical, financial, workforce, compliance, investor — reads from the same governed record. A med-pass, an admission, a payer posting, an MDS update writes once.
Visualization renders the canonical entity graph enforced at the database layer via RLS and has_role(uid, role).
When SeniorCRE is selected as the system of record, a med-pass scan, an admission, a payer posting, or an MDS update writes once and every SeniorCRE surface reads that write — not a copy, not a sync, not a nightly job. When an incumbent remains the system of record, SeniorCRE ingests the authoritative event with lineage to its origin system and applies operator-approved reconciliation rules to produce the governed enterprise record. The operator chooses which applies, by domain and by community; the record preserves that choice and the lineage under it.
Reconciliation is one of the four disciplines of the operating record: definitions, source authority, reconciliation, lineage. People approve definitions and rules once, in writing; the record then applies the approved rules, and any exception the rules cannot resolve returns to an authorized operator — no contested value governs until it is ruled on — so census, ADT, billing, eMAR, and payroll disagreement is resolved by governed rule instead of by manual reconciliation in the recurring critical path.
Portfolio dashboards, covenant rollups, quality-measure views, and survey evidence are designed to read from accepted records with authority and lineage — no production latency claim is made.
Every event is designed to append to an immutable log scoped to the same entity hierarchy as the read path. Assembling survey, SOC 2, and HIPAA evidence from that log is a design target that must clear function-specific readiness review; it is not available today.
Isolation is scoped to operator, property, and unit at the data layer — not in middleware, not in a service mesh. Access is mediated by granular role-based access.
Assistants are designed to cite the definitions, authority, and lineage the operator declared. Every answer resolves to evidence the operator owns and can export.
For two decades the market bought senior housing & care software in two layers. The system of record captured what happened. The system of intelligence tried to read across all of it — usually a BI overlay stitched to a warehouse. SeniorCRE is designed to connect intelligence to operator-accepted evidence. No production latency or implemented record-native intelligence outcome is established.
| Dimension | BI overlay on many systems | Operator-controlled operating record |
|---|---|---|
| How intelligence is produced | BI overlay ETL’d from many systems of record | Read from the canonical operating record |
| Time from event → insight | Hours to days (warehouse refresh) | Computed from the Operator-Controlled Operating Record at request time |
| SI grounding | Federated copies; schema drift | Canonical model; citable, exportable |
| Cross-domain question (admit → bill → covenant) | Multi-vendor stitching | One query against one model |
| Who owns the insight | BI vendor / IT | Operator owns the record — and the intelligence above it |
| When intelligence breaks | When any upstream schema shifts | When the operating record itself changes (versioned, governed) |
| Dimension | Operator-controlled operating record | Modular best-of-breed | Single-vendor suite |
|---|---|---|---|
| Architecture | One Operator-Controlled Operating Record above the systems you already run. | Best-of-breed joined by HL7/FHIR/CSV; the operator carries the integration tax. | Single-vendor suite; deep in one domain, thin elsewhere. |
| Care continuum | IL · AL · MC · SNF on one record; mixed acuity native. | Per-tool variation; transitions require re-keying. | Usually AL+MC or SNF, rarely both. |
| Portfolio rollups | HoldCo → REIT → OpCo → PropCo from one hierarchy. | Periodic BI rebuild; drifts each cycle. | Strong only when every property runs the same suite. |
| Data sovereignty | Operator-controlled export with documented schema. | Per-vendor terms; export quality varies. | Vendor-gated; export quality is a switching cost. |
| System replacement | None required — start where you sit. | Rip-and-replace per tool. | Suite migration. |
Context engineering bridge
The operating record does more than store data. For an SI answer, it assembles the narrow slice of accepted facts the task requires, plus the definitions, source authority, reconciliation rule, lineage, and authorization boundary that tell the model what it may rely on.
Read the context engineering explainerThe record is only as governed as the path data takes to get into it. SeniorCRE specifies five ingestion modes, to be chosen per source system and per property rather than imposed portfolio-wide. None is built yet. Modes are ordered by how much the source system has to change — Mode A requires nothing beyond exports the operator already produces.
| Mode | How it works | Cadence | Status |
|---|---|---|---|
| Mode A — Operator-exported files | Census, payroll, GL trial balance, and staffing exports the operator already produces, mapped into canonical entities at load time. | Per export (typically daily to monthly) | Not yet built — specified; depends on the operating record, which is not built yet |
| Mode B — Scheduled report drop | A recurring drop to a governed location (SFTP or object storage) with a fixed file contract, so mapping does not change between periods. | Scheduled — daily or weekly | Not yet built — specified; depends on the operating record, which is not built yet |
| Mode C — Read-only database or replica view | Read-only access to a reporting replica or vendor-provided views, pulled on a defined window with no write path back to the source system. | Defined pull window | Design intent — not live in operator production |
| Mode D — Clinical event feeds (HL7 / FHIR) | ADT, order, and observation events mapped to resident and care-plan evidence, with PHI classification required before storage. | Event-driven | Design intent — outbound clinical transmission not enabled |
| Mode E — Vendor API connectors | Direct system-to-system connectors to EHR, PMS, payroll, and scheduling vendors under executed agreements. | Vendor-defined polling or webhook | Roadmap — named-vendor connectors are not built; no vendor integration is live in operator production today |
Bring one operating number your systems disagree on. A first governed-field phase is scoped with agreed definitions, read-only access, a named approver and witnessed acceptance.
A governed record has to state how much it can be trusted for a given period, per property, per source. The trust score is specified, not built. As designed, it is not a single opaque number: it decomposes into four sub-scores that can each be inspected, and it is reported alongside the figure rather than behind it. A figure with a degraded sub-score is still shown — labeled, not hidden.
| Sub-score | What it measures | What degrades it |
|---|---|---|
| Freshness | Age of the most recent accepted load per source, per property, against that source’s expected cadence. | A late or missed drop, a stalled pull window, or a source that silently stopped producing. |
| Completeness | Share of expected entities and required fields present for the period — properties reporting, beds accounted for, shifts with hours, accounts with balances. | Missing properties, partial payroll periods, unmapped cost centers, gaps in the bed board. |
| Reconciliation | Agreement between sources that should describe the same fact — census vs. billing days, scheduled vs. paid hours, ledger vs. subledger. | Cross-system variance beyond a declared tolerance for the period. |
| Lineage | Share of reported figures that resolve to source rows with intact sync metadata (source, period, batch, mapping version). | Manual adjustments, unattributed overrides, or figures assembled outside the record. |
Definition
Canonical means the governed representation produced after definitions, source authority and reconciliation have been applied — not a database that is right about everything.
Authority stays with the operator and with the source systems that legitimately hold it. What SeniorCRE keeps is the reconciled value the operator has declared the enterprise accepts as true, and the lineage proving how it was reached.
What it never means
How SeniorCRE meets you where you are
You do not have to rip out your stack on day one. SeniorCRE reads where authorized, governs where accepted, and becomes the Operating Infrastructure above the fragmented systems you already run — so leadership sees which definition and source governs each figure, while underlying tools are retired only if and when the operator chooses.
Read authorized EHR, eMAR, CRM, billing, payroll, and accounting records through governed ingestion patterns — operators retain incumbent systems where they work and replace them only where SeniorCRE is deliberately selected for that role.
Govern resident, care plan, ledger, shift, property, and entity evidence with explicit definitions, source authority, reconciliation, and lineage.
Sit above the stack as the Operator-Controlled Operating Record — target-state portfolio visibility, exception alerts, and SI workflows only after authority is declared.
Status as of November 13, 2026 (last modified 2026-11-13)
| 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 November 13, 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.
Design scope: authorized source evidence such as admissions or payer postings is captured for the selected function. Medication administration/eMAR is not built and is excluded from starting scope.
Design requirement: retain the source event and mapping to the governed resident, ledger, shift or property/unit, with a declared purpose and period.
The write appends to an immutable, tenant-scoped audit log, designed so future survey, SOC 2, and HIPAA evidence functions can read from it once each clears readiness review.
Designed downstream use requires operator-approved purpose, permissions and accepted lineage. Unresolved exceptions return to the accountable operator; no latency or production outcome is claimed.
What makes an operating record governed
A record can be complete, auditable, evidence-backed and human-attested and still leave an enterprise question unanswered: which definition had authority to govern this decision?
Senior housing & care enterprises operate across clinical, workforce, occupancy, compliance, financial and capital systems. Those systems can produce different values without any system being wrong. An Operator-Controlled Operating Record preserves those facts, establishes the applicable definition and authority, and records why one meaning governed a particular decision.
A record is not governed merely because:
Those are important controls, and increasingly standard across enterprise software. Nothing here suggests they are easy or that they are ours. Governed operating truth requires something further.
What exactly does the fact mean?
The metric, entity, period and measurement moment are written down and approved by the operator — not inherited from whichever system happened to produce the number.
Which source is authorized for that definition?
A named system holds authority for that definition, and the reason it holds authority is recorded. Domain systems keep the authority that legitimately belongs to them.
For what decision does that authority apply?
Authority is scoped to a decision, not asserted globally. The definition that governs staffing is not necessarily the definition that governs a covenant.
What happens when another legitimate source differs?
A deterministic rule, written before the disagreement, applied the same way every period, with a stated variance tolerance.
Who possesses authority to resolve disagreement when policy cannot?
A named role, established in advance, whose ruling is recorded against the value — so it does not have to be re-argued next period.
Why did this value and this definition govern?
Not only where the number came from. Which definition applied, which source held authority, which rule resolved the difference, and who ruled.
What other valid facts existed, and why did they not govern this decision?
Competing legitimate values are kept, not eliminated. A record that deletes the alternative cannot explain the decision it did not make.
Governed truth
Data
Definition
Authority
Decision context
Reconciliation
Governed truth
Decision
Execution
The governing doctrine is unchanged: EVIDENCE → DISAGREEMENT → AUTHORITY → OPERATOR-CONTROLLED OPERATING RECORD → INTELLIGENCE → EXECUTION. These seven objects are what the Operator-Controlled Operating Record contains. Authorization sits between decision and execution; it is not a fifth stage.
Attestation answers: “Who approved this determination?”
Authority answers: “Why did this definition govern this decision?”
Auditability proves what happened. Authority lineage proves why it was allowed to govern.
The question is no longer whether a record is governed. The question is: what does the governance have authority over?
Definitions, source authority, decision context, reconciliation, adjudication, lineage and preservation are built; external operator deployments have not begun. Enforcement of these objects through a single agent gateway — including any MCP-exposed path — is architecture and design intent on the build roadmap, not a live capability.
Human authority
Three concepts are routinely treated as one. They are not the same, and only the third settles an enterprise dispute.
Human review
A person checks SI output.
Human attestation
A person takes responsibility for a determination.
Institutional authority
The organization has established that this person or role possesses authority over this definition or this decision.
SeniorCRE supports review and attestation, and is designed around institutional authority: the record of who was established to decide what governs, before the disagreement occurred.
Who approved it?
Who had authority to decide what governs?
Systems hold facts. Decision layers organize evidence. The Operator-Controlled Operating Record establishes what has authority to govern.
Connected systems provide broader information. Interoperability moves information across workflows. SI can organize that information and support human judgment. Responsible SI governance can constrain how it is used. These are valuable capabilities, increasingly available across enterprise software, and SeniorCRE claims none of them as unique.
Unifying, matching, merging, deduplicating and remembering data can make the available information cleaner and more useful. None of those operations establishes authority when legitimate systems disagree.
When independently authoritative systems contain different legitimate answers, “trusted data” does not by itself determine which definition applies, which source possesses authority, for which decision, during which effective period, under which exception, or why that meaning governed. An Operator-Controlled Operating Record makes those determinations explicit.
Ground truth is not something a platform gets to declare. The operator declares the definition, assigns source authority, governs reconciliation, and preserves the decision with lineage.
An institutional operator should be able to demonstrate not merely that its data is trusted, connected or interoperable, but why a particular definition and source possessed authority for a consequential decision.
Connected information tells the operator more. Operator authority determines what governs.
Illustrative — not operator data
Which trusted value has authority for this decision?
Operational occupancy
91.7%
Source: trusted · Value: valid
Revenue occupancy
89.9%
Source: trusted · Value: valid
The operating record preserves both values. Neither is an error to be eliminated.
Staffing counterexample
Staffing may legitimately invoke the operational definition instead: operational occupancy governs at 91.7%, while 89.9% remains preserved as a valid revenue value.
Lineage
Why each value governed its decision is preserved — definition, designated source authority, reconciliation state, and the human who adjudicated.
The system should not globally eliminate one value. The operator determines which valid meaning governs each consequential decision.
Trust is important. Authority makes trust institutional.
Definitions, source authority, reconciliation state, lineage and human adjudication are design intent for the Operator-Controlled Operating Record, which is not yet implemented in any community. Enforcement of these controls through a single agent gateway — including any MCP-exposed path — is architecture and design intent on the build roadmap, not a live capability, and none of it runs in external operator deployments today.
Where authority sits
Enterprise information describes what the organization knows. Operator authority determines which of several legitimate meanings governs a consequential decision.
Systems of record
EHR, CRM, PMS, workforce, ledger — each independently authoritative for its own domain.
Enterprise information
Increasingly available from major enterprise platforms. A genuine improvement over reasoning across raw, disconnected systems.
Operator authority
Operator-declared, decision by decision. This is the layer SeniorCRE governs.
Governed operating truth
What the organization is authorized to treat as true for this decision.
Approved intelligence
Any authorized model or agent, reading what authority has already established.
Decision
Authorization
Sits between decision and execution. Not a fifth stage of the chain.
Execution
The governing framework is unchanged: EVIDENCE → DISAGREEMENT → AUTHORITY → OPERATOR-CONTROLLED OPERATING RECORD → INTELLIGENCE → EXECUTION. Better information strengthens DATA. Operator authority is what produces TRUTH. When systems disagree, the operator governs.
SI models, assistants and agents will continue to improve and change, and multiple vendors will supply them. The operator’s institutional definitions, authority rules, reconciliation history, decision rights and lineage should persist independently of the intelligence consuming them.
SI can reason. The operator governs.
An owner requires a standard of governance and evidence. It does not select the operator’s software stack.
Where truth is governed
Execution policy determines what may happen. Truth policy determines what the enterprise is authorized to treat as true before it happens.
Source Systems
EHR, CRM, PMS, workforce, ledger — each preserved exactly as asserted.
Evidence & Provenance
Each assertion bound to its origin, timestamp, definition and lineage.
Disagreement Detection
Material conflicts surfaced, never silently averaged or overwritten.
Operator Authority Chain™
Operator-declared decision rights: who may decide, for which purpose.
Operator-Controlled Operating Record
The governing determination — what governs for this purpose, and why — with its authority, evidence and lineage.
SeniorCRE Intelligence
Reasons from governed context. Model confidence never creates organizational authority.
Controlled Execution
Actions only within explicit authority, policy, approval and audit boundaries.
The governing framework is six stages — EVIDENCE → DISAGREEMENT → AUTHORITY → OPERATOR-CONTROLLED OPERATING RECORD → INTELLIGENCE → EXECUTION. Authorization and approval controls occur between decision and execution; they do not become a fifth stage. Govern the truth before you automate the decision. When systems disagree, the operator governs.
Modern agentic platforms increasingly control SI execution through identity, permissions, deterministic business rules, human approvals, validations, and audit trails. Those controls matter, they are becoming standard properties of enterprise software, and SeniorCRE claims none of them as an invention.
But they begin after another institutional question has been answered: what information is the enterprise authorized to rely upon? If two operating infrastructure contain different legitimate values, an agent can be perfectly authorized to execute while still acting on the wrong definition.
SeniorCRE governs the path from evidence to the Operator-Controlled Operating Record before SeniorCRE Intelligence and controlled execution apply.
Illustrative — not operator data
An SI agent authorized to update the capital forecast
System A
Operational occupancy — 91.7%
System B
Revenue occupancy — 89.9%
Both values are valid.
Only then: SI recommendation → decision → authorization → execution
Permission to execute does not establish authority over truth.
An agent can be authorized to act. The operator still determines what governs.
Definitions, source authority, reconciliation state, lineage and human adjudication are design intent for the Operator-Controlled Operating Record, which is not yet implemented in any community. Enforcement of truth policy and action policy through a single agent gateway — including any MCP-exposed path — is architecture and design intent on the build roadmap, not a live capability.
Master data management is excellent architecture when several records represent the same underlying fact and the enterprise needs one canonical representation of it. Senior housing & care decisions also depend on facts whose meanings legitimately differ by domain — and those should not be merged.
Ground truth is not something a platform gets to declare. The operator declares the definition, assigns source authority, governs reconciliation, and preserves the decision with lineage.
Unifying, matching, merging, deduplicating, or remembering data improves context. It does not establish authority when legitimate systems disagree.
One person.
These records should normally be matched, mastered, and reconciled. One canonical representation is the right answer, and master data management is the right tool.
Both may be correct.
Neither is bad data. Neither should globally overwrite the other. The question is which definition the operator has authorized to govern the decision in front of them. Illustrative example; figures are not operator results.
WHEN SYSTEMS DISAGREE
|
IS ONE VALUE WRONG?
/ \
YES NO
| |
DATA QUALITY / MDM BOTH MAY BE VALID
| |
CORRECT / MASTER DEFINITION + AUTHORITY
RECORD |
DECISION CONTEXT
|
GOVERNED TRUTHStaffing
Clinical / operational occupancy
91.7%
Capital planning
Revenue occupancy
89.9%
No globally surviving value is required. Authority changes with the decision context, and both readings stay preserved with the definition that was in force.
A golden record answers
“What is the mastered value?”
An Operator-Controlled Operating Record answers
“Which valid definition governs this decision?”
| Dimension | Master data / golden record | Operator-Controlled Operating Record |
|---|---|---|
| Problem being solved | Multiple representations of the same entity or fact | Multiple legitimate definitions or authorities affecting a consequential decision |
| Typical action | Match, merge, deduplicate, standardize | Define, authorize, reconcile, adjudicate |
| Conflict handling | Determine which field value survives | Determine which valid meaning governs this decision |
| Authority | Field- or source-based survivorship and mastering rules | Definition + decision context + domain + source + effective period + operator policy |
| Result | Golden / master record | Governed truth for a defined operating purpose |
| Preservation | Source lineage and merge history | Competing valid facts, plus authority and decision lineage |
| SI role | Ground SI in clean, linked, mastered data | Ground SI in operator-authorized meaning for the decision being made |
| Execution | Provide clean context to downstream systems | Govern truth before recommendation, authorization, and permitted execution |
How to read this table. It contrasts two architectures, not two vendors. No column asserts that any named product lacks a capability. Master data management and operator-controlled operating governance answer different questions and can coexist in the same estate. SeniorCRE capability descriptions reflect built, validated, or roadmap — not built; no operator-production deployment has completed.
Data lineage tells you where a number came from. Authority lineage tells you why that number governed. Both matter; they are not the same record.
Source lineage
Where did the fact originate?
Transformation lineage
What happened to it technically — mapping, standardization, merge?
Authority lineage
Why did this definition and this source govern?
Decision lineage
Which decision relied on it, who authorized it, and what followed?
As SI agents become capable of acting directly across enterprise systems, the critical control point moves upstream. Before an agent acts, the enterprise must know not only where a fact came from, but whether that definition is authorized to govern the decision being made.
Govern the truth before you automate the decision. When systems disagree, the operator governs.
Domain authority belongs where it belongs. Decision authority belongs to the operator. Source precedence is not the same as decision authority.
A trustworthy number may still be the wrong number for a particular decision.
Authority depends on the decision: purpose, facility, population, reporting period, measure and operator policy decide whether a number applies. Sources do not have to collapse into one universal figure.
Concept illustration — fictional data; not a deployed or operator-validated capability.
Question: “Which facility has the greatest opportunity to reduce nursing overtime?”
Facility A
8.2% of worked nursing hours
Trailing 12 weeks · skilled resident-day mix 48%
Facility B
5.6% of nursing payroll dollars
Most recent calendar quarter · skilled resident-day mix 19%
HOLD — the denominators, windows and resident mix differ. No ranking is defensible yet.
Numerator · Denominator · Units · Job roles · Population or cohort · Reporting period · Effective dates · Source freshness · Operating context · Adjustment method · Approving owner
No algorithmic risk adjustment or facility ranking is applied unless independently validated. Nursing agency expense is never inferred from generic contract-labor accounts.
Proof pass
What is built, and what is exercised only. Availability varies by source system and contract; nothing here asserts an enabled vendor or payor integration.
Designed to retain a governed resident and unit representation for census, with lineage to originating systems.
DesignedNot yet implemented in any community. Not running in any operator production environment.
How Quality Occupancy is measuredDesigned to support care, labor, revenue and compliance views against operator-authorized evidence.
DesignedNot yet implemented in any community. Not running in any operator production environment.
Platform overviewDesigned to retain retrievable audit evidence and decision lineage; not implemented in any community.
DesignedNot yet implemented in any community. Not running in any operator production environment.
Not yet implemented in any community. Build, validation and operator acceptance remain required. Stated as of November 13, 2026.
Designed to support retained source systems by operator choice; connector scope requires separate evidence.
DesignedNot yet implemented in any community. Not running in any operator production environment.
Not yet implemented in any community. Build, validation and operator acceptance remain required. Stated as of November 13, 2026.
Designed to ground proposed intelligence in operator-authorized evidence with source citations.
DesignedNot yet implemented in any community. Not running in any operator production environment.
SI oversight and governanceDesigned to support operator-controlled export of the operating record.
DesignedNot yet implemented in any community. Not running in any operator production environment.
Open Data Governance CenterNothing here runs in a named operator’s production environment as of November 13, 2026.
What changes in 90 days
Start with one reporting disagreement and the exports you already produce. The windows below illustrate a gate-based evaluation, not a delivery calendar; no system replacement is required.
Days 1–30
Name the record
Systems inventory, survivorship rules, and the reconciliation set agreed in writing. Nothing is migrated and nothing is replaced — the operator declares which source governs each field.
Days 31–60
Reconcile in the open
For the agreed first-field scope, review authorized exports side by side and document differences. Record-based reconciliation requires build and validation before operator acceptance; this phase does not promise a multi-domain or clinical workflow.
Days 61–90
Govern the disagreements
Review first-field test results and the proposed authority decision with the operator. Operational reliance requires recorded acceptance against the agreed criteria; board, covenant and labor workflows are not automatic deliverables of this evaluation.
Sequence and phase content describe the evaluation plan offered to founding-cohort operators as of November 13, 2026. This is an evaluation sequence, not a committed go-live duration — timing is gate-based and agreed with each operator in writing. Status of the underlying surfaces follows the maturity nomenclature stated on each capability page; no connector is running in operator production today.
Ten questions. Five dimensions. One number that tells you whether you are leading from one operating record — or being managed by your stack.
IDENTITY · BEFORE & AFTER
The same portfolio. The same residents. The same board. What changes is whether you are managing a stack or leading from one operating record.
10-question diagnostic. Browser-only. No email required.
What could intelligence do after the operator establishes what governs?
Review SeniorCRE’s governed SI approachDoctrine
Organizations have long accepted the general ledger as non-negotiable. Decision governance is next. That is the operating record.
Definition. Authority. Reconciliation. Lineage. The four that make data governable.