Event planning steps, in the order they actually go
Table of Contents
The week before your event should be detail work. Confirming numbers, walking the room, checking what arrived.
On the last few events you've run, that week has been something else. You were still writing the document your team needed rather than checking it, and the reason goes back months to the order things got built in.
Prefer to watch? The full breakdown is in the video below. Otherwise, let’s dive in.
Every layer sits on the one below it
Events get built in layers, and each layer sits on the one underneath it. That sounds obvious right up until you watch what happens when it goes out of order.
You build the timeline before the date is settled, and when the date moves, the timeline gets rebuilt. You start assigning who owns what before the agenda exists, so nobody can tell how much coverage any session actually needs. You commit to a venue before you know what has to happen in that room, and then the room doesn't fit the event.
None of that is wasted effort exactly. It's effort spent twice, and the second time always lands later than you want it to, when you have less room to absorb it.
An order doesn't mean working on one thing at a time, by the way. Most of this runs at once. Your logistics plan starts collecting details the moment you have any; your guest communication starts with the announcement and carries on until the follow-up, and you'll have five things open on a Tuesday afternoon. That's normal. What the order tells you is what has to be settled before what, and which pieces can't be finished while something underneath them is still moving.
An order is not a calendar, so you can start from where you are
You don't have to be at the beginning of planning for any of this to be useful. Go through the layers, find the first one that isn't actually settled, and pick it up there. You don't start over.
That's the useful part of having an order rather than a calendar. It doesn't care what week you're in. It only cares what's sitting underneath what.
Worth separating two words that get used interchangeably here. Unfinished and unsettled are different things, and only one of them is a problem. A guest list that's still filling is unfinished, and that's fine, because it's supposed to be moving. A guest count you've never actually landed on is unsettled, and everything you build on top of it gets built twice.
The five layers, and what each one is waiting on
Layer 1: The decisions everything else sits on
The first layer is what the whole event rests on. What the event is meant to do, meaning what the people in that room should get out of being there. What kind of event it is and how long it runs. Roughly how many people. When it is. The number you're planning against.
Those five come first because nothing underneath them is coming. Nobody has to send you anything before you can make them. You might do some research first, and doing research isn't the same as waiting on somebody to get back to you. There's a fuller version of this layer in the five decisions to make when you're planning an event from scratch.
Two of the five get misunderstood, so let me be specific.
Your guest count doesn't need to be final. It needs to be a working number, close enough that you'd pick the same room for it. Your venue and your caterer will come back later with the date they need final numbers by, and that's a separate thing entirely.
Your budget is the highest number you believe this is going to cost. It's an estimate, built before anything is final, from a rough headcount and the two or three places you're considering, with cushion on top.
This layer is also where you decide where all of this is going to live. One place, because everything you settle from here forward has to land somewhere your team can reach without asking you.
Layer 2: The timeline, the budget, and the agenda
The second layer is where the planning actually gets built: your timeline, your budget in detail, your agenda, and the registration and tech setup running underneath all of it.
Your timeline and your budget can be worked in either order, and they feed each other either way. What goes on the timeline isn't the conversations you're having; it's what has to come out of them. The date you need a quote back by. The day a decision has to be made so the thing after it can start. The deadline your venue gives you for final numbers. You'll have core milestones that hold and plenty of dates that move around them, and a timeline that can absorb a change without falling apart is a timeline doing its job.
Your budget sharpens as quotes come back. A quote goes into your estimate column, replacing whatever number you'd guessed, because a quote is still an estimate until it's been paid. Your actual column is a separate thing, and it fills in later, as you sign, as deposits go out, and as final invoices come through. That's what the event really cost, sitting next to what you thought it would. Most of the gap between those two columns lives in the cost categories a standard event budget template leaves out.
Then your agenda, which is the shape of the days. How many sessions, how long they run, what happens between them, where the breaks fall, and what the program is going to need from the venue, the AV, and the catering. You don't need finished content for this. You need the shape.
Registration and your tech decisions belong here too, while there's still room to make them well. Which platform, what the flow looks like, where the data lands, who can get to it. Sorting that now is a much calmer piece of work than sorting it six weeks out with people already trying to sign up.
If you want somewhere to put the first layer and a good part of the second, The Event Brief is a free workbook that gets it onto one page. Four short sections, ending with what your event is, who it's for, how many people it's for, when and where it happens, what you can spend, and what's still open.
Layer 3: Speakers, your team, and your guests
The third layer is the people, and it always takes longer than anybody expects.
Your guests aren't one item on this layer. They're the reason the whole thing exists, and they should be sitting in the back of your mind through every layer of this. Every decision you've already made and every one still ahead of you gets judged on what it does to their experience of being there.
Guest communication is the one to settle first, and it starts well before anyone registers. How you're announcing the event and what the invitation says, then what someone gets the moment they sign up, what arrives in the weeks between, and the know-before-you-go that goes out the week of. Some of those details keep arriving right up to the last minute, which is exactly why they need a place waiting for them rather than a plan to sort it out later.
Then your speakers and facilitators. The good ones get booked fast, so when a speaker decision goes round and round for weeks, the person you wanted says yes to somebody else while you're still discussing it, and you end up choosing from whoever's still free. Their yes also releases a few things sitting behind it: once you know who's speaking and what's happening in their session, you can sort most of your AV, and your agenda stops hanging in limbo.
Who does what on your team comes from the shape of your event, not just the agenda. The sessions tell you part of it, and everything around them tells you the rest. How many people you need at registration. Who's handling transportation. Who's setting rooms and turning them over between sessions. Anything left without a name on it tends to be the thing that surfaces on the day, usually while you're already doing something else.
Sponsors, if your event has them, sit here as well, and they run on somebody else's calendar. Start the outreach at this layer, and the answers will arrive when they arrive.
Layer 4: Turning the plan into something that runs
The fourth layer turns everything you've built into something that can actually run on the day.
Your logistics plan is the big one, and you've been filling it in since your first vendor conversation. This layer is where it stops being a collection of details and becomes the document your team lives in. Every room and how it's set. What each session needs in it. When each vendor arrives and who's meeting them. What's been shipped, where it is, and who signs for it. Meal counts and timings. Who's on registration and when. That's the one somebody can open and answer a question from without coming to find you, which is the whole reason it exists, and what belongs in an event planning spreadsheet covers how to lay it out.
Your run of show is a different document for a different set of people. That one is production-facing, and it's about timing and cues. An agenda says ten o'clock, keynote. A run of show says who cues her, when the mic goes live, who advances the first slide, how she knows her time is nearly up, and where she goes when she's done.
Then your team briefing, so everybody knows what's theirs, what they can decide without you, and when to come and find you.
You also make a plan for the things that go sideways, because something will. That isn't a catalog of every possible disaster. It's the two or three most likely for your event, with what happens in the first thirty minutes and who owns each one.
When those exist, the last stretch before your event is much more about confirming numbers and walking rooms than about building anything.
Layer 5: After the event ends
The fifth layer decides how hard your next event is, and its value isn't obvious until you've been through this a couple of times.
Within a couple of days, while it's all still fresh, write down what went better than you expected and what broke or came close to it. This doesn't have to be a report, and it doesn't have to be tidy, so get it down however it comes out. What you're protecting is the detail, because the detail fades fast and it fades first. What to capture in the first 48 hours after your event goes through this one in more depth.
Then run your actual numbers next to your estimated ones so you can see where things went. That's how you get better at estimating, and it turns this year's surprises into next year's line items.
Close out your vendors properly. Check final invoices against what was in the proposal, question anything that appeared out of nowhere before you pay it, and write one honest line about each vendor while you still remember clearly whether you'd use them again, use them again with conditions, or go somewhere else next time.
Then put all of it in one folder with the year and the event name on it, in the same place every time. The run of show as it was actually used, the reconciled budget, the debrief, your vendor notes, and the contracts. That folder is what the next event opens with, instead of a blank page.
You're planning it either way
Two thoughts tend to come up at this point, and both of them are fair.
The first is that you don't have time to add something else while you're in the middle of planning an event. Here's the math on that. You're planning it either way, and those hours are getting spent regardless. What changes with the order is whether they get spent once or spent twice on the pieces that have to be rebuilt.
The second is that you should be able to do this yourself. You can. Everything here works whether or not you ever hear from me again, and it costs you nothing to go and close your first open layer this afternoon. What's hard to do by yourself is see the thing you're not seeing yet. That's usually the one that costs you.
If you'd rather not do it on your own, [The Backstage Pass to Better Events]([BACKSTAGE PASS URL /b/]) is a membership where you work through the planning of your own event one layer at a time, with the tools and templates to build each piece when you get to it, written Q&A when you're stuck on a decision, and a group of people doing this same work at the same time.
Where to start this week
The order matters more than the calendar does. Your last week is either detail work or document-building, and which one it turns out to be was decided months earlier, by what got settled before what.
So this week, go through the five layers in order and stop at the first one that isn't settled, meaning unsettled rather than merely unfinished. Write down what the open question is and what it would take to close it, and start there.
