The Manager on Duty in a Crisis

There is a specific moment that defines the manager on duty. It is the moment when a problem grows past one desk, one department, one person, and starts touching the whole property at once. A power event that darkens the building. A weather night that fills the lobby with stranded travelers. A system failure at the worst hour, cascading into overbookings and a line out the door. In the ordinary run of a shift, everyone knows their lane. In that moment, the lanes blur, and the whole operation instinctively turns and looks for one person to make sense of it. That person is the MOD.

I have carried that role, and I have watched others carry it well and badly. The difference is almost never about knowledge or effort. The managers who struggle in a crisis are usually the ones working hardest, sleeves up, personally trying to solve every piece. The managers who hold it together are doing something that looks, from the outside, almost restrained. They are standing slightly back, seeing the whole board, and moving pieces. This piece is about what that restraint actually consists of, because it is a discipline, not a personality trait, and it can be learned.

What is the job, really?

Here is the trap almost every new MOD falls into: they think the job is to fix the crisis. It is not. The job is to make sure the crisis gets fixed, which is a different thing entirely. The manager on duty is the single point of decision, not the single point of action. The instant you confuse those two, you become the bottleneck. Every thread runs through your hands, you fall behind on all of them at once, and the whole operation slows to the speed of one overwhelmed person.

The MOD's real product is coherence. When things break, the natural state of a property is fragmentation: the front desk knows one thing, housekeeping another, engineering a third, and nobody has the whole picture. Guests get contradictory answers. Staff duplicate work or leave gaps. The MOD exists to be the one place where all of it comes together into a single, current understanding of what is happening and what happens next. That is a job only one person can do, and it is exactly the job you abandon the moment you dive into fixing a single problem yourself.

I learned this the way most people learn it, which is by getting it wrong first. Early on, faced with a property that had several things breaking at once, my instinct was to grab the most concrete problem and solve it with my own two hands, because solving felt like progress and standing back felt like doing nothing. What actually happened was that while my head was down on that one task, the other threads drifted, nobody was watching the whole, and small problems that a word from me would have caught grew into bigger ones. The lesson stuck: the moment I feel the pull to roll up my sleeves and personally handle the crisis is precisely the moment I am about to stop doing my actual job. Standing back is not doing nothing. Standing back and holding the whole picture is the single hardest and most valuable thing the role requires.

Triage: sort by what matters, not what is loudest

When several things go wrong at once, the first skill is triage, and triage is harder than it sounds because problems do not present themselves in order of importance. They present in order of volume. The guest shouting in the lobby feels like the emergency. The quiet issue nobody is flagging yet, the one about safety or about a booking situation that is about to cascade, is often the one that actually matters more. A good MOD has to resist the gravity of the loudest thing in the room.

The ordering I lean on is the same hierarchy that governs any hotel emergency: life first, property second, operation third. Anything touching a person's safety leaps to the top, no matter how quietly it arrived. Below that, protecting the building and its systems. Below that, keeping the operation running. Hold that ladder and a chaotic pile of problems suddenly has a shape. You are not choosing between equals. You are placing each thing on a rung and working top down.

Put the three rungs beside the reflex each one has to overcome and the ladder gets easier to hold under noise.

Notice that the right column is almost always the same trap: letting volume, rather than the ladder, decide where you go next.

The loudest problem is almost never the most important one. Triage is the discipline of looking past the noise to the thing that actually matters.

The practical move is to name the top priority out loud, assign it to someone, and then deliberately turn to the next one rather than hovering over the first. Naming it aloud does two things. It commits you to a decision instead of letting everything swirl, and it tells your team where the focus is so they can align behind it. Triage, at bottom, is deciding what not to touch right now with as much clarity as you decide what to grab first.

Delegate, or become the bottleneck

Once you have sorted the priorities, the temptation is to start knocking them down yourself, one by one, because you are competent and fast and you trust your own hands. This is the exact instinct that sinks a crisis. Every task you take personally is a task the rest of your team cannot help with, and it is a task that occupies the one person whose attention the whole building needs.

Delegation in a crisis is not a nicety. It is the mechanism that multiplies you. When you give a clear task to a clear owner and step back, you have effectively cloned yourself onto that problem while keeping your own hands free for the thing only you can do. The MOD who delegates well can run a property through a genuinely bad night. The MOD who delegates poorly can barely run themselves.

What good delegation sounds like under pressure

• Name the person, the task, and the finish line. "You own the lobby line, keep it moving, come find me if it backs past the door" is an assignment. "Someone deal with the lobby" is a wish.
• Give authority with the task. If you hand someone a problem but make them come back for permission at every turn, you have not delegated, you have added a step. Tell them what they are allowed to decide.
• Trust the owner and check the outcome, not the process. Hovering signals you do not trust them and pulls your attention right back to the thing you handed off.
• Match the task to the person. A crisis is a bad time to develop someone. Give the hardest threads to your steadiest hands and let them work.

Delegation like this only works if you have built the team for it before the crisis, and that is not something you can conjure in the moment. It grows out of the everyday work of trusting your people with real decisions, which I write about in empowering the desk to fix problems. A team that is used to being trusted on a normal Tuesday will catch what you throw them on a hard night. A team that is used to asking permission for everything will freeze the instant you need them to run.

How do you communicate when everything is moving?

The third pillar is communication, and it runs in three directions at once. The MOD is the hub the information passes through, and each audience needs something different.

Guests need reassurance and a next step. Not the full technical picture, not your stress, just an honest acknowledgment that something is off and a clear sense of what happens now. Managing the room full of guests during a visible crisis is a discipline of its own, one I get into in keeping the lobby calm in a crisis, and the MOD's job is to make sure that calm is being held even while a dozen other things are on fire.

Staff need specific instructions and explicit permission to act. In a crisis, people default to caution and wait to be told, which is exactly the wrong reflex when speed matters. The MOD has to counteract that by being clear and by actively pushing authority outward: yes, do that, you have the room to solve it, do not wait for me.

Leadership needs an early, honest heads up. The worst thing you can do to a general manager is let them discover a serious situation after the fact, or from a guest, or from a review. Even in the thick of it, a quick, factual notification up the chain buys you support and prevents the far worse conversation later. Managers who hide the mess until it is huge do it out of fear, and it always costs them more than the honesty would have.

Across all three directions, the constant is tone. The MOD's composure is not a private matter. It broadcasts. A rattled manager creates a rattled team creates a rattled lobby, and the reverse is just as true. The calm you carry is not decoration on top of the work. It is a functional part of the work, maybe the most important part, because it is the thing that lets everyone else do their jobs.

A worked example: three things break at once

Abstract advice is easy to nod at and hard to use, so let me run the pillars through a single bad hour, the kind of pileup that turns a manager into an MOD. Picture a full house on a stormy evening. Three things land inside ten minutes: a guest reports a strong burning smell on an upper floor, the property management system freezes with a line of arrivals waiting, and a loud dispute breaks out at the desk over a charge. Every one of them wants you now. Here is the order a steady MOD moves in.

1. Triage against the ladder, out loudThe burning smell touches life and leaps to the top even though it arrived quietly. It gets your first decision. The frozen system threatens the operation; it is serious but not dangerous. The dispute is the loudest thing in the room and, on the ladder, the lowest. You say the order aloud so the team hears it: safety first, system second, the desk argument last.
2. Assign owners with authority and a finish line"You, walk to the floor with me now and we call it in together." "You own the desk line, switch to the paper backup, you have authority to comp a late arrival's parking if it keeps things moving." "You, take the disputing guest to the side, listen, and hold until I am free; you can offer a folio review." Each person leaves with a task, a boundary, and permission to act.
3. Hold the picture, do not disappear into one taskEven while you walk to the smell, you keep a thread on the other two. You do not become the person personally keying in registrations. Your hands stay free so your eyes stay wide.
4. Communicate in three directions as it movesA quick line to the guests in the lobby that the desk is running a manual process and will reach everyone. A factual heads up to your general manager that you have a possible safety issue and a system outage in progress. And a steady word to your team that they are handling it well.
5. Close each thread deliberatelyThe smell is cleared or handed to responders, the system comes back and reconciliation begins, the dispute is resolved or scheduled for followup. You confirm each one is genuinely owned before you exhale.

Notice what the MOD did not do: personally solve any single problem. The value you added was the order, the owners, and the calm, which is exactly the value only the person at the center can add.

The mistakes that sink a manager on duty

The failures in this role are predictable, which is good news, because predictable failures can be trained out. A few show up again and again.

• Chasing the loudest thing. The dispute at the desk feels urgent because it is noisy. Letting volume set your priority order is the most common way an MOD gives a quiet, dangerous problem room to grow.
• Doing instead of directing. Grabbing a task with your own hands feels like progress and reads, to you, as leadership. It is the moment you stop holding the picture and become a bottleneck.
• Delegating without authority. Handing someone a problem but making them return for permission at every turn is not delegation, it is adding a step and keeping the decision on your desk.
• Hiding the mess from leadership. Managers who keep a serious situation quiet until it is huge do it out of fear, and it always costs more than the early, honest call would have.
• Forgetting the human close. Ending the crisis operationally but walking away without thanking a shaken team leaves people running on adrenaline with nowhere to put it.

After the wheels are back on

The MOD's job does not end when the immediate crisis passes. There is a handoff to make, a record to ensure exists, and eventually a review to run so the property learns from the night instead of just surviving it. In the hours right after, your team is running on adrenaline and needs you to signal that the worst is over, to thank them plainly, and to make sure nobody is left holding a loose end. The formal learning comes later, but the human close happens right away, and it is the MOD who sets it.

If you are working the overnight, all of this compresses, because the MOD role and the person alone at the desk may be nearly the same, with the fewest hands available. That version of the job has its own shape, which I cover in the overnight emergency playbook. But whether you are running a full team through a storm or holding a skeleton crew together at 3am, the three pillars do not change.

The role, in three words

• Triage. Sort by what matters, not what is loud. Name the top priority and place everything else on the ladder.
• Delegate. Give clear owners clear tasks with real authority. Stay out of the doing so you can hold the seeing.
• Communicate. Reassure guests, direct and empower staff, warn leadership early. Let your calm set the tone for all of it.

The manager on duty in a crisis is not the hero who single-handedly saves the night. That image is exactly the one that gets managers into trouble, because it pulls them into the weeds where they are least useful. The real MOD is quieter and more powerful than that: the person standing slightly back, holding the whole picture, making sure every problem has an owner and every person has a next step, and radiating a calm that lets a shaken building steady itself. Do that, and the wheels come back on faster than anyone expected, and your team walks away knowing they had someone at the center they could trust. Hold the picture, trust your people, and let your calm carry the room.