What is Data Lineage?

Company data & APIs
Data quality & provenance
3 min read

The short answer

Data lineage tracks the path of data through sources, transformations and destinations.

Data Lineage: why it matters

Automated company-data workflows need clear meanings and traceable transformations. An operation that runs successfully can still produce a result that is unsuitable for the intended business question.

How to assess it in practice

Record how a field changed across systems so errors can be traced beyond the latest displayed value. Start by defining the question the team needs to answer. Identify the relevant record or evidence, check its scope and date, and retain the reasoning behind the result. If evidence conflicts, keep that conflict visible for review.

Worked example

Illustrative workflow: a team reviewing a business adds a separate check for data lineage. The reviewer’s task is to record how a field changed across systems so errors can be traced beyond the latest displayed value. The outcome is recorded together with the supporting evidence; an unresolved question stays open rather than being converted into a positive result.

Illustrative scenario

A risk ratio changes after a mapping update. The lineage record identifies the revised input field and calculation version rather than leaving an unexplained score movement.

Distinctions that matter

Data Lineage belongs to the data quality & provenance topic family. Read Data Provenance alongside it to understand the adjacent question. Each page has its own intended scope; shared context does not make the concepts equivalent.

Evidence and review output

Review these

Relevant quality dimension
Population and comparison basis
Source and transformation context

The review should produce

A quality finding with an interpretable method, affected records and a remediation owner rather than an unexplained overall score.

Across this family

Quality has several dimensions and must be assessed for the intended use case. Filled fields can be inaccurate, recent retrieval can hide old evidence and a single source label can obscure transformations. Measure the dimension actually needed by the decision and retain its scope.

A note from practice

Lineage should explain transformations and dependencies between source and output. Record field mappings, calculation versions and joins so a downstream value can be traced and reproduced.

Limits and common mistakes

The practical boundary is important: Record how a field changed across systems so errors can be traced beyond the latest displayed value. Do not substitute a related label for this check or assume that missing information is a negative finding. Source-specific and jurisdiction-specific rules require their own review.

Frequently asked questions

Which evidence should I review?

For this topic, focus on relevant quality dimension, population and comparison basis, source and transformation context. The relevant source and dates should be retained with the finding.

How is Data Lineage different from Data Provenance?

Data provenance records where information came from and how it was obtained or transformed. The distinction matters because the evidence needed for that concept may not resolve the question addressed on this page.

What should the result of the review contain?

A quality finding with an interpretable method, affected records and a remediation owner rather than an unexplained overall score. Preserve material conflicts instead of replacing them with an unexplained success flag.

Continue learning

Explore Data quality & provenance

See the registry record behind every answer.

Primary, government-sourced data on 600M+ companies in 200+ countries, with full source attribution.

Book a demo Talk to us