Conference

Conference — in a public sector organisation

The sound check happens in an empty hall at half-past seven, and by nine the first delegate is through the door expecting everything to work. A public-sector conference is two events: the programme — sessions, speakers, the AV that makes them audible and visible from the back — and the evening that follows, in the same room or another, where the day's formality is meant to relax without coming apart.

This guide is written by the crew who rig both. It covers what to decide early, what the room dictates, and where a conference usually fails its evening.

The programme comes first, and the programme is technical

A conference is a sequence of sessions, each with different speakers, different slides, different microphone needs. The organiser's problem is not creative — the content already exists — it is operational: every handover must be silent, every slide must appear when called, and if one session overruns the rest of the day compresses.

The AV rig is sized to the worst case, not the average. If one speaker uses video with audio, you need playback for all of them. If one panel has five people, you need five microphones even when most sessions have two. The room is built for the whole day, which means deciding the format of every session before anyone arrives.

What the room does to sound

An atrium looks impressive and fights every word spoken in it. A low-ceilinged training hall swallows projection but gives back clean speech. The room decides half the technical spec, and most conference venues were not built for conferences.

Walk the room early if you can, or ask for dimensions and photos if you cannot. Ceiling height, surface materials, columns, windows. Public venues often have house AV and rules about who can use it; state venues often have nothing and assume you will bring it. Both need checking before the quote is written, because what works in one room is insufficient or illegal in another.

If the conference is bilingual, decide whether interpretation is whispered, streamed to an app, or fed through receivers. Each has a different technical and spatial demand. Interpretation booths need sightlines, power and space that is usually taken by something else.

The changeover problem

The gap between sessions is when everything breaks. A speaker finishes, the audience claps, the next speaker walks to the stage, and in those forty seconds the slides must change source, the microphone must be reset, the clicker must be paired, and the session chair must know what happens next without being told in front of two hundred people.

The only fix is a run-through, preferably the afternoon before. Every speaker connects their machine once while the room is empty, every slide deck is checked, every microphone is labelled. It is boring, it saves the day, and it is the part an organiser forgets to schedule because it is not on the published programme.

If there is a livestream or a recording, add another rehearsal window. The speaker who is fine in person often stands where the camera cannot see them.

Catering is not a break from the event — it is part of the sequence

Coffee at ten-fifteen means the previous session must end at ten, which means it must start on time, which means registration must close and the opening must begin without waiting for latecomers. A delay at breakfast compounds through the morning.

Public procurement often splits catering and production into separate contracts, which means two suppliers who have never worked together are now expected to coordinate in real time. If you control both, write the minute-by-minute sequence and share it. If you do not, ask the caterer when setup begins, when breakdown starts, and whether the space you have given them is enough to work in while the session before the break is still running.

Alcohol is minimal or absent, and the meal is usually a buffet timed to let people move and talk. That is where the day transitions into the evening — informally, in a corridor, without announcement — and it is almost never given the attention the morning programme receives.

The evening is under-planned because it feels optional

A conference day ends at five, formally. The evening event starts at six, often in the same venue, sometimes in another. It is described as networking or a reception, which makes it sound as though it will take care of itself, and it will not.

The mood has to shift — from rows facing forward to clusters facing each other, from amplified speech to background sound, from paying attention to letting go — but the room is still the room and tired people in work clothes do not relax because you have dimmed the lights. If the evening is in the same hall, the chairs must be cleared and something else must appear in the empty space. If it is elsewhere, everyone has to move, and a third of them will use the journey as permission to go home.

Decide what the evening is for. A standing reception with no programme and quiet music suits a ministry event where half the room barely knows the other half. A DJ and a dance floor suit a team that has spent the day sitting still. Both are defensible; neither works if added as an afterthought.

Two kinds of event company

One kind takes the brief, adds margin, and forwards it to subcontractors it has never worked alongside — a lighting supplier here, a catering company there, a separate AV tech for the livestream. Every line earns, nothing connects, and when something fails on the day there is no one who knows both what was promised and how it is actually rigged.

The other kind quotes, builds and runs the event with the same people. The crew who hang the lights are the ones who struck them last week at a different venue, the AV tech has worked every configuration of the room, and the site lead knows what failed last time and why. After 5 Events is the latter — the production team writing this guide — because the event is a technical system and systems fail at the seams between suppliers.

Public procurement requires written offers that itemise, and that is easier when each line is something this crew has rigged before, not something estimated on behalf of someone else.

What to settle before calling anyone

The day's programme, session by session: how many speakers, whether there are panels, whether any session uses video, whether interpretation is needed. The room, its size and what is already in it. Whether the evening is in the same space or elsewhere, and whether it has a programme or is left open. The budget and whether it sits above the procurement threshold that requires competing offers.

The decision you now face is not whether the event will happen — it will — but whether the AV for the day and the evening that follows are planned as one sequence or patched together from separate briefs. The first call settles which it will be.

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 occasion in another kind of company
The same reader, other occasions
Let's talk about your event

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

Get in touch