The conference timeline: from decision to opening
A conference does not fail because nobody worked. It fails because one decision slipped by two weeks, and everything built on it slipped with it.
Twelve weeks is a comfortable run for a conference of two hundred to a thousand guests. Less is possible and happens often, but the choices narrow: the available hall becomes the hall rather than the chosen one, and the speaker you want may already be committed. This sequence counts backwards — week twelve is twelve weeks before the event, not after.
Weeks 12–10 · What cannot wait
Three decisions belong here because everything after them depends on them: the date, the venue and the target headcount. The three are bound together: the hall caps the number, the number rules out halls, and the date constrains both because good venues book early.
This is also when the permit file opens with the venue owner. That item is missing from most schedules, and meeting it late does not mean revising one line — it means rebuilding the whole schedule.
Weeks 9–7 · Programme and speakers
The programme is written in hours before speakers are invited, not after. The reason is practical: a speaker needs to know their slot and its length before accepting, and one invited without those details accepts and then withdraws when they arrive.
- Session count, the length of each, and the gaps between them.
- Who opens and who closes — two slots that cannot be filled at the last minute.
- Are there parallel sessions? If so the venue needs two rooms, not one.
- Simultaneous interpretation: decided here, because it needs booths, rigging and interpreters booked.
Weeks 6–4 · Registration and identity
The longest queue at any conference is the registration queue, and the cause is always the same: registration began on the day. It opens here, badges are printed in advance, and the morning becomes handing over a badge rather than entering data. We ran this for more than 1,500 staff at Alinma Bank's open day.
The visual identity closes here too, because print needs two weeks and large format may need more. Every identity change after this point is paid for twice: once in design and once in reprinting.
Weeks 3–2 · The details that get forgotten
- Catering: how many, when, and where it is served — and whether the corridor takes the tables at all.
- Protocol: who receives the senior guests, where they sit, who accompanies them. Written by name, not by title.
- Photography: a written plan of which moment is needed and for whom — not a photographer wandering and catching what he can.
- A fallback for every item outside your control: a speaker who did not arrive, a deck that will not open.
Week 1 · The rehearsal
The time lost at a conference falls between sessions, not inside them: one speaker steps down, the next hunts for a microphone, a deck will not open. The rehearsal tests those gaps specifically, not the sessions. And the sound is set for a full room rather than for what an empty one sounds like.
Whatever goes untested in rehearsal will be tested in front of the guests.
Event day · One point of decision
The day itself needs no meetings, only one point that knows where everything is: the next speaker, the guest who has arrived, the room that has filled. Decisions leave from there alone, so the floor team never takes conflicting instructions from three people at once. Everyone calls it the operations room; its value is not in the name but in there being exactly one of it.
Common questions
Are twelve weeks genuinely necessary?
No, but they are comfortable. We have delivered in shorter runs, and what changes is the range of choices rather than the quality: the hall that is free, the speaker who is free, the materials that print locally at speed. Tell us the target date and we will say plainly whether it is deliverable — we do not accept a date we know we cannot meet.
Which item slips more often than any other?
Identity sign-off, then speaker confirmations. The first slips because it passes through several internal approvers; the second because it is outside the organiser's control to begin with. Which is why the schedule is built with margin rather than on the assumption that everything lands on time.
Do you book the venue or do we?
Either works. When we do it, we also handle the venue on permits, insurance and the access schedule — the items that surface late when nobody owns them. When you do it, we need a copy of the venue's conditions early, because they govern half the schedule.
Read next
- Conference and forum managementHow a hall of a thousand guests is run, and the five points where a conference stumbles.
- How to read an exhibition stand quoteThe lines a quote must contain, the ones left unsaid until days before opening, and three signals that a number is incomplete.
- The exhibitor's checklist: before you enter the hallWhat to know and prepare before build day, written from the side of the people who receive exhibitors in the hall.
- Choosing an event venue in the Eastern ProvinceEight items to check on a site visit before signing — height, power, loading access, parking — and what each one means for your event.