Conference

Conference — a guide for the team lead

A conference is two events pretending to be one. The day session needs microphones that work the moment a speaker steps up, a screen visible from the back without glare from the windows, and changeovers that do not leave forty people watching a technician crouch by a laptop. The evening needs a different room or a very fast reconfiguration, and by then everyone is tired and the atmosphere depends on things working without hesitation.

Most of what goes wrong is structural: a venue chosen for its price or location without asking whether the room can carry sound, a timeline that assumes everything will run to schedule, an AV brief that describes outcomes — 'we need good sound' — instead of naming what will actually happen.

The venue decides what is possible

You need two things from a room and most conference venues deliver one. The first is sightlines: every seat must see the screen without neck strain, and daylight must not wash it out. The second is acoustics, and this is where optimistic planning meets physics. A glass-walled room with hard floors will throw every word back as mush by the time it reaches the fourth row, and no microphone solves that — the microphone makes it louder mush.

Walk the room before you commit. Sit in the back corner. Ask what happens to the tables during the evening portion, because a room that works for a seated presentation often becomes a long corridor once the chairs are cleared. If the answer involves moving everything to another space, add thirty minutes to the timeline and expect half your guests to vanish during the changeover.

Restaurants are rarely conference venues. They have ambient music systems, not PA. They have mood lighting, not stage light. If the plan is 'we'll just bring a screen and a microphone', the plan is that the back third of the room will not hear the middle section of every sentence.

The technical brief is a list, not a wish

Write down every session and what it requires: one presenter with slides, a panel of four with handhelds, a video that must play without buffering. Then write down what happens between sessions — how long it takes to mic the next speaker, whether the laptop changeover is the presenter's own device or a single machine everyone loads onto in advance.

If there is a livestream or recording, it becomes the critical path for everything. The camera cannot wait. The stream cannot drop. That means a wired internet connection, not venue WiFi, and it means a technician whose only job that day is to ensure the stream does not become the thing everyone remembers.

Ask the venue what power is available and where it lives. A projector, a PA, a livestream rig and a coffee station can trip an unlabelled breaker twenty minutes into the morning session, and finding the fuse box becomes a theatrical performance no programme includes.

The timeline is always wrong

Add fifteen minutes to every estimate you make, because a session that overruns by eight minutes will compress every break, push lunch into the afternoon slot, and turn the evening event into something that starts in daylight and ends when half the team has already left for the last bus.

Registration takes longer than you think if the list is not printed and alphabetised. Lunch takes longer if it is a buffet and there is one queue. The changeover between day and evening takes longer if it involves the venue moving furniture, because the venue is also serving another event and their staff are not on your clock.

If the evening includes a DJ or live music, the sound check cannot happen during the final afternoon session. Either the evening sound is rigged in a separate space, or there is a gap in the programme. Most organisers find this out when the PA goes live in the middle of someone's closing remarks.

The evening is under-planned

The day portion has a programme, a printed schedule, assigned roles. The evening portion has 'drinks and networking', which means no structure, no reason to stay, and a slow exit that starts the moment the formal part ends. If you want people to talk to each other, they need a reason to stay in the room, and that is not the same as permission to leave it.

Food helps if it is served in waves — something when they arrive, something thirty minutes later — because it resets the duration. Music helps if it is live and starts before the energy drops, not after. A single anchor — a table, a bar, a performance area — helps because it gives the room a centre.

The mistake is assuming the evening will self-organise. A tired group of colleagues will do what is easiest unless the environment makes something else easier, and the easiest thing is always to leave.

Two kinds of supplier

One kind of event company takes your brief, marks it up, and forwards it to the PA supplier they found that morning, the AV technician who has never seen the venue, and the staff agency that sends different people every time. They coordinate by email. You pay for every hand the brief passes through, and when something breaks the answer is that it is someone else's responsibility.

The other kind quotes the work, builds the rig, and runs the day with their own crew — the same people who answered the phone. After 5 Events is the second kind, which is why the person who walks you through the technical rider is often the person standing by the desk when registration opens. It is not a better sales pitch; it is a different way of working.

What to settle now

Confirm the venue and walk it with someone who knows what a room does to sound. Decide whether the evening is in the same space or requires a move, and add that time to the schedule. Write the session list with technical requirements for each, not a general request for 'AV support'. Know how many people are coming, because a rig for thirty and a rig for a hundred and thirty are different species of problem.

The decision you face is whether to forward the problem or own it. If you are calling four suppliers and hoping their quotes align on the day, you are coordinating a event. If you are calling one crew that will still be there when the last case is packed, you are organising one.

Who is writing this

A crew, not a middleman

These guides are written by After 5 Events — the team that grew out of the After 5 band and DJ roster and has stood on the stage itself. We are not an agency that forwards your brief to subcontractors and takes a commission on every line: the people who plan your evening build the stage, run the sound and light, and are in the room when the doors open.

When you get to booking

The pages this guide has probably made you want to ask about.

The same reader, other occasions
The same occasion from another chair
Let's talk about your event

Describe it in a few sentences — we reply within one business day.

Get in touch