Documentation and Lineage for Analytics Engineers
Documentation and lineage in dbt means describing models and columns in YAML, generating a searchable docs site, and using the dependency graph to see where data comes from and what depends on it. Column-level lineage extends this to individual fields for impact analysis.
Stage: dbt in Depth · Part of the Analytics Engineer roadmap · Last reviewed 19 November 2026
What to learn in Documentation and Lineage
- Write model and column descriptions in a YAML file
- Generate and browse the dbt docs site
- Use doc blocks to reuse long descriptions
- Read the lineage graph to find affected downstream models
- Explain what column-level lineage adds over model-level lineage
Documentation and Lineage interview questions
How does dbt generate lineage?
Each ref and source call in a model records a dependency. dbt assembles these into a directed acyclic graph that shows upstream and downstream relationships, and the docs site displays it for any model.
Why document columns and not only models?
Column descriptions explain meaning, units and edge cases that names cannot, which prevents misuse and repeated questions. Tests and descriptions together act as the contract between modellers and consumers.
Where Documentation and Lineage fits in the Analytics Engineer roadmap
Documentation and Lineage belongs to the dbt in Depth stage (intermediate level), which takes about 7 hours. The core craft.
Other units in this stage
Back to the full Analytics Engineer roadmap