The hour before doors is the worst time to teach anyone anything, and yet it is when most door briefings happen. People arrive, some of them volunteers who have never done this before, and someone gathers them in a half-circle and talks for twenty minutes while everyone glances anxiously at the entrance. By the time the doors open, half of what was said has evaporated, and the door learns its job in front of the first hundred guests.
There is a better way, and it is shorter, not longer. A good door brief takes about five minutes because it covers only what someone needs to function in the first ten arrivals. Everything else is learned on the job, with a confident person nearby. The art is in deciding what goes in the five minutes and what does not.
Brief for the first ten arrivals, not the whole night
The mistake in most briefings is trying to cover every scenario before anyone has scanned a single person. The VIP who needs escorting, the lost ticket, the press list, the accessibility entrance: all of it gets crammed in at once, and none of it sticks because nobody has any context yet. The person at the door does not need to know how to handle a forwarded pass before they have checked in one normal guest.
So brief for the common case first. What does a standard arrival look like. Where do they stand, what do they show, what does the scanner do, what does a successful check-in look like on screen, and what do you say to wave them through. Get someone confident with that loop and they can handle the overwhelming majority of arrivals immediately. The edge cases come later, once the basics are automatic.
The five-minute brief, in order:
- The one job: scan the pass, confirm the green tick, welcome them in.
- What a problem looks like: a red result, a name that does not match, a pass that will not scan.
- The one rule for problems: step them aside, call me over, keep the queue moving.
- Where I am, and how to get my attention.
- A quick practice scan, so the first real one is not the first ever.
That practice scan is the most valuable thirty seconds of the brief. Reading about a check-in and doing one are different things, and you want the first real attempt to be the second time, not the first.
The one rule that prevents most door chaos
If you teach door crew nothing else, teach them this: when something does not work, step the person aside and call for help, rather than trying to solve it in the doorway. A stuck arrival blocking the queue is a far bigger problem than the stuck arrival itself. Move them to one side, let the line keep flowing, and deal with the problem without an audience.
Most door panic is not caused by hard problems. It is caused by a hard problem happening in the middle of a moving queue, with everyone watching.
This single habit, step aside and call over, means a nervous volunteer never has to solve anything difficult alone in front of a crowd. It also means your queue almost never stops, because one tricky case does not freeze the whole door. Keeping volunteers confident is mostly about removing the situations that frighten them, and we go further on that in keeping volunteers confident on the day.
Give people lanes, not a free-for-all
A brief is much shorter when each person has one clear job. If everyone is doing everything, you have to explain everything to everyone. If you split the door into lanes, you can give each person a short, specific brief and let them get good at one thing fast.
A simple split for a busy door:
- Scanners, who do nothing but scan passes and welcome people.
- A floater, who handles anything that gets stepped aside.
- A greeter at the front, who tells people which lane to join and answers the obvious questions before anyone reaches a scanner.
Each of those roles can be briefed in under a minute, because each is narrow. The greeter in particular takes huge pressure off the scanners, because most of the confusion is dealt with before it reaches the actual check-in. Giving crew their own lanes and logins is a broader topic, covered in giving crew their own lanes and logins, but even an informal version helps.
Brief the tools, not just the people
Half of a smooth door is the crew knowing what to do, and the other half is the tools doing the heavy lifting so the crew has less to remember. A check-in screen that shows the same three things every time, the count, the name, the next action, is a screen you barely have to explain. When the software is calm and predictable, the brief gets shorter because there is less to warn people about.
This is worth keeping in mind when you choose how to run your door. A complicated interface needs a long brief and produces hesitant crew. A simple one needs a short brief and produces confident crew. The five-minute brief is partly a result of the crew's experience and partly a result of the tools not fighting them.
After doors open
The brief does not end when the doors open. The first ten minutes are when you find out what you forgot to cover, so stay near the door and watch. When you see the same question come up twice, answer it once for everyone. When the rush passes, gather the crew for thirty seconds to flag anything that tripped them up. That running correction is far more effective than any amount of pre-event lecturing.
A five-minute brief works because it respects how people actually learn under pressure: a little to start, the rest in context, with help close by. Skip the marathon briefing, teach the common case, give people the one rule for problems, and let the door teach the rest. Your crew will be calmer, your queue will move, and you will have spent the hour before doors doing something other than talking.
