Reading a dashboard: understand where the hotel stands in 5 minutes

Wednesday morning, ten minutes before the daily huddle. Adam, the general manager, coffee in hand, opens the hotel’s dashboard (the most important metrics on a single screen). The screen fills with numbers: occupancy, ADR, RevPAR, pace, pickup, segments, channels, fourteen days forward, fourteen days back. Dozens of data points, all of them looking important.

And this is where most leaders come unstuck. Either they get lost in it — scrolling the numbers for ten minutes and still not knowing at the end whether it’s a good or a bad morning — or they glance and close it, because it’s “a lot.” Yet a good dashboard is not a data pile but decision support: it’s there so that in five minutes you learn where the house stands and what you need to watch today.

This lesson gives a concrete, five-step reading order — and teaches the “green / amber / red” thinking with which a leader doesn’t analyse but spots where action is needed.

A dashboard isn’t for reading everything

The most important mindset shift comes right at the start: a dashboard is not for reading, but for scanning. The goal isn’t to understand every number, but to find the two or three that today deviate from normal.

For that you need an internal yardstick. Next to every number you have to be able to place a comparison — against last year, against the budget (the plan), or against the usual level — and this is how the number takes on a colour:

• Green — on plan / last year, or better. Nothing to do, move on.
• Amber — slightly behind, worth watching, but not yet an emergency.
• Red — meaningfully behind, needs action today.

The leader doesn’t look at every number the same way. They run down the colours, skip the greens (good news needs no decision), and put their time on the ambers and reds. This is the difference between “I get lost in the numbers” and “in five minutes I know where I stand.”

The five steps — a required order

The order is no accident: it runs from the most important, most action-demanding things toward the fine-tuning. So if something comes up and you only have time for two steps, you’ve looked at the two most important ones.

1. Today and tomorrow — occupancy versus last year. The nearest two days, because there’s barely anything left to change on them, but you have to know what’s coming. Will we be full? Are there still sellable rooms that need a push today?

2. The pace of the next 14 days. Pace (the booking rate) tells you whether the coming days are filling faster or slower than this time last year (same point last year). This is the early warning system: here you see the trouble while you still have two weeks to act on it.

3. RevPAR versus budget. The month-to-date performance measured against the plan. A single number that tells you: on the revenue side, are we running to plan?

4. Warning days. The specific dates that stand out as strikingly weak (or unexpectedly strong). These have to be looked at by name.

5. A segment or channel anomaly. Has something shifted in the mix? Less corporate, more expensive OTA, a segment plunging out of nowhere? This is the subtlest signal, but often it’s the one that explains the rest.

A worked example: a dashboard snapshot

Let’s see what Adam sees on this Wednesday morning on Hotel Peaqplus City’s (80 rooms) dashboard, step by step. The Peaqplus Dashboard module automatically puts the last-year and budget comparison next to every number, so Adam doesn’t have to work out the colour in his head — only read it off.

Now let’s read it with a leader’s eye, in five minutes.

1. Today and tomorrow. Today 90% — green, we’ll be full, nothing to do. Tomorrow, though, is 75%, and this time last year it was 82%; that’s amber. Not a drama, but there are still 20 empty rooms for tomorrow that a last-minute push tonight could work on. He notes it.

2. The 14-day pace. Overall +4% OTB (on the books — the rooms already booked) versus last year — green, the near future is fine. But “total” is an average, and the average hides (see lesson 8 later): in the detail there’s a red day. This carries us on to step 4.

3. RevPAR versus budget. Month to date, 82 EUR RevPAR against a plan of 85. The gap is (85 − 82) / 85 = −3.5%. Amber: it hasn’t collapsed, but you have to watch where the shortfall comes from. The pace is green, so volume isn’t the problem — then it has to be sought in rate or mix. This foreshadows step 5.

4. Warning day. Here’s the red: next Friday 45% OTB, this time last year it was 62% — a 17 percentage-point shortfall on a day that nearly filled up last year. There are nine days to act: adjust the rate, tell sales, launch a promotion. This is the single most important task of the morning.

5. Segment anomaly. The corporate (company, contracted) room nights for next week are 18% behind last year. This immediately ties together with points 3 and 4: if the stable, well-paying corporate demand drops out, its place is taken either by empty rooms (the red Friday) or by cheaper OTA bookings — which also explains RevPAR’s amber. This isn’t a pricing question but a sales question: what happened with the contracted company?

Five items, five minutes — and Adam has two concrete jobs for the daily huddle: (1) the red Friday next week has to be handled, and (2) he needs to look, with Francis (sales), at why corporate fell for next week. The rest is green: no need to touch it. This is the dashboard’s job — not for you to read it, but to tell you where to look.

Back to Adam

Adam closes the laptop — five minutes have passed. He doesn’t know every number on the dashboard by heart, and doesn’t want to: he knows two things for certain, the red Friday and the corporate drop, and this is what he takes to the huddle. At the meeting they don’t talk “about the numbers in general,” but about these two, specifically.

Notice what Adam did not do. He calculated nothing — the comparison and the colour came from the Dashboard. He didn’t analyse — the decision is made at the daily huddle, together with Daniel and Francis. And he didn’t get lost — he consciously skipped the greens. A leader’s job isn’t to be the fastest reader of the dashboard, but to look at it in the right order, with the right question: where does it deviate from normal, and what do I have to act on today? A good dashboard answers this in five minutes — a bad one (or a badly read one) takes half an hour and decides nothing.

We carry this same logic forward, narrowed to the owner’s viewpoint — 4 numbers that are enough — in lesson 23. And the daily, in-depth reading of the dashboard — the detailed analysis of pickup curves and pace anomalies — is shown from the revenue manager Daniel’s perspective in the RM Academy lesson Reporting basics.

Key takeaways

• A dashboard is not for reading but for scanning: you don’t understand every number, you find the two or three that deviate from normal.
• Every number needs a comparison (last year / budget / usual) that gives it a colour: you skip green, you put your time on amber and red.
• A required five steps, in this order: (1) today-tomorrow occupancy versus last year, (2) the 14-day pace, (3) RevPAR versus budget, (4) warning days, (5) a segment/channel anomaly.
• Pace is the early warning: here you see the trouble while you still have days to act on it — the red warning day is the single most important task of the morning.
• The numbers often tie together: one corporate drop can explain a weak day and a RevPAR shortfall at once. The leader doesn’t look at them separately but reads out the story.