Front desk supervisor duties: what the person running the shift owns

A front desk supervisor owns the shift, not the department. They read arrivals against sellable rooms before the shift starts, place agents where the peak falls, approve small exceptions inside limits the hotel sets, sample-check registrations, KBS (guest identity notification) entries and cash, correct agents away from guests, and close the drawer and the handover with the next leader.

An agent is made shift leader on a Friday and works the Saturday night shift alone: a full arrival list, one room out of order, a guest disputing a minibar charge and two agents who both want to be at the desk at eight. Nothing in the job they were doing before prepared them for that hour. This article sets out front desk supervisor duties as they are actually lived during a shift: what to read before it starts, how to place people at peak, which exceptions you may approve, what to sample-check, how to correct an agent, and how to hand the floor over intact.

What changes on the day an agent becomes a shift leader?#

The work stops being a list of tasks and becomes a shift that has to be covered, decided and handed over. The new leader still checks guests in, but no longer only that.

An agent is measured on the tasks they complete. A shift leader is measured on whether the desk held at peak, whether exceptions were decided inside their limits, and whether the next shift started with accurate information. Three new objects of attention come with this: the arrivals against the rooms actually sellable, the people on the floor and where they stand, and the promises made to guests that outlive the shift.

The role sits between the agent and the duty manager. The shift leader carries the floor; the duty manager carries the building and the night. Write the role down before the promotion, not after the first dispute: a short document naming what the person decides alone, what they decide and report, and what they must escalate. The most common failure is a promotion with no change of mandate: the person keeps the agent's task list, adds the supervisor's responsibilities on top, and burns out inside a season.

Then tell the team what changed, in plain words. Who to bring a problem to at 21:00 is a fact the whole desk needs, not only the person promoted. A written job description, reviewed with the new leader in their first weeks, is one way to make the mandate explicit; a hotel orientation process is another place to anchor it.

What does a front desk supervisor do before the shift starts?#

They read the shift before they work it: arrivals against sellable rooms, the previous handover's open promises, and the people available to cover the peak.

Arrivals against rooms is the first comparison. Take the arrival list and set it against the rooms that can actually be sold and occupied, after out-of-order rooms, late departures and unassigned groups are removed. The gap between the two lists is the shift's first problem, and it is cheaper to find at 15:00 than at 23:00.

Read the handover for commitments, not events. A guest promised a late checkout, a room move agreed for tomorrow, a charge to be reviewed: each one is a debt the shift has to pay or renegotiate. Check the special cases before they arrive, including groups, guests with accessibility needs, repeat guests, and any booking whose notes contradict its rate or room type.

The ten-minute pre-shift read#

Confirm who is on the floor and when the relief falls. A break plan written at the start of the shift survives a busy hour better than one improvised during it. Look at the day's shape too: the arrival curve, the departure curve, and the restaurant or spa bookings that will pull guests through the lobby at the same time.

What to do when the arrival list and the room list disagree#

Note what you cannot fix and say so early. An overbooked night or a broken room is a duty manager decision, and raising it hours before the guests arrive gives the manager options: a room brought back into service, a walk arranged on the hotel's terms rather than in a panic. When the lists disagree, the shift leader's job is to quantify the gap, name the affected arrivals and bring the problem upstairs, not to solve it quietly at the desk.

How does a shift leader place people at peak hour?#

By matching the shape of the arrival curve to the tasks that cannot wait, and by putting the strongest agent where the queue forms rather than where the work is calmest.

Separate the desk's work into what must happen at the counter, such as check-in, key handover and payment, and what can happen away from it, such as registration completion, phone calls, billing corrections and wake-up calls. At peak, move the second person off the counter: a colleague working the queue, checking documents and answering questions before guests reach the desk shortens the wait more than a second pair of hands behind it.

Count the hour before you staff it. Arrivals per hour from your own list, times an average check-in, divided by the minutes available, gives a starting number of agents for that hour; the same arithmetic, worked through with real numbers, is described in how many desk agents a peak hour needs. Protect one person from the queue entirely during a heavy arrival window, so billing questions, group check-ins and the phone do not stop the line.

Watch for the leader who steps behind the desk at the first queue. Helping is right; taking over is not. The leader's job at peak is the queue, the exceptions and the room moves, not the fastest check-in. Plan the relief before the peak, not during it: a break taken at 19:30 is a break; the same break at 21:15 is an absence.

Which exceptions may a front desk supervisor approve, and which go to the duty manager?#

The shift leader approves small, reversible, guest-facing exceptions inside a written list the hotel sets. Anything that changes money beyond that list, moves a guest out of the hotel, or sets a precedent goes to the duty manager.

The test is not the amount alone. Ask whether the decision is reversible, whether it is visible to other guests, and whether refusing it would end the conversation. Two of three yes usually means escalate.

These are examples a hotel might set and write down, not a rule. The same logic extends to rate decisions generally: who may change a rate, and by how much, belongs in written discount limits and override rules, not in a manager's memory.

The three questions before approving anything#

Is it reversible? Is it visible to other guests? Would refusing it end the conversation? A late checkout to 13:00 is reversible and invisible to other guests: shift-level. A refund is neither easily reversible nor invisible: duty manager. A room move when the house is full is visible to every guest who asks the same thing afterward: escalate.

Why a written limit protects the supervisor#

Write the limits down with numbers and time windows, and date the document. A limit that lives in a manager's memory changes with the manager's mood and cannot be taught to a new leader. Record every approved exception in the shift log with the reason, not only the amount: the pattern of exceptions is what tells the manager whether the limits are set correctly. Tell guests who decided, honestly. A guest who hears that the supervisor approved it inside the hotel's rules trusts the answer more than one who hears that someone will see what they can do.

What should a front desk supervisor sample-check during a shift?#

A small, rotating sample of the things that fail silently: registrations, KBS entries and cash. Sampling finds systematic errors while they can still be corrected, which a full audit weeks later cannot.

Registrations first: pull a few check-ins from the shift and compare the identity document, the registration card and the record in the system. Look for missing fields, mismatched names and unsigned forms. For KBS, the guest identity notification, confirm that notifications for the shift's check-ins were prepared and sent from the check-in flow, and that no arrival was left without one; where an entry is wrong, correct it through the same flow rather than beside it. The full check-in sequence is set out in a front desk checklist for guest identity and KBS.

Count cash with the agent at handover, not after they leave. A difference found with the person present is a training moment; the same difference found the next morning is an accusation. Sample the billing, not only the cash: a few open guest bills checked for posted charges, correct routing and anything left unposted that will surprise the guest at checkout.

How many is a sample#

Rotate what you sample, and keep it small. Checking the same agent every shift teaches the others that the check is about that person rather than the standard. A few items per category per shift, varied from day to day, is enough.

What to do with a difference you find#

Write what you found and what you did, in one line each. Three similar findings in a month are a process problem, not three individual mistakes, and the shift log is where that pattern becomes visible.

How do you correct an agent in the moment, away from the guest?#

Fix the guest's problem at the counter, then correct the agent privately within the same shift. The guest should see the outcome, never the correction.

Take over the transaction, not the person. Step in with a sentence that hands the guest a solution, and let the agent stay beside you so they see how it was resolved. Correct in the back office, in three parts: what the guest saw, what the standard is, and what to do next time. Keep it to the specific event, not the person's general ability, and do it before the shift ends: a correction held for a weekly meeting loses the detail and arrives as a verdict rather than a lesson.

Ask before you assume. A registration missing a field is sometimes a system problem, a queue problem or a form that was never restocked, not carelessness. Praise in the same currency: if you correct in private, say the good things in private too, or the team learns that only mistakes get attention. For a new agent in their first weeks, keep the correction to one thing at a time and check the next attempt yourself; too many corrections in one shift teach nothing.

How does the shift close, and what does the next leader inherit?#

The shift closes with the drawer counted with the agent, the day's exceptions recorded, and a handover that lists open promises, not a diary of events.

Count the drawer with the agent before they leave the building; a signature on a count nobody witnessed records a number, not a fact. Record the shift's exceptions with reasons: what was approved, what was refused, what was escalated and to whom, so the manager can see whether the limits are working.

Write the handover as commitments: guest name, room, what was promised, by when, and who owns it on the next shift. Anything without an owner is a complaint waiting to happen. Flag the physical state of the house too: rooms that came back late, rooms that should be out of order, maintenance issues reported by guests that have not been logged yet. Hand over in person where the shifts overlap, and keep it short: the written handover is the record, the conversation is where questions get asked. Read the next shift's arrivals before you leave, so the promises you made are ones the next leader can actually keep. The fuller version of this closing routine is in the front desk shift handover checklist.

Write the role down before the next promotion#

One page is enough: what the shift leader decides alone, what they decide and report, and what goes to the duty manager. Then walk a new leader through a pre-shift read, a peak plan and a handover before their first solo shift. The duties in this article only hold together when the limits, the sample checks and the handover are written rather than remembered.