Skip to contentReferrals are open — $110 per referral, or 10% for life

Production

The event production timeline that survives to the day

A production timeline does not collapse because you estimated the tasks badly. It collapses because you dated what you control and forgot what you need from other people.

Alexis · Co-founder of Squena · September 3, 2026 · 9 min read

In short

An event production timeline is built backwards: you start from the day the doors open and work back, task by task, to today. What makes it hold is not the level of detail. It is placing the irreversible milestones first, and giving every task that depends on somebody else two dates — the day you send, and the day you must have received.

Every organiser I have watched work builds a timeline. Almost none of them still uses it after the third week. That is not a discipline problem. Most timelines are built the wrong way round.

Why most timelines die in three weeks

The natural instinct is to start from today and move forward. This week I contact venues, next week I ask for quotes, then I choose. That is an action plan, not a timeline. It has no idea what is late, because nothing in it has a deadline that comes from anywhere.

A production timeline does the opposite. It starts from the doors opening and works back. Every task then inherits a latest date rather than a preferred one. A slip becomes readable straight away: either it eats a buffer, or it moves a milestone.

Irreversible milestones: the only ones to place first

An irreversible milestone is a moment after which going back costs money, not just time. It is what structures the plan, because it is the one thing you cannot recover by working harder.

On an event there are rarely more than five or six. Placed first, they cut the calendar into stretches that everything else fits inside.

MilestoneWhat becomes irreversibleCost of going back
Venue signedThe date and the capacityDeposit lost, often 30%
Technical purchase orderThe stage plan and the power drawSupplier cancellation fees
PrintThe programme, the signage, the namesA full reprint
Ticketing opensThe price and the announced capacityRefunds, and your reputation
Licensing notice servedThe declared safety arrangementsRestart the process, statutory wait
Catering orderedThe number of coversBilled on the forecast, not the turnout

Notice what that list does not contain: choose the caterer, approve the artwork, brief the team. Those are tasks, not milestones. They move without breaking anything, as long as they stay ahead of the milestone they feed.

The delay everyone underestimates

Timelines that collapse almost all have the same crack. They date the work you do, and not the wait for what other people owe you.

  • A technical supplier quote: three to ten working days, longer if the request lands in August or December.
  • Artwork approval by a partner or a sponsor: budget for two rounds, never one.
  • An insurance certificate or a licensing notice: the statutory period is a floor, not an estimate.
  • A grant decision: the committee's calendar, not yours.
  • An answer from an artist or a speaker: it goes through an agent, so through two diaries.

These waits do not compress. They start earlier, or they do not happen. Some cannot even be negotiated. In England and Wales, a Temporary Event Notice must be served at least ten clear working days before the event. Clear excludes both the day the council receives it and the day of the event itself.

How far ahead: rough markers by format

These orders of magnitude are for a first pass. They do not replace your own experience of the format, but they stop you starting too late, which is the most expensive and most common mistake.

FormatFirst milestoneTechnical lockPrint
Conference, 100 to 300 people3 to 4 months ahead6 weeks3 weeks
Convention, 300 to 1,500 people8 to 12 months ahead3 months6 weeks
Festival, several stages10 to 14 months ahead4 months8 weeks
Client evening, 50 to 150 people6 to 10 weeks ahead3 weeks10 days
Trade show with exhibitors10 to 12 months ahead3 months6 weeks

What a task needs in order to move

A task that drags is almost always a badly written task. Four things are enough, and rarely more than one is missing.

  1. An action verb and a single object. « Caterer » is not a task; « choose the caterer from the three quotes » is.
  2. A named person. Not a team: a team does not feel late.
  3. A latest date, inherited from the milestone that follows it — not picked by feel.
  4. What is blocking it, if anything. A task that is waiting and does not say for what is an invisible task.

The fourth point is the one people skip. It is also the one that transforms the weekly review: instead of going round all twenty tasks, you look only at the ones waiting on something.

Why the spreadsheet eventually gives out

A timeline in a spreadsheet works very well — up to three conditions, and all three arrive.

  • When a milestone moves, nothing follows. You shift everything that depends on it by hand, and you always miss one.
  • When two people open it, the reference version disappears. The file is soon called TIMELINE_v4_final_REAL.
  • When you want to know what is committed, the plan and the budget do not talk. The signed quote lives in a mailbox.

This is not an argument against spreadsheets. It is the moment the tool changes job. As long as the timeline fits in a column of dates, keep it. The day it has to connect to suppliers, quotes and the committed budget, a column of dates is no longer the right shape.

The weekly review that replaces twenty follow-ups

A timeline does not need updating every day. It needs a fixed, short appointment, always in the same order.

  1. What was due this week and is not done. Nothing else first.
  2. What has been waiting on somebody else for longer than the planned lead time. That is where the real delays hide.
  3. The next irreversible milestone, and what has to be closed before it.
  4. What has moved in the committed budget since last week.

Twenty minutes is enough, and the order matters. Starting with the week's wins makes for good morale and a bad review.

The part almost nobody does

The day after the event, the team is exhausted and the timeline is archived. That is exactly the moment it is worth the most.

Three questions, written down while it is fresh: which lead time turned out to be wrong, which milestone was placed too late, and which supplier delivered what they said. Those three answers are worth more than any template. They are also what the UK Health and Safety Executive asks you to have thought about before the next build begins.

It is also why a timeline is better off living in the same place as the supplier database. The note « this one returned their quote in three days » is only worth something if you find it again next year, on their record.

Frequently asked questions

What is the difference between a production timeline and a plan?

A plan starts from today and moves forward. A timeline starts from the day the doors open and works back, so every task inherits a latest date rather than a preferred one. That is what makes a slip readable: you can see immediately whether it eats a buffer or moves a milestone.

How far ahead should you start an event timeline?

Three to four months for a conference of 100 to 300 people, eight to twelve months for a convention, ten to fourteen for a festival with several stages, and six to ten weeks for a client evening. Starting too late is the most expensive mistake, because the milestones you cannot move are the ones furthest out.

What is an irreversible milestone?

A moment after which going back costs money rather than time: the venue signed, the technical order placed, the print run, ticketing opening, the licensing notice served, the catering ordered. There are rarely more than five or six, and they are the ones to place first.

Why does my timeline never hold after a few weeks?

Almost always because it dates the work you do and not the wait for what other people owe you. A quote, an approval, a licence, a grant decision: each has a lead time you do not control. Give every dependent task two dates — when you send, and when you must have received.

Can you run an event timeline in a spreadsheet?

Yes, until three things happen: a milestone moves and nothing follows, two people open the file and the reference version disappears, or you need to know what is committed and the plan does not talk to the budget. Until then, keep the spreadsheet.

What do you do with the timeline after the event?

Write down three answers while it is fresh: which lead time was wrong, which milestone was placed too late, and which supplier delivered what they promised. That is the only version of the timeline that is worth anything next year.

Sources

Read next