Data Lineage and Audit Trail
Data lineage traces each reported number back through runs, snapshots, transformations, and raw sources for full auditability.
Explanation
An audit trail connects reported risk or P&L figures to the underlying runs, including snapshot IDs, model IDs, and library versions.
Snapshots and models themselves link back to transformation configurations and raw data snapshots from external vendors.
Lineage enables auditors and model risk teams to reconstruct how a number was produced and challenge each step if necessary.
A robust lineage system supports governance, reduces dispute resolution time, and builds trust in a central analytics framework.
lineageauditgovernancetraceability
Interactive visualisation
Data lineage and audit trail
A reported number should link back through runs, snapshots, transforms, and raw sources. Click nodes to inspect metadata.
Lineage depth
Depth
3
Completeness
100% of expected metadata present (toy scoring).
Interpretation
- Lineage is not “nice to have”. It is what makes numbers auditable.
- A run without snapshot/model/version is not reproducible.
- “Challengeability” comes from being able to replay each step.
Lineage tree
click a node
Metadata
Reported number
key
INFO
metric: VaR(99%)
key
INFO
date: 2026-02-01
key
INFO
desk: Rates
In production you want immutable IDs + checksums + config hashes so every step is replayable.