Hotel Operations Dashboard: What GMs and Ops Leaders Actually Need Every Morning
Most hotel operations dashboards are revenue dashboards with the GM's name on the distribution list. They show rate position, pickup pace, and RevPAR vs. budget — useful data, but not what the person running the building needs to start their day. Operations leaders and revenue leaders work from the same property but they need different morning views.
The revenue brief and the ops brief are different documents
A revenue manager starts the day asking: where is rate pressure today, what is pickup doing, and what needs a pricing adjustment before the next booking window closes? The view they need is forward-looking, focused on available inventory, and oriented around revenue optimization decisions.
A GM or VP of Operations starts the day asking: what is walking through the door today, what does the building need to be ready for, and is anything about to go sideways? Their view is present-oriented, focused on the physical operation, and oriented around service delivery and staffing decisions.
Most hotel management companies send both audiences the same spreadsheet. The revenue team squints past the staffing notes. The ops team scrolls past the rate shop. Everyone has the data they need and the context they don't.
Revenue Brief
- OTB occupancy vs. budget and prior year
- 7-day and 21-day pickup pace
- ADR, RevPAR, rate vs. comp set
- Forecast gap to budget
- Underpriced or soft-demand dates
- Channel mix and segment trends
- RMS recommendations and overrides
Operations Brief
- Today's arrivals, departures, stayovers
- VIP arrivals and special requests
- Group arrivals and room blocks
- Housekeeping workload and staffing
- Open maintenance tickets by priority
- Out-of-order rooms affecting today
- Expected occupancy and covers for F&B
What a useful hotel operations dashboard actually shows
The ops morning view has a different structure than the revenue view. It answers a specific set of questions about the building's readiness for the day ahead. Here's what belongs in it.
Today's occupancy snapshotRooms occupied last night, expected departures, new arrivals, and projected stayovers. This drives housekeeping room assignments, staffing counts, and linen requirements — before the revenue team's rate calls happen.
VIPs, specials, and group arrivalsAny guest with a note, a loyalty flag, a comp authorization, or a group block. The GM should not learn about the CEO staying in room 412 at check-in. This belongs in the morning view, early enough to brief the front desk and housekeeping leads.
Out-of-order and out-of-service roomsWhich rooms are blocked today and why. How many are maintenance-related vs. deep clean vs. renovation hold. Whether any OOO rooms are blocking inventory that revenue needs to release.
Maintenance ticket summaryOpen tickets by priority — not the full list, but the count by urgency band plus anything guest-facing that's been open more than 24 hours. One line per critical item is enough. The goal is visibility, not a full work order system in the morning email.
Housekeeping workload estimateDepartures + stayover room freshens + arrivals. This number drives staffing decisions that need to be made before 8am — before housekeeping leads have started assigning rooms, and before front desk has begun check-in prep.
F&B and outlet contextExpected covers for breakfast service, group meal functions, and any events that require early kitchen prep. If the property runs a restaurant or banquet service, this is ops-critical data that typically sits in a separate S&C system and rarely makes it into the morning brief.
Exception flagsAnything that deviates from normal operating parameters — a group with a late arrival window, a VIP with an outstanding special request, a suite that's still being turned, a maintenance item that hasn't been resolved since yesterday's brief. The ops view should surface exceptions, not bury them in a full data table.
Why ops dashboards are usually late, incomplete, or wrong
The operational data required for a hotel ops morning view comes from at least three separate systems: the PMS (for arrivals, departures, and room status), a maintenance or property management platform (for open tickets), and a sales and catering system or shared calendar (for group functions and events). None of these systems talk to each other automatically.
The result is that the ops brief gets assembled the same way the revenue brief does: manually. Someone logs into the PMS, pulls room counts, checks the maintenance log, verifies the group arrival list, and compiles it before the team meeting. The brief is only as current as the last time someone ran the process.
The problem is not that the data doesn't exist. It exists in each system. The problem is that someone has to extract it, assemble it, and deliver it every morning — and when that person is busy, traveling, or out, the ops team starts the day without a clear picture.
What a sample hotel ops morning brief looks like
Below is an anonymized example of an ops-oriented morning view for a mid-size property. The revenue metrics are present but abbreviated — just enough context for the GM, not a full revenue report. The operational detail gets the primary real estate.
The multi-property ops challenge
A single property's ops brief is manageable to assemble manually, even if it's tedious. Across a portfolio of 10 or 15 properties, it becomes a full-time job — or a job that doesn't get done consistently.
The multi-property ops leader typically wants two things: a portfolio-level exceptions view (which properties have something that needs their attention today) and the ability to drill into any individual property's full operational picture. Most management company reporting stacks serve neither view well. The portfolio roll-up shows revenue metrics. The property-level view requires logging into each PMS individually.
The automation path here is the same as it is for revenue reporting: the data already exists in the source systems. The gap is the assembly layer between the raw exports and a morning view the team actually uses.
Where automation fits in the ops reporting workflow
The source data for an ops morning brief — room counts, arrival lists, maintenance summaries, F&B covers — comes from scheduled PMS exports, a maintenance log export, and whatever the S&C or calendar system can produce. Most of these can be delivered via scheduled email or file export without any API integration work.
Once those source deliveries are reliable, the assembly step can be automated: parse the arrival file, match the maintenance export, pull the F&B function list, and produce the ops brief in the format the GM and housekeeping leads already expect. The result is the same view the team has always used — it just arrives before anyone sits down, and it stays current without manual intervention.
If a source file is late or missing, the brief should say so clearly rather than showing yesterday's numbers as if they were today's. That reliability behavior is usually the most valuable part of the first pilot — not the report itself, but the fact that the team can trust what they're looking at.
The ops brief and revenue brief can come from the same underlying automation system. They pull different data and go to different audiences, but the reliability infrastructure underneath them is the same. Building both from a single source inventory is usually the natural path after the first pilot proves out.
What to audit before building an ops dashboard
Before building anything, map the sources: which system holds arrivals and departures, how maintenance tickets are tracked, where F&B functions are logged, and whether any of these can produce a scheduled export or email attachment. The inventory of available sources determines the scope of the first build.
The most common blocker is not a missing API — it is not knowing which exports are available and whether they are already being scheduled. Most PMS systems can produce a daily arrivals report, a housekeeping report, and an in-house report on a scheduled basis. If those three are already arriving somewhere, the ops brief is usually a 2-3 week pilot away.
← Back to all postsWant to see what your ops brief source inventory looks like?
The source report inventory maps every scheduled report your morning workflow depends on, including what happens when it doesn't arrive. That's the starting point for an ops brief automation pilot.