My first real relationship with hotel numbers started at three in the morning. As a night auditor at Alohilani, I was the one who closed the day and produced the report that leadership would read with their coffee a few hours later. I would roll the date, reconcile the revenue, and print the summary that said, in a single page, how the day had actually gone. I did not always understand everything on it back then. But I understood that this one page was the truth of the day, and that people who ran the building lived by it.
Years later, on the other side of that report, I learned how to read it like an operator. Because producing the numbers and using them are two different skills. Anyone can print a flash. Knowing what it is telling you, and what to do about it before the day gets away from you, is where the job actually lives. So let me walk through the morning report the way I read it now, running rooms teams that need me to see the story in the numbers before the shift starts.
What the report is, and what it is not
The daily revenue report goes by a few names. The flash, the daily flash, the morning report. Whatever the property calls it, it is the same thing: a short summary of how the hotel performed the day before and how the near future is shaping up. It lands early because hotel decisions are time sensitive, and a leader needs to know where things stand before the day forces choices on them.
What it is not is the P&L. The daily report is fast and directional, built from the numbers you can pull the morning after. The full financial picture, with all the costs walked down the page, comes later and lives in the monthly statement I described in read a hotel P&L like a GM. Think of the daily flash as the pulse and the P&L as the full physical. You take the pulse every morning because you cannot wait a month to find out something is wrong.
A single day in isolation tells you almost nothing. A day read against what you expected tells you what to do next.
The other thing the daily report is not is a verdict on your people. A soft night is not proof the team failed, and a strong one is not proof they carried it. Demand does a great deal of the work, and the report measures the whole market landing on your building as much as it measures anything you did. I keep that in mind every morning, because it is easy to read a bad number as a bad shift. Usually it is a bad date, or a market that softened, and the frontline did fine inside conditions they did not set. Separating those two things is part of reading the report honestly.
The numbers on the page
Every property formats its flash differently, but the core is always the same handful of measures, and they build on each other. Here is what I look at, and in roughly what order:
- Rooms sold and occupancy. How many rooms went out the door, and what share of the house that was. This is the volume, the plainest number on the page.
- ADR. The average daily rate, or what you earned per sold room. Volume without rate can be a busy, unprofitable night, so I never read occupancy alone.
- RevPAR. Revenue per available room, which folds rate and occupancy into one figure. It is the headline number, and I wrote about its uses and its trap in what RevPAR actually tells you.
- Other revenue. Food and beverage, parking, and the ancillary lines, so you see the whole take, not just the rooms.
- The comparisons. Actual against budget, against forecast, and against the same day last year. This is where the report stops being a scoreboard and starts being a signal.
The one that headlines the page deserves a plain definition:
Why is a single day almost meaningless?
Here is the mistake I see new managers make. They read the flash, see a big revenue number, and feel good. Or they see a soft one and panic. Both reactions treat the day as if it stands alone, and it does not. A number by itself is just a number. Its meaning lives entirely in what you compare it to.
A strong day is only strong if it beat what you expected. If you forecast a sold out night at a high rate and you delivered exactly that, you did your job, but there is no news in it. If a quiet Tuesday came in well above budget, that soft looking number is actually a win worth understanding, because something drove demand you did not predict. The comparison is the whole point. Actual against budget tells you how you are doing against the plan. Actual against last year tells you the trend. Actual against forecast tells you how well you are reading your own hotel, which is a skill that compounds. Read the day against those three lines and the same number that meant nothing suddenly tells you something you can act on.
The comparisons also protect you from the opposite mistake, which is celebrating a number that only looks big because the market handed it to you. A citywide event or a holiday can lift every hotel in town, and on those nights a record revenue figure is not a sign that you priced or sold well. It is a sign that demand was everywhere. The way you find out whether you actually captured that demand is to look at how your gain compares to the plan and to the prior year, and, if you have it, to how the wider market moved. A day that beat budget by a little while the whole market beat it by a lot is a day you left money behind, even though the top line looked great. The number felt like a win. The comparison told the truth.
This is also why I read revenue and rate together rather than fixating on either one. A day can post strong revenue because you sold a very full house at a soft rate, and that is a different story than a day that earned the same revenue on fewer rooms at a stronger rate. The first bought its number with volume and probably with more labor and more cost. The second earned it with rate, which flows to profit far more cleanly. The daily report shows you both, and the operator who reads only the revenue line misses which kind of day it actually was.
Here is that idea as a worked example, with illustrative numbers rather than any hotel I have run. Two days at a 200 room hotel land on exactly the same rooms revenue:
| Same revenue, two stories | Day A | Day B |
|---|---|---|
| Rooms sold | 180 | 150 |
| Occupancy | 90% | 75% |
| ADR | $170 | $204 |
| Rooms revenue | $30,600 | $30,600 |
If you read only the revenue line, these two days are identical. They are not. Day A filled 30 more rooms to reach the same number, which means more housekeeping hours, more amenities, and more wear on the building for the same top line. Day B earned it on rate, which arrives with almost none of that added cost, so it will show better underneath even though the flash headline matches. Read the two together and you see which day actually paid off. That is the whole reason I never let the revenue figure stand alone.
The rate gap the flash headline hides is easy to see once you chart it. Here are the two days by ADR, the same illustrative figures from the table:
Day B earned the same revenue on a stronger rate and a lighter house, so it carried less cost to get there. The flash headline treats the two as equal, but the rate bar is where the profit story actually lives.
The part that looks forward
The best daily reports do not just look backward at last night. They look ahead, and this is the part that changes how you run the coming week. The forward view is usually called pace, and it answers a simple question: for the nights still to come, how are bookings building compared to where they normally would be at this lead time?
Pace is an early warning system. If a date two weeks out is pacing well ahead of normal, demand is strong and it is a signal to hold rate or push it up, because you will fill the house without discounting. If a date is pacing soft, that is the moment to act, while there is still runway to drive demand, adjust rate, or open a channel. By the time a soft date arrives, it is too late. The room expires at midnight. Reading pace in the morning is how you fix a weak night before it becomes one, which is exactly the logic behind how forecasting drives every money decision. The forecast sets the plan, and the daily report is where you check the plan against reality every single morning.
What makes pace tricky, and what takes time to learn, is that not every date fills at the same rhythm. A business hotel books close in, so a midweek date can look empty ten days out and still finish strong on the strength of last minute corporate demand. A resort weekend or a holiday books far ahead, so if it is not pacing well early, waiting rarely rescues it. That means a soft pace number is not automatically an alarm. You have to know the normal booking curve for that kind of date at your hotel before you can tell whether soft means trouble or simply means early. Reading pace well is really reading it against the pattern, not against zero.
The other forward signal I never skip is the group and block picture, because a single large piece of business can swing a whole week. A group that picks up more rooms than blocked, or releases rooms it will not use, changes the house count for those nights in one move, and the transient rate strategy has to flex around it. The morning report is where I catch those shifts early, while there is still time to sell into freed up space or protect inventory a growing group will need. A hotel that watches only its transient pace and ignores the groups is reading half the page.
From reading to deciding
None of this matters if you stop at reading. The whole reason the report lands on your desk early is so you can do something while there is still time. So every morning I try to turn the page into a short list of decisions. Did last night beat or miss the forecast, and why? Is anything in the coming week pacing soft enough to act on today? Does the staffing plan still match what the house count is telling me? Is there a rate move to make while demand supports it?
That last question connects the money report to the floor. A strong pace on a future date is not just good news, it is a staffing input, because a full house needs the right people scheduled to serve it well. This is the loop that ties revenue to operations, and it is why a rooms leader reads the flash and the arrival curve together, not as separate documents. The number on the report becomes a shift you build, an idea I carry through staffing to occupancy without hurting service. Reading the report is the input. Building the day is the output.
What this means if you run a desk
When I moved into rooms operations in San Francisco, leading teams that ran from sixty to ninety people and more, the morning report became a habit I would not skip. Not because I loved numbers for their own sake, but because that one page told me where to point my attention before the day pointed it for me. A soft pace meant a conversation about rate. A strong last night that missed forecast meant I was misreading something and needed to learn what. The report was a teacher, and it taught me a little more about my own hotel every morning.
So if you are early in your career and the daily flash still looks like a wall of figures, start small. Find the three comparison columns, budget, forecast, and last year, and read every number against them. Ignore the rest until those make sense. Then add pace, and start asking what the coming week needs from you today. Do that for a few months and something clicks. You stop seeing a report and start seeing your hotel, breathing, day by day, in numbers. That is the skill. Not printing the page, the way I once did at three in the morning, but reading it well enough to change what happens next, which is the whole reason anyone bothers to print it at all.