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

# Request Analytics

> How your team performed on guest requests — where time went, and where it went wrong.

**Request Analytics** answers the question the board cannot: *not what is open now, but how did we do.*

Pick a period at the top — **Today**, **7 days**, **30 days**, **90 days**, or **1 year**. Today is measured against yesterday, in your hotel's own calendar day.

***

## What is on the screen

Ten sections, each answering one question:

| Section                     | The question                                                   |
| --------------------------- | -------------------------------------------------------------- |
| **Right Now**               | What is open at this moment                                    |
| **Request Trend**           | Is the volume rising or falling                                |
| **Department Scorecard**    | Which departments are keeping up                               |
| **What Went Late, and Why** | Where the time was actually lost                               |
| **When Requests Arrive**    | Which hours are busy, in three-hour blocks                     |
| **Busiest Rooms**           | Which rooms ask most                                           |
| **How Requests Arrived**    | Which channel guests used                                      |
| **Who Filed Them**          | Guests, or your own team                                       |
| **Guest vs Hotel**          | Guest requests against your own work orders                    |
| **Who Carried the Work**    | Per person, with the work nobody was assigned named separately |

Sections with a chart can be read as a table instead, using the control in their corner.

<Info>
  **This screen says when it cannot measure something.** A request type your hotel has given no target time is reported as **not measured** — not as on time, and not as late. Where a figure covers only part of the requests, it says how many it judged. A number here is either real or absent; it is never filled in to look complete.
</Info>

***

## What you do here

<Steps>
  <Step title="Start with What Went Late, and Why">
    It separates work nobody picked up from work that was picked up and then ran long. Those are two different problems — one is staffing, the other is process — and the rest of the screen reads differently depending on which you have.
  </Step>

  <Step title="Check the Department Scorecard against your own expectations">
    A department that looks slow may simply have no target set. Read the coverage the section states before drawing a conclusion.
  </Step>

  <Step title="Use When Requests Arrive to shape a shift">
    If the same hours are consistently busy, that is worth comparing against who is on the floor at the time.
  </Step>

  <Step title="Check the rooms at the top of Busiest Rooms">
    A room well ahead of its neighbours is worth looking into. The screen counts requests; it cannot tell you whether the cause is a fault, a long stay, or one demanding guest.
  </Step>
</Steps>

<Tip>
  **Give it a longer window before you conclude anything.** One quiet day tells you very little on its own; the same shape across several is what is worth acting on.
</Tip>

***

## What happens next

Nothing changes from this screen. What it tells you is acted on elsewhere: targets and alerts under [Requests](/front-desk/settings/requests), staffing on your rota, a recurring room fault as a work order on [Active Requests](/front-desk/requests/active).