> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/inventory/lineage/how-to-use-lineage-effectively.md).

# How to: Use Lineage Effectively

We recommend the following best practices:

* Always check lineage before deleting assets
* Start investigations from Inventory → Asset → Lineage
* Use health tags + lineage together for prioritization
* Focus on assets with:
  * High downstream impact
  * Low usage (high cleanup ROI)

### Use Case: Impact Analysis

Before changing a dataset:

* Check downstream assets
* Understand how many reports will break
  * See if there is any activity on the reports
  * Look at the health signals of the report
* Start a [workflow](/guides/workflows.md) to notify the owners and other stakeholders of the dataset and report.

### Use Case: Cleanup & Cost Reduction

Go to Inventory and filter on unhealthy assets. Specifically, look for:

* Unused reports built on active models
* Models with no downstream usage

Then:

* Start a [workflow](/guides/workflows.md) to notify the owners and other stakeholders of the dataset and report.
* Archive or delete safely

### Use Case: Root Cause Analysis

If a report is broken:

* Trace upstream dependencies
* Identify whether the issue originated in the BI tool or further upstream


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.datalogz.io/guides/inventory/lineage/how-to-use-lineage-effectively.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.