For Organizers · 12 min read

How to run a Call for Papers (end-to-end)

A great conference is made in the boring weeks nobody sees — the three months between "we should do a CFP" and "accepted speakers notified." Here is the end-to-end playbook we've watched hundreds of organizers run, distilled to the steps that matter.

Step 1 — Name the shape of the event, not the topic

Before you write a single submission question, describe the shape of the event in two lines: format (single track / multi track / unconference), length, audience seniority, and the single promise a speaker can deliver on. This document shapes every decision downstream.

Step 2 — Design the submission form

A good CFP form asks as few questions as possible, but the right ones. Always include: abstract, audience takeaway, talk arc, and evidence of past delivery. Avoid "bio + photo" vibes — those belong on the speaker profile. On submitcfp you can clone a proven preset (Meetup / Conference / Hackathon) and tune fields per track.

Step 3 — Open early, close firmly

Give speakers at least 4 weeks, ideally 6. Broadcast the opening day everywhere (Twitter, LinkedIn, Slack communities, speaker Discords), then silence until mid-cycle. Close the CFP at the exact stated hour — extensions punish the speakers who hit the deadline.

Step 4 — Curate a program committee

Recruit 2× the reviewers you think you need. Pair senior reviewers with newer voices. Assign reviewers to tracks they actually know. submitcfp lets you invite reviewers by email, assign them to specific tracks, and track their progress live — so you know who to nudge before deadlines slip.

Step 5 — Run multi-stage reviews

Two stages is the sweet spot for most conferences: a broad L1 screen, then a deep L2 for borderline talks. Enable blind review mode (hide speaker identities) for L1 to fight unconscious bias, and optionally reveal identities at L2 where lived experience matters. Auto-promotion thresholds keep the funnel moving.

Step 6 — Decide in one sitting

Once reviews are in, do not let decisions drag for a month. Block a single program committee meeting, rank submissions by average score, and batch accept / reject with thresholds. Use the Diversity & Inclusion dashboard to sanity-check your lineup before publishing.

Step 7 — Publish privately, notify publicly

Publish results privately first so accepted speakers see their status in-app immediately. Give yourself 24 hours to personally email borderline rejections with kind, honest feedback (a reputation investment worth its weight in gold). Then fire the mass Notify Speakers email.

Step 8 — Build the agenda in public

Drag accepted talks into rooms and time slots with submitcfp's agenda builder. Publish the URL as soon as you have a draft — it creates FOMO, pushes ticket sales, and lets speakers cross-promote weeks earlier. Embed the schedule on your event website in one line of code.

Step 9 — Debrief, always

After the event, survey attendees and speakers, export the full dataset from submitcfp (submissions, reviews, scores, agenda, feedback), and write down three things you'll change next year. This is the 5% of the work that compounds.