Every event organizer knows the drill: you've booked 25 speakers, and now you need a bio, a headshot, a talk title, and slides from each one — by different deadlines, in different formats, scattered across email threads. By show week you're chasing the last five people and renaming headshot-final-FINAL-2.jpg at midnight.
It doesn't have to work that way. Here's a repeatable process for collecting speaker materials cleanly — what to ask for, when to ask, and how to track every item so nothing slips before showtime.
Before you send a single request, decide your full list. Asking for everything once beats five follow-up emails. A typical conference needs:
Pin down the exact specs up front (dimensions, formats, word counts). Vague asks are the #1 cause of wrong files and re-dos.
List each item a speaker must submit and the exact requirement next to it ("Headshot — JPG/PNG, min 1000×1000px"). This becomes the single source of truth you'll track against. Set two deadline tiers: bio/headshot/title early (for promo) and slides later (closer to the event).
Don't collect in a shared folder or a reply-all thread. Each speaker should get a private link where they submit their items — so files arrive labeled by person, not as 25 anonymous attachments named IMG_4471.jpg. Avoid tools that force speakers to create an account; every extra login step costs you completion.
The painful part of speaker wrangling isn't receiving files — it's knowing who still owes you what. Use a view that shows each speaker and each item as outstanding / submitted / approved, so you can chase only the people who are actually missing something instead of emailing everyone.
When a file comes in wrong (low-res headshot, off-spec deck), you need a clean way to say "redo this" without it getting lost. Approve good submissions, request a new version where needed, and mark the final version explicitly — so versioning doesn't become bio_v3_realfinal.docx.
Once everything's in, export a single organized folder with files auto-named by speaker and item (jane-doe_headshot.jpg, jane-doe_slides.pdf). That folder is what you hand to your designer, AV team, and web team — no manual renaming, no "which headshot was the final one?"
You can run all five steps manually with a spreadsheet plus a Drive or Dropbox folder — but you'll do the tracking, renaming, and chasing yourself. A purpose-built collection tool like Draftpile does steps 2–5 for you:
Draftpile is free for 3 rooms; Pro is $19/mo or $190/yr for custom branding and unlimited rooms. See the Draftpile for events page for the full walkthrough, or how it compares to a plain transfer tool in Draftpile vs WeTransfer.
Collect every speaker's bio, headshot, and slides in one room.Give each speaker a private link, see who's still outstanding at a glance, and export a clean named folder for your design and AV teams. Free for 3 rooms — no account required.
Send each speaker a single request listing exactly what you need (headshot specs, short and long bio, talk title) with a clear deadline, and collect through a private upload link per speaker rather than email attachments. A purpose-built tool like Draftpile gives each speaker their own link, tracks which items are still outstanding, and exports a clean named folder — so you're not chasing inboxes or renaming files.
Most events need a high-res headshot, a short and long bio, the talk title and session description, the slide deck (usually due later), a company logo, social handles and pronouns, and any A/V or accessibility requirements. Specify exact formats and dimensions up front to avoid wrong files.
Set two deadline tiers (bio/headshot/title early for promo, slides closer to the event), ask for everything in one upfront request, and use a tool that shows per-speaker status so you can send reminders only to the people who are actually missing something.
Yes — choose a tool that allows link-based uploads without sign-in. Draftpile, Dropbox File Requests, and Jotform let speakers upload via a link with no account. Avoid Google Forms file uploads and shared Google Drive folders for this, since both require speakers to have a Google account.
Collect each speaker's items under one labeled link, mark the final version of each file, and export a single folder with files auto-named by speaker and item (e.g. jane-doe_headshot.jpg). That gives your design, web, and AV teams one clean handoff instead of a pile of IMG_xxxx attachments.
CFP platforms like Sessionize handle talk submission and review before speakers are selected. This guide covers material collection after selection — gathering the final bios, headshots, and slides you need to run the event. Many organizers use a CFP tool to choose speakers, then a collection tool to gather the assets.