How to Manage Conference Speakers (Without Chasing Their Files)
You have thirty speakers, and you need a slide deck from every one. The bios and headshots came in weeks ago. It is one week out, and just three of them have sent their slides. The rest are quiet, and you are about to spend your evening writing the same email over and over.
Managing conference speakers is mostly this: collecting the right files from busy people who put your deadline near the bottom of their list, then keeping all of it straight until the doors open. Speakers are not difficult on purpose. Their talk feels finished in their head long before the file lands in your inbox, and your reminder is easy to skip.
This guide is the organizer's side: what to collect, when to ask for it, how to chase stragglers without nagging, and how to track speaker submissions so nothing goes missing the morning of.
How to Manage Conference Speakers: Start With a Roster, Not an Inbox
The first mistake is running speaker management out of your email. Every reply lives in a different thread, the headshot is buried three messages deep, and you cannot answer the one question that matters: who still owes me what.
Build a single roster instead. One row per speaker, one column per thing you need: bio, headshot, slides, session title, AV notes, agreement signed. A spreadsheet works to start. The point is that you can scan it in ten seconds, see the gaps, and track speaker deadlines without digging through email.
If you keep your files in a shared folder and your roster in a spreadsheet, the two drift apart. A shared folder takes a file called "slides_final.pptx" and a dozen like it, but it will not match them to your roster or tell you who has not sent anything. With Submitto, files arrive tied to the speaker who sent them, and your missing list stays current, so the two never drift.
Decide Exactly What You Need From Each Speaker
Be specific about every item before you ask. Vague requests get ignored or come back wrong, and a short bio or a low-resolution headshot means a second round of chasing.
- Bio. Set a word count, a point of view, and a sample structure so you do not get a resume back. A conference bio of 100 to 150 words in the third person works well, and some conferences cap it around 100. Give the number and a one-line example of the opening, and the bios come back in a consistent shape.
- Headshot. Ask for a high-resolution file, at least about 2000 pixels on the long edge, which is enough for the program in print and the website. State the format so you do not get a thumbnail pulled from a social profile, or worse, a headshot buried in a PDF.
- Slides. Name the format, the aspect ratio, and the deadline. Set the expectation early that slides run from the tech table, not from a speaker's laptop, which is what lets you collect and check them in advance.
- The rest. The session title and description, a signed speaker agreement, and any AV notes, like a microphone preference. Collect the title and agreement with the bio; the AV notes can wait until the slides.
Some items depend on where the speaker is and where the event is held. A release form, tax paperwork, or insurance for a paid speaker is one of them, so flag those rather than assume one form fits everyone.
Set Real Deadlines, and Set Them Early
Pick deadlines that give you room to fix problems, not ones that land the night before. Stagger the work: bios and headshots first, because the program and website need them, then slides last, because speakers keep editing those.
A schedule that works:
- Eight weeks out: confirmed session title, bio, and headshot. These feed the program and any printed materials, so they cannot wait.
- Two to three weeks out: the final slide deck, in the format you specified.
- The week of: any last revisions, collected in one place so the AV team is not handed a moving target.
Ask for slides earlier than you think. Collecting decks before the event lets you catch the obvious problems, a missing font, a video that will not play, the wrong aspect ratio, the wrong file format, while there is still time to send it back. That fix is easy two weeks out and impossible an hour before the session.
Chase the Stragglers Without Nagging
A speaker missing a slide deadline is normal, so plan for the follow-up instead of dreading it. Two well-timed reminders cover most people: one about a week before the deadline, and one two days before it. More than that and you are just nagging.
Make each reminder easy to act on. Put the deadline in the subject line, name what is still missing, and link straight to where speaker uploads land. Keep it plain text from a real reply-to address. A line like "We still need your headshot and slides by Friday" beats a polite paragraph that buries the ask.
The reminder you actually want is the specific one. "25 of 30 presentations have come in. Here are the ones you're missing." That only works if your list is current at any moment, so you always know who is missing. Track it by hand and every reminder starts with rebuilding that list. Keep it current instead, and you can see who is still missing and remind just them in a click, not an evening.
Keep the Files Straight So the Handoff Is Clean
Collecting the files is half the job. The other half is keeping them organized so that on event day, the AV team can find the right deck for each session and room without asking you.
Name files consistently from the start. Agree on one pattern, put the date in a sortable format like 2026-03-14 so versions line up in order, and mark a file "final" exactly once. The classic trap is a folder full of "final_v2" and "FINAL_real" decks where no one can tell which is current. A simple version number, v01 then v02, with the date, fixes it, or you skip the ritual with a tool that names files to your convention as they arrive.
Sort decks by session in running order, not by who sent them. The AV team works through the day in sequence, so lay the folder out in running order with one current deck per session. Over a shared folder, that sorting is manual work you do the night before. For the document your team runs the day from, see the guide on building a run of show.
