# impact analysis, defined with a sourced example

GLOSSARY, read 10 Nov 2026

**The short answer.** Checking what will be affected before a change ships, by walking downstream from the thing you plan to alter. It answers which models, dashboards and users depend on a column you want to rename or drop. Some tools run it automatically on code changes. Foundational runs impact analysis in CI on pull requests and can block a merge.

## Definition

Checking what will be affected before a change ships, by walking downstream from the thing you plan to alter. It answers which models, dashboards and users depend on a column you want to rename or drop. Some tools run it automatically on code changes.

## Example from a real tool

**Example.** Foundational runs impact analysis in CI on pull requests and can block a merge.

## Related terms

- [root cause analysis](/glossary/root-cause-analysis/): Working backward from a bad number or failed check to the step that caused it.
- [lineage graph](/glossary/lineage-graph/): The network of assets and the links between them that a lineage tool builds.
- [downstream](/glossary/downstream/): Everything that depends on a given asset: the tables, dashboards and models that come after it.

## Where to read more

- [The Lineage Depth Matrix](/matrix/)
- [All glossary terms](/glossary/)

## Sources

- docs.foundational.io/en/articles/12802881-solution-architecture.md: https://docs.foundational.io/en/articles/12802881-solution-architecture.md (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalineagecompare.com/glossary/impact-analysis/
