The Hotel Revenue Manager's Morning Routine: What It Looks Like and Where It Breaks
The first 90 minutes of a revenue manager's day sets the direction for everything that follows. Get the picture right, and the rate calls, the team conversation, the exception follow-ups all happen with the right context. Get it wrong — or start with a data view that took so long to build it's already outdated — and the whole day runs behind. Here's what that routine actually involves for most hotel teams, and where it reliably breaks.
The typical morning sequence
Pull the PMS daily close manual
Log in, navigate to the reporting module, run the daily close for yesterday. Export to CSV or Excel. This is usually the first manual step and the one everything else depends on. If the PMS was slow overnight or an export format changed, this step already adds time.
Check the rate shop manual
Open the rate intelligence tool — Lighthouse, RateGain, or whatever the property uses — and scan the next 14–21 days for positioning anomalies. This is usually done by eye, scrolling through dates. Notes get added to a separate tab or a mental note that may or may not make it into the brief.
Build the morning view manual
Open the shared Google Sheet or Excel file. Paste in the PMS figures, update the pickup rows, add the rate shop notes, check the budget variance columns, verify the formulas didn't break. This is the step that takes the most time and produces the most errors — copy-paste into the wrong row, formula that references last week's data, a date range that's off by one.
Review and distribute
Sanity-check the output, flag the exceptions, add any context that doesn't fit in the numbers, and send or share with the team. This is the step that should take the most time and thought. In practice, it often gets squeezed by however long the assembly steps ran over.
Morning standup or review call
Walk through the brief with the team, ops director, or ownership. Answer questions. Follow up on rate exceptions from the previous day. Identify the two or three dates that need action. This is the valuable part — the work the revenue manager was actually hired to do.
That sequence is roughly 90 minutes of total morning work. About 60 of those minutes are assembly — pulling, cleaning, combining, pasting. About 30 are actual analysis and discussion. For most revenue managers, the ratio is backwards from what it should be.
Where it breaks
The most common failure point is the PMS export step. Not because it's technically difficult, but because it's manual and therefore variable. If the export takes longer than expected, if the format changed after a system update, if the file lands in a slightly different location than usual — any of those add time to every subsequent step.
The second common failure point is the assembly sheet itself. A Google Sheet that's been in use for two years has accumulated complexity. Formulas that reference other formulas that reference a tab someone renamed eight months ago. Conditional formatting that fires incorrectly because a row got inserted in the wrong place. A column that was added for a specific one-time analysis and never removed. The sheet works until it doesn't, and when it doesn't it's not obvious why.
The hardest failure to see is the one that doesn't look like a failure. The brief goes out every morning. The numbers look reasonable. The team uses it. But a revenue manager spending 60 minutes on assembly every day is spending 260 hours a year — six and a half full work weeks — on work that produces no insight by itself. That's the invisible cost.
What a better version of the same routine looks like
The sequence doesn't have to change. The revenue manager still reviews a morning view, still flags the exceptions, still runs the standup. What changes is that the first three steps in the timeline — the pull, the rate shop check, the assembly — happen automatically while they're still drinking their first coffee.
The automation layer picks up the PMS export at 5:30am, normalizes the format, pulls the rate shop data from its scheduled export, computes the pickup and variance columns, applies the exception thresholds, and drops the finished view into the shared sheet. By 7am, the brief exists. The revenue manager's morning starts with the review step, not the build step.
The standup is the same. The rate calls are the same. The judgment is the same. The only thing that changed is that the 60 minutes of assembly were handled by a script that runs while nobody's watching, which means the 30 minutes of analysis get the manager's full attention instead of whatever's left after the assembly ran long.
The objection I hear most often
"We've tried to standardize this before and it never sticks." Usually what happened is someone built a more structured template and expected people to follow it, or someone set up a partial automation that broke when a source changed and nobody fixed it because nobody owned it.
The version that sticks is the one that doesn't require any behavior change from the team. The brief shows up looking exactly the way it looked before, in the same place, with the same columns. The only observable difference is that it exists before anyone had to build it. That's the version people keep using.
← Back to all postsHow much of your morning is assembly vs. analysis?
The workflow audit takes about five minutes and surfaces exactly where the time goes in your current morning reporting process — and which parts are worth automating first.