Conference planning checklist: owners, deadlines, and acceptance checks
Use an editable conference planning checklist covering the brief, budget, speakers, registration, rehearsals, event day, and follow-up.
A conference checklist becomes useful when each task has an owner, a due date, and a clear definition of done. “Sort out registration” is too vague to hand over. “Complete a test registration, payment, confirmation, and cancellation” gives the team something they can verify.
Download the conference planning checklist (CSV)
Open the file in Excel, Numbers, or Google Sheets. These are editable worksheets, with no sign-up required.
Agree on the brief and decision owners
Write down who the event serves, what participants should get from it, the format, the budget limit, and who approves commitments. Separate assumptions from confirmed decisions. Name the person who can resolve a programme change or approve an expense when the main organizer is unavailable.
The sequence below is a planning framework, not a universal timeline. A small member meeting and a multi-day congress have different lead times. Set deadlines around supplier commitments, registration promises, and your organization's approval process.
Before announcing the event
Scroll sideways to see all columns.
| Work | Definition of done |
|---|---|
| Event brief | Audience, format, dates, and intended outcomes are approved |
| Budget | Expected revenue, committed costs, assumptions, and contingency are recorded |
| Venue or delivery setup | Availability, access, capacity, and production responsibilities are confirmed |
| Programme outline | Session formats, speaker requirements, breaks, and audience needs are mapped |
| Registration offer | Ticket inclusions, restrictions, refund terms, and help contact are clear |
Before opening registration
Complete the attendee journey yourself with a test record: read the event page, register, receive confirmation, find joining information, and request help. Check the cancellation process and the information a guest receives after it. Remove test records from reporting or label them so they can be excluded.
For an association event, decide how member status is checked and who resolves a mismatch. For any restricted session, explain eligibility before people commit. Confirm how attendees can request accommodations and who follows up on those requests.
Before the programme is final
Collect speaker names, titles, biographies, session descriptions, and delivery requirements using one agreed format. Ask speakers to approve their public details. Record permission and responsibilities for any recording or subsequent distribution.
Build an agenda and internal run of show. Check room transitions and overlapping sessions. Confirm how a cancellation will be communicated and whether a backup session or extended break is the sensible response.
Before event day
Rehearse with the people who will operate the event. Include an attendee using their own phone or computer, a speaker, a moderator, and the support lead. Check access, microphones, screen sharing, session timing, and the route for asking for help.
Assign a decision owner for a room change, a speaker absence, and an access problem. Keep venue emergency procedures and the relevant contacts available to staff. Confirm those procedures with the venue and qualified local personnel; a generic planning checklist cannot establish that an event is safe.
During the event
Keep a brief issue log containing the time, impact, action, and owner. Resolve urgent problems first; retain enough detail to find repeated issues later. When a change is approved, update the information attendees actually use and confirm that front-of-house staff know it happened.
After the event
Reconcile invoices, document sponsor deliverables, send promised materials, and review attendee feedback. Publish recordings only according to the permissions and access arrangements agreed for the event.
Use a post-event report to turn findings into decisions. Give the next event team a short handover: what changed, why it changed, and what still needs a decision. Preserve useful evidence rather than writing a long list of generic recommendations.
For the platform portion of the plan, explore ConferenceTap's organizer tools and test the workflow against the checklist before relying on it at the event.