Run an effective preshift meeting people actually use

I have sat through preshift huddles that were a complete waste of everyone's time, and I have run a few of them myself before I knew better. The manager reads the same three reminders they read yesterday, recites a corporate line nobody absorbs, asks "any questions" into a silence that means no, and sends everyone to the floor exactly as unprepared as they arrived. The team learns, correctly, that this meeting is a tax they pay to start their shift, and they pay it with their bodies while their minds are already elsewhere.

The frustrating thing is that a preshift is one of the highest-leverage few minutes a floor leader gets. Done well, it is the moment you turn a group of individuals who happen to be scheduled together into a team that knows what today needs from them. Done badly, it is worse than nothing, because it teaches people that your meetings can be safely ignored, and that lesson bleeds into every other thing you try to say. The difference between the two is almost entirely about whether the preshift is actually useful, every single time.

What is a preshift really for?

A preshift is not an announcement session. It is an alignment session. The goal is not to transmit information at the team, most of which they could read on a screen, but to make sure everyone walks onto the floor holding the same picture of what today is going to demand. On a front desk, no two days are the same. A quiet Tuesday and a sold-out Friday with three VIP arrivals and a group checking in at 4 are completely different shifts, and the team needs to know which one they are walking into before it hits them.

So the real question a preshift answers is: what does today, specifically, need from us? Not what does every day need, not what does the handbook say, but what is different about this shift that the team should carry with them. When I frame it that way, most of the filler falls out on its own, because the recycled reminders do not answer that question and the team knows it.

It also helps to separate the preshift from the handoff that feeds it, because the two answer different questions.

The handoff feeds the preshift, but collapsing the two into one is how both end up done badly.

A preshift is not for what the team could read on a screen. It is for what only today needs from them.

The best preshift I can run comes straight out of the same reading I do at the start of my own shift. Before I say a word to the team, I have already looked at the shape of the day, and the huddle is just me sharing the part of that picture the team needs. In that sense a preshift is the public version of the private work I describe in the first hour of a manager on duty shift. I cannot run a useful huddle if I have not first read the day myself.

What actually belongs in the huddle

Over the years the content settled into a short list. Not a rigid script, because a script is how a preshift dies, but a set of questions I make sure I have answered before I let the team go.

1. The shape of the dayHow busy, when the pressure lands, what the arrivals and departures look like. Straight from the arrivals report, translated into "here is when it gets hard."
2. The VIPs and the special situationsWho needs extra care, which room got moved and why, the guest returning after a problem last time. The specifics that let an agent look like the property remembered.
3. The one likely pressure pointThe single thing most likely to go sideways today, named out loud so nobody is surprised by it: a tight housekeeping turn, a late group, a maintenance hold on a room type we are short on.
4. Today's one focusA single thing I want the team to hold onto through the shift. Not ten priorities, which is the same as none, but one: warmer greetings, cleaner handoffs, a specific standard we let slip yesterday.

That is genuinely most of it. The discipline is subtraction, not addition. Every item I am tempted to add, I test against one question: does the team need this to run today well, or am I saying it because it is on a list somewhere. If it is the second, it goes. A preshift stays alive by staying lean, and it dies the moment it becomes a container I feel obligated to fill.

What a good three-minute preshift sounds like

To make the shape concrete, here is roughly how one of mine goes on a busy afternoon, start to finish, in about three minutes. "Okay, quick huddle. Today is heavy: 130 due in, and the pressure lands between four and six when the group overlaps the transient rush, so brace for that window. Two VIPs tonight, the Tans in 1204 are a return after a housekeeping miss last visit, so we want that one to feel effortless. The likely pressure point is kings, we are tight, so if you are quoting an upgrade, check inventory before you promise it. One focus for tonight: the greeting before the ask, all the way through the rush, because that is the thing that slipped yesterday when it got busy. Anything from last night I should know? Anyone seeing something I am not?" Then I stop and actually listen, and I close with one specific bit of recognition from the day before. That is it. Shape, VIPs, pressure point, one focus, a real question, one thank-you. No filler, nothing they could have read on a screen.

The one thing to focus on beats the ten things to remember

The single focus is the part I would fight hardest to keep. Human attention on a busy floor is narrow, and if I send the team out with ten things to remember, they remember roughly none of them, because none of them was marked as the one that mattered. If I send them out with one, they carry it. And because I only pick one per shift, I can actually connect it to what I am seeing, which makes it land as leadership instead of nagging.

Choosing that one thing is also how a preshift reinforces standards without turning into a lecture about them. If greetings slipped at hour ten yesterday, today's focus is the greeting, framed as a thing we are proud of rather than a rule we are enforcing. That is the same patient, repeated connection between the small task and the pride in it that makes standards that stick when the manager is not watching. A preshift is one of the few tools I have to do that work on purpose, a little at a time, day after day.

How do you keep it from becoming noise?

Here is the failure mode that kills every huddle eventually: it becomes a ritual. The team can predict every word before you say it, so they stop listening while appearing to listen, and now you have a meeting that costs real time and transmits nothing. Once a preshift becomes noise, it is very hard to make it signal again, because you have trained the team to tune it out and untraining that is slow work.

The defense is relentless usefulness. Every single preshift has to earn the team's attention on its own merits, which means every one has to be different, because the day is different. The fastest way to become predictable is to recite the standing announcements, so I cut them. If something can go in a written log or a group message, it goes there instead of into the huddle, where it would just be filler that teaches people the huddle is filler. I protect the preshift's usefulness the way I protect a scarce resource, because that is exactly what it is.

I also keep it short on purpose, even on days when I could talk longer. Ending a huddle while the team still has attention left is how you keep them wanting to be there tomorrow. A preshift that runs long, that becomes a standing meeting people dread, has already failed no matter how good the content is, because the length itself is now the message. Short and useful beats thorough and dreaded every time.

Let the team talk

The other thing that keeps a preshift alive is that it is not only me talking. The people who worked yesterday know things I do not: which guest was difficult and might still be around, what broke last night, where the housekeeping crunch actually landed. A huddle that is a pure monologue wastes all of that, and it quietly tells the team that their read of the floor does not matter to me, which is the opposite of what I want them to believe.

So I ask, and I mean it. Anything from last night I should know? Anyone seeing something I am not? On a good day someone surfaces the thing that would have blindsided me at 6 p.m., and now we are ahead of it. On every day, the act of asking tells the team that this is a shared read of the shift and not a briefing delivered down at them. That small shift in ownership is a big part of why the useful preshifts feel useful. The team is not receiving the plan. They are helping build it.

The preshift is a small act of leadership

It is easy to think of the huddle as a logistics formality, a box to tick before the real work starts. It is more than that. Those few minutes are one of the only times in a shift when the whole team is together and looking at me, and everything I do in that window teaches them something. A rushed, bored preshift teaches them that today is just another shift to get through. A sharp, specific, warm one teaches them that today matters and that I have already thought about how to make it go well.

The team also reads my energy in that moment and borrows from it, the same way they borrow my composure on a hard night. If I start the huddle flat, the shift starts flat. If I start it with genuine focus and a little warmth, that carries onto the floor with them. I do not have to be loud about it. I have to be present and prepared, which the team can feel instantly and which no amount of scripted enthusiasm can fake.

A preshift is also one of the few reliable moments I get to catch people doing something right. When a guest praised an agent yesterday, or someone handled a hard checkout with grace, the huddle is where I can name it in front of the team, briefly and specifically. That thirty seconds does more for morale and for standards than a dozen private compliments, because the whole team hears what good looks like and who did it. Recognition given in the huddle also teaches the room what I actually value, which is far more persuasive than a poster on the back wall telling them the same thing.

There is a quieter benefit too, one I only noticed after years of running these. The preshift is the one point in the day when I get to look at every member of the team, together, before the floor pulls us all into our separate lanes. In those few minutes I can see who came in tired, who seems off, who is carrying something. That read shapes how I run the rest of the shift: who I check on, who might need a lighter section, who I should hand something bigger to because they are clearly ready for it today. The huddle is not only me giving the team information. It is me gathering it, in the one window where the whole team is in front of me at once.

None of that works if the preshift itself is dead. All of these benefits, the alignment, the recognition, the read of the room, sit on top of one requirement: that the team actually shows up present rather than enduring it. Which brings the whole thing back to usefulness. Protect the preshift as a genuinely useful few minutes and it becomes a tool that does five jobs at once. Let it decay into ritual and it does none of them, no matter how faithfully you hold it.

If your preshifts have gone stale, and most do without maintenance, the fix is not a better template. It is a harder question, asked before every huddle: what does today actually need from this team, and what is the one thing I want them to carry onto the floor. Answer that honestly, cut everything that does not serve it, keep it short, and let the team speak. Do that consistently and the preshift stops being the tax people pay to start their shift and becomes the few minutes that make the shift run better, which is the only reason to hold it at all.