After 5 EventsThe venue was chosen for the activity, not the evening
The climbing park has no indoor space. The manor house kitchen closes at seven. The conference centre's restaurant is a hallway with six tables. These are not problems during the zipline, but they are the entire problem three hours later when there is nowhere to put thirty people who are supposed to be talking to each other.
This happens because the activity comes with a venue, and it is easy to assume that venue works for the whole day. It does not. An activity venue is built for the activity. The room you need for the evening — with tables, with a bar that can serve thirty people in under twenty minutes, with enough space that a circle of chairs does not feel like a staff meeting — is a separate requirement.
Ask before you book the activity: what happens here after six? If the answer is that people leave, you are planning two events, and the second one has no location.
There is no plan for the transition
The activity ends at five. Dinner is booked for seven. Two hours sounds like plenty of time, and it would be if the activity venue were next door to the restaurant and everyone were already changed and the bus were waiting. It is not, they are not, and it was not.
What actually happens: the activity runs late, because activities do. People need to change, and there is one bathroom. The bus is twenty minutes away and takes forty minutes to get back to town. You arrive at the restaurant at twenty past seven and half the group is annoyed before they sit down.
The transition is not dead time. It is the first part of the evening, and if it is chaotic or rushed, the evening starts chaotic and rushed. Either the activity and the dinner are in the same place, or there is a genuine buffer — an hour at the venue with drinks, or transport that does not require everyone to be ready at the same minute. Schedule it as if something will go wrong, because something will.
The evening has no structure, so it has no momentum
Dinner is booked. People sit down, they eat, they talk to the two people next to them, and then it is over. No toast, no moment, nothing that makes the evening different from lunch. By nine-thirty the organisers are wondering why people are leaving.
A team-building evening is not a regular dinner. The entire point is that people talk to each other across the usual lines, and that does not happen by accident. It happens because someone structures it: a welcome that names why everyone is here, a moment between courses that gets people moving, a close that marks the night instead of letting it drift.
This does not mean speeches. It means someone thought about rhythm — when people sit, when they stand, when there is a reason to talk to someone three tables away. Without that, you have booked a restaurant, not an evening.
The sound system is assumed, not specified
The restaurant says they have sound. What they mean is there is a Bluetooth speaker behind the bar. You find this out when someone tries to give a toast and nobody past the fourth table can hear it.
Sound is not a detail. If anyone is speaking — a welcome, a toast, a thank-you, a game with instructions — and the room holds more than twenty people, you need a system that reaches the back clearly. Restaurants have background music systems. They do not have systems for speech, and speech is harder than music. You are asking for clarity in a room that was built to scatter sound, and a ceiling speaker cannot do it.
Ask what the sound system is for. If the answer is music, assume it will not work for speech. If the answer is that they host events all the time, ask to hear it. If the venue does not have what you need, it is a line item, not an assumption.
The organiser is also the crew, and has no evening
Someone has to meet the bus, check people in, make sure the restaurant has the final count, deal with the person who did not bring a jacket, find out why the projector is not working, and run the transitions. If that person is the organiser, the organiser does not get an evening. They get a shift.
This is the quietest mistake and the most common. The organiser planned the event, so the organiser ends up running it, because there is nobody else. They are the one people come to with questions, and they are the one watching the clock, and they spend the night making sure everyone else is having a good time.
There is a reason crew and hosting are separate roles. Crew runs the room so the host can be present. If you are doing both, you are doing neither properly. Decide early whether you are hosting or producing, and if the answer is hosting, someone else needs to be the person with the radio and the timeline.
The two kinds of event company
One kind takes your brief, marks it up, and sends it to a roster of subcontractors they may never have worked alongside — a sound company here, a caterer there, a driver somewhere else — and earns on every line. The other kind quotes, builds and runs the night with the same people. You will not hear the difference in the sales call. You will hear it at six-fifty when something needs to change and there is either someone with a radio who can fix it, or there is a forwarded email thread.
After 5 Events is the second kind. The crew writing this is the crew on the floor.
What to decide now
You know the activity and you know the date. Before you call anyone, settle three things: whether the evening is in the same place as the activity, what the transition between them looks like, and whether you are running the night or someone else is. Everything else is negotiable once those are clear.