> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-device-management/verifone-central/rollouts/monitor-estate-wide-rollouts/rollout-dashboard-kpis.md).

# Rollout dashboard KPIs

Use rollout KPIs to assess rollout health and progress.

<div data-with-frame="true"><figure><img src="/files/CVX8AL2L8cGXR1eTmeVk" alt=""><figcaption></figcaption></figure></div>

### When to use this page

Use this page when you need a quick summary of rollout health across devices.

Use it to spot failures, confirm progress, and check the current success rate.

### KPI definitions

* **FAILED** — devices that failed to download or install the software. This count includes **Download failed** and **Installation failed**.
* **SUCCESSFUL** — devices where the package was installed successfully.
* **IN PROGRESS** — devices with rollout jobs that have started but are not yet complete.
* **NOT YET STARTED** — devices with rollout jobs that are scheduled but have not started yet.
* **SUCCESS RATE** — the percentage of rollout jobs that completed successfully.

### Use this dashboard to

* track rollout progress
* identify failures
* measure completion rates

### Interpret the KPIs

Use these quick checks:

* a high **FAILED** count means you should inspect rollout details and affected devices
* a large **IN PROGRESS** count means the rollout is still moving through the estate
* **SUCCESS RATE** helps you judge whether the rollout is completing at the expected level

### Related pages

* [Monitor estate-wide rollouts](/verifone-central-device-management/verifone-central/rollouts/monitor-estate-wide-rollouts.md) — inspect rollout and batch status
* [Managing rollouts](/verifone-central-device-management/verifone-central/rollouts/managing-rollouts.md) — take action on rollout jobs


---

# 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.verifone.com/verifone-central-device-management/verifone-central/rollouts/monitor-estate-wide-rollouts/rollout-dashboard-kpis.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.