Manager on duty in a hotel: the rounds, the log and what to check

A manager on duty (MOD) is the person who holds the hotel's authority when the general manager is off site: at night, at weekends and on holidays. The role is a written mandate, a fixed walking route through guest and back-of-house areas, and a log that turns what the walk finds into work orders and a morning handover.

It is 23:40. A lift has stopped between two floors, the restaurant is closing and a guest at reception wants a different room. The general manager's phone is off. Someone in the building has to be allowed to decide, and to write down what they decided. After reading this piece you will have a manager on duty checklist hotel teams can actually use: a mandate, a decision table, a walking route with checks at each stop, and a one-page log format.

What is a manager on duty in a hotel, and who takes the turn?#

A manager on duty is the person who carries the general manager's authority for a defined shift, usually the evening, the night, the weekend or a public holiday, when the GM and the heads of department are not on site.

The role is a mandate, not a job title. The name, the shift window, the mobile number and the spending limit are written down and posted where the team on shift can see them. A mandate nobody has read is the same as no mandate.

Who takes the turn varies by hotel: heads of department on rotation, a resident manager, or a dedicated night manager. In a small hotel it is often the most senior person on shift, which works only if the authority is written. The MOD is not a second general manager and not a security guard; the MOD does not run a department, but holds the building, decides within limits and records.

MOD, duty manager, night manager: the same job under different names#

Hotels use the terms interchangeably, and the differences are mostly about hours. A duty manager often covers the evening; a night manager owns the overnight window; a resident manager lives on site and covers the off-hours by default. What all three share is the mandate: written limits, an escalation route and a log.

The role exists because reports describe the past and a walk describes the present. The morning report carries the numbers; the walk carries what the numbers cannot see. If you are building that morning page, see the hotel daily report a GM reads in the morning.

What the role is not#

It is not a department head doing two jobs, and it is not a patrol. The shift opens with a handover in and closes with a handover out. A shift that starts without a handover starts blind, and the first hour is when small problems are still small. Three duties in one line: walk the property, decide within the mandate, record what happened.

What may the manager on duty decide alone?#

Only what the hotel wrote down in advance. A workable rule is that the MOD may spend a fixed amount per guest and per shift without asking, and must escalate anything touching safety, the law, a large sum or the hotel's reputation.

Write three tiers and give each one real examples: decide alone, decide and inform, escalate now. Guest recovery usually sits in the first tier: a room move, a meal, a transfer, a late checkout. A refund, a rebate on the bill or a free night is usually capped or escalated, because money decisions are hard to reverse.

Money has two limits, not one: a cap per guest and a cap per shift. Add who may authorise a call-out for a plumber, a locksmith or an electrician after midnight, and how that person is reached. Keep the escalation list on paper and in the phone: general manager, owner, technical manager, security lead, and the out-of-hours numbers for the lift, the boiler and the fire system.

Safety comes first and paperwork second. On a fire alarm, a guest taken ill or a burst pipe, the MOD acts, then records; nobody waits for permission to stop an operation that is unsafe. The MOD may always stop something on safety grounds: close a pool, stop alcohol service, shut an outlet. Restarting it is a morning decision with a name attached.

A sample three-tier decision table#

Walking a guest to another hotel when the house is full is a contract and practice question; decide in advance who books the replacement room, who pays for the transfer and who tells the guest, and confirm your own position with a legal adviser.

What is the route, and in what order should you walk it?#

Walk the way a guest arrives, then the way the building works: entrance, lobby, public areas, corridors and floors, food and beverage, then back of house, kitchen, staff areas and plant rooms.

The order is deliberate. Guest areas are inspected while they are busy, at check-in peak and during dinner service, because that is when queues, smells and broken things show themselves. Two short rounds beat one long one: an early evening round during peak service and a late round after closing catch different faults, and the late round is the only one that sees the kitchen at close.

Vary the time and the route. A fixed 21:00 route teaches the team exactly when to expect you, and the corridor that is never walked is the corridor that is never cleaned. Walk it on foot, with a torch and a phone, and stop to talk to guests and staff; the walk is an inspection and a conversation at the same time. Write findings down as you go, with the exact location. A finding remembered at 03:00 is a finding lost.

Budget about an hour for a full route in a mid-size hotel, and fifteen minutes for a shorter late round covering entrance, lobby, fire panel and plant rooms. The route is not the room inspection and not the morning meeting: rooms are checked by a supervisor before release, as covered in the room inspection a supervisor completes before a room is released.

Why plant rooms come last#

Plant rooms come last for two reasons. First, they are indoors, locked and always available, so they are the easiest stop to skip when the evening runs late. Second, they close the loop: you walk past everything the plant rooms keep alive on your way to them. If you schedule them first, dinner service pushes them out; if you schedule them last, only discipline pushes them out.

How to keep the route from becoming a ritual#

Change the start time, reverse the direction occasionally, and take a different department head with you now and then. A route that never changes stops being an inspection and becomes an appointment.

Guest areas: what to look for at each stop#

At every stop, ask the same four questions: what is broken, what is dirty, what is unsafe, and what would a guest notice before a staff member does.

The four questions at every stop#

The questions work because they force a verdict. "Looks fine" is not a finding; "dead lamp above the seating area, left of reception" is. Below is a short walk checklist; each item is something a person can see or touch in under ten seconds.

Restrooms are the fastest honest test of a hotel's standards. A smell is a finding, not an atmosphere.

Back of house and plant rooms: what the guest never sees#

This is where the next 48 hours are decided. A kitchen closing badly, a store left open, a leak above a ceiling or a fire panel in fault reaches a guest long before the morning meeting does.

The kitchen at close#

Check surfaces, fryer oil, waste removed, fridge and freezer temperatures recorded, gas off, no food left out, and staff leaving through the correct door. The late round is the only one that sees this, which is why one long evening walk is not enough on its own.

Stores and the loading bay should be locked, with deliveries not stacked in a corridor, waste separated and no boxes in front of an exit. In the laundry, look for lint, machine faults, and chemicals stored, labelled and locked. In staff areas, check the canteen, lockers, rest room and staff entrance. A staff toilet in poor condition tells you what the team thinks management thinks of them.

The plant room in five minutes#

Plant rooms: electrical room locked and dry, boiler and hot water, water tanks, pumps, generator fuel level and test log, and a fire panel with either no faults or a named person who knows about them. Outside: car park lighting, refuse area, pool plant and the chemical store.

How does a finding become a work order?#

A finding becomes a work order when it has an owner, a severity, an exact location and a date, and it is closed only when someone has checked the result.

Severity, owner, location, date#

Severity sets the response time, not the order of writing: safety, guest-facing now, guest-facing soon, cosmetic. Every finding gets written, but not every finding gets the same clock. Four fields make an entry usable: what is wrong, where exactly (building, floor, room or asset number), who owns it, and by when.

One photo wide and one close, taken where the problem is, saves an argument at 09:00 about which corridor and which ceiling. The same entry should be readable by the morning team without translation: the night's finding is the day team's task list. For the full path from complaint to closed job, see how a hotel maintenance work order runs from a guest complaint to a closed job.

Repeat findings are a different problem. The same item three nights running is not a work-order failure, it is a process failure, and it goes to the head of department by name. Closing needs a second pair of eyes for safety items: the person who reported the fault should not always be the person who signs it off.

What goes in the log, and how is it handed over?#

The log is a short factual record of the shift: what was found, what was decided, who was told and what is still open. It is written for the person taking over, not for the archive.

Fields: date, shift, MOD name, round times, findings by area, decisions with amounts, incidents, open items with an owner, and guest names only where the record genuinely needs them. Write facts, not opinions. "Corridor outside 412, carpet wet about 1.5 m, source unknown, towels down, plumber called 23:10" can be acted on; "housekeeping issue" cannot.

The one-page shift note#

Keep it to one page. A log that takes twenty minutes to write is a log that stops being written in a busy week. Handover is five minutes spoken plus the written note: the verbal part carries the tone and the risk, the written part carries the detail.

What the morning meeting should take from it#

The morning meeting takes the open items and the decisions, not the whole log. Reading the log aloud is how a useful record becomes a document nobody opens. The meeting that picks up these items well is the 15-minute daily operations meeting.

Personal data does not go in a shared notebook. Anything that identifies a guest belongs in the system's own record, not in a book that passes between shifts.

What to do next#

Write the mandate before the next shift, not after the next incident: one page naming who holds the hotel tonight, what they may spend and decide, the route they walk, and the fields the log must contain. Then walk the route once yourself, at the hour the MOD walks it, and see whether the log you designed is the log you would want to read at 08:00.