Event management checklist Every task, one name

Run your next company event without anything slipping between teams.

You get the full checklist below, sorted by phase and by workstream, with a clear “done when” on every task. We sorted it that way so each owner can see their whole job at once. You also get a free download of the final punch list for the last days before the event.

Copy the checklist into your own tool, cut what you don’t need, and put one name on every task that’s left.

Get the final punch list

Phase 1: As soon as the event is approved

Start here the day someone says yes to the event. Nothing in this phase books anything. It decides what the event is for and who answers for it, and the first row is the question I’d put before everything else: “What do you want to be true 30 days after this event?”

How to read the tables: each row is one task. Workstream is the part of the event the task belongs to, so an owner can filter for their whole job. Done when is what you can point at to prove the task is finished. Rows marked Whole event shape every workstream, so they sit with the executive sponsor or the event lead.

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
Name one owner for each workstream you kept	Whole event	Every workstream has exactly one name against it

If you reach the end of this phase and can’t put a name against every workstream you kept, that’s the point to look at corporate event planning help from Events Authority.

Phase 2: Planning and booking

This phase turns the brief into bookings. Every booking should trace back to a line in the brief. If one can’t, question it before you sign anything.

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
Decide what proof the event should leave behind	Proof capture	Photos, testimonials and guest feedback each have a plan and an owner
Arrange travel and hotel, if guests or your team are traveling	Venue and logistics	Rooms and travel are booked, or guests have been told exactly how to book

Phase 3: Build

The build is where the event gets made: the content, whatever guests will put their hands on, the look, and every message a guest will receive. Write the guest emails now, while there’s still time to make them good.

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
Share the guest emails with everyone working the event	Guest communications	Everyone on the team has read what the guests will read
Write the run of show	Day-of operations	Every segment has a start time, an owner and a cue

Phase 4: The final two weeks

By now the decisions are made. The final two weeks are for confirming them, and two things carry this phase.

The first is the outstanding items list. Three days out, pull every item still missing a commitment, an owner or a confirmation onto one list, and reissue it daily until it’s empty.

The second is the freeze. Two days out, every task should be Ready for Review (the work is finished and waiting for its owner’s sign-off) or Complete, and nothing should be In Progress on rehearsal day. Anything changed after the freeze goes into the room unrehearsed.

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
Pull the outstanding items list three days out	Whole event	Every open item is on one list with one name and a time beside it
Freeze the plan two days out	Whole event	Every task is Ready for Review or Complete, and nothing is In Progress on rehearsal day

Phase 5: Event day

On the day, the checklist hands over to the run of show. Cues, not decisions. Whoever runs the room should be able to work every row here from the handoff notes without having to call anyone.

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
Send the thank-you email the same evening	Guest communications	Sent on the evening of the event, naming what guests actually did

Phase 6: The week after, and the debrief

The event ends. The checklist doesn’t. This phase gathers the proof, puts a name on every follow-up, and checks the event against the outcome you wrote in phase one.

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

How to use this checklist

The tables are a starting point. Five moves turn them into your plan:

1. Copy it into whatever your team already tracks work in. A shared spreadsheet does the job; so does a project tool.
2. Delete what doesn’t apply. Whole workstreams can go: an internal event with no product to show can drop product or demo readiness. Deleting a row is a decision. A row left blank is a gap.
3. Put one name on every row that’s left. Several people can work on a task, but one name answers for it. A plain way to record that is a RACI chart, a standard project-management tool: for each task, who is Responsible for doing it, who is Accountable for it, who is Consulted and who is Informed, with exactly one Accountable per row.
4. Add a due date and a status to every row. Count due dates back from event day. Five statuses do the job: Not Started, In Progress, Blocked, Ready for Review and Complete.
5. Review it on a rhythm: weekly while the event is far off, daily in the final two weeks, starting with whatever is Blocked and who it’s waiting on.

The checklist says what to do and how you’ll know it’s done. The reasoning behind each phase, from the outcome sentence to the debrief, is in the guide on how to plan a corporate event.

This checklist is written for events your company hosts, such as a customer day, a partner event, a launch, an executive session or an internal event. If you’re exhibiting at someone else’s show, you’ll need booth, lead capture and sponsorship rows that aren’t here.

An example from a real event plan

Several rows above also appear in the plan for a partner launch event I planned for a client in 2026.

I was engaged to plan this event.

It was an invite-only launch and hands-on workshop, held the day before a larger industry conference. I planned it end to end, and the client’s own team ran it on the day, from the plan. The build started about a month out. Ownership ran on a RACI matrix, with one Accountable name on every task.

What that plan and this checklist have in common:

• Five success criteria, written before anyone was assigned a task. That’s phase 1.
• Four guest emails written in advance, each with a send date: a seat confirmation about two weeks out, a checklist a week out, a final call the night before, and a thank-you on the evening of the event. They’re written in phase 3 and sent across phases 4 and 5.
• Daily written check-ins in the final two weeks, every task Ready for Review or Complete two days out, and nothing In Progress on rehearsal day. That’s phase 4.
• A list, three days out, of every item still missing a commitment, an owner or a confirmation, with the debrief already on it. Also phase 4.
• Handoff notes to whoever ran the day: what was shipped and where each item goes, what to switch on and by when, what the venue would place, which photos to take, and who was on standby by phone. Phases 4 and 5.

The workstream names on this page are generalized to fit any company-hosted event, so they don’t all match the plan’s own labels. A client case study walks through that launch plan in full.

What a list of tasks leaves out

A task list tells you what has to happen. It doesn’t tell you who will notice when it hasn’t.

Here’s the truth: a checklist without owners is a wish list. Every row looks handled because it’s written down, and nobody checks whether it moved, because checking was never anybody’s job. Then the event week arrives, and the row nobody owned is the one you hear about.

So read your checklist down the owner column before you read it down the task column. A blank there is the most important line on the page.

Common questions

What should be on an event management checklist? Every task the event needs, from the outcome sentence to the debrief, grouped by phase and by workstream, with one owner and a clear “done when” on each. The phases on this page run from the day the event is approved, through planning and booking, the build, the final two weeks and the day itself, to the week after and the debrief.

How far in advance should you start an event checklist? There’s no universal lead time, because the type of event, its size and how early the venue books up all change it. Start the checklist the day the event is approved and count every due date back from event day. For one example, the build for that partner launch started about a month out. If the due dates don’t fit the time you have, cut scope or move the date before you squeeze the tasks.

What is the difference between an event planning checklist and an event management checklist? The two terms overlap. On this page, an event planning checklist covers the build-up: deciding, booking and building. An event management checklist covers that and the rest: running the day and closing the event out afterward. The checklist above covers both.

Who should own the event checklist? The event lead keeps the checklist, every row on it has exactly one Accountable owner, and the executive sponsor makes the final call when two options collide. Several people can work on a task, but one name answers for it.

Is there a downloadable version of this checklist? Yes, for the final stretch. The event planning checklist template page, linked at the top of this page, has a free Word download of the final punch list: the three-days-out list of every item still missing a commitment, an owner or a confirmation. The full checklist is on this page to copy into your own tool.

One name on every row

Put a name on every row, then build the event.

For an outside read on your plan before the build starts, request a complimentary event assessment.