The Revenue Manager's Morning Routine, Optimized

A note for revenue managers whose day starts with four browser tabs and an export button.

It’s 07:50. You log into the PMS and run yesterday’s reservation report. While it exports, you open the channel manager to check parity and distribution status. Then the rate-shopping tool, scrolling for overnight compset moves. Then Excel, where the three exports get pasted, cross-referenced, and turned into the morning summary.

By 09:40 you know what happened yesterday. The actual work — deciding what to do about it — can now begin. Except the morning meeting is at 10:00.

If this is your morning, you already know it’s not a good morning. What’s easy to miss is how much it costs, why it survives every good intention to fix it, and what the realistic alternative looks like. That’s this article.

The anatomy of the two-hour morning

The morning has four stops, and the times are remarkably consistent across the revenue managers we talk to:

• PMS — about 30 minutes. Pickup, segment and channel breakdown. The data you actually want, in a format built for reservations, not analysis.
• Channel manager — about 20 minutes. Rate parity, distribution status, what the OTAs are showing.
• Rate shopping — about 20 minutes. Where you stand against the compset, and whether anyone moved overnight.
• Excel — about 30 minutes. Where the three exports above become one picture. This is the step people call “analysis.” It’s mostly formatting.

Call it 100 minutes. Here’s the observation that matters: none of these steps is analysis. Every one of them is assembly — moving numbers from where they live to where you can look at them. The job title says revenue manager. The morning says data courier.

What assembly actually costs

The arithmetic first. 100 minutes a day, five days a week, is roughly 8 hours — a full working day per week spent assembling data instead of using it. Over a year, that’s on the order of 350 hours of skilled revenue-management labor doing work a machine (or a well-designed process) should do.

The hours are the visible cost. Three quieter ones compound underneath:

The analysis debt. There’s a category of question you never ask because assembly ate the time: “How does our corporate pickup on Booking.com compare to the same week-position last year?” Multi-dimensional questions like this are where the real money hides — and they’re exactly the ones a manual toolchain makes expensive. (We wrote about this gap in Your RMS is the Steering Wheel. Where’s the Dashboard? — it applies with or without an RMS.)

The fragility. The Excel workbook that holds the morning together is a personal toolchain. It works — as long as its author is in the building. It breaks on a PMS export format change, a vacation, or a job change, and the next revenue manager rebuilds it from scratch.

The timing. A competitor drops weekend rates on Friday night. Your assembly process confirms it Monday at 09:40 — after three nights of bookings have already shifted. The two-hour morning isn’t just slow; it’s slow at the exact hours when acting still helps.

Why the two-hour morning persists

Nobody designed this morning. It accreted.

Each tool is fine alone. The PMS does reservations well. The channel manager distributes well. The rate shopper shops well. The gap is between them — and no one owns “between.”

It grew gradually. The routine was 20 minutes once. Then a new channel, a new segment structure, a new report the owner asked for. Each addition cost five minutes. There was never a single day where the morning obviously broke — it just quietly became two hours over a few years.

Assembly feels like work. It produces a visible artifact: the morning file, the formatted summary. Analysis produces decisions, which are harder to point at. On a stressful day, assembly is the comfortable task — you can finish it. That comfort is worth being suspicious of.

The workbook is a point of pride. Fair enough — a macro-laden workbook that stitches three systems together is impressive. It’s also unpaid software maintenance, done at 08:00, forever.

The design principles of a 15-minute morning

The fix is structural, not motivational — “be faster in Excel” is not a plan. Four principles, in priority order. Tooling helps with all of them, but the principles come first; you can apply the last two in a notebook.

1. Data arrives assembled, or it isn’t a morning task. Push, not pull. The one view — pickup by channel and segment, compset overnight moves, forecast vs actual — should exist before you sit down, built overnight by a system, not at 08:00 by you. Integrated platforms do this as their whole job (full disclosure: we make one); a disciplined export-automation setup can approximate it. What doesn’t work is keeping assembly inside the 08:00–10:00 window — those are the hours when decisions still change outcomes.

2. Exceptions announce themselves. You shouldn’t discover the −20% pickup day by scanning 30 rows of normal ones. Threshold alerts — on pickup misses, compset moves, parity breaks — invert the morning: instead of reading everything to find the three things that matter, the three things that matter are the first things on screen. Scanning normal numbers to confirm they’re normal is the largest hidden cost in the routine.

3. The first minutes follow a fixed sequence. Same order, every day: yesterday’s pickup vs forecast → composition (which channel, which segment) → compset overnight → flagged exceptions. This is the 5-minute check that Pickup 101 describes, and the fixed order is what makes it fast — you notice deviations precisely because the baseline never changes.

4. Decisions get one line, written where the data is. If the morning produces a decision — hold the rate, match the move, push a promotion — the why gets one dated sentence attached to the data that triggered it. Three months later, at the review, that sentence is the difference between learning from the decision and re-litigating it. (5 Signs You’re Leaving Money on the Table covers what happens when this audit trail doesn’t exist.)

The 15-minute version, minute by minute

What the optimized morning actually looks like — tool-agnostic:

07:55 — The briefing is already there: yesterday’s pickup, OTB for the next 30 days, compset overnight moves, two exceptions flagged.

08:00–08:05 — Exceptions first. A Tuesday three weeks out is pacing behind; one competitor dropped weekend rates 8% overnight.

08:05–08:12 — Investigate the one that matters. Composition shows the weak Tuesday is a corporate slowdown, not transient softness — that’s a note to sales, not a rate move. Decision: hold rate, flag the account team. One line, logged.

08:12–08:15 — Scan the rest to keep the baseline feel. Everything else is normal. Done.

The two hours didn’t become fifteen minutes because anyone got faster. The assembly left the morning. The 5-minute data check stayed; the courier work went to a machine that runs at night; the remaining ten minutes are the actual job — investigation and a decision.

What the reclaimed time is for

The honest answer isn’t “a calmer morning,” although you get that too. It’s the work that the two-hour version silently cancelled: the monthly forecast-accuracy review, the segment strategy you keep postponing, the retrospective on whether last quarter’s pricing decisions actually worked, the multi-dimensional questions from the analysis debt.

And one change your GM will notice before you do: you arrive at the 10:00 meeting with a recommendation instead of a spreadsheet. The conversation starts at “here’s what I think we should do” — because the “here’s what happened” part was done before anyone sat down.

When the two-hour morning is actually fine

Not every property has this problem, and it would be dishonest to pretend otherwise.

• Small, simple operations — under ~30 rooms, one dominant segment, two or three channels — often have a genuine 15-minute manual morning already. There’s nothing to optimize; tooling would add cost, not time.
• Chain properties with a central reporting layer may already receive the assembled view from corporate. The gap this article describes is an independent-hotel gap.
• If your assembly is 20 minutes, not 100 — your problem isn’t the toolchain, it’s the ritual. Apply principles 3 and 4 and stop there.

The two-hour morning is worth fixing when it’s real — and at mid-sized independent properties with multi-channel, multi-segment business, it almost always is.

Where to go from here

The For Revenue Managers page walks through two full day-in-the-life timelines — one for an RM pricing manually, one for an RM running an RMS — showing where the assembly work goes in each setup.

For the tooling side of the principles: Business Intelligence covers the arrives-assembled view (principle 1), and Ping alerts covers exceptions announcing themselves (principle 2). The design philosophy behind both — AI that works in the background and claims your attention only when the data says so — is the subject of The Best Hotel AI Is Invisible.

If you’d rather start by locating your own operation on the spectrum, the Self-Assessment Quiz takes 5 minutes and tells you which part of the routine is costing you most. And the morning routine is one slice of a larger system — the hotel data analytics guide shows the whole map, from data sources to the decision loop.

Or keep the four tabs. They’ll be there tomorrow at 07:50.