The 5 Source Reports Behind Every Hotel Morning Brief
Every hotel management company I've worked with builds their morning view from roughly the same five sources. The names change depending on the PMS. The format changes depending on who's pulling them. But the underlying reports are almost always the same — and that consistency is exactly what makes automation practical.
This matters more than it might sound. If the sources are consistent across portfolios, then the automation pattern is also consistent. You're not building something custom for each company — you're solving a problem that exists the same way almost everywhere.
Here are the five reports, what each one does, and where the manual work actually lives.
This is the foundation of every morning brief. It shows what actually happened yesterday: rooms sold, occupancy percentage, ADR, RevPAR, and usually some segment breakdown between transient, group, and contract. Every PMS produces it — Maestro, Opera, Cloudbeds, Mews, all of them.
In most operations, someone exports this in the morning, either as a PDF, a spreadsheet, or a scheduled email attachment, and uses it as the baseline for the day's review.
Opening the export, pulling the key numbers, comparing them to the same day last week and same day last year. That comparison is almost always done by hand.
Where yesterday tells you what happened, the OTB report tells you what's coming. It shows how the next 7 to 30 days are pacing — rooms on the books by date, how pickup has moved over the past week, and which dates are accelerating or stalling.
This is the report most revenue managers spend the most time in. The pickup story is what drives rate decisions today. Strong pickup on a high-demand date is a signal to push price. Soft pickup on a date that should be filling is a signal to review strategy before it's too late to act.
Comparing today's OTB snapshot to last week's, calculating the week-over-week change by date, noting which dates are moving in the right direction and which aren't. This is often done in a spreadsheet that someone updates manually each morning. If you want a structured starting point for what the pickup view should contain, the hotel pickup report template walks through the fields and what to flag.
Most hotel groups subscribe to a rate intelligence tool — Lighthouse, OTA Insight, RateGain, or similar. These tools track comp set rates across OTA channels and deliver the data as a scheduled export or email report.
The rate shop tells you where you're priced relative to the market on each date. Underpriced on a high-demand night? Overpriced when the comp set has dropped? This is where those gaps show up, and it's essential context for any rate decision made that morning.
Opening the export, finding the dates that matter, comparing own rate to the competitive midpoint, noting the gap. For a multi-property group, this gets repeated for each property — the same manual steps, multiplied by the number of hotels in the portfolio.
Every property has a budget, and most have a rolling forecast. The morning brief usually includes a check on where actuals are tracking against both — month-to-date occupancy, ADR, and RevPAR compared to what was planned.
This tells you whether the property is ahead or behind for the month and by how much. It's the context that makes the other data meaningful. Strong pickup on a date that's already running ahead of budget looks different than strong pickup on a date where you're behind and need the volume.
Pulling actuals from the PMS and referencing the budget file to calculate the variance. This almost always lives in a spreadsheet that someone updates manually each morning, often maintained by one person who owns it entirely.
Not every group uses this as part of the daily morning brief, but many do. The channel manager report shows where bookings are coming from — which OTA, which rate plan, what the channel mix looks like for the next few weeks.
It's particularly useful for properties with heavy OTA dependence or active direct booking programs where channel performance shifts meaningfully from day to day. For groups managing rate parity across channels, it's an essential morning check.
Pulling the export and cross-referencing it against the OTB picture to understand not just how many rooms are booked, but which channels are driving the booking pace and at what rates.
Why the consistency matters
The reason these five reports can be automated reliably is precisely because they're consistent. The same sources, pulling at the same time, producing the same output format, every morning. That's the pattern automation is built for.
What makes manual assembly slow isn't that the data is complicated. It's that someone has to open five separate files, cross-reference them against each other, and write the combined view by hand — every morning, for every property in the portfolio.
Automating the assembly doesn't require replacing any of these reports. It means connecting them — pulling from each source automatically, combining the data, and delivering the view that currently takes 45 minutes to build in essentially no time at all. The team still reads the same information. They just don't have to assemble it.
The starting point, in every project I've done, is mapping exactly which versions of these five sources the team uses — what they're called, where they live, what format they arrive in, and who touches them. That map is what the automation is built from. If you want to do that mapping now, the source report inventory tool lets you document each source, its delivery method and schedule, and what the workflow should do if it doesn't arrive — which is the first reliability question worth thinking through before any build starts.
← Back to all postsKnow which of these five sources your team uses?
The source report inventory documents each one — what it's called, how it arrives, when it's expected, and what the workflow should do if it's late or missing. That inventory is the starting point for any automation build.