A day in the life of an RM — morning, noon, and night

Across the 11 lessons so far, we’ve looked at the building blocks of revenue management: the KPIs, the segments, the channels, the booking window, the length of stay, seasonality. Each of these on its own can stand alone — but in the revenue manager’s daily work they operate all at once, together.

In this lesson we follow an average Monday for Daniel, hour by hour. Not because every RM works exactly like this (hotel size, the team, the tools change it a lot), but so you can see how the building blocks fit into a concrete daily routine. In lessons 16-32 (the intermediate level) we cover each of these more deeply — for now the goal is the map, not the detail.

Morning coffee — 07:45

Daniel walks into the office with a hotel coffee. He turns on the two screens: on one, the PMS (Property Management System, in Hotel Peaqplus City’s case Sabeeapp), on the other, the reporting tool — a combination of Excel and a web BI dashboard.

The first question is the same every day: what happened yesterday?

He opens the morning report:

Metric	Yesterday (Sunday)	Last week’s Sunday	Change
Occupancy	56%	62%	-6 pp
Average rate	EUR 95	EUR 98	-EUR 3
RevPAR	EUR 53	EUR 61	-EUR 8
Room nights sold	45	50	-5

A quick read, in 2 minutes:

• We saw Sunday in lesson 9 (Seasonality) — a structurally weak day.
• 56% isn’t dramatically low, but the -6 pp versus last Sunday deserves attention.
• Whether the -6 pp is a trend or noise — for that, you have to look at the next few Sundays too.

Daniel makes a note: “Sunday pace — review again in 2 weeks.”

Pickup check — 08:00

The second report: the pickup state of the next 90 days. Here Daniel looks date-by-date, not in a monthly average.

The pickup board is a colour-coded table where each date is a row, and the columns show:

• The current occupancy
• The same “point” last year (see lesson 18, Same Point)
• The budget target
• The expected pickup that fits the booking window

A detail, for the next 7 days:

Date	Day	Occupancy now	Last year same point	Expected final	Action needed?
Nov 6	Monday	78%	72%	~88%	None — good pace
Nov 7	Tuesday	82%	78%	~92%	None
Nov 8	Wednesday	72%	75%	~85%	Watch
Nov 9	Thursday	65%	70%	~80%	Action — low pace
Nov 10	Friday	71%	75%	~88%	Watch
Nov 11	Saturday	85%	82%	~96%	None
Nov 12	Sunday	48%	52%	~62%	Action — Sunday promo

Two action points stand out. Thursday (Nov 9) is 5 pp underperforming versus last year — perhaps the corporate segment is slower. Sunday (Nov 12) is structural weakness — a promo action needs launching during the week.

Daniel makes a note: “Examine corporate segment for Nov 9. Activate Sunday Brunch package for Nov 12.”

Compset watching — 08:30

The third routine: what the competitors are doing. Hotel Peaqplus City watches its compset’s (4 similarly-sized urban 4-stars) rate movements daily — with a rate-shopper tool (see lesson 32).

The table: the 4 compset hotels’ BARs for the next 14 days. Each cell holds the 4 price points. Daniel looks for the differences:

• Nov 7 (Tuesday) — compset average EUR 118, Hotel Peaqplus City EUR 110. -EUR 8 underperformance. Maybe there’s an event in town we didn’t notice. Or the compset is overpushing — worth checking their pickup (but Daniel can’t see that).
• Nov 10 (Friday) — compset average EUR 132, Hotel Peaqplus City EUR 125. -EUR 7. The same picture.
• Nov 18 (Saturday) — compset average EUR 145, Hotel Peaqplus City EUR 110. -EUR 35! Dramatic underperformance.

Daniel immediately asks the question: “What’s on Nov 18? An event that’s not in my calendar?” A quick Google: an arena concert — Coldplay. This wasn’t on the sales team’s radar earlier. The rate must be raised immediately — from 110 to EUR 145-150.

This is a classic event-discovery moment. Compset watching is often the earliest signal of a missed peak event.

Daniel’s action: an immediate BAR increase for Nov 18, and an email to the sales team: “Coldplay on Nov 18, why wasn’t it on our radar?”

Price revisions — 09:15

After discovering the events, Daniel starts formal price revisions. The pricing engine (the Peaqplus pricing engine or another RMS, see lesson 56) generates suggestions, but Daniel reviews them — he doesn’t go on autopilot.

The morning price-revision list, with today’s actions:

• Nov 11 Saturday (this weekend) — pace OK (~96% expected), no change.
• Nov 9 Thursday — corporate pace slow, activate a non-refundable promo at -8% off the corporate rates.
• Nov 12 Sunday — launch the Sunday Brunch package (room + breakfast + late, 16:00 check-out).
• Nov 18 Saturday (Coldplay) — BAR 110 → EUR 148. MLOS = 2 (mandatory 2-night minimum).
• Nov 17 Friday (the day before Coldplay) — BAR 125 → EUR 138. We raise the prior day too, because Coldplay guests typically book Friday-Saturday.

The price revisions change 5 dates at once. Daniel notes the reason for each — in lesson 64 (Decisions and Revenue Track) we see why it’s important to document every decision.

The pricing engine sends the changes through the Channel Manager (see lesson 6) to all channels — Booking, Expedia, own web, GDS, all refresh within 15 minutes.

Pre-lunch sync — 10:30

After the morning data work, Daniel holds a short phone sync with the sales manager: what’s expected this week on the group front?

• A large MICE group (60 rooms × 3 nights, in March) — contract signing expected Wednesday.
• A Dutch tour operator (15 rooms × 2 nights, in November) — Daniel says: “We turn this down. With 15 rooms, transient pickup will catch the capacity, and the tour operator rate of EUR 70 is too low for that week.”
• Two smaller business groups — sales asks whether it can accept them. Daniel agrees, but stipulates the blackout dates (the high-pickup days).

Beyond this, the marketing team also syncs for half an hour: “How do we plan the promotion of the November 12 Sunday Brunch package?” — Daniel asks for a targeted Facebook + Google Ads campaign, audience: local, 35-55, interested in dining.

Lunch — 12:00

Daniel goes down from the office to the hotel restaurant (because he watches the F&B team too — who comes, what the average table value is, how full the dining room is). A 30-minute coffee break with the F&B manager, where they discuss:

• The November breakfast-consumption trend
• The spa packages’ sales statistics
• The operational prep for launching the Sunday Brunch

An RM is not just a position over the rate number — in a mature organization they watch the F&B and the wellness too, because these make up the TRevPAR (see lesson 4).

Afternoon segment analysis — 13:30

The afternoon is deeper analysis. Daniel starts with a concrete question: “Why is corporate pickup slowing for November?”

He opens a segment pace report — the corporate segment’s pace track for the next 30 days. The curve is 2-3 pp behind last year for the whole month.

Possible explanations, which Daniel examines one by one:

1. A global corporate trend? — Per STR data, the corporate segment is stable in November.
2. A specific corporate-client attrition? — He opens the top 10 corporate accounts’ occupancy over the last 6 months. Two clients (BankX and AcmeKft) have dropped drastically — a 30-40% fall.
3. A drop in sales activity? — In the last 3 months fewer new corporate contracts were signed (1 instead of 3).

The picture comes together: two large clients fell out, and new client contracts are slowing. This is a structural question, not a rate question. Daniel makes a note: “With the sales manager at Monday’s meeting — top corporate-account retention and new business priority.”

With this realization he does not launch a rate cut — because the corporate segment is not price-sensitive (see lesson 8). A rate cut here would only give the existing bookings away cheaper, without bringing new clients.

Compset deep-dive — 15:00

In the second half of the afternoon Daniel takes the time for a deeper compset analysis. Not daily BAR movement, but strategic positioning:

• The 4 compset’s average ADR over the last 3 months: EUR 112
• Hotel Peaqplus City’s average ADR: EUR 108
• Hotel Peaqplus City stands at -3.5% from the compset average

This is structural underpositioning. Daniel sees three possible explanations:

1. Product position — is the hotel weaker in something (age, location, amenities)? Possible, but Daniel doesn’t think this is true.
2. Brand strength — is the hotel less well known? Possibly — the digital marketing budget is low.
3. A price-timid RM — are the price revisions too conservative? This is a possible self-critique.

Daniel decides: over the next 30 days he’ll set the BAR EUR 2-3 higher on average days. This is a cautious experiment — if occupancy doesn’t drop, it stays permanent and produces +EUR 20-30k extra revenue a year. If it drops, it can be pulled back.

Weekly revenue meeting — 16:00

One of the day’s peak events: the weekly revenue meeting. Attendees: Daniel (RM), Adam (GM), the sales manager, the marketing manager, the F&B manager. Duration: 60 minutes.

The agenda (covered in detail in lessons 28 and 47):

1. Last week’s review (10 min) — Daniel summarizes the occupancy, ADR, RevPAR figures, the segment breakdown, and the two main lessons learned.
2. Next 14 days’ outlook (15 min) — the pickup tracks date-by-date, highlighting the critical days (low pace, peak events).
3. Top 3 actions (15 min) — what will we do this week? Daniel brought 4 priorities today: launching Sunday Brunch, the Nov 18 Coldplay pricing, corporate-account retention, the BAR increase for the next 30 days.
4. Group contracts (10 min) — sales brings the contracts expected this week.
5. Other / blockers (10 min) — a problem or question from anyone.

This Monday, after closing the action plans, everyone gets a list back, with an owner and a deadline.

Evening wrap — 17:30

The day’s last 15 minutes are the wrap: Daniel goes through today’s notes and assembles tomorrow’s to-do list:

• Develop the top corporate accounts’ retention plan with the sales manager
• Check the Nov 18 BAR revision (did it go through on all channels)
• Check the Sunday Brunch promo material
• Add the Coldplay event to next year’s calendar too
• Refresh the compset BAR analysis tomorrow morning
• Email the sales manager: re-approach the two lost clients (BankX, AcmeKft)

He closes the two screens, takes off the headset. Tomorrow: another morning report, another pickup check, more decisions.

One day of the 365 — a step toward a whole year’s performance.

What’s the takeaway

This “daily routine” is not a strict schedule — it’s an average Monday. On a Tuesday Daniel does the budget revision instead, on a Wednesday the forecast update, on a Thursday the review of tour-operator contracts. But the core routine is the same every day: morning report, pickup check, compset watching, price revisions.

A revenue manager has the macro impact of micro decisions: 8-15 price revisions a day, 4-6 group decisions a week, 2-3 strategic actions a month. Individually small things. Over a year, an 8-15% revenue difference versus a mediocre RM.

And most importantly: all of this is made possible by the concepts built up in the earlier lessons (KPIs, segments, channels, parity, booking window, length of stay, seasonality) acting together. The absence of any one of them — leaves the RM blind at a specific decision.

In lessons 16-32 (the intermediate level) we cover these daily routines more deeply: how to read a pace report, how to analyze channel mix, how to run a revenue meeting. The map has spoken — from here comes the depth.

Key takeaways

• An RM’s day is routine yet decision-dense — morning report, pickup check, compset watching, price revisions, group decisions, segment analysis, the revenue meeting.
• The morning report is a 2-minute read — not deep analysis, but quick situational awareness.
• Compset watching often discovers missed events — a competitor’s price jump is a warning sign of an event the sales team hasn’t found yet.
• Price revisions aren’t automatic — a pricing engine suggests, but the RM reviews and documents. Every decision’s reason recorded, for later learning.
• The weekly revenue meeting ties together the sales-marketing-F&B-RM communication — the week’s action plans are locked in here.