Day-by-day strategy — every date its own case

Monday, Sep 28, 4 p.m. — the last agenda item of the weekly revenue meeting (run in the format built in lesson 47) is the October outlook. Adam, the GM, looks at the monthly summary: “October is running +2 percentage points above the curve. That is fine — let’s move on to November, that’s where I see question marks.”

Daniel, the hotel’s revenue manager, does not move on. “October as a month is fine. But in October we don’t make one decision — we make thirty-one. The +2 points is an average — and behind that average there are four dates in serious and worsening trouble, plus three event days we are underpricing against the compset. The monthly number hides all of it.”

This lesson is about what Daniel compressed into those two sentences: revenue management is not a monthly game but a date-level one. Every date has its own demand pattern (lesson 37), its own compset situation (lesson 44), its own event backdrop. A “monthly strategy” is therefore not a strategy — at best a direction. The real work: designating the critical dates and working them one by one.

The average lies — decomposing the monthly number

Let’s see what Adam’s +2 points is made of. Hotel Peaqplus City (80 rooms), October as of Sep 28, the daily pace gaps (current OTB — on the books, i.e. the occupancy already booked — vs. that date’s booking curve level), grouped:

Date group	Number of days	Avg pace gap	Contribution (days × pp)
2 strong weekends (Oct 2-3 and Oct 9-10)	4	+16 pp	+64
3 event days (Oct 23-24 and Oct 30)	3	+11 pp	+33
4 critical lagging dates	4	−17.3 pp	−69
Normal days	20	+1.7 pp	+34
Total	31		+62 → 62 / 31 = +2.0 pp

The monthly average is mathematically accurate and operationally useless. The +2.0 points is really an average pulled up by two strong weekends and three event days — while four dates sit 15 to 20 points behind, and their position worsens week by week. If Daniel reacted to the monthly number (“all good”), the four critical dates would roll into check-in with no action taken.

This is the central claim of the lesson: the monthly average is not a decision unit. The date is.

The revenue risk of the four critical dates — step by step

Take the worst date and work through what the lag means in euros. Thursday, Oct 15, 17 days before check-in:

• Thursday curve at 17 days (3-year average, using the lesson 37 method): 48%
• Current OTB: 28% → pace gap −20 pp
• Curve expected final: 84%
• Pace-adjusted expected final (lesson 37): 84% × (28 / 48) = 49%
• Shortfall vs. the curve expectation: 84% − 49% = 35 pp → 80 rooms × 0.35 = 28 rooms
• Thursday ADR expectation: 96 EUR → risk: 28 × 96 = 2,688 EUR

A single Thursday. In a month the monthly report calls “+2 points, all good”.

The pace-adjusted estimate is the upper risk estimate — it assumes the lag carries itself forward proportionally to the final. The conservative estimate (the current point gap persists but does not grow) is the lower bound. The four critical dates with both methods:

Date	Curve now / OTB now	Gap	ADR	Conservative estimate (gap persists)	Pace-adjusted estimate (lesson 37)
Oct 7 (Wednesday), 9 days	52% / 37%	−15 pp	94 EUR	12.0 rooms → 1,128 EUR	final ~58% → 19.2 rooms → 1,805 EUR
Oct 8 (Thursday), 10 days	55% / 39%	−16 pp	96 EUR	12.8 rooms → 1,229 EUR	final ~60% → 19.2 rooms → 1,843 EUR
Oct 15 (Thursday), 17 days	48% / 28%	−20 pp	96 EUR	16.0 rooms → 1,536 EUR	final 49% → 28.0 rooms → 2,688 EUR
Oct 16 (Friday), 18 days	50% / 32%	−18 pp	105 EUR	14.4 rooms → 1,512 EUR	final ~58% → 25.6 rooms → 2,688 EUR
Total				~5,400 EUR	~9,000 EUR

(The conservative calculation: gap in pp × 80 rooms × ADR — e.g. Oct 15: 0.20 × 80 = 16 rooms × 96 EUR = 1,536 EUR. The pace-adjusted column uses the rounded finals; the curve finals: Wednesday 82%, Thursday 84%, Friday 90%.)

Together the four dates carry between 5,400 and 9,000 EUR of revenue risk. Reality typically lands between the two — but both numbers say the same thing: there is something to work on, and there is still time (9-18 days of booking window).

The three underpriced event days — the error in the other direction

The critical dates are the downside errors. The event days are the upside errors: pace is excellent (+10-12 pp) — these are exactly what pulls Adam’s monthly average up — but measured against compset rates (the rate-bridge logic of lesson 44), Hotel Peaqplus City is selling the remaining rooms too cheaply:

Date	Own BAR	Compset median	Gap	Expected remaining sales	Cautious increase	Foregone revenue
Oct 23 (Friday, convention)	110 EUR	132 EUR	−22 EUR	94% final − 46% OTB = 48 pp → 38.4 rooms	+18 EUR	691 EUR
Oct 24 (Saturday, convention + concert)	118 EUR	144 EUR	−26 EUR	96% − 52% = 44 pp → 35.2 rooms	+20 EUR	704 EUR
Oct 30 (Friday, festival weekend)	112 EUR	132 EUR	−20 EUR	94% − 40% = 54 pp → 43.2 rooms	+16 EUR	691 EUR
Total						~2,100 EUR

The “cautious increase” is deliberately not the full compset gap — event demand is strong but not infinite, and we do not want to punch through the rate-bridge band either. Even so: projected onto the remaining sales, ~2,100 EUR stays on the table if we do not act.

The full picture: behind the “October is fine at +2 points” sit 7,500-11,000 EUR of saveable revenue — on four lagging dates and three underpriced event days. That is what the monthly average hides.

Date typology — not every day is the same case

The first step of day-by-day work is to classify the dates — because the type decides the nature of the action:

Date type	Telltale sign	Nature of the action
Event peak	Known demand generator (concert, convention); frontloaded curve (lesson 37)	Rate maximisation + LOS steering with the DCAL cells (lessons 33-34); watch the compset gap
Compression day	No event of its own, but the city is filling — the compset closes out, unconstrained demand above capacity (lesson 39)	Rates up + restrictions (lesson 42); capture the overflow demand
Normal day	Running on or near the curve	One look a week is enough — it does not get daily energy
Critical lagging	A normally good date now significantly behind the curve and worsening	Diagnosis + active intervention — the main terrain of day-by-day work
Structurally weak	Recurring pattern (typically Sunday): its curve runs to a low final by design	Not a critical date! Needs structural tools, not daily firefighting: an LOS package (lesson 42), a promo (lesson 46), a group base (lessons 40-41)

The most common mistake is mixing up the last two types. A Sunday standing at 35% fourteen days out is not lagging — by its own Sunday curve, that is exactly where it should stand. Treat it as a critical date and cut the rate, and all you do is damage ADR on a date that is weak for structural reasons. Conversely: a Thursday standing at “only” −15 points is a genuine alarm — because Thursday is normally a good day.

Designating a critical date — the rule set

Which dates make the critical list? Not by feel — by scoring. Hotel Peaqplus City’s simple five-criteria system, run on every date of the 90-day horizon:

Criterion	Rule	Points
Pace-gap level	−5…−12 pp = 1 point; below −12 pp = 2 points	0-2
Slope (direction)	The lag grew over the past 7 days = 2; flat = 1; closing = 0	0-2
Booking window	The date is in its main pickup zone (typically 7-30 days) — there is time and there are tools to act = 1	0-1
Compset context	The compset is filling / raising rates while we lag — so it is our problem, not the market’s = 1	0-1
Event backdrop	No calendar / structural explanation for the gap (no calendar shift, no Sunday pattern) = 1	0-1

4 points or more: critical list. 2-3 points: watch list (re-checked in 72 hours). The two most important nuances:

• The slope matters more than the level. A date at −15 points that stood at −18 a week ago is closing — the curve is pulling it in; let it work. A date at −10 that was at −4 a week ago is tearing open — a far more urgent case, even though its lag is smaller. We score the trajectory, not the snapshot.
• The booking window is the currency of action. A lag 3 days out can only be helped by last-minute levers; one 60 days out has everything open but is not urgent. The 7-30 day zone is where the lag and the room to act are both large — that is why it earns its own point.

As a check, the Oct 15 Thursday: level 2 (−20 pp), slope 2 (a week ago it was −12 — OTB barely moved while the curve climbed), window 1 (17 days), compset 1 (both the Aurelia and the Danubea show tightening availability), event backdrop 1 (no explaining cause). 7/7 points — it goes to the top of the list.

”Working” a date — the six steps

A date has made the critical list. What does working it one by one mean? Six steps, always in this order — diagnosis first, then the tool:

1. Curve position and pickup tempo (lesson 37). Where does the date stand against its own curve, and what did daily pickup look like over the past 7 days? This gives the size and the trajectory of the problem.
2. Segment mix in the OTB. Which segment is missing? If leisure is on the curve and corporate is behind, that is a different diagnosis (and a different lever) than the reverse.
3. Compset rates and rate-bridge position (lesson 44). Where do we stand against the anchor competitor? Are we sticking out of the band on the upside — i.e. is the lag rate-side?
4. Event calendar. Is there an explaining cause — an event in last year’s base that does not exist this year; a calendar shift? If so, the date may not be critical at all — its curve base is simply distorted.
5. Lever selection. The diagnosis decides which one: rate (lessons 35-36), loosening restrictions (lesson 42), channel levers — visibility, OTA ranking, weighed against channel profitability (lessons 22 and 43) —, a promo (lesson 46), or a group / sales action (lessons 40-41 — a well-priced group is the fastest base-builder for a lagging date).
6. Decision + review date. In writing: what we did, what we expect from it, and when we look at it again (typically +3-5 days). A decision without a review date is not a decision — it is a hope.

Applied to Oct 15: pickup has been slowing for 7 days (step 1), the shortfall is in the leisure segment (step 2), the BAR (106 EUR) sits ~6% above the top of the rate-bridge band built on the Danubea anchor (~100 EUR) (step 3), and there is no explaining event (step 4). So the lever is rate + visibility (step 5): BAR back into the bridge band (−8 EUR, to 98 EUR), and an OTA-visibility check — not a panic promo. Review: Thursday, Oct 1 (step 6). Practised, these six steps take 6-9 minutes per date — which is how a top 10 list fits into 60-90 minutes of weekly deep work.

The weekly routine — the top 10 list

Day-by-day strategy does not mean deep-analysing all 90 future dates every day — nobody has the hours for that. The ratio that works:

• 15 minutes daily — the scan. The scoring runs across the 90-day horizon; Daniel only looks at: who is new on the critical list, whose slope has flipped, which earlier decision is due for review. (Lesson 50 devotes full depth to this pickup-based daily decision-making.)
• 60-90 minutes weekly — deep work. Taking the top 10 critical dates through the six steps, with decisions and review dates.
• Revenue meeting — a fixed agenda item (lesson 47). The top 10 list is one of the meeting’s standing blocks: not “how is October doing?”, but “what happened to last week’s ten dates, and what are this week’s ten?”. That way the meeting also produces date-level decisions, not monthly impressions.

Back to the Sep 28 meeting

Right there in the meeting, Daniel decomposes Adam’s monthly number: behind the +2 points, four critical dates carrying 5,400-9,000 EUR of risk and three event days with ~2,100 EUR of foregone revenue — together roughly 7.5-11k EUR, still saveable, because every one of these dates has booking window left.

Adam’s reaction is the point: “So when I say ‘October is fine’, what I am really saying is that I have not looked.” Exactly. The monthly number does not lie on purpose — it averages, and averaging hides the decision situations. From this week on, the October agenda item is: the top 10 critical dates, one by one, each with a decision and a review date.

Manually vs. Peaqplus

Manually, day-by-day work means combing the pace report line by line: 90 dates × pace gap × slope calculated by hand in Excel, with compset rates from daily OTA browsing on the side and the event calendar in a separate file. The full routine is several hours a week — which is why in most hotels it keeps shrinking until only the monthly average is left. In other words, exactly the thing this lesson is about is what gets lost.

In Peaqplus, the native surface for date-level work is the Pricing Map calendar view — the DCAL layer built in lessons 33-34 (the demand calendar) is handled by this module in Peaqplus. One calendar shows the demand and rate picture per date, so working a critical date — curve position, rate level, LOS structure — happens on one screen instead of cross-referencing four reports. The Insight Engine, meanwhile, flags outlier and lagging dates automatically, so collecting critical-date candidates does not depend on manual filtering: the flags provide the candidate list. Fine-tuning the scoring, the diagnosis and the lever selection stay with the RM — the system answers “where to look”; “what to do” is yours.

Key takeaways

• The monthly average is not a decision unit — the date is. A “+2 points, good month” can comfortably hide four critical dates and three underpriced event days, together 7.5-11k EUR of saveable revenue.
• Date typology: event peak, compression, normal, critical lagging, structurally weak — each with a different kind of action. A structurally weak date (typically Sunday) is not a critical date: it needs structural tools, not daily firefighting.
• Critical dates are designated by scoring: pace-gap level + slope + booking window + compset context + event backdrop. The slope matters more than the level — the trajectory counts, not the snapshot.
• Working a date is six steps: curve position → segment mix → compset/rate bridge → event calendar → lever selection → decision with a review date. Diagnosis first, then the tool.
• The routine that works: a 15-minute daily scan + weekly deep work on the top 10 critical dates + a fixed agenda item in the revenue meeting.