> 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/analytics/dashboards.md).

# Dashboards

### Overview

Dashboards provide a quick view of key metrics.

They support recurring governance reviews and stakeholder updates.

{% hint style="info" %}
Screenshot placeholder: dashboard with 3+ widgets and a visible date range/filter.
{% endhint %}

### Key Concepts

* **Dashboard**: collection of widgets aligned to a review purpose
* **Widget**: metric or chart backed by Project data
* **Filter**: constraint that focuses the dashboard view

### How It’s Used

Use dashboards for weekly status reviews.

Use filters to shift from portfolio view to a single Segment or Process.

### Benefits

* Faster governance reviews
* More consistent reporting across Projects
* Earlier visibility into blocker and overdue signals

### Setup Steps

{% stepper %}
{% step %}

### Select the review purpose

Define the recurring question the dashboard answers, such as delivery readiness or blocked work.
{% endstep %}

{% step %}

### Create a baseline dashboard

Create one shared dashboard as the default for the Organization or line of business.
{% endstep %}

{% step %}

### Add a small set of widgets

Start with 3–6 widgets. Expand only after definitions are stable.
{% endstep %}

{% step %}

### Apply filters consistently

Apply filters such as Segment, Process, or date window to keep comparisons valid.
{% endstep %}
{% endstepper %}

### Best Practices

* Keep one baseline dashboard per line of business.
* Keep widget definitions stable to protect trend comparability.
* Pair dashboards with Save Views for follow-up actions.

### Summary

Subpages:

* [Creating Custom Dashboards](/analytics/creating-custom-dashboards.md)
* [Dashboard Widgets](/analytics/dashboard-widgets.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 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://help.transform.ai/analytics/dashboards.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.