Data Lineage vs Data Provenance vs Audit Trail vs Data Catalog
Four terms that people mix up, each answering a different question about your data.
Short answer: data lineage shows the path data took and what changed along the way. Data provenance says where data came from and who made it. An audit trail is a log of actions: who did what and when. A data catalog is an inventory of the datasets you have, with descriptions and owners. They overlap, but they are not the same thing.
Data lineage: the path and the changes
Lineage answers: how did this file become this file? It lists the input, each step that changed it (converted, filtered, joined, masked), and the result. Good lineage also shows what happened to each column: kept, changed, added, renamed or dropped. See what data lineage is and column-level lineage.
Data provenance: where it came from
Provenance answers: where did this data originate, and who produced it? It cares about the source, the date and the creator. Lineage includes the source as its starting point, but provenance by itself says little about the steps in between.
Audit trail: who did what and when
An audit trail is a log of events: a person ran a job, edited a record or exported a file, at a certain time. It is about actions and people. It does not have to explain how the content of a dataset changed, and a lineage does not have to say which person did it.
Data catalog: a map of what exists
A data catalog lists datasets, their descriptions, owners, tags and sometimes quality notes, so people can find them. It is about discovery. Many catalogs show lineage as one feature, but a catalog is the inventory, not the history of one file.
A small example
A file customers.csv arrives from the sales system on 14 November. Someone converts it to Parquet, masks the email column, removes rows with no city, and joins it to orders.csv to count orders per region. The result is query_result.
- Lineage: customers.csv → convert → mask → filter → join with orders.csv → query_result, with the email column marked as masked and a new region column added.
- Provenance: customers.csv came from the sales system, exported on 14 November.
- Audit trail: Priya ran the masking at 10:05 and the query at 10:12.
- Catalog: query_result is listed as a monthly orders summary, owned by the analytics team.
Which one do you need?
- "What did you do to this file?" You need lineage.
- "Where did this data come from?" You need provenance.
- "Who changed it and when?" You need an audit trail.
- "Where can I find the right dataset?" You need a catalog.
- "Can I prove the file I am sending is the one this process produced?" You need lineage plus a fingerprint of the file.
Where Data Utility fits
Data Utility records lineage for the files you work on in its tools: the input, each step with its settings, the output with its row count, and what happened to each column. It does not keep a catalog, and it has no user accounts, so it cannot say which person did a step. It is built for the person who changes files by hand and needs to explain or prove what they did. Try the free data lineage tool and see an example.
Related tool pages
- Free Data Lineage Tool: Transform Data and Download the Lineage: Free online data lineage tool: see every step applied to a file as a graph, then download a lineage report with a checksum. Runs in your browser, no upload.
- Data Lineage Version History: Keep a version history of your data lineage and compare any two versions: steps, settings, columns and row counts. Export a report. Free and private.
- Free Data Lineage Tool: A free data lineage tool for files: transform data, see input, transformations and result as a graph, and download a shareable HTML report. No signup.
- Data Lineage Report as HTML: Download a data lineage report as one HTML page: a tree from the input file through every transformation to the result, with a SHA-256 checksum.
- Share Your Data Together with Its Lineage: Send a result file and the proof of how it was made in one ZIP: your data, an HTML lineage report and a JSON copy. Free, made in your browser.
- Data Audit Trail for CSV and Excel Files: Keep an audit trail of what was done to a CSV or Excel file: conversions, cleaning, joins and masking, with the settings used. Free, in your browser.
Also try
How to use the Data Lineage: step by step
- Run your file through the Data Utility tools you need.
- Open Data Lineage to see the path and the column changes.
- Download the result with its lineage report to share the history.
When to use the Data Lineage
- Explain data governance terms to a team
- Choose the right tool for an audit question
- Prepare for a data privacy review
- Teach students the difference between the terms
Example
Input: raw.csv
Output: raw.csv → clean → mask → final.csv
Frequently asked questions
What is the difference between data lineage and data provenance?
Lineage shows the path data took and the changes along it. Provenance focuses on where data came from and who created it. Lineage usually starts from the provenance of the source.
Is an audit trail the same as data lineage?
No. An audit trail logs actions and the people who did them. Lineage describes how the data itself was transformed. They answer different questions and are often used together.
Is a data catalog the same as data lineage?
No. A catalog is an inventory of datasets for finding and understanding them. Many catalogs show lineage as one feature, but the lineage is the history of how a dataset was made.
Do I need all four?
Not always. A team that works with files by hand often needs lineage first. Larger organizations usually need a catalog and audit logs as well.
What is column-level lineage?
It follows each column through the steps: kept, changed, added, renamed or dropped, so you can see where a value in the result came from.
Does Data Utility keep an audit trail of who did what?
No. It has no user accounts, so it records what was done to the file, not which person did it.
Is lineage useful for privacy reviews?
Yes. It can show that a personal column was masked or removed before a file was shared. Check the result against the report before you rely on it.
Tip: When someone asks "who did it?", that is an audit trail question. When they ask "what was done?", that is lineage.