The email takes twenty seconds to write: “Which section of the ballroom did the client approve?”
Answering it can send three people into an old proposal, two shared drives and a hallway conversation with whoever was on the sales call. If three people each spend five minutes, that one email cost fifteen staff minutes before anyone counts the waiting or the interruptions.
I want people asking when they’re unsure. I also want the hotel to stop making them unsure about the same thing every week.
Measure the repeat work, not the people
Start with the work that had to be redone and the missing information that caused it. Don’t start with a ranking of who asked the most questions. The person asking may be the one protecting the event from a mistake everyone else missed.
Pick one handoff, say sales to conference services, and a short window. Tell the team what you’re trying to fix: a clearer decision record, better room content or fewer outdated floorplans floating around. People cooperate with an audit that’s obviously trying to help them.
Sort each question by cause
For every clarification, ask why it happened:
- Missing: the answer was never written down.
- Conflicting: two documents said different things.
- Outdated: someone used an old version.
- Hard to find: the answer existed but nobody could locate it.
- New: the client changed something or added a requirement.
- Judgment: it needed a technical call from AV, engineering or the chef.
Only the first four are friction you can remove. Asking which ballroom section was approved is rediscovery. Asking about the menu the client chose yesterday is planning. An AV review of a brand-new production design isn’t waste just because it happened over email.
Follow one cause across several desks
A room with two names can create work in sales, conference services and banquets. Count each correction as a separate person’s problem and you hide the one thing causing all of them.
Write down the shared cause and the total effort it created, without counting the same minutes twice. Keep waiting time separate from active digging.
Then fix one thing: align the room name, pick the official floorplan or add a field for the decision that keeps going missing. Repeat with similar events and see whether the questions drop.
A four-week version
Pick a handful of recently contracted groups. For each one:
- Count the clarifications needed to reconcile rooms, layouts and setups.
- Note which ones came from missing, outdated or unclear room information.
- Time the rework and note which department did it.
- Check whether anything led to overtime, a vendor charge, a concession or a last-minute reset.
- Decide whether shared, current room information could reasonably have prevented it.
Then improve the handoff and run the same check on the next batch. Ask both teams whether the new package was easier to use, and look at whether real costs changed. Don’t invent a standard dollar figure per mistake.
Watch quality, not just quiet
Fewer questions is only good if the instructions are also clearer and the corrections went down. A team that’s afraid to speak up can produce a beautifully quiet process right up until event day.
Keep the tracking light. If a field doesn’t help the decision you’re trying to make, drop it. You need useful evidence, not a second job for the event manager.
The finding you want sounds like “this missing decision caused repeat work, and this change helped.” It should never sound like “these people are the problem.”
What a good handoff should contain in the first place: The Contract Is Signed. Why Does Conference Services Have to Start Over?
