01Shared definitions
The metric means the same thing across communities and reporting periods.
- Financial analogue
- A chart of accounts and an accounting policy manual
Loading...
What separates an operator that capital extends from one it merely renews: the ability to show which number governs, who decided, and how it can be traced — before anyone asks.
The institutional question is not only "How are the communities performing?" It is "Can we trust the operating truth quickly enough to make capital decisions from it?"
Capital scales with operators on confidence, not on performance alone — confidence in the numbers, the definitions behind them, the decisions made from them, and the operator accountable for them.
Integration can move data. Analytics can summarize it. AI can interpret it. None of those actions, by itself, establishes which source has authority when valid systems disagree. That determination is a governance act, and it belongs to the operator — not to a vendor, an integration rule, or a model.
Finance leadership already recognizes each of these in another form. The controls describe the operating record, not a product: an operator can begin establishing them with the systems it runs today, and can later choose to deploy SeniorCRE for selected system-of-record functions.
The metric means the same thing across communities and reporting periods.
The organization knows which system or human authority governs for a defined metric and context.
Conflicts are surfaced, resolved against written rules and documented rather than silently averaged or overwritten.
An executive can trace the number, the exception, the approval and the decision path.
AI can inform or execute only inside defined authority and escalation boundaries.
The same discipline can be deployed across portfolios, owners and new assignments.
The analogues are offered to make the standard legible to finance leadership. Operating controls are not subject to the same statutory regime as financial controls.
1 — Reported
Each system reports its own number; the package reconciles by hand; institutional memory holds the method.
Correct-looking answers, slowly; recurring questions; quiet discounting of every figure.
Written definitions for the metrics that most often require explanation
2 — Defined
Definitions are written and shared, but source authority is still negotiated in the moment.
Fewer definitional disputes; conflicts still resolved by whoever is closest to the package.
Source authority assigned by metric and context, in advance
3 — Governed
Definitions, authority and reconciliation rules are established; exceptions and approvals are recorded; lineage is retained.
Answers with the evidence path attached; variance explained by cause; faster cycles.
The same standard applied across every community and owner, with AI bounded by explicit authority
4 — Institutional
The governed record is repeatable across portfolios and assignments; AI workflows operate inside defined decision rights; the whole chain can be evidenced on demand.
Confidence to extend, assign and scale; diligence becomes confirmation rather than discovery.
—
Levels describe governance posture, not software. An operator can reach Level 2 with no new technology, and cannot reach Level 4 with technology alone. Most organizations sit at Level 1 or 2 with pockets of Level 3 in whichever domain an executive has personally disciplined — usually finance. The gap is that the discipline lives in people rather than in a record, and people do not scale to the next portfolio.
Why does occupancy in your package differ from the rent roll?
Definitions; source authority
The definition in force, the designated source for that metric and context, and the reconciliation to the rent roll with each difference classified.
Walk me from this NOI number back to the communities.
Lineage
A traceable path from the portfolio figure through community figures to source values, rules and approvals.
Is this variance a business change or a reporting change?
Definitions; reconciliation
Changed conditions separated from changed definitions, timing rules or source conflicts, by community.
Who signed off on this, and when?
Human authority; approvals
The named authority, the timestamp and the basis of approval, retained with the number.
How do you know acuity-driven labor is under control?
Care-to-labor linkage
Care-plan-derived staffing requirements against scheduled and worked hours, with exceptions flagged for review.
If we gave you six more communities, what would change?
Repeatability
The same definitions, authority assignments and reconciliation rules applied to new communities without rebuilding the reporting process.
What is your AI doing with our data?
Human authority; boundaries
Which workflows are read-only, which are human-approved, which are excluded, and the record each one reasons from.
If we changed operators, would our data come with us?
Ownership; portability
The operator’s own data-ownership and export commitments, alongside the published commitment to free export at termination and no exit tolls.
A synthesis of recurring owner questions. The third column describes what a governed record is designed to make available; it is not a representation of any operator’s current production state.
An owner who can stop asking the questions in the first column has already decided to send the next community.
Which operating metrics most often require explanation or reconciliation with ownership — and do we know why?
What a yes showsSelf-awareness about where truth is contested
When two systems disagree, is source authority predetermined, or negotiated in the moment by whoever is closest to the package?
What a yes showsAuthority by design, not by proximity
Can an executive trace a reported number back through definition, source, exception and approval without calling the person who built it?
What a yes showsLineage that survives staff turnover
Which decisions are consequential enough that AI should never act without explicit human authority — and is that written down anywhere?
What a yes showsA control environment that AI extends rather than escapes
Could the same governance standard be deployed across a new portfolio without rebuilding the reporting process from scratch?
What a yes showsReadiness for the next assignment
An Operator-Controlled Operating Record isn't valuable merely because the record is governed. It is valuable because the operator can demonstrate its governance to the capital entrusted to it.
Demonstrate a repeatable control model for operating truth during owner evaluation and onboarding, rather than reconstructing one under deadline.
Reduce the friction of recurring questions by making definitions, exceptions and lineage visible before they are asked.
Separate a changed business condition from a changed definition, timing rule or source conflict — and defend the forecast on that basis.
Give decision-makers a more defensible operating basis for capex, refinancing and growth discussions.
Apply the same governance discipline as additional communities or owners are taken on, without a new reporting build each time.
Establish authority and human decision rights before automating consequential operating workflows, so AI extends the control environment rather than escaping it.
The proposition is deliberately modest. Stronger operating governance can strengthen an operator’s institutional posture. It does not guarantee additional assignments; no infrastructure does. It can make an operator easier to diligence, easier to monitor and easier to scale with.
Nor does governance align interests. Owner and operator are paid differently, and on the expense line they can reasonably want different things; no operating record removes that. What governance removes is the argument about the facts, so the conversation between owner and operator can be about what to do rather than which number is right.
1 — Inventory
List the ten metrics that consumed the most reconciliation time last year. For each, write the definition in force today — or discover that there are three.
The owner sees: An operator that knows where its own truth is contested
2 — Assign
For each metric, designate the authoritative source by context and the human authority who approves exceptions. Put it in writing and share it with the owner. For the metrics that decide who gets paid — revenue occupancy, incentive-fee NOI, covenant figures — agree the definition with the owner, and change it only when both agree.
The owner sees: Source authority predetermined rather than negotiated — and the numbers the owner is paid on agreed rather than asserted
3 — Evidence
Deliver one monthly package with the evidence path attached for those ten metrics: definition, source, reconciliation, approval. Ask the owner which questions it no longer needs to ask.
The owner sees: Answers that arrive with their lineage — and the basis for extending the standard
Deliberately technology-independent. An operator that completes these three moves has established the governance that any operating record, including SeniorCRE’s, is designed to make durable and repeatable.
Exhibit · Operating record governance
Senior housing & care operators typically run 6–12 disconnected systems, each correct inside its own boundary.
When systems disagree, the operator governs.
Section 01 · Govern the operating record
Not six universal conflicts. Priority and source authority are set by the operator.
| Domain | Assertions to distinguish |
|---|---|
| Available capacity | Licensed capacity, rentable inventory, care configuration, out-of-service units |
| Move-in / move-out | Lease date, care start or end, billing start or end, physical presence |
| Agency labor | Scheduled coverage, worked time, submitted hours, invoiced cost |
| Resident days | Clinical presence, billable days, budget assumptions |
| Rate / RevPOR | Quoted, contracted, and charged rates; approved resident-day basis |
| Care levels | Clinical assessment, regulatory category, operator pricing tier |
A documented rule reduces debate. It does not eliminate change or new evidence.
| Measure | Define before use | Review when |
|---|---|---|
| Occupancy | Resident, unit, or bed basis; usable capacity; period | Capacity or availability changes |
| NOI / EBITDAR | Included accounts, exclusions, adjustments, purpose | Accounting policy or contract changes |
| Labor hours / FTE | Scheduled, worked, paid, or invoiced basis | Pay rules or coverage models change |
| Residents / occupied units | Two different objects; label and calculate separately | Unit configuration or resident status changes |
Governance first. Intelligence second. Execution last.
Definition · Authority · Reconciliation · Lineage
Section 02 · The authority chain
Preserve what each system asserted: source, time, scope, lineage.
Expose competing assertions and gaps.
Apply operator-declared authority through the Operator Authority Chain™.
Hold the determination, rationale, status, and supersession.
Reason within the governing scope: what moved, why, what to do.
Act only within granted authority.
Design intent
Bound one consequential disagreement, govern its value, then analyze what moved and why. Expand only after agreed evidence gates clear.
Status: pre-production. The Operator-Controlled Operating Record is designed, not yet implemented in any community; no third-party integration is live in operator production. Illustrative categories; no integrations or vendor shortcomings are asserted.
The same twelve tests an institutional owner would apply in diligence, run against your own organization. None of them requires inspecting a system, and nothing you enter is submitted or stored.
Connected systems provide broader context. Interoperability moves information across workflows. AI can organize that information and support human judgment. Responsible AI 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 context 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 context 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
Connected context contains 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 built; external operator deployments have not yet begun. 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.
Systems hold facts. Decision layers organize evidence. The Operator-Controlled Operating Record establishes what has authority to govern.
Where authority sits
Enterprise context 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 context
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 → GOVERNING RECORD → INTELLIGENCE → EXECUTION. Enterprise context strengthens DATA. Operator authority is what produces TRUTH. When systems disagree, the operator governs.
AI 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.
AI can reason. The operator governs.
An owner requires a standard of governance and evidence. It does not select the operator’s software stack.
The institutional question is not only "How are the communities performing?" It is "Can we trust the operating truth quickly enough to make capital decisions from it?"
The standard the owner is entitled to state is published in full, so an operator can read it before it is applied to them. Deployment stays the operator’s choice: keep the systems you run and govern what they produce, or deploy SeniorCRE for selected system-of-record functions.
Status: the Operator-Controlled Operating Record is designed. The first community implementation is next. Evidence is published when it exists, not before.
DATA → TRUTH → DECISION → EXECUTION. Systems produce data; the operator governs which version is true; decisions are made on that governed truth; execution happens only inside authority the operator has granted. When systems disagree, the operator governs. Provenance proves where an answer came from. Authority proves why it was allowed to govern. Model confidence never creates organizational authority.
The owner specifies the standard. The operator chooses the system. The record is the operator’s. The visibility is the owner’s. Owners: see the Institutional Owner standard (seven expectations, twelve tests). Operators: see the Institutional Operator standard. Deployment detail: deployment models.
The operator owns its record and can take it with it. Our portability and ownership commitments are published in the Open Data Governance framework.
Evidence & Provenance
By showing its evidence rather than re-reconciling it. Each governed figure keeps its sources, definition version, conflicts and authorizing role, so a lender or REIT can trace it without a new spreadsheet.
The operator governs. SeniorCRE records what governs. The operating record is designed; it is not yet implemented in any community or in operator production.
See the evidence architecture