Skip to main content
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: Sections with a chart can be read as a table instead, using the control in their corner.
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.

What you do here

1

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.
2

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.
3

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.
4

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.
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.

What happens next

Nothing changes from this screen. What it tells you is acted on elsewhere: targets and alerts under Requests, staffing on your rota, a recurring room fault as a work order on Active Requests.