> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/getting-started/tutorial-using-analytics-dashboards.md).

# Tutorial: Using Analytics Dashboards

### Overview

Dashboards summarize delivery signals into a single view.

This tutorial opens one dashboard and applies filters for review.

### Key Concepts

* **Dashboard**: curated set of widgets for a reporting purpose
* **Widget**: chart or metric backed by Project data
* **Filter**: constraint applied to focus a review

### How It’s Used

Use dashboards during weekly governance.

Use dashboards to align stakeholders on progress and risk.

### Benefits

* Faster status reviews
* Consistent reporting across Projects
* Earlier visibility into slippage and blockers

### Setup Steps

{% stepper %}
{% step %}

### Open Analytics

1. Navigate to **Analytics**.
2. Select **Dashboards**.
   {% endstep %}

{% step %}

### Select a dashboard

1. Open a dashboard aligned to the review purpose.
2. Confirm the dashboard scope matches the intended Project.
   {% endstep %}

{% step %}

### Apply filters

1. Apply one filter at a time.
2. Validate widget updates after each filter change.
3. Clear filters after the review.
   {% endstep %}

{% step %}

### Share the output (optional)

1. Capture a link or export when supported.
2. Include filter context in the summary message.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Review one dashboard consistently for trend comparability.
* Keep filters consistent across reporting cycles.
* Pair dashboard review with a saved work list for follow-up.

### Summary

Related:

* [Getting Started with Analytics](/analytics/getting-started-with-analytics.md)
* [Dashboards](/analytics/dashboards.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/getting-started/tutorial-using-analytics-dashboards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.