Operator playbook
Audit Trails and Lineage: Tracing Every Figure to Its Source Record
How operators capture data lineage and audit trails across multiple platforms so every reported figure traces to its source records and approvals.
Download the checklistOperators make figures traceable by recording lineage — the source system, records, definition and reconciliation behind each reported figure — and by keeping an audit trail of every change to governed values: previous value, new value, user, time and reason. When anyone asks how a number was produced, the answer is a lookup rather than a reconstruction.
Part of How Operators Govern Data Across Multiple Systems, the six-step operator data governance playbook.
Section 01
Why it matters
A board member asks why last quarter's occupancy changed between two reports. A lender asks how agency spend was calculated. A surveyor asks who changed a care record. In many organizations, each question starts an investigation that depends on who still remembers.
Lineage and audit trails make those answers routine. Lineage explains how a figure was built. The audit trail explains how the underlying records changed. Together they let an operator show its work.
SeniorCRE calls the governed record of that work the Operational Evidence Layer: a layer over existing systems where each figure carries an Evidence Card showing its sources, definition, reconciliation state and approvals. The concept matters more than the product name — any operator can begin capturing lineage with the steps below.
Section 02
How to do it
Step 1
Decide which figures need lineage
Start with figures that leave the building: owner, lender, board and regulatory reporting. Expand to internal dashboards later.
Step 2
Record the build path
For each figure, capture the source systems and records, the dictionary definition applied, the reconciliation it passed and the period it covers.
Step 3
Collect audit logs from each system
Bring view and change logs for governed fields into one reviewable record. Contracts should guarantee access to them.
Step 4
Require a reason for changes
Changes to governed values after close should carry a reason and an approver, not only a user and time.
Step 5
Test traceability
Each quarter, pick a reported figure at random and trace it to source records. Record how long it took against your target: [time placeholder].
Section 03
Working template
| Element | Example content |
|---|---|
| Figure | Occupancy, Community [A], [period] |
| Definition | Dictionary entry [ID], effective [date] |
| Sources | Census system records; billing records for comparison |
| Reconciliation | Passed within [tolerance]; breaks [number] closed |
| Approval | Steward review; owner approval at close |
| Changes since close | None, or adjustment [ID] with reason and approver |
Source: SeniorCRE illustrative template with placeholders. No operator data shown.
Section 04
Common failure modes
- Lineage in a personal spreadsheet. When the analyst who built it leaves, the organization loses the ability to explain its own numbers.
- Logs nobody can read. Audit logs held only by the vendor, in formats the operator cannot query, are not a control.
- Changes without reasons. A log that records who and when but not why cannot answer the question auditors actually ask.
Section 05
Frequently asked questions
Section 06
Continue the playbook
Next step
Scope a governance program around the systems you run today.
SeniorCRE · Operator playbook · Guide 5 of 6 · Updated October 20, 2026