On a heavy arrival afternoon, you can tell within thirty seconds which agent prepped and which one did not. The prepared agent greets the guest, glances at a screen that already has the room assigned and the profile clean, confirms one or two things, and hands over a key with a real conversation happening the whole time. The unprepared agent is heads down, hunting for a room, discovering the rate looks wrong, and asking the guest to wait while a small problem becomes a five minute problem with a line forming behind it. Same PMS, same guest, completely different stay, and the difference was decided before either guest arrived.
That is the heart of fast PMS workflows, and it surprises people who think speed at checkin is about typing quickly. It is not, mostly. It is about moving the work to where the guest is not standing. Everything that can be done before arrival should be, so the moment at the counter is short because it is nearly empty of tasks. I learned this at the Waikiki Beach Marriott and again running rooms in San Francisco, and it is the single biggest lever a desk has over how the lobby feels. Here is how to build the workflow that makes checkin quick without ever making it careless.
Why the counter is the wrong place to work
The counter is where the guest experiences your preparation, not where you should be doing it. Every task you perform while a guest waits is a task performed under the worst conditions: someone watching, a line building, and your own attention split between the screen and the person. Work done there is slower and more error prone than the same work done twenty minutes earlier on a quiet arrivals list. So the goal of a good workflow is to empty the counter moment of everything that does not strictly require the guest standing there.
What actually requires the guest? Verifying who they are, confirming details only they can confirm, and securing payment. That is a short list. Everything else, the room assignment, the rate check, the profile cleanup, the special request setup, can and should happen before they arrive. When you strip the counter down to just the guest facing steps, checkin stops being a construction project and becomes what it should be: a warm handoff of a key to a room that is already ready for a person you already understand.
The counter is where the guest sees your preparation, not where you should be doing it.
What does pre-arrival prep actually cover?
Pre-arrival prep is the work you do on the day's arrivals before the lobby fills, and it is the highest leverage hour on the desk. You are reading the arrivals list the way a good auditor reads a balance, looking for the things that will bite later so you can defuse them now. The whole practice starts with reading that list well, which deserves its own attention and which I break down in the arrivals report, line by line. But here is what the prep itself involves.
The pre-arrival checklist
- Assign rooms deliberately. Match room type, connecting needs, accessibility, and any preference on the profile now, while you can think, not while a guest waits.
- Check the rates. A rate that looks wrong is a conversation. Find it on the list, understand the code, and resolve it before the guest asks about their bill.
- Clean the profiles. A missing loyalty number, a stale card, a preference not carried over. Fix what you can and flag what you cannot.
- Flag the ones that need a person. A VIP, a special request, a balance issue, an early arrival. Know which reservations will need a conversation so none of them ambush you.
To show why that quiet hour pays off, here is roughly how the counter time compares when an arrival is prepped versus walked in cold.
The prepped bar is short because the work moved earlier, not because a single step was skipped.
The point of the list is not to do the checkin early. It is to remove every surprise. When the guest arrives and everything you prepared holds, checkin is fast. When you skipped prep and the surprises land at the counter one by one, checkin is slow no matter how quickly you type. Prep is where the time is really made.
The fast checkin, step by step
Because people ask me to show it rather than describe it, here is the workflow I teach, split into the part you do before the guest arrives and the part you do at the counter. The whole design is to load the first list and empty the second.
Before the guest arrives
- Assign the roomOff the arrivals list, matching room type, floor, connecting, and accessibility to what the profile asks for.
- Confirm the rate planSo a package, corporate rate, or comp does not surprise anyone at checkout.
- Clean the profileLoyalty number attached, contact details current, preferences carried over from the last stay.
- Stage the folioFor known reservations with payment on file, so the bill is built and waiting rather than started live.
- Flag the conversationsMark the VIPs, early arrivals, and balance issues so you meet them ready instead of surprised.
At the counter
- Greet and locate the reservation you already prepped, so the screen is context you glance at, not a search you run.
- Verify identity against the ID. This one never moves earlier; it has to happen with the guest present.
- Confirm the one or two details only they can confirm: nights, departure, a card if payment is not yet secured.
- Secure payment, authorizing the card for the full expected stay, not just the first night.
- Cut the key and orient them, and the transaction is done in the time it takes to have a warm sentence or two.
Notice how short the counter list is. Everything heavy sits in the first list, done in the calm of a quiet arrivals hour. The guest experiences only the second list, which is why a well-prepped checkin feels effortless from their side of the desk.
The keystrokes, and what they are really for
Now to the part people expect, the actual speed on the system. Yes, learning your PMS well enough that your hands know the paths matters. Knowing the fast route through a checkin, the shortcut to the folio, the quick way to post a charge or split a bill, all of it shaves seconds, and seconds add up across a busy day. But I want to reframe why fluency matters, because the seconds are the smaller half of it.
The bigger reason to be fluent is attention. When your hands know the system, your eyes and mind are free for the guest. You can hold eye contact, hear the tiredness in someone's voice, notice they mentioned a special occasion, because you are not spending your attention hunting for a button. A slow agent is not just slow. They are absent, looking at the screen instead of the person, and guests feel that absence even when the checkin technically works. Fluency buys presence, and presence is worth far more than the thirty seconds. The judgment layered on top of that fluency, knowing when to override the system rather than obey it, is a whole subject I get into in what Opera PMS won't teach you.
Habits that build real speed
- Learn the paths, not just the buttons. Drill the common tasks until the sequence is automatic and your attention is elsewhere.
- Keep the profile open. The guest record is your context. Reading it as you work is how you catch the preference before they mention it.
- Batch the pre-keying. Prepare keys and folios for the arrivals you can, so the counter step is confirmation, not creation.
Pre-keying and the ready arrival
One workflow deserves its own mention because it changes the feel of a busy afternoon: preparing the arrival as far as the system safely allows before the guest reaches you. For known reservations with clean profiles and secured payment on file, you can have the room assigned, the folio set, and everything staged so that when the guest walks up, the remaining steps are verification and the key. Done well, this is the difference between a fifteen second greeting and a two minute transaction, repeated across every arrival on the list.
The discipline is knowing how far you can safely stage without cutting a corner. You never pre-verify identity, and you never assume a card that has not cleared. But you can absolutely have the room chosen, the rate confirmed, the requests set up, and the guest's context in front of you, so the counter moment is warm and quick because the machinery is already done. This staging is only possible because the PMS sits at the center of everything and lets you prepare each piece in advance, which is the whole reason the stack is built the way it is, a point I anchor in the systems that run a modern hotel.
Does fast checkin ever cut corners?
It should never, and this is the line I hold hardest with new agents, because speed tempts people to skip. A fast checkin is not a shortened checkin. It is a rearranged one. Every step that protects the guest and the property still happens: you confirm who they are, you confirm the rate they are paying, you secure the payment, you make sure the room actually fits their needs. None of that gets dropped. What changes is when it happens. The verification lands at the counter because it has to. Everything else was handled before, so the counter is light.
When I audit a desk that has gotten sloppy in the name of speed, the tell is always the same. It is not that they type too fast. It is that they moved a required step off the list entirely, stopped confirming rates or stopped checking that the assigned room genuinely matched the request, and called the missing work speed. That is not a fast workflow. It is an incomplete one that will generate a rate dispute or a room change an hour later, which costs far more time than it saved. Real speed is thoroughness moved earlier, never thoroughness removed.
The recovery workflow when prep is not enough
No amount of preparation catches everything, so a good workflow also has a plan for the arrival that goes wrong at the counter anyway. The room you assigned turns out not to be ready. The card declines. The guest arrives three hours early into a full house. What separates a calm desk from a flustered one here is not luck. It is having a rehearsed path for the common failures, so the agent is executing a plan instead of inventing one while a guest watches. The best agents I have worked with treat these moments as routine because they have run them before, in their heads and on real shifts.
The workflow for a snag is simple to state and hard to do under pressure: acknowledge it honestly, keep the guest oriented, and move to the fallback without a visible scramble. If the room is not ready, you do not freeze and reassign in a panic. You already know which comparable rooms are clean, because you read the status during prep, so you offer the alternative smoothly. The preparation that speeds up the easy checkins is the same preparation that rescues the hard ones. A desk that prepped the arrivals list is never truly surprised, only occasionally rerouted, and guests cannot tell the difference between a plan and a recovery when the recovery is that smooth.
Building the workflow into a team
Getting one agent to prep is easy. Getting a whole desk to prep consistently is a leadership job, and it is worth the effort because it changes the property's entire arrival experience. The way I have built it is by making prep a named part of the shift, not an optional extra someone does if they have time. There is a window before the arrival wave where the desk works the list together, splits the load, and clears the surprises. When that window is protected and expected, the afternoon rush stops being a rush.
The payoff compounds. A desk that preps well has shorter lines, fewer room changes, fewer rate disputes, and more attention to give each guest, which loops back into upselling and service and everything else the front office is measured on. It also has a calmer team, because nobody is firefighting surprises that a quiet hour of prep would have prevented. The agents feel the difference before the numbers show it, and once they feel it, they defend the prep window themselves.
So if you want faster checkins, stop looking for a faster typist and start building a better workflow. Move the work off the counter and onto the arrivals list. Learn your system well enough that your attention belongs to the guest. Stage every arrival as far as it safely goes. Never confuse a shortened process with a rearranged one. Do all of that and the busiest arrival afternoon of the month will look, from the guest's side of the counter, like the calmest desk they have ever checked into, which is exactly the impression you were trying to make all along.
Questions from the desk
How can a front desk speed up checkin?
Most of the speed is won before the guest arrives. Pre-assigning rooms, resolving profile and rate issues in advance, and pre-keying the arrivals with special needs turns the counter moment into a short, warm confirmation instead of a scramble. The fastest checkin is the one you mostly finished an hour earlier.
What is pre-arrival prep in a PMS?
It is the work an agent does on the arrivals list before the lobby fills. It includes assigning rooms, flagging VIPs and special requests, checking that rates and profiles are clean, and spotting any reservation that will need a conversation, so nothing surprises you at the counter.
Do keyboard shortcuts really matter at the desk?
They add up. A few saved keystrokes on one checkin is nothing, but multiplied across a busy arrival day it is real time and a calmer desk. More importantly, fluency frees your attention for the guest, so you are looking at a person instead of hunting for a button.
Does a faster checkin mean cutting corners?
No, and it should not. The goal is to move the work earlier, not to skip it. Verifying identity, confirming the rate, and securing payment still happen. A good workflow front-loads everything that does not require the guest, so the counter moment is short because the preparation was thorough.
What are the actual steps of a fast checkin?
Before arrival: assign the room, confirm the rate, clean the profile, stage the folio, and flag anything that needs a conversation. At the counter: greet, verify identity, confirm the one or two details only the guest can confirm, secure payment, and hand over the key. Everything that does not need the guest happens earlier.
How much time does pre-arrival prep actually save?
A prepped arrival can drop from a two to three minute transaction to a fifteen to thirty second confirmation. Across a heavy arrival wave of dozens of rooms that is the difference between a backed-up lobby and a calm one, plus far fewer room changes and rate disputes later in the shift.