> ## Documentation Index
> Fetch the complete documentation index at: https://help.opmaint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reports and dashboards

> See how your maintenance is really running: workload, response times, downtime and cost.

Every work order, reading and part used in Opmaint feeds its reports. The more consistently your team records work, the more these numbers tell you.

## Questions reports answer

> **Workload**
>
> How many jobs are open, overdue or completed, by site, team or person.

> **Preventive vs reactive**
>
> How much of your work is planned versus firefighting.

> **Assets**
>
> Which assets break down most and how much [downtime](/asset-downtime) they cause.

> **Cost**
>
> What parts and work are costing you, per asset and per site.

## Numbers worth watching

| Measure | What it tells you |
| - | - |
| **PM completion rate** | Whether scheduled maintenance is actually being done on time |
| **Overdue work orders** | Whether the team is keeping up or falling behind |
| **Planned vs reactive work** | Whether you are getting ahead of failures or chasing them |
| **Downtime by asset** | Where preventive effort will pay back fastest |

## Making reports trustworthy

Reports are only as good as what goes in. Three habits make the biggest difference:

* Link every work order to an asset
* Record parts used on the job
* Close work orders when the work is done, not days later

## Related

> **[Data export](/data-export)**

> **[Asset downtime](/asset-downtime)**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.