Coherence before Intelligence.
Operator data governance framework
Operators govern data across multiple systems by defining each decision-critical metric, assigning source authority by purpose and period, reconciling differences under approved rules, escalating unresolved exceptions to an authorized human, and preserving the evidence and approval behind every accepted value. Connecting systems alone does not establish authority.
SeniorCRE® Governance Desk · Educational guide · Updated
Govern the decision, not just the connection
A warehouse, integration feed or shared dashboard can align access to data. The operator still has to decide what a metric means, which evidence governs for this purpose, and who can authorize an exception. This method can be applied to retained systems with controlled documents and human review; it does not depend on a deployed SeniorCRE product.
Begin with one community and a bounded reporting period. Use authorized exports with stable entity IDs, source timestamps and access controls. Do not copy resident or employee identifiers into a broadly shared worksheet; use restricted evidence references instead.
The steps below are a practical implementation checklist, not a replacement for the seven-layer technical architecture or the executive operating sequence.
How do operators govern data across multiple systems?
Decision → Definition → Authoritative source → Reconciliation rule → Approver → Lineage
01
Start with the decision and its scope
Name the decision before choosing a metric or a platform. Limit the first exercise to one community and one reporting period.
- Required inputs
- Decision owner, community ID, reporting purpose, downstream recipients, period, local timezone and close cut-off.
- Acceptance criteria
- The owner confirms the exact decision, scope and cut-off; a reader can distinguish a snapshot from a period total.
02
Write a reproducible metric dictionary
Define numerator, denominator, units, inclusions, exclusions and effective version. Preserve legitimate departmental measures under separate names.
- Required inputs
- Existing definitions, source fields, calculation, entity keys, treatment of absences, paid leave, credits and late entries.
- Acceptance criteria
- A second analyst recomputes each metric from the same evidence and definition version with the same result; missing inputs are explicit exceptions.
03
Declare source authority by field and purpose
Assign authority to a specific source field for a defined decision, not to an entire vendor. A clinical event date and a billing date may both be valid for different purposes.
- Required inputs
- Source inventory, row IDs, extract timestamps, field mappings, source owner, authorized fallback and freshness requirements.
- Acceptance criteria
- Every governed field has a documented source and accountable owner; a missing or stale source blocks acceptance unless an authorized fallback is recorded.
04
Reconcile differences and register exceptions
Compare like periods and definitions first. Apply only an approved rule; never average conflicting values to make the disagreement disappear.
- Required inputs
- Unaltered source readings, definition versions, tolerance, matched event evidence, rule ID, exception owner and deadline.
- Acceptance criteria
- Each difference has an evidenced explanation or an open exception. An unresolved exception is not presented as an accepted number.
05
Authorize a determination through the RACI
Separate preparation from authority. One accountable role decides whether a value may govern; accountable roles must be assigned to real people before use.
- Required inputs
- Responsible preparer, accountable approver, consulted domain owners, informed consumers, delegation scope and conflict-of-interest policy.
- Acceptance criteria
- The authorized approver records the determination, rationale, effective period and timestamp. Escalations follow a named delegate or remain unresolved.
06
Preserve lineage and test downstream use
Keep original assertions, the governing determination and any later restatement together. Propagate the approved version identifier to downstream reports.
- Required inputs
- Source references, definition and rule versions, approval record, supersession link, recipient list and access/retention policy.
- Acceptance criteria
- An independent reader can reconstruct the figure and approval without editing originals; a restatement retains both versions and notifies affected recipients.
Five working documents
Use the populated synthetic rows to understand the structure; replace them with approved operator definitions and evidence. Named holders, approval timestamps and actual exception deadlines remain blank. RACI means Responsible, Accountable, Consulted and Informed.
- CSV
Metric dictionary
Definitions, units, scope and evidence fields.
- CSV
Source-authority matrix
Authority by metric and decision purpose.
- CSV
Reconciliation exception register
Differences, rationale, owner and approval fields.
- CSV
Approval RACI
Preparation, authorization and escalation roles.
- Markdown
Worked census, labor and revenue example
Reproducible arithmetic and a blank acceptance record.
| Task | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
| Approve metric definition and purpose | Metric steward | Domain executive | Operations, workforce, controller | Report consumers |
| Declare source and fallback authority | Source owner | Domain executive | IT/data custodian, metric steward | Analysts |
| Prepare reconciliation evidence | Analyst | Metric steward | Source owners | Domain executive |
| Authorize unresolved determination | Metric steward | Authorized domain executive | Affected source/domain owners | Report consumers |
| Approve closed-period restatement | Metric steward | Authorized domain executive | Controller, affected decision owners | All prior recipients |
Synthetic training scenario
One community. Three metrics. Three determinations.
Synthetic training scenario, not an operator result, product demonstration, staffing recommendation or financial forecast. All source IDs, counts, hours, revenue units and role approvals below are invented. Revenue uses arbitrary units, not currency.
Scope: one invented community, synthetic Days 1–7. Census is a Day 7 snapshot; labor and revenue are seven-day totals. Proposed role approvals below illustrate the method and are not real sign-offs.
CEN-01 · Synthetic
End-of-day physical census
Source assertion
98
Evidenced adjustment
-2
Illustrative determination
96
residents
- Decision
- Accept 96 for the physical-census report; retain 98 as the separately labeled roster count.
- Definition v1
- Distinct residents physically present at 23:59 local time on synthetic Day 7; excludes two temporary absences. Not billed census or licensed-unit occupancy.
- Source authority and evidence
- Census event ledger + absence events · CEN-EXPORT-01; ABS-01; ABS-02
- Reconciliation rule
- The property roster includes two absent residents. Verified absence events explain the difference; billing eligibility is not changed. The competing reading is 96 residents.
- Proposed approver
- Regional operations lead; a real named holder and timestamp are required before operational use.
- Acceptance criteria
- 98 distinct roster IDs, two documented absences, matching cut-off and no unresolved identity exceptions.
- Lineage
- Retain the original exports and readings, matched source IDs, definition v1, rule version, rationale and approval. A revised determination references the original rather than replacing it silently.
LAB-01 · Synthetic
Worked direct-care hours
Source assertion
840
Evidenced adjustment
-24
Illustrative determination
816
hours
- Decision
- Accept 816 for worked-hours analysis; preserve 840 for paid-hours reconciliation. No staffing or clinical sufficiency inference.
- Definition v1
- Approved direct-care clock hours during synthetic Days 1–7; excludes paid leave. Paid hours and scheduled hours remain separate metrics.
- Source authority and evidence
- Approved timecards + payroll earning codes · TIME-EXPORT-01; PAY-EXPORT-01; LEAVE-01
- Reconciliation rule
- Payroll reports 840 paid hours including 24 paid-leave hours. The clock evidence supports 816 worked hours, not a payroll error. The competing reading is 816 hours.
- Proposed approver
- Workforce director; a real named holder and timestamp are required before operational use.
- Acceptance criteria
- Each hour traces to a timecard or leave earning code; time windows match and no unapproved timecards remain.
- Lineage
- Retain the original exports and readings, matched source IDs, definition v1, rule version, rationale and approval. A revised determination references the original rather than replacing it silently.
REV-01 · Synthetic
Net posted service revenue
Source assertion
3,100
Evidenced adjustment
-100
Illustrative determination
3,000
arbitrary revenue units
- Decision
- Accept 3,000 for this defined net-posted metric. The controller must separately approve real accounting treatment.
- Definition v1
- Posted service charges less posted credits for synthetic Days 1–7; excludes cash receipts and unposted estimates. Illustrative units only, not an accounting policy.
- Source authority and evidence
- Posted general-ledger detail + billing credit register · GL-EXPORT-01; BILL-EXPORT-01; CREDIT-01
- Reconciliation rule
- Billing gross charges are 3,100 units. A posted 100-unit credit reconciles the gross billing reading to 3,000 net ledger units. The competing reading is 3,000 arbitrary revenue units.
- Proposed approver
- Controller; a real named holder and timestamp are required before operational use.
- Acceptance criteria
- Charge rows, posted credit and ledger control total agree; no unposted item is silently included.
- Lineage
- Retain the original exports and readings, matched source IDs, definition v1, rule version, rationale and approval. A revised determination references the original rather than replacing it silently.
Do not mix denominators across domains
Seven-day worked hours and net revenue cannot be divided by one end-of-day census snapshot to create a valid per-resident-day measure. Obtain the matched resident-day total for all seven days, approve its definition and exclusions, and preserve that denominator’s evidence. These reconciliations do not establish causation, savings, staffing adequacy or patient-outcome improvement.
When may the number govern?
Only after the operator accepts the definition, evidence, reconciliation and determination for the stated purpose and period. A plausible number or a low variance is not approval.
- All required inputs are present, access-authorized and within the operator’s declared freshness window.
- A second analyst reproduces the value using the recorded versions and source rows.
- Every material difference is explained or remains visibly unresolved; unresolved values do not govern.
- The named accountable person records scope, rationale and an approval timestamp.
- Downstream readers receive the accepted version and can reconstruct its lineage; restatements retain and reference prior versions.
The operator sets tolerances, deadlines, retention and delegation rules. This guide supplies no universal production thresholds, implementation timeline or guarantee. Track exception counts and resolution time only after defining the measurement method and baseline.
From definition to operating practice
- Read the Operator-Controlled Operating Record doctrine
- What is a governed operating record?
- Apply the existing cross-system runbook
- Read the definition-and-authority register guide