Event Planning Checklist: Every Step From 12 Months Out to the Day After
When you book the room, book the debrief too. A useful event planning checklist gives the survey, sponsor recap, and next-event decisions the same treatment as catering: a deadline and an owner.
Use the month markers below as a working schedule. Replace each role in the Owner column with one person’s name; one person can cover several roles. Add exact dates from your contracts.
If you have inherited an event already underway, check earlier decisions before making new commitments.
How far ahead should you start?
Start venue sourcing earlier for the largest bookings. Expect lead times of 18–24 months for large convention venues. Check your destination and dates before assuming a 12-month runway is enough.
For a smaller event, compress the schedule while keeping the dependencies: approve the brief and budget, secure the venue and essential people, then open registration. Move any task earlier when a supplier deadline requires it.
1. Prepare
12 months before: Set the brief and the finish line
| ✓ | Action | Owner |
|---|
| ☐ | Write the audience, purpose, capacity, and one primary outcome on a one-page brief. | Event lead |
| ☐ | Choose the format: compare professional event ideas or corporate event ideas against that outcome. | Program |
| ☐ | Approve a budget ceiling, funding sources, contingency allowance, and who can authorize spending. | Finance |
| ☐ | Name the event lead and task owners; reserve time for the survey, sponsor reports, and debrief. | Event lead |
11 months before: Confirm dates and venue
| ✓ | Action | Owner |
|---|
| ☐ | Check date options against holidays, competing events, travel, and your audience’s working calendar. | Event lead |
| ☐ | Visit shortlisted venues; check usable capacity, accessible routes, room layouts, Wi-Fi, power, and loading access. | Operations |
| ☐ | Review the venue contract: inclusions, minimum spend, deposits, cancellation, setup access, and final-number deadlines. | Finance |
| ☐ | Confirm the booking and any room blocks; record every payment, release date, and supplier deadline. | Operations |
10 months before: Build the program
| ✓ | Action | Owner |
|---|
| ☐ | Map sessions, meals, breaks, networking, and room changes; allow time to move between spaces. | Program |
| ☐ | Invite priority speakers; confirm fees, travel, accessibility needs, recording permissions, and backup options. | Program |
| ☐ | For panels, use the planning guide, format ideas, and moderator questions. | Program |
| ☐ | Send a save-the-date once the date and venue are confirmed; state who the event is for. | Communications |
9 months before: Secure partners and suppliers
| ✓ | Action | Owner |
|---|
| ☐ | Define sponsor packages with deliverables, deadlines, audience fit, and the evidence each sponsor will receive. | Partnerships |
| ☐ | Request comparable quotes for catering, audiovisual production, staffing, photography, and other required services. | Operations |
| ☐ | Book critical suppliers; add their cancellation terms, payment dates, and delivery requirements to the plan. | Operations |
| ☐ | Assign someone to confirm venue requirements, insurance, permits, security, and emergency arrangements for this event. | Operations |
8 months before: Open registration and promotion
| ✓ | Action | Owner |
|---|
| ☐ | Publish the event page: audience, takeaways, agenda, date, time zone, location, access details, price, and contact. | Communications |
| ☐ | Test registration, payment or RSVP, confirmation email, cancellation, and waitlist on a phone. | Registration |
| ☐ | Ask only useful registration questions; provide a contact for dietary and accessibility requests. | Registration |
| ☐ | Launch invitations with tracked links for each partner and channel; set a weekly registration review. | Communications |
7 months before: Choose tools that can produce the report
| ✓ | Action | Owner |
|---|
| ☐ | Test conference engagement software with two sample sessions, attendee access, and a report you could actually use. | Technical |
| ☐ | Map registration, live interaction, and reporting; use this event engagement platform overview to plan the audience workflow. | Technical |
| ☐ | Decide which profile fields explain responses, who can see them, and how people choose follow-up contact. | Event lead |
| ☐ | Set anonymous-question and moderation rules; for internal events, review these anonymous town hall platform options. | Program |
6 months before: Design participation and meetings
| ✓ | Action | Owner |
|---|
| ☐ | Give each session a participation moment and a purpose; choose from these event engagement ideas. | Program |
| ☐ | Schedule networking with enough room and time for introductions; adapt these networking event ideas. | Program |
| ☐ | If exhibiting, confirm booth services, shipping, staffing, and the visitor follow-up plan using these trade show ideas. | Partnerships |
| ☐ | Review bookings and committed costs against the budget; adjust scope if funding or demand has changed. | Finance |
5 months before: Prepare content and hosts
| ✓ | Action | Owner |
|---|
| ☐ | Collect speaker titles, biographies, photos, session descriptions, and content deadlines in one shared folder. | Program |
| ☐ | Brief speakers on the audience and intended takeaway; choose suitable interactive presentation activities. | Program |
| ☐ | Assign a host and clear instructions to any networking game; provide a quieter way to take part. | Program |
| ☐ | If using a quiz, select and check the questions and answers; confirm timing, scoring, and any prizes. | Program |
4 months before: Prepare the questions and follow-up
| ✓ | Action | Owner |
|---|
| ☐ | Draft live poll questions with clear answer options; note when to ask and what the response will change. | Program |
| ☐ | Assign a moderator and answer owner using this live Q&A workflow; define how unanswered questions will be handled. | Program |
| ☐ | Draft the post-event survey, attendee email, no-show email, and sponsor recap; assign send dates now. | Communications |
| ☐ | Define report measures, data sources, and comparison periods using the event analytics and ROI guide. | Event lead |
3 months before: Confirm the attendee experience
| ✓ | Action | Owner |
|---|
| ☐ | Walk the arrival-to-departure route: transport, check-in, accessible seating, toilets, catering, quiet space, and exits. | Operations |
| ☐ | Confirm menus, dietary handling, supplier arrival slots, equipment, signage locations, and waste collection. | Operations |
| ☐ | Set staffing shifts and backups for registration, room support, technical support, speakers, and sponsor contacts. | Operations |
| ☐ | Check promotion against the attendance goal; prioritize channels bringing relevant registrations. | Communications |
2 months before: Build the day-of run sheet
| ✓ | Action | Owner |
|---|
| ☐ | Write one timed run sheet with setup, cues, sessions, breaks, room changes, closing, and breakdown. | Event lead |
| ☐ | Give each cue one owner, a contact number, and a fallback; name the person authorized to change the schedule. | Event lead |
| ☐ | Run an end-to-end technical rehearsal: microphones, slides, remote speakers, captions if used, QR codes, polls, and reports. | Technical |
| ☐ | Plan for a missing speaker, internet failure, delayed start, medical incident, and evacuation with the venue team. | Operations |
1 month before: Lock the working plan
| ✓ | Action | Owner |
|---|
| ☐ | Reconfirm suppliers, speakers, travel, sponsor deliverables, and venue deadlines; close outstanding approvals. | Operations |
| ☐ | Finalize slides, signs, badges, room plans, speaker introductions, and approved sponsor assets. | Program |
| ☐ | Send practical joining instructions; invite questions and reconfirm requested accommodations privately. | Communications |
| ☐ | Test the survey and email segments; produce a sample report and schedule the debrief while calendars are still open. | Event lead |
Final week and the day before
| ✓ | Action | Owner |
|---|
| ☐ | Submit final numbers by each supplier’s deadline; confirm dietary and access arrangements. | Operations |
| ☐ | Brief staff and volunteers; distribute the current run sheet, contact list, room map, and escalation route. | Event lead |
| ☐ | Download backup slides and attendee lists; prepare spare adapters, batteries, chargers, tape, and printed signs. | Technical |
| ☐ | Send the final reminder with arrival time, route or joining link, access contact, and cancellation option. | Communications |
| ☐ | The day before, walk the venue, confirm deliveries, test check-in and every room, and check the weather or transport alerts. | Operations |
2. Run
Day-of run sheet
Example for a one-day conference running 09–17. Replace these times with your program and venue access hours; add a row for every session, room, and technical cue. Keep one current version with the event lead.
Before doors open, record: schedule decision-maker ______ · venue contact ______ · technical contact ______ · team channel ______.
For each session, identify the fallback if a speaker or connection fails.
| Time | Cue / action | Owner |
|---|
| 07–07 | ☐ Open venue; check room layout, exits, signage, deliveries, and supplier arrivals. | Operations |
| 07–08 | ☐ Test sound, slides, remote links, check-in, QR codes, polls, and the backup connection. | Technical |
| 08–08 | ☐ Brief the team and speakers; confirm cue owners, contact channel, and schedule changes. | Event lead |
| 08–09 | ☐ Open check-in; record actual arrivals and direct attendees to the first room. | Registration |
| 09–09 | ☐ Welcome attendees; explain the schedule, participation link, access support, and emergency information. | Host |
| 09–12 | ☐ Run morning sessions and the planned break; cue speakers, moderate questions, and log timing changes. | Program |
| 12–13 | ☐ Open lunch and networking; check catering, room resets, and afternoon speakers. | Operations |
| 13–16 | ☐ Run afternoon sessions and breaks; track session attendance and collect unresolved questions. | Program |
| 16–17 | ☐ Close with one next step, the survey link, and the promised follow-up date. | Host |
| 17–18 | ☐ Manage departures and breakdown; return equipment, save data, log incidents, and release staff. | Operations |
3. Results
Start the results phase at closing. The first deadline is the next day; sponsor reporting and improvement actions continue afterward.
Within 24 hours
| ✓ | Action | Owner |
|---|
| ☐ | Send attendees the survey within 24 hours, with a thank-you and any resources already promised. | Communications |
| ☐ | Send no-shows a separate message with available resources and an optional reason-for-absence question; omit attendance-rating questions. | Communications |
| ☐ | Reconcile registrations, cancellations, actual attendance, and session counts; preserve question and poll exports. | Registration |
| ☐ | Assign unanswered questions and requested introductions to named owners with response dates. | Program |
Keep the survey short:
- How useful was the event?
- What can you apply?
- What remained unanswered?
- What should we change?
- Would you like a specific follow-up? Make this optional and explain what happens next.
Within 7 days
| ✓ | Action | Owner |
|---|
| ☐ | Send each sponsor a recap: promised versus delivered activity, actual reach, relevant themes, and agreed follow-up data. | Partnerships |
| ☐ | Share contact details only for the follow-up participants agreed to; distinguish information requests from meeting requests. | Partnerships |
| ☐ | Review feedback with response counts; group themes and check them against the original comments and questions. | Event lead |
| ☐ | Hold the debrief; log what to keep, stop, and change, with one owner and a due date for each change. | Event lead |
Within 30 days, or the agreed reporting window
| ✓ | Action | Owner |
|---|
| ☐ | Reconcile invoices, revenue, staff time, and follow-up costs; compare actual spending with the approved budget. | Finance |
| ☐ | Update outcomes as follow-up happens; keep requests, booked meetings, completed meetings, and confirmed business separate. | Partnerships |
| ☐ | Archive the final report and change log with the next event brief; book a review of outstanding actions. | Event lead |