Stop Calling Promotions Free Traffic

The new host on day three is still learning where to stand when the line bends toward the door. They know how to smile, greet, and keep moving, but they do not yet know which guest is relaxed, which one is in a hurry, and which one is about to ask why the offer online is not working at the register.

We hear a lot of hospitality wisdom that goes like this: a promotion is easy traffic. Get people in, ring the sale, keep it moving. But when the offer is timed, public, and tied to a big cultural moment, the truer read is different. A promotion is an operational event before it is a marketing win.

That is where a lot of bad shifts start. Not because the idea was foolish, and not because the team could not handle pressure, but because leaders treated demand as the whole story and missed the extra decision-making that comes with it.

In a recent piece in Nation's Restaurant News, Chipotle said it would run a buy-one-get-one entrée offer during the World Cup final, timed to the match's hydration break, and framed partly around guests who "accidentally" fill water cups with lemonade. That is a clever hook, and it will get attention. But the floor does not receive "attention" as an abstract concept. The floor receives a compressed burst of arrivals, more explanation at the counter, more exceptions, and more guests measuring fairness in real time.

The research on what happens next is not vague. Gallup's State of the Global Workplace has repeatedly found that managers account for 70 percent of the variance in team engagement. The useful read for hospitality is not that culture lives in a poster. It is that the quality of a shift changes materially based on whether the person running it gave the team a clear plan. And Toast has warned in its restaurant promotions guidance that promotions can increase traffic while also straining labor, inventory, and service if they are not planned against operations. None of that is theoretical to anyone who has watched a simple offer turn a clean lunch into a stack of recoveries.

Here is what this looks like in real life. The host gets asked whether the offer applies to mobile orders. The cashier needs to explain the timing three different ways in thirty seconds. A line cook starts seeing mix distortion on one high-appeal item because the deal pulls guests toward the same entrée path. Beverage use changes because guests who came for the offer add one more item, or argue over what counts. A manager leaves coaching and jumps on exception handling. A strong team can hold that together for an hour. A tired one can spend the next three hours trying to catch back up.

The received wisdom says the real job is to get more guests through the door. The truer job is to reduce the number of decisions each guest and each worker has to make once they get there.

That is the part these promotions often hide. The demand bump is visible, so leaders plan for bodies. The decision load is less visible, so leaders underplan the script. Yet in floor operations, script matters. Not robotic language, real clarity. What exactly qualifies. When it starts. When it ends. Who can override. What the host says first. What the cashier says when the app lags. What the expo says when one station gets buried. What the shift lead watches every ten minutes. If those answers live only in one manager's head, the team ends up improvising fairness guest by guest.

And guests can feel that improvisation immediately. They do not experience it as a planning gap. They experience it as, "Why did that person get the deal and I didn't?" or, "Why did I wait fifteen minutes for something that was supposed to be quick?" In hotels, restaurants, cafes, and stadium-adjacent operations, that same pattern shows up whenever a public offer collides with a tight window. The issue is rarely effort. The issue is whether the operation translated the promotion into a simpler shift.

For frontline teams, especially the newer ones, this matters because promotions tend to push the hardest conversations to the least protected roles. The host gets the first complaint. The cashier gets the policy debate. The runner gets the look that says the timing feels off. If that is you, and the rules keep changing midshift, that is not a personal failure. It is a system asking you to carry ambiguity in public.

For operators and managers, the lesson is not to stop promoting. It is to stop acting surprised when a marketing idea creates service work. A timed giveaway during a major event is not just more covers. It is a temporary rewrite of arrival patterns, item mix, guest expectations, and escalation paths. If you plan only labor count and not decision count, you are still underprepared.

There is pride in getting one of these windows right. A newer host steadies because the greeting is clear. The cashier has one sentence that resolves most confusion. The kitchen knows which item is about to run hot. The floor lead stays available for actual saves instead of doing policy archaeology at the counter. That is good operations, and guests feel it as ease, even if the room is busy.

Promotions do not test how much volume your team can endure, they test how much ambiguity your operation leaves behind.

So this week, stop launching or accepting guest-facing offers without writing the exception script first. Stop assuming the team will "figure it out" because they usually do. They probably will. But they should not have to do it in front of a line.