> For the complete documentation index, see [llms.txt](https://docs.diro.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diro.app/en/reports/dashboard-and-analytics.md).

# Dashboard & Analytics

**Dashboard.** The first page after login shows your business's condition over the date range you choose.

## What you can see

* **Bookings** — number of bookings, broken down by status.
* **Revenue** — total and trend over time.
* **Peak hours** — when your slots fill up the most.
* **Rankings** — top-performing services, providers, and branches.
* **Period comparison** — percentage up or down against the previous period of the same length.

## Using the date filter

The date picker at the top affects every card on the page. Period comparison always uses the previous period of the same length — 30 days compared with the previous 30 days, not a calendar month.

## What to pay attention to

**Peak hours** tells you when to add providers or raise prices. **Underperforming services** tells you what needs to be replaced or promoted. **Revenue trend** tells you whether your last promotion actually worked.

## Export

Booking and transaction data can be exported for further processing or handed to your accountant.


---

# 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.diro.app/en/reports/dashboard-and-analytics.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.