The best five minutes I spend all day happen before the day really starts. Before the arrival wave, before the lobby fills, before anyone at the desk has taken a single guest, I get the shift together for a quick huddle. We stand, we do not sit. It takes five minutes, sometimes less. And it changes the entire character of the shift that follows, because for those five minutes the whole desk stops being a set of individuals and becomes a team that sees the same day.

The pre-shift meeting is one of those practices that sounds trivial written down and is anything but in the running. Skip it and every agent discovers the day independently, one guest at a time, which is a slow and expensive way to learn that the house is oversold or that a difficult VIP is arriving at three. Run it well and the team walks onto the floor already knowing the shape of what is coming, already aligned on the one thing that matters most. It is the cheapest lever I have for a smooth shift, and it is the first thing that gets dropped when a desk is busy, which is exactly backward.

The practice has a name worth defining precisely before we get into how to run it.

Pre-shift stand-up. A short standing huddle, usually five minutes, that a front desk lead runs before the rush so the whole team shares one picture of the day: house count, arrival peak, VIPs and groups, carryover, and the single priority.

Named that way, it is less a meeting than a moment of alignment the rest of the shift is built on.

What the stand-up is really for

The purpose of the pre-shift is not information, exactly. Most of what I cover in it is technically available to anyone who reads the reports. The purpose is shared context. There is a real difference between information that exists somewhere in the system and a picture that everyone at the desk actually holds in their head at the same time. The huddle closes that gap. It takes the day out of the reports and puts it into the team.

Consider what happens without it. An agent takes a walkin at two, not knowing the house is nearly sold out, and quotes a rate we should not have offered. Another sends a guest to a room that was quietly being held for a VIP, because nobody told her it was held. A third gets blindsided by an arriving group of forty that the last shift knew about and never passed along. None of those are competence failures. They are alignment failures, and every one of them is prevented by five minutes of everyone hearing the same thing before the doors get busy.

A team that shares one picture of the day makes decisions the way one good person would. A team that does not makes decisions the way strangers do.

What a good pre-shift covers

The content of the huddle should be specific to today, not a generic recap of how the desk works. Everyone already knows how to check someone in. What they do not know until you tell them is what makes this particular shift different from yesterday's. So I keep the agenda tight and pointed at the day in front of us.

  • The house. How full are we, how full are we about to be, and where is the inventory tight? This one number frames every decision the team will make.
  • The arrival shape. When does the wave peak, and how big is it? This tells the team when to brace and when there is slack.
  • VIPs and groups. Who needs special handling, who is arriving when, and what has already been arranged for them.
  • Carryover. What came down from the last shift: the open service recovery, the held rooms, the followup due at nine.
  • The one priority. If the team does nothing else well today, what is it? Name it clearly and name only one.

That last point does more work than any other. A huddle that lists ten priorities has none, because the team cannot hold ten. When I name a single priority, the group at forty rooms tonight, the VIP anniversary at three, the oversell we are managing, I give the shift a center of gravity. Everything else flows around that one thing, and when the floor gets loud, the team already knows what not to drop.

A five minute script you can actually run

People ask me what a good huddle sounds like, so here is the shape I use, timed so it never runs long. Thirty seconds of recognition to open: one specific, true thing the last shift did well. About ninety seconds on the numbers: house count, where inventory is tight, and when the arrival wave peaks. A minute on the people: the VIPs by name, the groups and their timing, and what has already been arranged. Thirty seconds of carryover: the open issue, the held room, the followup nobody should drop. Thirty seconds on the single priority, said plainly. And the last thirty seconds belongs to the team, not me: anything I should know, anyone carrying something from yesterday. That is roughly four minutes of content and a minute of margin, and it fits in a doorway before the lobby fills.

Timed out, the huddle has a shape that keeps it from ever running long.

  1. Recognition, 0:30One specific, true thing the last shift did well.
  2. The numbers, 1:30House count, where inventory is tight, and when the arrival wave peaks.
  3. The people, 1:00VIPs by name, groups and their timing, and what is already arranged.
  4. Carryover, 0:30The open issue, the held room, the followup nobody should drop.
  5. The one priority, 0:30Said plainly, and only one.
  6. The team, 0:30Anything they should add before the doors open.

Held to that shape, the huddle stays short enough that nobody resents it and specific enough that everybody learns something.

I also use the huddle to make sure the standards travel, not just the logistics. It is easy to spend all five minutes on numbers and forget that the pre-shift is a chance to remind the team what good looks like on this desk. A quick word on how we greet, how we handle a guest who arrives frustrated, the small note we leave for a returning guest, keeps the service level from drifting shift to shift. Standards decay quietly when nobody restates them, and the pre-shift is the natural place to keep them alive without it feeling like a lecture. Thirty seconds on the how, not just the what, is often what separates a technically smooth shift from one a guest actually remembers.

How do you run one people actually value?

The failure mode of pre-shifts is that they become a ritual nobody respects, five minutes of the lead talking while the team waits for it to end so they can start working. When that happens, it is not the concept that failed, it is the execution, and it is almost always because the huddle got long, generic, or one-directional. A pre-shift that runs fifteen minutes or repeats the same speech every day teaches the team that it is a tax, not a tool.

The fixes are simple and they are all about respect for the team's time. Keep it to five minutes and end on time, every time, so the team learns it will never eat into their shift. Make it specific to today, so it always tells them something they did not already know. And make it useful, so they leave the huddle able to do their job better than they could before it. When the pre-shift reliably makes the shift easier, you do not have to enforce attendance. The team protects it, because they have felt what the day is like without it.

The other thing that makes a huddle land is that it draws directly on what the last shift left. A good pre-shift is not invented fresh each morning; it is largely read off the record the previous team wrote down. The clearer that record, the sharper the briefing, which is the direct link between the huddle and the front office pass-down log. When the log is precise, I walk into the pre-shift already knowing what is open. When it is vague, I spend the huddle guessing, and the team feels it.

Common mistakes that kill a huddle

  • It runs long. The moment a stand-up regularly passes seven or eight minutes, it stops being a stand-up and becomes a meeting nobody wants. Protect the clock harder than you protect the content.
  • It goes generic. If you could have given the same huddle yesterday, it taught the team nothing. Anchor every point to today's specific numbers, guests, and pressure.
  • It only lists problems. A huddle that is all warnings trains a team to brace and flinch. Name at least one win, so the team learns what to aim at, not just what to fear.
  • It runs one direction. If the lead talks and nobody else does, you waste the knowledge standing in the circle. Always leave room for the team to add.
  • It gets skipped when busy. The busiest days are exactly the ones that need alignment most. Skipping the huddle to save five minutes usually costs an hour later.

The part that is not about logistics

There is a second job the pre-shift does that has nothing to do with arrivals or the house count, and it is at least as important. The huddle is where the tone of the shift gets set. If I start it rushed and grim, the team carries that onto the floor. If I start it composed and specific, with a moment of genuine recognition for something the last shift did well, the team carries that instead. Five minutes of the lead being calm and clear is worth more than any pep talk, because the team reads the lead's state and matches it.

I make a point of naming good work in the huddle, briefly and specifically. Not empty praise, but a real observation: the way someone handled a difficult checkout yesterday, the save on an oversold night, the guest note that turned a complaint into a thank-you. It costs nothing and it does two things at once. It tells the person they were seen, and it tells the whole team what good looks like on this desk. A pre-shift that only ever lists problems trains a team to brace. One that also names wins trains a team to aim.

The huddle is also where I let the team talk, not just listen. The lead does not have every piece of information, and some of the most useful things I have learned about a coming shift came from an agent speaking up in the pre-shift: a returning guest who had a bad experience last time, a group contact who is particular about something, a room that felt off during yesterday's stay. A pre-shift run entirely one direction wastes the collective knowledge standing in the circle. So I ask. Anything I should know about today? Anyone carrying something from yesterday? The huddle where people feel free to add is worth far more than the one where they only receive, because a front desk knows things in aggregate that no single report ever captures, and five minutes is enough to surface the piece that saves the afternoon.

One more thing I have learned: the pre-shift is where newer agents get to see the whole picture, not just their slice of it. An agent who only ever works their own transactions never learns to think about the house, the curve, or the day as a system. Standing in the huddle and hearing the lead frame the shift teaches that wider view by repetition. Over weeks, a newer agent starts to anticipate the same things the lead does, because they have heard the day framed that way fifty times. The huddle is quietly a training ground for judgment, and the desks that run it consistently tend to grow their next supervisors faster, because everyone has been practicing the habit of seeing the whole floor.

From the huddle to the floor

The pre-shift is the setup, and the payoff comes the moment the team hits the floor. An aligned desk staffs itself better, because everyone understands where the peak is and can flex toward it, which is the same logic behind how you staff the desk to the arrival curve. An aligned desk reads the room better too, because agents who know a big arrival is coming at three are already watching for it, which sharpens the situational awareness I write about in reading the lobby in ten seconds. The huddle does not run the shift. It aims the people who do.

I have led teams of sixty to ninety and more, and the ones that ran smoothest were never the ones with the most talent stacked at the counter. They were the ones that started every shift on the same page. Talent scattered across a desk that does not share a picture will get shoved around by the day. Ordinary agents who all see the same day, know the one priority, and trust the lead's read will absorb a wave that should have buried them. The difference between those two desks is often nothing more than whether someone spent five minutes gathering them before the doors opened.

So when the shift gets busy and the temptation is to skip the huddle and just get on the floor, I do the opposite. That is exactly the day I make sure we stand together for five minutes first, because a busy shift is precisely when alignment pays the most. The calm you want at the peak is set in the quiet before it, in a five minute huddle that no guest ever sees and that quietly decides whether the desk in front of them is a team or just a group of people who happen to be standing next to each other.