Conference Planning Checklist

Quick answer

Conference planning runs on dependencies, not dates: the call for abstracts gates the program, the program gates marketing, and speaker confirmations gate everything printed. This checklist organizes the 12 months by phase — foundation (12–9 months out), program build (9–5), production (5–2), and show-ready (final 8 weeks) — with the program-side tasks generic checklists skip.

Foundation — 12 to 9 months out

Set the goal that decides trade-offs later: attendance, revenue, member value, or CE delivery — pick the primary
Lock dates against competing events, holidays, and your industry's travel calendar
Contract the venue with room block, AV, and F&B tied to realistic attendance — last year's actual, not the stretch goal
Set the budget with a 10–15% contingency line that nobody is allowed to pre-spend
Recruit the program committee and agree the topic tracks — vague tracks now become off-target submissions later
Choose the program stack: submissions, review, speaker management, agenda — the systems decision that haunts or helps every later phase
Open sponsorship sales with inventory defined: booths, sessions, amplification packages, receptions

Program build — 9 to 5 months out

The phase generic checklists skip. This is where the conference is actually made.

Launch the call for abstracts 8–12 weeks open, with structured forms that collect what review needs (track, format, objectives, disclosures)
Promote the call in waves — launch, mid-point, final week — through your speaker CRM and member channels
Assign reviewers by topic with conflicts excluded; score against a rubric, blind where your field expects it
Run decisions on a hard calendar: authors need acceptance 4–5 months out to book travel
Send acceptances with confirm-by deadlines; collect bios, headshots, AV needs, and disclosures in the same flow — not four chase emails
Build the agenda from accepted sessions, checking the grid per speaker, per room, and per track
Confirm keynotes and invited speakers with contracts, fees, and recording consent in writing
Open registration the day the program is strong enough to sell — session-level agenda published

Production — 5 to 2 months out

Marketing runs on the program: session and speaker promotion, not generic save-the-dates — give speakers tracked share assets
Collect presentations and posters with format checks and a real deadline one week before show
Lock AV orders per room from actual session formats — the panel needs four mics, the workshop needs power at tables
Publish the mobile app / online agenda from the same data as the printed program — divergence here is the classic day-one embarrassment
Brief moderators and session chairs: timing, Q&A handling, and the overrun protocol
Staff plan with names per role per slot: registration desk, room monitors, speaker ready room, floaters
CE/CME paperwork filed: learning objectives, disclosures, evaluation mechanics approved by the accreditor

Show-ready — final 8 weeks

Freeze the program two weeks out — after that, changes go through one owner and update every surface from one record
Build run of show docs per stage and rehearse transitions the day before
Print with a change plan: what happens to signage, program book, and app when a speaker drops day-of
Confirm every speaker one week out with their room, time, AV setup, and where to check in
Pre-write the post-event: survey ready to send within 24 hours, content capture (recording, transcription) confirmed per room
Debrief scheduled for the week after — while the team still remembers, with the survey data in the room

Frequently asked questions

Twelve months for a program-driven conference — the call for abstracts alone needs 8–12 weeks open plus review time, and authors need acceptance 4–5 months out to book travel. Smaller single-track events compress to 6 months; the dependency order stays the same.

Dates and venue first, then the call for abstracts, then review and acceptances, then the agenda, then registration and marketing — because marketing sells the program, and the program doesn't exist until review finishes. Logistics runs parallel but never gates content.

When there is a program worth buying — ideally a session-level agenda. Early-bird windows work best against a visible program; registration opened against a bare save-the-date converts your most loyal attendees only.

The program layer: structured abstract collection, reviewer assignment with conflict checks, acceptance-to-confirmation flows, and speaker material collection. Generic checklists cover venue and catering, then compress the actual conference content into one line item.

Assume they will happen and design for it: freeze the program two weeks out, route changes through one owner, and keep agenda, app, program book, and signage generated from one session record so a swap updates every surface at once.

Registration, plus a program layer for submissions, review, speaker management, and agenda build. Suites bundle a thin version of the program side; teams with real review workflows typically run a dedicated platform like Sessionboard beside their registration system.