1.3 · The runway: project management for events

BeginnerDuration ~9 min readTools Your master sheet, Runway tab

The big idea: you don’t plan an event forward from today, you plan it backwards from the date, along the chain of things that can only happen in order.

The analogy

Nobody schedules a shoot in story order. The board gets built around whatever is hardest to move: the location you only have for two days, the actor who flies in on Thursday, the light you can’t reschedule. Everything else arranges itself around those. Then the whole thing is counted backwards from the day you have to deliver, and the call sheet for day one is one of the last documents written, not the first.

The reason is that a schedule isn’t a wish list in date order. It’s a map of what depends on what. You can’t shoot the scene until you have the location. You can’t send the call sheet until you have the schedule. A first-timer looks at that and sees admin. A working producer sees the only thing standing between the film and a very expensive morning where nobody knows where to stand.

Your event runs on exactly this logic. You already know how to think this way.

How it works

Start from the only fixed thing you have. The date.

Almost everything else about an event is negotiable, and the date stops being negotiable the moment you announce it and people put it in their calendars. So the plan gets built from that end backwards. Your runway is the working time between today and that date, plus the plan that fills it. Not the countdown on its own, which tells you nothing. The runway is the countdown with work attached to it, and it’s read right to left.

The clearest published example belongs to DevOpsDays, the volunteer-run conference series this course keeps borrowing from. Theirs runs twelve months. Venue search first, because venues book out. Then budget, because the budget tells you what sponsorship you have to raise. Then venue picked, organizers confirmed, prospectus out to sponsors, call for speakers open, marketing running, registration open, speakers selected, program published. Read that list once and the months jump out at you. Read it twice and you notice the months aren’t the useful part. The order is.

You aren’t running a twelve-month event. A community event of a hundred and some people compresses that same shape into roughly ten to sixteen weeks, and the compression works because the reasons behind their long gaps mostly don’t apply to you. They start hunting venues a year ahead because conference halls book out that far. They send the prospectus most of a year out because large companies lock their budgets a fiscal year in advance. Your venues and your sponsors move faster than that. What survives the compression, every single time, is the sequence.

Which brings us to the thing that makes the sequence real. Some of your tasks are waiting on each other and some aren’t. The chain of tasks that can only happen in order, where every link waits on the one before it, is the critical path, and for an event it runs roughly venue, then date, then program, then registration, then marketing. You can’t announce a date you haven’t secured a room for. You can’t open registration for an event with no date. You can’t promote a program you haven’t booked. Those links have no slack in them at all. Slip one and the finish line moves, because there is nothing else you could have been doing in the meantime.

Everything off that chain has slack, and slack is fine. The poster can be designed late. The raffle mechanics can be decided late. The badge design genuinely does not care. The most common way a first big event goes wrong isn’t laziness, it’s working hard on the wrong link. Two beautiful weeks of graphics while the venue is still “waiting to hear back.”

So each link becomes a milestone on the sheet. A milestone isn’t a task and it isn’t a phase. It’s a dated line that is either done or not done, with one name attached to it. “Work on sponsors” is not a milestone. “Prospectus sent to eight brands, owner Marie” is. The test is whether you could check its status at a glance, without a conversation. If checking it needs a conversation, rewrite it until it doesn’t.

Write those milestones in T-minus, not only in calendar dates. T is the event, so T-8 weeks is eight weeks before doors and T-0 is show day. It earns its keep two ways. It carries the reason inside the label, because “registration opens at T-8” tells you something that “registration opens September 14” doesn’t. And when your date moves, and dates move, every row shifts together instead of being retyped one at a time.

Then there’s one milestone that behaves differently from the others. The freeze. Two weeks out, everything countable stops changing: vendor orders, food counts, printed materials, the program, the head count you gave the venue. Not because change is bad, but because past that line every change costs more than it returns, and you need those last two weeks for the work that can only be done last. Briefing volunteers. Writing the run of show. Sleeping. Good ideas that arrive after the freeze go on a list for the next event instead of into this one. On a set this is picture lock, and it’s the same instinct. At some point the edit stops being improved and starts being delivered.

Last piece, cadence. DevOpsDays starts meeting semi-monthly while the event is still most of a year away, and the reason they give is visibility. Somebody has to look at how tickets and sponsors are actually going on a schedule, rather than whenever panic happens to arrive. Your runway is a fraction of theirs, so the interval compresses with it. Weekly, in the hour you already blocked in your calendar back in Lesson 0.3. Inside the freeze, shorter and more often.

Your August event has one wrinkle worth naming out loud. The live podcast and the sponsor booths both sit on the critical path, and neither of them looks like it does. A podcast has a guest, and a guest has a calendar, so booking that guest gates when you can announce the program. Booths need floor, which means the venue conversation isn’t “how many seats” but “how many seats plus how many tables and where does power come from.” Ask that in week one, not week eight.

The receipts (evidence, if you want it)

The most concrete published volunteer-conference runway, counted in T-minus months, is DevOpsDays’: venue search at T-12, budget discussions at T-10, venue picked at T-9.5, organizers confirmed at T-9, sponsor prospectus out at T-8, call for proposals open and semi-monthly team meetings starting at T-7.5, marketing running at T-7, registration open at T-6.5, speaker voting at T-4.5, program launched at T-3.5, and a volunteer check one month out (devopsdays.org/organizing).
The reasons they attach to those dates are the transferable part: “Venues book out in advance, and in fact, larger venues book out years in advance”; “Sponsors, especially larger companies, lock in budgets the financial year prior”; and the program launch matters because “Your program absolutely drives visibility of your event” (devopsdays.org/organizing).
Published runway lengths: 6 to 12 months for large conferences and galas, 3 to 6 months for mid-size events such as workshops and product launches (Lyyti, event planning timeline; 12-month checklists at i4a). The 10 to 16 week figure this course uses is the compressed shape of the DevOpsDays skeleton for a 100 to 150 person community event, derived in the course’s industry map: venue and sponsors first, registration open by roughly 6 to 8 weeks out, program locked roughly 3 to 4 weeks out. It’s a derivation, not a published benchmark.
The freeze: all vendor orders, catering counts, and materials finalized by 2 weeks out (Crestline conference planning checklist).
Critical Path Method: identify the longest chain of dependent tasks, which sets the minimum duration of the project, and know that slippage anywhere on that chain slips the whole thing (Asana, critical path method; applied to event planning at Meegle).
A published mid-runway health check: DevOpsDays asks whether you hit “about 40-50% of expected ticket sales minus sponsors, speakers, organizers, and volunteers by a month or so out,” and names a spike pattern across ticket announcement, early-bird close, speaker announcement, agenda announcement, and the last two weeks (devopsdays.org/organizing).
Promotion runway scales with event weight: 12 to 16 weeks for flagship conferences, 8 to 10 for mid-size B2B events, 4 to 6 for webinars (Samaaro, event promotion timelines). Interpolated to a community event that lands around 6 to 10 weeks of active promotion, which is why the marketing milestones sit where they do on your runway. Lesson 2.1 builds that stretch out properly.
Cadence: DevOpsDays kicks off semi-monthly organizer meetings because “it is good to establish a healthy cadence with check-in points and being able to get visibility on how ticket, sponsorship and submissions are going” (devopsdays.org/organizing).

Your one move

Open the Runway tab on your master sheet. Put the August event date in the bottom row, marked T-0. Then work upward and write these milestone rows, each with a real calendar date and one person’s name against it:

T-12 weeks: venue confirmed
T-11: date announced publicly
T-10: sponsor prospectus out
T-8: registration opens and promotion launches
T-6: guests, podcast, and program confirmed
T-4: program published
T-2: freeze
T-1: volunteer briefing done, run of show written
T-0: doors

Stretch or squeeze the weeks to fit the runway you actually have. Don’t reorder them. Twenty minutes, done when every row has a date and a name.

Want to go further?

Highlight the rows that sit on the critical path: venue, date, program, registration, promotion. Now look back at what you actually worked on this past week and check how much of it touched a highlighted row. That number is the honest one.

The needle: an event is won before doors open, and the runway is the calendar of the winning. Every row on it is a decision pulled earlier than it wants to be made.

Terms introduced

Check

You can move on when you can… name the five links of the critical path in order, point at the freeze date on your own sheet, and say of any task in front of you whether it’s on the chain or has slack.

Go deeper

Next up: 1.4 · The money: three-tier budgeting, where the runway gets its second layer. Every milestone that costs something now needs a number and a date where you decide whether to commit.
devopsdays.org/organizing publishes the full T-minus timeline with the reason attached to every date. Worth reading top to bottom once, ignoring the months and watching the order.