Check-in queues: how many desk agents a peak hour needs, from your own arrivals data

Check-in wait time is the minutes between joining the desk line and receiving a key. To plan it, take your own arrivals per hour, multiply by the minutes one check-in takes for that guest type, divide by 60, then add one spare agent: a queue grows faster than the arithmetic suggests near full load.

A transfer bus empties at the door and thirty guests walk to a desk staffed by two agents. Nothing in the shift plan called this a peak, because the plan counts rooms sold, not people arriving in the same ten minutes. After reading this you will be able to estimate the desk load for any hour from your own arrivals data, decide how many agents and stations that hour needs, and know which minutes to remove first.

Where do the minutes in a hotel check-in actually go?#

A check-in is four blocks of work, not one: confirming who the guest is, taking payment, explaining what they need to know, and handing over the keys. Each block has its own length and its own way of being shortened.

Identity comes first. The document is checked in person at the desk, and the guest identity notification (KBS, misafir kimlik bildirimi) is prepared from the check-in flow. In Türkiye, every stay involves a payment, a fiscal document (an invoice or e-document), a guest identity notification (KBS) and personal data (KVKK, the personal data protection law). Each of these steps has to happen somewhere in the stay, so none of them can be squeezed out of the desk conversation; they can only be prepared.

Payment is usually the longest block and the one that fails most often. A card pre-authorisation, a deposit, a prepaid booking that only needs verifying, or a split between two cards: each is a different length. A second attempt at a terminal costs minutes nobody planned for.

Explanation is short per guest and the most movable block: breakfast hours, wifi, the pool, parking, the lift, the questions every guest asks in the first two minutes. A printed card or a guest app carries most of it.

Keys are the handover: encoding cards, writing room numbers, matching connecting rooms, and the walk to the lift. Preparing keys before the peak turns this block into a handover.

The blocks differ sharply by guest type. A solo business traveler on a prepaid rate, a family with two rooms and a child, and a group with a rooming list are three different transactions with three different lengths. One number for all of them will mislead the roster.

Time a sample of twenty check-ins block by block for one week. The result tells you which block to attack, and it is usually not the one the team blames.

How do you get arrivals by hour from your own data?#

Use three sources together: the arrival time the guest gave, the transfer or flight schedule, and the timestamp of the actual check-in. The gap between the plan and what happened is the number that ruins staffing plans.

Pull the arrival list from the hotel management system (PMS) and sort it by hour, not by date. For example, a night with 90 rooms sold can have 12 arrivals in one hour and 3 in another. The daily total hides exactly the hour you are staffing.

Count guests, not only rooms: multiply each booking by its own occupancy. Two rooms with four guests each are a different load from two single rooms, even though both are two check-ins.

Flag the batches: transfer buses, shuttle times, flight arrival boards and tour operator drop-offs. A bus is a batch, not a trickle, and it lands as one event. Compare promised arrival time with the actual check-in timestamp for the last eight to twelve same-weekday nights: one night is a story, a month of Tuesdays is a pattern. Watch the tail as well; the last two hours before midnight often carry delayed flights, late drivers and released no-shows, which arrive together and without warning.

Keep the sheet simple enough that a duty manager can update it. A study nobody refreshes becomes a document about last winter.

How many desk agents does a peak hour need?#

Multiply arrivals in the hour by the minutes one check-in takes, divide by 60, and you have the agents who are busy. Round up, then add one spare agent for exceptions.

Split the minutes by guest type before multiplying. A weighted average of prepaid and pay-at-desk check-ins is more honest than one number for everybody. The result is agent-minutes, not a headcount: dividing by 60 converts it into how many agents are occupied during that hour, which is the input to a roster, not the roster itself.

Stations matter as much as people. Two agents sharing one card terminal and one key encoder is one agent with a queue in front of it. Add the fixed work that shares the same hour, too: telephone calls, walk-ins, room moves, extra towels, and the preparation for night audit. Those minutes come out of the same pool.

Round up, never down. If the calculation says 1.6 agents busy, the answer is two agents working and a third available, not one and a half. Then check the calculation against the observed wait. If two agents produced a fifteen-minute line, the minutes per check-in were underestimated, and the estimate, not the team, is wrong.

Here is the arithmetic as a worked example. Every number is a labelled example, not a benchmark; your hotel's own numbers replace them.

Why does a queue grow faster than the arithmetic suggests?#

Because the arithmetic assumes a steady stream and arrivals come in bursts. When the desk is nearly full, one slow transaction delays everyone behind it, and the line does not clear before the next burst lands.

Utilisation, in plain words: at half busy, a burst is absorbed by the idle half. At nine-tenths busy, the same burst becomes a line, because there is no idle half left to absorb it. Variability sets the wait, not the average: a passport that needs a second look, a card that fails, a guest who wants to change rooms. The average check-in is calm; the slow tenth is what people remember.

Batch arrivals create the queue in a minute and take an hour to clear. Thirty guests from one bus cannot be served faster than the desk can serve them, whatever the plan said. Blocking makes it worse: a guest with a problem can hold one agent for twenty minutes, the other agents absorb the line until they cannot, and then the whole desk stops moving.

Run the recovery test: after a burst, can the desk clear the line before the next arrival wave? If the answer is no, the queue carries over into the next hour and the next shift. This is why one agent is kept free for exceptions rather than added to the line. That agent is not idle capacity; it is what stops a single problem from becoming everybody's problem.

How do you cut the minutes each check-in takes?#

Move work out of the queue: collect what you can before arrival, prepare keys and folios in advance, and give groups their own desk, their own agent and their own process.

Ask before arrival: estimated arrival time, contact details, payment method, room preference, and who is traveling. Each answer removes a question from the desk conversation. What to ask guests before arrival is a list worth building once and reusing every season.

Settle payment where the booking allows it, so the desk verifies instead of charges. A prepaid arrival is a handover, not a transaction. Prepare in a batch before the peak: keys encoded for expected arrivals, registration cards printed, folios opened, connecting rooms confirmed. This is fifteen quiet minutes that buy an hour of calm.

Give groups a separate desk and a loaded rooming list, with keys handed out per room and charges routed to a master folio. Group bookings handled at the main desk block every independent guest behind it.

Fix the order of the steps and write it down, so a new agent is nearly as fast as an experienced one and every guest gets the same sequence. The check-in procedure step by step should live at the desk, not in someone's memory. Then measure again after the change: one minute saved per check-in is eighteen agent-minutes in the example hour above, which is most of a second agent.

What do you do for guests who are already waiting?#

Waiting is tolerable when it is bounded and comfortable: give an honest time, take the luggage, offer a seat and a drink, and start the parts of check-in that do not need the desk.

Promise a time, not a feeling. A number the guest can hold on to, and then keep it; if it slips, say so before the guest asks. Triage the line: a prepaid guest with no questions can be handled in ninety seconds at a side station, while a guest with a problem goes to the exception agent.

Take the physical weight away: luggage to the room or to storage, a seat, water, somewhere for children to sit. A guest who has put the bags down is already calmer. Let waiting guests enter their own details on a tablet or a link while they stand in line, so the desk only confirms; the data is typed once, by the person who knows it best.

The minutes after the key matter as much as the minutes before it. A short wait followed by a confused arrival still reads as a bad check-in, which is why the first ten minutes from the door to the room belong in the same study. And record the wait: a timestamp when the guest joins the line and another when the key is handed over. Next month's plan should use those numbers, not impressions.

Does the same method work for checkout peaks?#

Yes, with two changes: departures cluster harder than arrivals, and the work per guest is shorter but the payment and document steps are heavier.

Pull departures by hour from the PMS, not by day. A fixed checkout hour creates a spike in the last sixty minutes before it, and that spike is predictable to the minute. Minutes per checkout go to bill review, payment, the fiscal document, luggage and farewell; the bill conversation is where the time goes, especially when a charge is disputed.

Express checkout removes the desk visit entirely for guests with no dispute: bill sent, key dropped, receipt issued. The line that remains is the line that actually needs an agent.

The overlap is an opportunity. The morning checkout peak and the afternoon arrival peak can share staff if the shift is planned as a curve rather than a block, which is the core of fair shift planning across the desk, floors and nights. Remember what sits behind the morning peak: the business day is closed by night audit, and the desk clearing a line is also finishing yesterday's work.

Same formula, same spare agent, same check against observed waits. The method is a habit, not a one-off study.

What to do next#

Pull the arrival curve for the last eight same-weekday nights, time twenty check-ins block by block with a stopwatch, and run the multiplication once. That single sheet turns a staffing argument into a number the team can check, and it gives you a baseline to measure every change against, from pre-arrival data to a separate group desk.