Data lineage
Where did it come from?
Keep the source file, record origin, and transformation path visible.
Data systems
Trust must follow the data.
A useful number has a known source, a controlled path, a matched total, and a clear refresh time.
Visual model
Trace it. Test it. Reconcile it.
Each control answers a different trust question. Together, they make a reporting result explainable.
Data lineageReconciliationFreshness
OriginSource record
→
LineageTrack every step
→
ControlMatch totals
→
TimeCheck freshness
→
OutputTrusted view
Reconciliation
Do totals still match?
Compare counts and values before and after each important transformation.
Freshness
Is the delivery current?
Separate the business date from load recency and declared period completeness. Explore data freshness →
Control rule
Do not hide exceptions.
Keep rejected and review-required records visible outside the published total.
Where I used it
Source-to-mart and freshness evidence
Counts and GBP totals reconcile. Monitoring views retain current status, rule evidence, and run history.
View evidence →Visible record states
Accepted, review-required, and rejected records remain traceable.
View evidence →Cross-system agreement
Python and PostgreSQL outputs agree across all reviewed measures.
View evidence →