Event planning checklist template Three days out, what's still open?
Template
Outstanding Items Checklist
A punch list for the three days before the event, plus a full-lifecycle checklist covering every phase from approval to the debrief, one tab per phase.
- A one-line-per-item tracking table for the final three days
- Six prompt sections: guests, program, room and look, proof and press, communications, after
- A full event checklist with one Excel tab per phase, approval through the week after
- 56 tasks, each with its workstream and its done-when
Download the Word file, 36 KBDownload the Excel file, 14 KB
Free. No email needed. Opens in Word and Excel.
Phase 1: As soon as the event is approved
| Done | Task | Workstream | Done when |
|---|---|---|---|
| Write the outcome: what should be true 30 days after the event | Whole event | One sentence someone could check later, agreed by the executive sponsor | |
| Write the success criteria before anyone is assigned a task | Whole event | A short written list of what the event must deliver, agreed before the first task is handed out | |
| Name the executive sponsor | Whole event | The sponsor is named in the brief and has agreed to make the final call when two reasonable options collide | |
| Decide who the event is for | Whole event | The audience is written in one line: who should be in the room, and why they would come | |
| Set the budget range, with a contingency line | Whole event | A range someone with authority has agreed to, and a named approver for the contingency | |
| Pick the date window | Venue and logistics | A month or a season agreed, checked against the calendars of the people you most want in the room | |
| Start the event brief | Whole event | Purpose, audience, date window, budget range and owner fit on one page, and everyone planning works from the same version | |
| Decide which workstreams this event needs | Whole event | Workstreams that don't apply are deleted from the checklist, not left empty |
Showing 8 of 9 rows. The rest are in the file.
Phase 2: Planning and booking
| Done | Task | Workstream | Done when |
|---|---|---|---|
| Shortlist venues against the brief | Venue and logistics | Each option is checked for format, budget line, date and the technology you plan to use | |
| Book the venue | Venue and logistics | Contract signed, date confirmed in writing, and a named contact at the venue | |
| Book the other vendors the event needs, such as catering, AV and printing | Venue and logistics | Each vendor has confirmed a date, a deliverable and a contact | |
| Draft the agenda by segment | Content and program | Every segment has a purpose, a length and a line on what the guest leaves with | |
| Confirm speakers and the host | Content and program | Each speaker has agreed to a topic and a slot in writing | |
| Choose one theme | Brand and theme | The theme fits in one line and is written into the brief | |
| Build the guest list | Guest communications | Every name has a reason to be in the room and a relationship owner on your side | |
| Send the invitation | Guest communications | Sent, asking for dietary and access needs, with replies tracked in one place and one named person answering them |
Showing 8 of 10 rows. The rest are in the file.
Phase 3: Build
| Done | Task | Workstream | Done when |
|---|---|---|---|
| Write the opening story or keynote | Content and program | The script is finished and the executive sponsor has read it | |
| If guests will use the product, build the demo around a task they finish | Product or demo readiness | The demo ends with each guest holding something they made or set up, not just something they watched | |
| Lock the version of the product guests will use | Product or demo readiness | No changes after an agreed date, and that version has been tested end to end | |
| Set up guest access or hands-on materials | Product or demo readiness | Every confirmed guest has working access or a set of materials, tested before the day | |
| Name the fallback if the network or the product fails | Product or demo readiness | The fallback is written down, with the name of whoever makes the call to use it | |
| Carry the theme through every touchpoint | Brand and theme | Invitation, badges, agenda screen, food and drink, swag and thank-you have each been checked against the theme | |
| Order signage, printed materials and swag | Brand and theme | Ordered, with delivery dates that land before the freeze | |
| Write every guest email, each with its send date | Guest communications | Seat confirmation, one-week email, night-before email and thank-you are written in final form, dated, with a named sender |
Showing 8 of 10 rows. The rest are in the file.
Phase 4: The final two weeks
| Done | Task | Workstream | Done when |
|---|---|---|---|
| Switch to daily written check-ins | Whole event | Every Blocked or In Progress task gets a written update each day | |
| Reconfirm every vendor | Venue and logistics | Each vendor has confirmed time, place and on-the-day contact | |
| Send the final guest count, with dietary and access needs, to the venue and caterer | Venue and logistics | The count and the needs are sent by the venue's deadline and acknowledged | |
| Send the seat confirmation, the one-week email and the night-before email on their dates | Guest communications | Each goes out on its send date, and every reply has an owner | |
| Schedule the rehearsal and the team walkthrough | Day-of operations | Time, place and who attends are on the calendar for the day before the event | |
| Ship materials to the venue | Venue and logistics | Shipped, addressed to a named person, with tracking sent to whoever runs the day | |
| Write the handoff notes for whoever runs the day | Day-of operations | The notes cover what is in each box and where it goes, what to switch on and by when, what the venue is placing, which photos to take, and who is on call | |
| Put the debrief on the calendar | Whole event | The invitation has gone to the people who need to be there, before the event |
Showing 8 of 10 rows. The rest are in the file.
Phase 5: Event day
| Done | Task | Workstream | Done when |
|---|---|---|---|
| Walk the room before doors open | Day-of operations | Every station is set against the handoff notes, and the tech is switched on by the agreed time | |
| Open check-in | Day-of operations | Check-in is staffed, with the guest list and materials in place, before the first guest arrives | |
| Run the event from the run of show | Day-of operations | Each segment starts with its owner in place, and any change goes through one named decision-maker | |
| Staff the tech table during hands-on segments | Product or demo readiness | One named person is at the tech table whenever guests are using the product | |
| Give the reminders in the handoff notes | Day-of operations | Each reminder is given at its time, to the person the notes name | |
| Take every photo on the photo list | Proof capture | Every shot on the list is taken and saved where the team can find it | |
| Capture testimonials and feedback in the room | Proof capture | Testimonial questions are asked of the guests who agreed, and feedback is collected before guests leave | |
| Keep someone on call | Whole event | The person on standby is reachable for the whole event window |
Showing 8 of 9 rows. The rest are in the file.
Phase 6: The week after, and the debrief
| Done | Task | Workstream | Done when |
|---|---|---|---|
| Write personally to the guests who gave the strongest feedback | Guest communications | Each has a personal note from their relationship owner within the week | |
| Give every follow-up an owner and a date | Whole event | No follow-up sits on the list without a name and a date beside it | |
| Send a feedback survey, if feedback wasn't collected in the room | Guest communications | Sent, with a closing date | |
| Gather the proof in one place | Proof capture | Photos, testimonials and feedback sit in one shared folder, with guest consent recorded | |
| Close out vendors against the budget | Venue and logistics | Every invoice is matched to its budget line, and any contingency spend is recorded with who approved it | |
| Hold the debrief against the outcome and the success criteria | Whole event | Each criterion is marked met, not met or too early to tell, with the evidence beside it | |
| Book the 30-day check | Whole event | A date 30 days after the event is on the calendar to answer the outcome sentence in writing | |
| Save the checklist for the next event | Whole event | The edited checklist, with this event's notes, is filed where the next event lead will find it |
All 8 rows of this part.
Thanks, that arrived.
That did not go through. Write a few words and send again.
This download has two files. The Outstanding Items Checklist, in Word, is a punch list for the last three days before your event. The full event checklist, in Excel, covers every phase from approval through the week after, one tab per phase. To read the full checklist online, see our event management checklist.
Everything on the punch list still needs a commitment, an owner or a confirmation. Reissue it every day until it’s empty.
Why do the last three days need their own list?
Three days out, treat nothing as almost done. It’s done, or it’s open.
A full event checklist is built for the long run-up: weeks of deciding, booking and building, sorted so each owner can see their whole job. If the plan has gone well, most of that list is ticked by the final stretch, and the lines that aren’t ticked are hiding among the ones that are. The big decisions were made weeks ago. What’s left is the small lines. The place cards nobody signed off. The prizes someone meant to order. The debrief everyone agrees should happen and nobody has put on a calendar.
Pulling the open lines onto their own page does two things. It makes them hard to miss, and it turns a vague feeling that something’s left into a list with a name and a time on every line. A short list gets worked. A long one gets skimmed.
When should you start an event punch list?
Three days before the event. That’s when the template is built to be issued, and the header of the Word file already carries a days-to-event box set to 3.
Before that, work from the full plan: every task, every owner, every due date counted back from event day. Build it from the full event checklist, the Excel file in this download, or read the same checklist on the event management checklist page linked at the top of this page. The reasoning behind each phase is in the guide on how to plan a corporate event. How far back the rest of the plan starts depends on the size of the event and the bookings it needs. The three days are the punch list’s own rule, and they hold whatever the size, because the list only carries what’s left.
If three days out is closer than you’d like and the full plan isn’t built yet, a punch list won’t rescue it. That’s the point to look at Events Authority’s corporate event planner service.
How do you use the punch list?
The Word file opens with its rule and a tracking table, then the prompts. Run it like this:
- Issue it three days out. Fill in the event name, the date you issued it and the days to event, then send it to everyone who owns a line.
- Give every item its own line. A line that holds two things closes half-done. Split it.
- Name what the line is missing. A commitment, an owner or a confirmation. If a line already has all three, it doesn’t belong on the list.
- Put one name on it. Several people can help with a line. One name answers for it.
- Put a time on it, not just a date. Three days out, “by Thursday” can quietly cost you a whole day out of the three you have left. “By 10 a.m. Thursday” gets missed early enough to fix.
- Reissue it every day. Mark what closed in the Done column and carry the rest forward with the new date. A line that survives two reissues needs a conversation, not another reminder.
- Aim for an empty list the day before the event. The file doesn’t set that deadline; I do. Anything still on the list then goes into the room unconfirmed, so decide it: close it, hand it to whoever runs the day, or cut it.
For step 4, an event RACI chart gives you that one name before the final stretch starts. For step 7, whatever you hand to whoever runs the day goes into the run of show.
The tracking table in the file follows the same order. Each row has a number, the item, which of the three it’s missing, one name, by when, and a Done column. The header above it carries the event name, the issue date and the days to event, so every reissue is dated and nobody works from yesterday’s copy.
The column that does the work is the one that names what’s missing, because each gap closes differently. The quoted lines below are made-up examples, not lines from any real event:
| Missing | Example of how it sounds | What closes it |
|---|---|---|
| A commitment | “Prizes would be nice.” Nobody has decided the item will happen. | A yes or a no from whoever can make the call, then an owner |
| An owner | “Someone’s doing the place cards.” The item is agreed, but no name answers for it. | One name, accepted by that person |
| A confirmation | “The printer said it should be fine.” The item is owned, but nobody has checked that it landed. | Something in writing: the reply, the order, the delivery on site |
Label the gap honestly. A line marked “confirmation” that is really missing an owner will sit there, confirmed by nobody, until the day.
What goes on the punch list?
Anything that still needs a commitment, an owner or a confirmation, and nothing else. The punch list gives you a place to start: sample prompts grouped by area, all labelled as samples, with the instruction to delete what doesn’t apply. Read them against your own event and keep the ones that make you stop.
- Guests. The final registration push to anyone invited who hasn’t answered, place cards and table assignments, and guest emails written and scheduled.
- Program. One presentation deck rather than one per speaker, a printed agenda for each seat, and music and sound cues chosen and tested.
- Room and look. Signage for check-in, the tech table and the capture station, what the team is wearing, and welcome kit items counted against the guest list, plus spares.
- Proof and press. The media kit, a plan for sound bites and b-roll (who, where and when), and the product flyer in print and digital.
- Communications. Who posts what during the event, the post-event communication plan, and the social push, scheduled.
- After. The debrief on the calendar with the people who need to be there, and shipping and tracking details sent to whoever leads on site.
The After prompts are the ones I’d read first. A debrief is easy to agree to and easy to leave off the calendar, and once the event is over, the people who need to be in it have already moved on to the next thing. Book it three days out, while everyone is still paying attention.
The prompts are memory joggers. Your event decides which ones stay, and a customer day, a partner dinner and a product launch will each keep different lines. Delete freely. A prompt you delete is a decision; a prompt you leave blank is a gap.
Where does this list come from?
The list comes from a partner launch event I planned for a client in 2026.
I was engaged to plan this event.
Three days out, the event brief put every item still missing a commitment, a role assignment or a confirmation onto its own list, with the debrief on it.
The punch list in this download is generalized from that list. It keeps the rule and drops everything specific to the event: every line in the file is a prompt, and none of it is client detail. The brief said “role assignment” where the template says “owner”; the test is the same. If a line still needs a commitment, an owner or a confirmation, it goes on the list, and nothing else does. The case study on this event walks through the rest of the plan.
What goes wrong in the last three days without one?
Without a punch list, the final stretch runs on memory and good intentions. Three kinds of line are the ones to watch.
One is the item between owners. Two people each think the other has the welcome kits. Both are sure someone does. Nobody does.
Another is the confirmation nobody asked for. The order was placed, so it feels done, right up until the box isn’t at the venue.
The last is the debrief that never gets booked. Nobody argues with it and nobody schedules it, and once the event is over, there’s no date forcing anyone’s hand.
Bottom line: if nobody owns the last three days, the event owns you. The file alone won’t fix that. A name on every line will, because a name is a person who notices when a line hasn’t moved.
Common questions
Is this a full event planning checklist template? Yes, and a punch list besides. The download has two files. The full event checklist covers every phase from approval through the week after, one tab per phase, with 56 tasks, each with its workstream and its done-when. The Outstanding Items Checklist is the punch list for the last three days before an event: every item still missing a commitment, an owner or a confirmation. You can also read the full checklist on the Events Authority event management checklist page, linked at the top of this page.
What format is the template? The Outstanding Items Checklist is a Word document. The full event checklist is an Excel file, one tab per phase.
What goes on an outstanding items list? Every item that still needs a commitment, an owner or a confirmation, one per line, with which of the three it’s missing, one name and a time. Once a line has all three, it’s done and it comes off.
When should you start an event punch list? Three days before the event, once the full plan is built. Reissue it every day until it’s empty, and aim to have it empty by the day before the event.
Who should own the punch list? The event lead issues it, reissues it and chases any line that hasn’t moved. Every line on it also has its own owner: one name, even when several people are helping.
Empty by the day before
Empty the list, then run the room.
For an outside read on the plan behind the list, request a complimentary event assessment.
Send over next year’s calendar and the packages you are looking at. You get a written read on which shows are worth the money and what is leaking on the way out.
Get your event assessmentCOMPLIMENTARY · ONE CONVERSATION · NO DECK