# Operator data governance: worked example

Updated 2026-10-15

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.

The Operator-Controlled Operating 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.

One synthetic community; Days 1–7. Source assertions are retained. The sequence below is an implementation checklist, not the technical architecture.

Decision → Definition → Authoritative source → Reconciliation rule → Approver → Lineage

## End-of-day physical census

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.

Authority/evidence: Census event ledger + absence events; CEN-EXPORT-01; ABS-01; ABS-02.

Rule: 98 + (-2) = 96 residents. Competing reading: 96.

Explanation: The property roster includes two absent residents. Verified absence events explain the difference; billing eligibility is not changed.

Proposed accountable role: Regional operations lead. No real named approval exists in this scenario.

Acceptance: 98 distinct roster IDs, two documented absences, matching cut-off and no unresolved identity exceptions.

Lineage: preserve all exports, matched rows, v1 definition and rule, original readings and determination; assign a real approver and timestamp before operational use.

## Worked direct-care 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.

Authority/evidence: Approved timecards + payroll earning codes; TIME-EXPORT-01; PAY-EXPORT-01; LEAVE-01.

Rule: 840 + (-24) = 816 hours. Competing reading: 816.

Explanation: Payroll reports 840 paid hours including 24 paid-leave hours. The clock evidence supports 816 worked hours, not a payroll error.

Proposed accountable role: Workforce director. No real named approval exists in this scenario.

Acceptance: Each hour traces to a timecard or leave earning code; time windows match and no unapproved timecards remain.

Lineage: preserve all exports, matched rows, v1 definition and rule, original readings and determination; assign a real approver and timestamp before operational use.

## Net posted service revenue

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.

Authority/evidence: Posted general-ledger detail + billing credit register; GL-EXPORT-01; BILL-EXPORT-01; CREDIT-01.

Rule: 3100 + (-100) = 3000 arbitrary revenue units. Competing reading: 3000.

Explanation: Billing gross charges are 3,100 units. A posted 100-unit credit reconciles the gross billing reading to 3,000 net ledger units.

Proposed accountable role: Controller. No real named approval exists in this scenario.

Acceptance: Charge rows, posted credit and ledger control total agree; no unposted item is silently included.

Lineage: preserve all exports, matched rows, v1 definition and rule, original readings and determination; assign a real approver and timestamp before operational use.

## Cross-domain use

Do not divide seven-day labor or revenue totals by a single end-of-day census snapshot. Per-resident-day measures require a matched resident-day denominator for all seven days. No relationship here proves savings, causation, staffing adequacy or improved outcomes.

## Operator acceptance record

Named preparer: ______
Named authorized approver: ______
Approved scope and period: ______
Definition/rule versions: ______
Evidence locations: ______
Unresolved exceptions: ______
Approval timestamp: ______
Downstream recipients: ______
Superseded version: ______

Guide: https://seniorcre.com/guides/operator-data-governance-framework