The Arrivals Report Runs Your Whole Day

There is a single document that decides whether my shift is calm or chaotic, and I read it before I take a sip of coffee. It is the arrivals report, the list of every guest due to check in that day. On most desks it prints out, gets a quick glance, and lands in a tray. That is a mistake. This one page is the closest thing the front office has to seeing the future, and if you actually read it, the whole day stops surprising you.

I learned this across very different buildings, from night audit at a Waikiki resort to rooms operations in San Francisco. The properties had nothing in common except this: the shifts that fell apart were almost always the shifts where nobody really read the arrivals report in the morning. The wave still came. They just met it blind, one guest at a time, at the counter, with a line building behind each surprise.

What is a hotel arrivals report, and why does it matter?

The arrivals report is the list of everyone expected to arrive on a given date, pulled straight from your property management system. It shows the room types owed, arrival times where the guest gave them, special requests, VIP and loyalty status, rate and package details, and length of stay. In plain terms, it is your forecast. Housekeeping has its board, sales has its group resumes, and the front desk has this. It is the single best answer to the question every AM lead should be asking at the start of a shift: what is today actually going to feel like?

Before going further, it helps to pin down the one term this whole piece turns on.

Read with intention, that single page is the closest thing the desk has to a forecast for the day.

Here is what most people miss. The report is not really about the names. It is about the shape of the day. How many rooms do I owe? What time do they land? Which room types are tight? Where are the guests who need something specific? Answer those four questions in the morning and you have already done the hardest thinking of the shift. Everything after that is execution, and execution is easy compared to the thinking.

Read it like a map, not a list

A list you read top to bottom. A map you read for terrain. When I open the arrivals report, I am not reading it like a roster. I am scanning for the pressure points, the places where the day could bunch up or break.

The first thing I want is the raw count against my availability. Rooms due to arrive versus rooms I will have clean and ready. That gap, or the lack of one, sets the tone for everything. On a tight day it tells me I need to be surgical about every early arrival and every late checkout. On a sold-out day it tells me to start thinking about the walk before it becomes an emergency, not after.

The report does not tell you what happened. It tells you what is about to, while there is still time to do something about it.

The count also tells me what kind of day I am running before the day tells me itself. A comfortable arrivals number against plenty of ready rooms means I can be generous with early checkins and flexible with requests. A tight number means I run lean and protect every room. And when the report shows more arrivals than I have rooms, which happens on a genuinely full house, it tells me to start planning for the worst case calmly, in the morning, rather than scrambling for options at nine at night. That early warning is the whole point. There is a big difference between managing a sold-out night from a plan you built at eight in the morning and managing it from panic at the counter.

Then I go looking for the specifics that eat time later. Connecting rooms for families. Accessible-room requests, which are non-negotiable and need to be protected early. Repeat guests and VIPs who expect to be recognized. Guaranteed late arrivals whose rooms I need to hold even when the house fills. Each of these is a small landmine if I find it at four o'clock, and a simple task if I find it at eight.

The read always runs in the same order, from the widest question down to the narrowest.

1. CountRooms due against rooms you will have clean and ready. This sets whether the day runs lean or generous.
2. ClockGroup arrivals by hour to find the wave, so you know when to brace and when there is slack.
3. Room typesFind the tight or oversold categories before a guest is standing in front of you.
4. FlagsVIPs, accessible and connecting rooms, and guaranteed late arrivals, each one a small task handled early.

Run in that order, the report resolves from a list of strangers into a handful of decisions you can act on.

A worked example: reading one morning's report

Let me make this concrete, because "read it like a map" is easy to say and harder to picture. Say I open the report at seven and it shows 180 arrivals against a house I expect to have fully clean by four. First read, the count: 180 arriving, roughly 175 rooms ready by mid-afternoon and the rest by early evening. That is tight but workable, so the day gets a "run lean" label in my head and every early checkout request becomes a real decision, not an automatic yes.

Second read, the clock. I group the arrivals by hour. Forty of those 180 land between four and six, which is the wave. Another cluster of thirty is a corporate block hitting around three. That shape tells me exactly when to have my full team at the counter and when I can let someone step off for a break. Third read, the room types. Two suites are oversold by one, and I only have three accessible rooms against four requests. Those are the real constraints, and I would rather know at seven than discover them at five with a guest standing in front of me. Fourth read, the flags: two VIP anniversaries, a connecting pair for a family of five, and one guaranteed late arrival at eleven at night whose room I will protect no matter how full we get. In ten minutes, a page of 180 strangers has become five decisions. That is the whole trick.

Laid out as a grid, that same morning's clusters make the shape of the day obvious at a glance.

The peak is not the raw total; it is those two stacked afternoon bands, and now I know exactly when to have everyone at the counter.

There is a habit of reading here that takes a while to build. A newer agent reads the arrivals report line by line and remembers almost none of it, because a list of names does not stick. An experienced one reads it in clusters. Ten arrivals in the same room type between four and six is a bottleneck, not ten separate events. Three accessible-room requests on a day you only have four such rooms is a single constraint you have to solve before anything else. A tour group and a corporate block landing within the same hour is a staffing decision. Once you start seeing the report this way, in groups and pressures rather than individual reservations, it takes less time to read and gives you far more. You are looking at terrain, and terrain has shape.

The pressure points I flag every morning

• Rooms due versus rooms ready. The gap decides how tight I have to play the whole day.
• Tight room types. If a category is oversold or nearly so, I know the puzzle before it lands on me.
• Accessible and connecting rooms. These get protected and assigned first, always.
• VIPs and repeat guests. Recognition is planned, not improvised at the counter.
• Early arrival requests and guaranteed late arrivals. The two ends of the day that quietly reshape your room flow.

How the report turns into action

Reading is only half the value. The point of seeing the day early is to do something about it while it is still cheap to do. A good read of the arrivals report flows straight into three moves.

First, I pre-block the hard rooms. Every guest with a real requirement, the connecting families, the accessible rooms, the VIPs, gets a specific room assigned in the morning, when I have options and a clear head. This is the single most valuable thing the report enables, and it pays back more than any other morning habit. When you pre-block rooms before the rush, the afternoon becomes a matter of handing out keys instead of solving spatial problems under a growing line. Every hard room you place at eight is one you are not untangling at the counter at four, with a guest watching and a queue forming behind them.

Second, I brief the team. The arrivals report is not just for the lead. In the pre-shift huddle I want the whole desk to know the VIPs by name, the tight room types, and the arrival curve. Everyone should be looking for the same landmines. A shared read means a guest who says "I think you have a note on my reservation" is met with recognition instead of a blank screen.

Third, I match my people to the curve. The report tells me not just how many are coming but when, and that shape is exactly what I schedule against. There is no reason to have the whole team standing at noon and be two agents short at five. Once I can see the wave, I can staff the desk to the arrival curve instead of spreading coverage flat and hoping.

The briefing is also where the report stops being one person's knowledge and becomes the team's. I have watched shifts where the lead read the arrivals report beautifully and told no one, and it barely helped, because the lead cannot be at every terminal at once. The value multiplies when the whole desk carries the same picture. A five-minute huddle where I walk the team through the day's shape, the VIPs, the tight types, the arrival curve, is worth more than any individual heroics at the counter later.

When should you run the arrivals report?

Twice, at least. I run it first thing on the AM shift, before email, before anything, because every decision I make that morning should be informed by it. Then I refresh it in the early afternoon, before the wave builds, because the day is alive. Reservations get added, arrival times firm up, a group picks up rooms, someone requests an accessible unit at the last minute. The morning read sets the plan. The afternoon read catches what changed. If you only look once, you are planning against yesterday's picture of today.

And a live report is only useful if the rest of the operation is live with you. The arrivals report tells me what is coming in, but housekeeping tells me what is actually ready to receive it. Those two pictures have to match, which is why the read does not end at the desk. It feeds straight into the front desk and housekeeping handoff, where "arriving at three" meets "room clean at two-forty" and the guest either walks upstairs or waits in the lobby.

What the report cannot tell you

For all of that, I want to be honest about the limits, because leaning on the report blindly is its own kind of mistake. The arrivals report is a forecast, and forecasts are wrong at the edges. Guests with a stated arrival time do not always keep it. A flight delay can push a block of your evening arrivals into a single late clump the report shows as spread out. Walkins never appear on it at all, and on a good-weather weekend they can add real volume you did not plan for. The report tells you the expected shape of the day, not the guaranteed one, and the best desks hold both ideas at once: plan hard against the forecast, and stay light enough on your feet to adjust when reality diverges from it.

The other common mistake is treating a name on the report as a promise. A guaranteed reservation is a commitment on paper, but no-shows happen, and a desk that has already given away a held room the moment a guest is ten minutes late has learned the wrong lesson from the report. Read it as probabilities, not certainties. A four o'clock arrival is likely, not guaranteed; a stated suite request is a strong signal, not a contract you can never adjust. The skill is holding the plan firmly enough to act on it and loosely enough to bend it when the day argues back.

The report will also not make the decisions for you. It will show you three early arrival requests on a tight day, but it will not tell you which one to accommodate first. That judgment is yours, and it gets better the more days you read this way. Over time you stop seeing a list of strangers and start seeing a day you have basically already lived once, in your head, at eight in the morning. When the real version arrives in the afternoon, most of it is familiar, and the few surprises are all you have to spend energy on. That is the quiet gift of reading the report well. It shrinks the unknown part of the day down to something a calm person can handle.

None of this is complicated. It is a page you already print, read with intention for ten minutes at the start of the shift. But those ten minutes are the difference between a desk that greets the day and a desk that gets run over by it. The rush is coming either way. The only question the arrivals report answers is whether you saw it coming, and I would rather meet the wave with a plan than meet it at the counter with a line to the door and no idea who is in it.