Pickup-based daily decision-making

It’s 8 a.m. at Hotel Peaqplus City. Daniel sits down with his coffee and opens the daily pickup report — pickup is the net balance of new bookings that came in over the previous day(s), broken down by stay date. It’s July 25, and his eye catches on one row: August 19, Saturday, 25 days before arrival (T-25). OTB: 30%.

OTB (on the books) is the occupancy already on the books. 30% for a peak summer Saturday, 25 days out. Daniel opens the same-point comparison next to it (the method from lesson 18) — last year’s point at the same distance from arrival: not last year’s final result for August 19, but where the house stood the same number of days before arrival. Last year, at this point, it was 45%.

Fifteen percentage points behind. Daniel’s stomach tightens, and the first reflex speaks up: “Cut the rate, now, immediately, before the Saturday slips away.”

That reflex is one of the industry’s most expensive automatisms. The 15 pp gap is a symptom — and you don’t prescribe medicine for a symptom without a diagnosis. This lesson — the closing lesson of the advanced level — is about how the morning pickup report turns from a source of panic into a decision system: a 15-minute routine, a diagnosis tree and three pre-built scenarios. The tools of the past 17 lessons come together here into a single daily practice.

Position and speed — the two numbers a decision is born from

Before we get into the routine, one principle that holds the whole lesson together. In lesson 37 (Booking curve analysis) we saw: OTB is the position — where we stand now; pickup is the speed — the rate at which occupancy is building. Together they form a basis for decisions; separately, neither does.

• Low position + strong speed = a catch-up is under way. Patience, monitor.
• Low position + weak speed = the gap will not close on its own. Suspected intervention case.
• Good position + slowing speed = an early warning — today’s good number can be tomorrow’s shortfall.

So the 30% for August 19 is, by itself, not a basis for a decision. The question is: at what speed is that 30% approaching the expected final, and is that speed enough? That is the question the morning routine answers.

The morning pickup routine — 15 minutes, five questions

The pickup routine is not browsing; it is a checklist with a fixed order. It costs Daniel 15 minutes, and every morning it is the same five steps:

1. Yesterday’s pickup — in total and by date. How many new room nights came in yesterday, and for which arrival dates? The total is the house’s pulse; the date-by-date breakdown shows where the demand is going.
2. Same-point comparison for the critical dates. The highlighted days of the next 30-60 days (weekends, event days, known weak spots) against last year’s same point. This is where August 19’s −15 pp jumps out.
3. Negative pickup — where? Cancellations appear in the pickup report as negative numbers. One or two scattered cancellations are noise; a negative wave concentrated on one date (for example a group eroding — lesson 29’s wash phenomenon) deserves its own investigation.
4. The slope: is the gap growing or shrinking? A single day’s same-point picture is a snapshot. The last 7 days’ trend is the real signal: if the gap has narrowed from 18 pp to 15, the catch-up is under way; if it has grown from 11 to 15, the situation is deteriorating. The same 15 pp means two opposite decisions depending on the direction of the slope.
5. Outlier days in both directions. Not only the lagging days but also the unusually fast ones — those signal a rate-increase opportunity (lesson 37’s “too fast” anomaly), and money is left on the table just the same if we fail to notice them.

The routine’s output is not an action but a short list of the dates to investigate today. Action comes after diagnosis.

The diagnosis tree — what is the 15 pp made of?

Seeing the gap, the reflex question is: “what do we do?” The right question is: “what is it made of?” The diagnosis tree runs down four branches, in a set order — the order matters because without answering the first two branches, the third and the fourth mislead.

Two notes on the tree. Branch (a) comes first, because if the base is distorted, every further analysis measures against the wrong target — and on summer dates this is common: festivals, concerts and calendar shifts wander from year to year. Branch (d) is the fastest to check, and the most embarrassing to skip: a forgotten MLOS (minimum length of stay restriction) or a dead OTA connection can silently block demand for weeks while the hotel analyses its “pricing problem”. In practice, the extranet status and the restrictions list can therefore be scanned in the first minutes of the diagnosis, in parallel with the other branches.

The worked example — splitting the 15 pp by segment

Back to August 19. Daniel starts the branch (a) investigation (we will come back to it) and in parallel runs branch (b): the same-point comparison by segment, with OTB expressed as a percentage of the house. This is the lesson’s central worked example — follow it through, because the whole logic of daily decision-making is in it.

A quick check: 8 + 4 + 3 = 15 pp — the house-level gap fully allocated. And it is already visible: the 15 pp is three different stories, with three different checks and actions.

• Transient −8 pp. The biggest item — yet transient is the least urgent. Why? Because there are still 25 days to go, and the bulk of transient demand (per lesson 37’s S-curve) arrives precisely in this window. Check: compset rates and availability (are the competitors slow too?) + the booking window picture (are this year’s bookings coming with shorter lead times than last year’s — if so, the gap is partly a timing shift, not missing demand). Action now: no pricing move at all — diagnosis and monitoring.
• Corporate −4 pp. Corporate is not an anonymous market; it is named partners. Check: the booking rhythm of the top 5 corporate accounts against last year — has someone dropped out, or merely shifted? Action: a sales call, not a pricing move. Treating a corporate gap with a rate cut is a category error: a contracted partner does not watch the public BAR.
• Group −3 pp. Check: is there a pending offer in the group pipeline for this date, and in what status — or was there a group last year that simply isn’t there this year? If a tentative group is eroding (lesson 29’s wash phenomenon), sooner or later it also shows up as negative pickup. Action: clarify the specific offer’s status with the sales team.

Quantifying the revenue at risk

How much money are we talking about? Step by step:

1. The gap in rooms: 15 pp × 80 rooms = 12 room nights behind on August 19.
2. The gap in revenue, for one night: 12 rooms × 105 EUR expected ADR = 1,260 EUR per night.
3. The affected period: the same-point table shows the shortfall is not a single day’s — all 7 days of the Aug 14–20 week sit in a similar, 12–15 pp gap. As an upper estimate — counting every day at the top of the band, i.e. the 15 pp / 12-room gap — 7 nights × 12 rooms × 105 EUR = 8,820 EUR of revenue at risk if the gap does not close at all.

This number is good for two things. First, it sizes the response: against an 8,820 EUR risk, a house-level rate cut lasting weeks is not proportionate — it would sell the demand that was coming in anyway at a lower price (and some flexible-rate bookings would cancel and rebook at the cheaper rate), burning far more than the risk it manages. Second, it establishes the urgency: 8,820 EUR cannot be ignored — a plan is needed. And this is where the lesson’s other backbone comes in.

Scenario thinking — the decision is born in advance, not under stress

The classic error pair every RM knows: the too-early panic rate cut (we slash the rate at T-25, then it turns out the demand would have come in on its own — it just came in cheaper), and the too-late reaction (we scramble at T-5, when most of the booking window has already closed and a rate cut only reaches the last crumbs). Both stem from the same thing: the decision is born in the moment of stress, not before it.

Scenario thinking turns this around: today, with a calm head, we work out three scenarios, each with a trigger point (a pre-agreed condition whose fulfilment releases the action) and an action package. The review date: T-15 (August 4) — close enough that most of the transient window is still ahead of us, and far enough that by then the current speed data shows a trend.

The philosophy behind the table, in three points:

1. This is not prediction; it is preparation. We are not claiming to know which scenario will happen — we are making sure that whichever happens, the answer is ready.
2. The quality of the decision does not depend on the single outcome. If we launch package B and it later turns out A would have happened anyway, the decision was still right — given the information available, it was the proportionate move. A good decision is not the same as a lucky outcome.
3. Fixing the “when do we act” in advance is the protection against stress. At T-15 Daniel no longer decides — he executes. The trigger was either met or it wasn’t; the action package either launches or it doesn’t. The mood of the day, Adam’s worried question in the corridor, one bad morning number — none of them overrides the strategy, because the strategy is in writing, and it was made earlier than the stress.

One practical addition: it is worth recording the scenario table at the weekly revenue meeting (lesson 47) and agreeing it with the GM. That way, when package B launches at T-15, it is not “Daniel got scared and is discounting” but the execution of a plan approved two weeks earlier — for organisational trust, that difference is enormous.

What happened to August 19?

Let’s follow through what the system delivered.

Branch (a) of the diagnosis tree scored a hit the same day. According to the event calendar, last year a food festival ran in the hotel’s district on August 18–20 — this year there is none; it moved to another part of town. The same point from two years ago for this date type was 38%, not 45% — so last year’s base was an outlier. The estimated size of the festival effect: 6 pp — 3 pp of it sitting in the transient gap (festival guests), 3 pp in group (last year the house held a festival-linked group block; this year, naturally, there is none). That 6 pp is not a loss but a measurement error — the target is corrected: the realistic reference point is not 45% but 39%, and from here on the scenario table’s triggers are measured against it.

On the corporate line, the sales calls clarified the picture: two key accounts’ projects slipped to September — the 4 pp is not lost but rescheduled demand. (It is expected to show up as a plus on September’s same point — Daniel notes it down, so that in September it isn’t celebrated as an “inexplicable” lead.)

The quick branch (d) check came back clean: the extranet is live, parity is fine, and the MLOS-2 sitting on the weekend is a deliberate setting, not a forgotten error — but it goes on the list as a liftable item of package B.

What remained was 5 pp of genuine transient weakness. The compset check showed the competitors’ availability is also unusually wide for the same week — a market-level, moderate slowdown, not a hotel-specific problem. At T-15 the corrected gap sits in the 8–12 pp band: scenario B, package 1 — the closed-group targeted promo, OTA visibility, lifting the weekend MLOS-2. A public rate cut: never happened.

The final: 88%. Up from the “hopeless” 30%, with no panic rate cut, ADR untouched. The July 25 reflex decision — an immediate house-level rate cut — would have cost orders of magnitude more than any risk it ever managed: it would have “solved” the 6 pp phantom gap and the 4 pp rescheduled corporate too, selling a good part of demand that was coming in anyway at a discount.

Manually vs. Peaqplus

Manually, the morning routine means cross-referencing PMS reports by hand: yesterday’s booking list, a date-by-date OTB export, looking up last year’s same point (minding the calendar shift), the cancellation list — stitched together in Excel. Realistically that is 45-60 minutes a day, and in most hotels that is exactly why it does not happen every day. The gaps then surface not at T-25 but at T-10 — when half of the scenario table is no longer an option.

In Peaqplus, the routine’s raw material is ready. The daily pickup report and the date-by-date breakdown live in the Business Intelligence module — of the five questions, the first, the third (a cancellation wave shows up as negative pickup right on the date rows) and the fifth can be answered at a glance. The Same Point YoY view shows last year’s same-point comparison, so the critical dates’ gap and its 7-day trend (the “slope”) can be followed without manual lookups. The Insight Engine flags outlier deviations automatically — so the routine’s “outlier days” step is not left to the vigilance of the eye. For estimating the expected final, Smart Forecast provides the reference (lesson 38) — at trigger evaluation (“will the gap close on its own?”) it is the second opinion next to the same point. The diagnosis tree and the scenario table, however, remain your work: the system surfaces the symptoms early and reliably — it does not take the diagnosis or the action decision off your shoulders.

Closing the advanced level

With this lesson the advanced level (33–50) comes to an end — and perhaps now it is clear why this is the lesson that closes it. The booking curve (37), Smart Forecast (38), the unconstrained demand mindset (39), the group toolkit (40–41), the LOS strategy (42), channel economics (43), the rate bridge (44), the total revenue mindset (45), the promotional toolkit (46), the revenue meeting (47), the day-by-day strategy (48) and the direct strategy (49) — all of them come together in this 15-minute morning routine and the decision system behind it as everyday practice. The expert level (51–67) carries on from here: its subject is system-supported, automated daily operation — how the machine layer takes over the mechanical part of the routine, so the RM’s time goes to the real decisions.

Key takeaways

• OTB is the position, pickup is the speed — a decision is born only from the two together. A 15 pp gap by itself is not an action signal: the direction of the slope (closing or opening) decides its meaning.
• The morning pickup routine is a fixed, 15-minute checklist: yesterday’s pickup by date → same point for the critical days → negative pickup → the gap’s 7-day trend → outlier days in both directions. Its output is an investigation list, not an immediate action.
• A gap gets a diagnosis tree first, not a pricing move: distorted base → segment shortfall → general demand weakness → technical/visibility cause. The four branches demand four different answers — and three of them are not pricing questions.
• The segment breakdown is the key to diagnosis: of the example’s 15 pp, 8 pp is transient (compset + booking window check), 4 pp corporate (sales call, not a rate cut), 3 pp group (offer status) — three stories, three actions.
• Scenario thinking is the antidote to panic: three scenarios, with pre-agreed triggers and action packages. At the review point we no longer decide — we execute; so neither the too-early rate cut nor the too-late scramble can happen.