How operators govern data across multiple systems: a runbook
Operators govern data across multiple systems by deciding, before the next disagreement, which definition applies, which system is authoritative for each field, what rule settles conflicts, who approves it, and what evidence is retained. Start with one decision exposed to a disputed number and work it through those six steps.
Written by SeniorCRE Governance Desk · Reviewed by John Hauber, Founder, SeniorCRE, LLC · Updated October 12, 2026
The Governing Record is designed and not yet implemented in any community. These guides describe a governance method an operator can apply with or without SeniorCRE; they make no deployment or outcome claim.
The six steps
Decision → Definition → Authoritative source → Reconciliation rule → Approver → Lineage
01 · Decision
Which decision is exposed when systems disagree?
Start from one consequential decision, not from a system inventory. Name the decision, who makes it, how often, and what it costs to make it on a contested number. Census, labor and financial reporting are the usual first candidates.
02 · Definition
What exactly does the number mean?
Write one versioned definition for the metric the decision depends on: numerator, denominator, cut-off time, inclusions and exclusions. A definition that cannot be reproduced from source rows is not yet a definition.
03 · Authoritative source
Which system is allowed to be right, for this metric, entity and period?
Declare authority per field, not per vendor. The property management system may govern unit status while the clinical record governs discharge timing. Record the declaration where every downstream report can read it.
04 · Reconciliation rule
What happens when valid sources disagree?
Write the rule once, before the next disagreement: the tolerance, which source prevails beyond it, and what happens to the reading that does not prevail. Reconcile once under governed rules; stop re-reconciling downstream.
05 · Approver
Who accepted the definition and the rule?
Assign a named accountable role to approve each definition and rule, with a timestamp. Changes go back through the same approver, so a new version is a governed event rather than a quiet edit in a spreadsheet.
06 · Lineage
Can the governing value and the decision be reconstructed later?
Retain every source reading, the definition version, the rule and the approval. Lineage is what lets a lender, surveyor or board member ask "why this number?" and get an answer without a rebuild.
Illustrative example
One occupancy figure, three defensible readings
- Property management — Unit released on move-out day87.4% occupancy
- Clinical record — Unit held until discharge closed88.1% occupancy
- Billing calendar — Billed days, third calendar86.9% occupancy
- Decision
- Which occupancy figure goes into the weekly ownership report and the staffing plan for the coming week.
- Definition
- Occupancy v4: occupied licensed units divided by available licensed units at 11:59 p.m. local time on the last day of the reporting week, versioned and approved.
- Authoritative source
- Property management system, for unit status.
- Reconciliation rule
- When the property management move-out date and the clinical discharge date differ by more than 24 hours, defer to the clinical discharge date.
- Approver
- A named accountable role (for example, the regional VP of operations), recorded with a timestamp.
- Lineage
- All three readings (87.4%, 88.1%, 86.9%) retained unaltered, together with the definition version, rule and approval, so the governing value can be replayed later.
Illustrative governance example. Figures are design intent, not operator results, customer deployments, production performance, or verified outcomes.
Run it on one disputed number first
Pick one census, labor or financial discrepancy, establish the definition and decision authority, and define the evidence required to demonstrate the governing workflow. Extend to the next metric only after the first is approved.
Related implementation guides
Review and change history
Author: SeniorCRE Governance Desk. Reviewer: John Hauber, Founder, SeniorCRE, LLC.
- — First published. Structured around decision, definition, authoritative source, reconciliation rule, approver and lineage, using the illustrative occupancy example from /operating-record.