Speaker management is not an inbox

Managing speakers for a conference should be a pipeline. Instead, it's a pile of email threads, a shared spreadsheet, and a lot of hoping nothing falls through the cracks.

The workflow from call for papers to someone walking on stage has at least six distinct steps. At most events, every single one of them is disconnected from the others.

How it typically works

A CFP goes out — often via a Google Form or a plain email. Submissions land in a spreadsheet. The review committee exchanges opinions over email, sometimes cc'ing the wrong people, sometimes forgetting to reply at all. Acceptance and rejection emails are sent manually, one by one.

Then the real chaos starts. Accepted speakers reply asking about AV setup, timing, and presentation format. Each reply spawns a new email chain. Presentations are uploaded as email attachments — often the wrong version, sometimes the wrong format. Scheduling happens in a separate tool, or a different tab in the same spreadsheet. Nobody's checking whether Speaker A is available at 2pm on day two, because the schedule builder doesn't know who the speakers are.

Every step is a silo. The CFP system doesn't talk to the review process. The review process doesn't talk to the schedule builder. The speaker doesn't know what's happening unless someone remembers to email them. And someone often doesn't.

What goes wrong

Plenty. Speakers submit and hear nothing for weeks — sometimes months. They assume they've been rejected, or they've already committed to a different event by the time you get back to them. Good speakers, lost to slow process.

Presenters send the wrong file format because the requirements were buried in paragraph four of an email from six weeks ago. Sessions get scheduled without checking speaker availability, and nobody finds out until the speaker does. Last-minute cancellations mean manually reshuffling the programme — moving sessions, updating the printed schedule, and emailing everyone affected.

For a conference with 20 speakers, you can muscle through this. For one with 50, 100, or 200 speakers, it's untenable. The admin overhead grows faster than the speaker list, and the quality of the experience — for both organisers and speakers — drops with every added name.

What it should look like

The fix isn't complicated. It's just connecting the steps that are already there.

Speakers submit through a portal with clear formatting requirements and submission guidelines — not a form that dumps into a spreadsheet. Reviewers score and comment in one place, with visibility into what others have said. No email threads, no forwarded PDFs.

Accepted speakers get notified automatically and can see their session details immediately — title, abstract, time slot, room assignment, AV setup. Presentation uploads happen in the portal with version tracking, so you always know which file is current and whether it meets the format requirements.

Speakers can check their own schedule, see their room assignment, and review logistics without emailing anyone. Discussion threads replace email chains for coordination — tied to the session, not buried in someone's inbox. And when the schedule changes, speakers see it in real time. No "please disregard the previous email" messages.

One system, one source of truth

ema handles the full speaker lifecycle: submission, review, acceptance, materials, scheduling, and event day. It's one system, not six tools held together with email.

The peer review workflow is built in — scoring, comments, committee visibility. Acceptance triggers notifications and gives speakers access to their portal. Uploads are versioned and format-checked. The schedule builder knows who your speakers are, when they're available, and what room they're in. Changes propagate automatically.

For conferences with 50 to 200-plus speakers, this isn't a nice-to-have. It's the difference between a coordinated programme and a chaotic one. Between speakers who feel informed and supported, and speakers who feel like they're shouting into a void.

The speaker workflow has always had all the right steps. They've just never been connected. That's what we built ema to fix.