The operator proof journey: from one disputed number to a documented case study
Start with one number your systems disagree on. Govern that number — definition, authoritative source, rule, approver, lineage — then agree a bounded pilot and its acceptance criteria before any work begins. A case study is written only from what was measured, and only with the operator’s consent.
Written by SeniorCRE Governance Desk · Reviewed by John Hauber, Founder, SeniorCRE, LLC · Updated October 12, 2026
Where this stands today: the Operator-Controlled Operating Record is designed and not yet implemented in any community. No operator has entered or completed this journey, and no case study exists yet. This page describes the path and the evidence each stage must produce.
Six stages, each with a gate
A stage ends when its gate is cleared. Moving on is always the operator’s decision.
Stage 01 · One disputed number
Which number do your systems disagree on, and which decision does it feed?
- The operator brings
- One metric, one community, one reporting period, and the decision that depends on it — the planned first proof is occupancy that explains revenue; staffing can follow later as an illustrative use.
- What is produced
- A written statement of the disagreement: every reading, the system it came from, and what the difference changes.
- Gate to the next stage
- The operator confirms the disagreement is real and that the decision matters enough to govern.
Stage 02 · A governed determination
Who decides which reading governs, under which rule?
- The operator brings
- A named data owner and an accountable approver with the authority to settle the definition.
- What is produced
- A versioned definition, a declared authoritative source per field, a reconciliation rule, a recorded approval and a retained lineage — see the demonstration below.
- Gate to the next stage
- The determination can be replayed from the retained readings without anyone re-arguing it. People approve the definition and rule; the system applies the approved rule; any exception it cannot resolve returns to an authorized operator, and no contested value governs until it is ruled on.
Demonstration
Two census values. One governed determination.
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.
Stage 03 · A defined pilot
What is in scope, what is excluded, and who holds authority?
- The operator brings
- Executive sponsorship, the communities and domains in scope, and the operator’s choice of deployment: govern the systems already in use, or run SeniorCRE itself as the system of record for selected functions.
- What is produced
- A written scope: metrics, communities, systems, exclusions, roles, and the evidence each stage must clear.
- Gate to the next stage
- Scope and exclusions are signed off by the operator before any operational use.
How a bounded platform pilot is scoped, and what it excludes
Stage 04 · Agreed acceptance criteria
What must be true for the pilot to count as passed?
- The operator brings
- The people who will judge the result — operations, finance and, where clinical data is involved, clinical leadership.
- What is produced
- Acceptance criteria written in advance, each tied to evidence that can be inspected rather than asserted.
- Gate to the next stage
- Criteria are agreed in writing before work begins and are not changed after results are seen.
Example criterion shapes — not targets or results
- Every governed census value for the pilot period can be replayed from its retained source readings.
- Every determination records the definition version, the rule applied and the approving role.
- No source reading is overwritten or deleted; a superseded value remains visible in lineage.
- The weekly staffing plan and the ownership report draw on the same governed value.
- A change to the definition produces a new version with its own approval, never a silent edit.
Stage 05 · Measured evidence
What did the pilot actually show?
- The operator brings
- Access for the agreed review, and a decision-maker for whether to continue.
- What is produced
- A record of each criterion — met, not met, or not yet testable — with the evidence attached, kept distinct by level: illustrative demonstration, real operator-file evidence, a real disputed value resolved under approved rules, recurring operational use (for example two consecutive closes), and documented executive acceptance.
- Gate to the next stage
- Continuing is a deliberate operator decision made from what was measured, not a default.
Stage 06 · A documented case study
What can be said publicly, and who approves it?
- The operator brings
- Consent. The operator owns its operations, including whether and how its results are shared.
- What is produced
- A case study limited to measured evidence, with the criteria, limits and anything not met stated alongside what was.
- Gate to the next stage
- Nothing is published without the operator’s written approval of the final text.
How return is measured across the organization
This page makes no ROI claim, because no operator has completed this journey and no result exists to cite. Which measures apply depends on the pilot’s scope and the data feeds in it; financial return is reported only when the evidence supports it. Recurring use and executive acceptance prove adoption — not ROI and not better patient outcomes. What can be stated in advance is what the pilot may measure, and who signs the criteria that turn measurement into a return figure.
- Reconciliation effort
- Staff hours spent re-reconciling the same numbers between systems each week, before and after governance of the pilot metrics.
- Labor variance
- The gap between the staffing plan and what payroll actually paid — including overtime and agency spend — once plan and payroll read the same governed census.
- Census disputes
- How often a meeting, report or decision stalls on “which number is right,” and how often it does after the determination is on record.
- Reporting consistency
- Whether operations, finance and ownership reports carry the same governed value for the metrics in scope, without manual adjustment downstream.
The acceptance criteria are signed by the people who will judge the result — operations, finance and, where clinical data is involved, clinical leadership. The return figure is documented at the end of the pilot from what was measured, with its limits stated. It is never promised at the start.
What we claim — and what we don’t
Operators deserve to know exactly where the line is. This is the whole of it.
What we claim
- Conflicting numbers between systems are a real, named cause of stalled decisions and rework — and they can be governed: defined, sourced, reconciled and recorded.
- A governed determination can be replayed from its retained readings, so the same dispute never has to be re-argued.
- The pilot is designed so that any improvement — in reconciliation effort, labor variance or reporting consistency — is measured against criteria agreed in advance, not asserted after the fact.
What we don’t claim
- We do not claim that resident or patient outcomes have improved under SeniorCRE. No community runs the Operator-Controlled Operating Record yet, so no outcome has ever been measured under it.
- We do not claim clinical results. Clinical judgment stays with clinicians; the record governs what the organization accepts as true, it does not practice medicine.
- We do not claim ROI, savings or accuracy figures. Any such number would be invented today, and invented numbers are exactly what this page exists to replace.
Whether outcomes improve is a hypothesis the pilot is built to test — with the operator’s own criteria, the operator’s own data, and results published only with the operator’s written approval.
Related guides
Bring the one number your systems disagree on.
The first conversation is about that number and the decision it feeds — not a demo.
Request a 30-Minute Assessment