A systems-of-record audit tests whether truth has a home, an owner, and a reconciliation path.
Start with the facts that matter to operating decisions: customer identity, account owner, contract value, invoice status, entitlement, product usage, employee status, vendor risk, support severity, project state. Then ask where each fact is created, changed, copied, and consumed.
For each fact, use plain questions:
- Which system is authoritative?
- Who owns the business rule?
- Which systems hold copies?
- Where are writes allowed?
- How do conflicts get resolved?
- What is the acceptable sync delay?
- What reports, workflows, or agents depend on it?
The audit should look for accidental authority. A spreadsheet that decides renewals. A workflow field that overrides CRM. A dashboard calculation treated as finance truth. A warehouse table used to correct operational systems without a defined path back.
It should also look for missing exception handling. Systems disagree. Merges go wrong. Integrations fail. Customers have weird hierarchies. The question is whether those cases have an owner and a place to be resolved.
Keep the output concrete: top authority gaps, risky bidirectional syncs, duplicate master records, unclear write paths, stale copies, and workflows that rely on unofficial truth. Rank them by operating damage, not architectural neatness.
The audit is successful when people know where to fix facts instead of arguing about which screen to believe. That is the systems-of-record job.
This is part 10 of 10 in Systems of Record.
