The event planning checklist for your last two weeks
Table of Contents
You've been to an event that ran well. Sessions started on time, the room was set before anyone walked in, and somebody always knew the answer. The team looked relaxed, like the whole thing came easy to them.
What you were looking at was a team that spent the final stretch pinning everything down. That work runs across the last two weeks; it follows an order, and the list is short enough for a team of one or two, which is what most events actually run on.
Prefer to watch? The full breakdown is in the video below. Otherwise, let’s dive in.
The last two weeks are a different job
Two weeks out, your job changes. Planning doesn't stop, since things keep moving right through doors open, but most of what's left is finalizing. Everything you already decided has to get locked down, which means confirmed, made final, and put in writing where the people running your day can find it.
The months of planning before that matter, and I'm not skipping past them. Those last two weeks are a separate kind of work, though. Very little of it is new decisions. Most of it is taking decisions you already made and finalizing them.
That's why you can plan an event beautifully and still walk into event week braced for it. Planning decides what the event will be. It doesn't confirm a vendor, turn an estimate into a real number, or put a name against check-in. Those only happen in the last two weeks, and whether they happen is what your event week actually feels like.
What should you finalize two weeks before an event?
Five things, in this order:
Reconfirm everything in writing: every vendor, venue contact, and speaker confirms the time, the place, and what they're delivering.
Close your final numbers: headcounts, meal counts, materials and room sets stop being estimates.
Finish and share the day-of plan: what happens, when, and who is doing it, walked through with everyone who runs the day.
Put a name on every event-day task: including the in-between work nobody has been assigned.
Settle how changes travel: one living document everyone knows is current, plus a direct message to whoever the change affects.
None of them is complicated. Each one takes real thought, and a few will stretch across days once you're waiting on other people, which is exactly why this starts two weeks out rather than three days out.
The five locks, in order
Lock 1: Reconfirm everything, in writing
Every vendor, every venue contact, every speaker gets a fresh written confirmation of the time, the place, and what they're delivering.
Here's why this one goes first. That yes you got in April has been doing a lot of work in your head ever since. The person who gave it might have changed roles without anyone thinking to tell you. Your speaker said "sounds great" back in month two and never specified what time she's arriving. The venue contact who walked you through load-in reports to somebody new now.
I learned this one the hard way. We'd been chasing catering answers from a venue for weeks, and one afternoon, right as I was getting ready to log off, our contact there finally emailed us. My boss replied with her questions before I'd even shut my computer down, and the next ping on my phone was her, telling me the email had bounced. Our contact no longer worked for the company. Nobody had told us he was leaving, and the person holding every detail we'd agreed on with that venue was simply gone. We spent the next stretch chasing people at that venue to work out who had our event now.
“Time passed, and that’s all it takes.”
On larger hotel events, this is standard. You go line by line through the whole event against what's planned: the room sets, the catering, the audio-visual, the tech needs, every time, as a matter of course. If you want the fuller version of how to run vendor and speaker relationships through a whole planning cycle, the pro way to manage retreat vendors and speakers covers that side of it.
One honest note about time. Sending the confirmations is an afternoon of emails. Getting everything back is not, because you're waiting on real people and there's always some back and forth. That's the reason this one starts the two weeks instead of ending them.
Lock 2: Close your final numbers
Every number that's been living as an estimate becomes a real number. Your headcount, your meal counts, your materials, your room sets. All of it has been roughly right all year, and roughly right was fine all year.
It stops being fine now, because other people are making commitments based on it. Your catering guarantee has a deadline, and that deadline does not care that changes are still coming in. A dietary update here, a cancellation there, somebody's assistant asking about a substitution. Whatever number you give them is the number you're paying for.
So you settle your numbers into the counts everybody needs, before the deadline forces you to guess. The alternative is picking a number at ten at night, hoping you rounded the right direction, and then paying for forty lunches nobody eats.
There's money attached to this beyond the counts themselves. Final numbers change what you owe, and a lot of vendor payments come due right around now, so check what's landing and when.
Lock 3: Finish and share the day-of plan
Not the agenda your guests see. The operational version: what happens, when, and who's doing it. Including the part that usually gets skipped, which is your guests’ first thirty minutes. Where they walk in, who greets them, where they go, and what's happening while they work out where they are.
This is the one that genuinely can't be done earlier, since it depends on every decision that came before it. Right now that plan exists, and it's living with you. You know how the day flows, and you can see it, while your setup crew has one piece, your A/V person has a different piece, catering has a third, and nobody has the whole thing.
Which means that on event day, every hour gets narrated live. By you. Written once, that plan replaces about a hundred of those conversations.
Writing it is only half the lock. Once it exists, you walk through it with everyone: your team, your vendors, your venue contact. Hotels call this a pre-con, and on bigger events everybody gets in a room beforehand and goes through the plan together so every team hears the same thing at the same time. You can run your version in one call. The plan is locked when the people running your day have walked it together.
Lock 4: Put a name on every event-day task
Most of these assignments already exist. Whoever has handled catering all through planning is your catering point on the day, and you're mostly making it official so everyone knows who to go to.
What you're checking for is the pieces nobody has been assigned. Check-in. Laying out materials after the venue resets a room. Meeting the photographer. The in-between work that never belonged to anyone.
“Any task without a name on it defaults to you. Automatically. Nobody decided that, it’s just what happens.”
So put names on those now, while there's time. Some of them will still be you, and that's completely fine. The difference is that you chose it rather than inheriting it at eight in the morning on the day. If assigning work has gone sideways before, the four retreat roles that make delegation actually work goes deeper into this. [
Then make sure people can reach each other. One contact list with your venue, your vendors, your speakers, and who's covering what on your team. For some teams, a group chat handles it beautifully: setup crew in one and vendors in another, whatever matches how your people already communicate. At nine in the morning on event day, reaching the right person should take one call rather than a scroll back through three months of email. This only makes sense to build now, because now is when you finally know who all those people are.
Lock 5: Settle how changes travel
I want to be straight about this one, because the word lock is a little misleading here.
Nothing about an event freezes. A speaker's flight moves. Someone develops an allergy. The room you were promised gets reassigned. That happens at every event and at every level, including the ones run by people with enormous teams.
So professionals don't try to stop things from changing. What they settle in advance is how everyone finds out. Every change lands in one living document that everybody knows is the current one, and on site that document is live, with people in it all day. On top of that, whoever the change actually affects gets a message directly, a text or a ping in the group chat, because if she was mid-task when it changed, then she hasn't looked yet and she needs to know now.
The trap you're avoiding is the change that only lives in a text to one person. Without that, the room change reaches catering and never reaches A/V, so lunch moves and the microphones don't. Two versions of the schedule circulate, and both look official. Somebody acts on information that was true two days ago.
Every change costs you a little credibility when it travels badly, and the last two weeks are made almost entirely of changes. Things will still move. They'll just move cleanly. For the wider version of planning around things that move, retreat contingency planning 101 is worth reading alongside this.
Not sure which of these is thinnest at your event right now?
The Event Pulse Check is free, takes about five minutes, and walks through every area of your event to show you what's solid, where the gaps are, and what to focus on next.
What a reconfirmation email actually says
Most confirming happens in passing. A quick message asking whether everything's still on, and a quick yes back, which tells you nothing about what changed in the four months since you agreed it. What makes a confirmation useful is the detail in it, because detail is what gives someone something to correct.
Four things do the work: what you agreed, when it's happening, where, and a date for them to reply by.
Subject: Confirming September 12, arrival and set
Hi Marcus,
Confirming what we have for the 12th so we're working off the same details. You're arriving at 7:30am for a 9:00 start, setting the main room for 60 in rounds of eight, with the linens in your quote from March. Could you reply by Friday to confirm, or tell me what's changed? Anything moving on your end is easier for both of us to handle now than during that week.
That email takes four minutes to write, and the replies are the point. Some come back confirmed, which is worth knowing. Some come back with a correction you'd never have caught. And some don't come back at all, which is information too, and it's why this goes first rather than last.
When it doesn't go to plan
Five things in order is a short list, and the two weeks you run it in rarely go cleanly. You're waiting on people who have their own events to run, and working from numbers that haven't settled yet. Three situations come up often enough to be worth deciding in advance how you'll handle them.
What if a vendor doesn't reply?
Chase once by phone, not by email, and give the call a purpose beyond chasing. You're confirming the details you sent, which takes ninety seconds and gets you an answer in real time.
If that doesn't land, escalate to whoever signed the contract or manages the account, and say plainly that you're confirming details for an event in two weeks and need a written response by a date. Silence from a vendor at this stage is one of the few genuine warning signs in the whole stretch, and finding out now is the entire reason you started here.
What if my numbers are still moving?
They will be, and the guarantee deadline doesn't care.
Give the number you're willing to pay for, then ask your caterer two questions: how late can you add, and what's the cutoff for changes? Most will take additions much later than they'll take reductions, which means the safe number is your confident count rather than your hopeful one. Ask, write down what they tell you, and stop guessing at it privately.
What if I'm the entire team?
Then do the first two and treat the rest as reduced versions of themselves rather than skipping them.
The day-of plan can be one page. The contact list can be one message thread with the numbers in it. Lock five can be a single line in whatever document you're already using, saying when it was last updated. None of these needs to be elaborate to work. They need to exist somewhere other than your memory.
Why the order runs this way
Reconfirming goes first because everything after it depends on knowing what's true. There's no point finalizing numbers against a vendor arrangement that changed in June without anyone telling you.
Numbers come second because other people's deadlines are driving them, and those dates don't move for you. The day-of plan comes third, since you can't write who's doing what at two o'clock until you know what's happening at two o'clock. Names and phone numbers come fourth, once you know who all the players are. Settling how changes travel comes last, because it keeps the other four current straight through doors open.
If you only have time for two of these, do the first two. Reconfirm everything, and close your numbers. Those are the ones that cost real money when they slip.
Two weeks out, starting with one afternoon
The event you admired, where the team looked relaxed and everything started on time, ran that way because five things were pinned down before you walked in. Budget helps, and so does being the kind of person who stays level under pressure. Neither one confirms a vendor or turns an estimate into a real number, and those two weeks are the same length for everyone.
So here's the version to run this week. Block one afternoon and send the reconfirmation round. Every vendor, every venue contact, every speaker, one short email each, naming the time, the place, and what they're delivering. Then watch what comes back, because the replies are where you find out what moved while you were deep in planning.
If you want a read on where your event stands before you start, the free Event Pulse Check takes about five minutes and shows you what to look at first.
