Service 02 — trace one number, account for every copy.
Data audits
Find the number everyone trusts until the meeting starts.
We follow a critical figure from the system that made it to the person who acts on it. Every extract, transform, cache, spreadsheet, definition, and owner goes on the record. The result is a practical answer to what can be trusted, what costs too much, and what should disappear.
The work
Follow the evidence, not the architecture slide.
An audit begins with one consequential number or dataset. Narrowing the question lets us inspect the real path deeply enough to expose the patterns affecting the rest of the platform.
01
Choose the decision
Name the number, who reads it, what action it changes, and the consequence of it being stale, incomplete, or differently defined.
02
Trace every hop
Walk backward through dashboards, semantic layers, marts, warehouse tables, stages, extracts, APIs, and source systems. Each copy gets a purpose, owner, freshness, and cost.
03
Test the claims
Compare definitions, grains, joins, keys, null behavior, row counts, freshness, access, and deletion behavior against the source and the decision it is meant to support.
04
Price the disagreement
Separate necessary boundaries from accidental duplication, then quantify storage, compute, egress, reconciliation effort, security surface, and decision risk.
What you leave with
Tangible, not theatrical
Copy inventory
A record of where the data lives, why each copy exists, who owns it, how fresh it is, and which consumers depend on it.
Source-of-truth map
A defensible path from origin to decision, with definitions, transformations, and boundaries written plainly enough to challenge.
Cost and risk findings
The operational, financial, compliance, and decision consequences attached to each unnecessary or uncontrolled copy.
Removal sequence
A prioritized plan to consolidate, retire, repair, or contract the highest-cost disagreements without breaking downstream work.
The xerocopy difference
Fewer places to be wrong.
A conventional audit often produces a maturity score and a longer shopping list. xerocopy produces a shorter list of truths. We ask whether every copy can defend its existence and whether a specific person can answer for it.
The recommendation is allowed to be deletion. A table can be retired, a pipeline replaced by a view, a metric definition narrowed, or an owner made explicit. The goal is not to make the diagram more impressive. It is to make disagreement more expensive to introduce.
If five copies answer the same question, you do not have redundancy. You have five chances to be confidently wrong.