
0 of 44 done
Ticks are saved in this browser.
You are running a conference mostly on your own, or with one or two other people. The venue, the speakers, the catering, the badges, the budget, the slides. All of it routes through you.
This event checklist lays the work out by phase, from roughly six months out to the day after. It is built for a conference or a corporate event, and it leans toward the parts a small team trips on: late confirmations, missing files, and a final week that fills up fast. Work through it in order, or jump to your phase.
Most of the stress in event planning is not the event itself. It is the weeks of chasing people for things they promised and forgot to send. A checklist tells you when each thing should already be in hand, so nothing surprises you on event morning.
Four to six months out: book what you cannot reverse
This is when the expensive, hard-to-reverse decisions get made. Booking later narrows your options and raises your costs.
A note on the speaker side, because it quietly eats your final weeks. Each speaker owes you a bio, a headshot, a session title, dietary needs, AV requirements, and eventually their slides. Bios and headshots should be in hand two to four months out, well before the program goes to print or gets published and promoted on the website. Collecting that from twenty or more people over email, in a mix of formats, some of them PDFs that are awkward to resize or edit, then renaming and sorting every file by hand, is where a small team loses days. Collecting speaker and exhibitor files through one link is worth setting up before the requests go out, not after.
Two to three months out: confirm vendors and start the public push
The foundation is set. Now you fill in the details and start the public push.
Vendor coordination is the classic small-team failure point. Speakers confirm late and sponsors are slow to send their logos, so you cannot go to print on time, and one weak link can stall months of work. The fix is one running list of who owes you what, so a late item shows up the day it is late.
Four to six weeks out: confirm the final details
The big pieces are booked. This phase is about removing ambiguity from every handoff.

One to two weeks out: the slides, the script, and the run of show
This is the week the missing files become a real problem, because everything downstream depends on them. You can finalize the script and the slide order, but you cannot build the master show deck, or know which decks carry embedded video and audio that need testing, until the slides are in.
When the slides arrive with random filenames, you still have to match each one to a speaker and sort them by session before the AV team can use them. A submission tracker that shows who is still missing turns it into a glance: "25 of 30 presentations have come in. Here are the ones you're missing." Files land sorted by session, renamed to your convention.
The final 48 hours: test everything
Event day: the run sheet takes over
By now the checklist hands off to a minute-by-minute run sheet. Your job shifts from preparing to managing the room.

The day after: close the loop
The event is over, but the close-out now saves you real time next cycle.
How to use this event checklist
Treat the phases as deadlines, not suggestions. Each item should be in hand by the end of its phase, so the next phase has what it needs. For a smaller event, like a one-day seminar or a workshop, compress the early phases but keep the order. The sequence protects you, not the exact week count.
One habit matters most: separate the things you control from the things other people owe you. You can book a venue on your own schedule. You cannot make a speaker send slides on yours. Track those owed items in one visible list from day one, and the late ones stop ambushing you. For the habits that keep event day on schedule, see these event management tips.

