Twenty speakers, sixty emails
A two-day industry conference has twenty-odd speakers: keynotes, panellists, a moderator for each panel, and a few workshop leads. For each one you need a biography for the website and programme, a headshot of usable size, a session title and abstract, technical needs, the slide deck, a signed speaker agreement and consent to be filmed. The client's content lead invited half of them. Your team invited the rest.
Bios arrive as a Word file, as a link to a LinkedIn profile, and as three lines typed on a phone. Headshots are tiny screenshots. Slides arrive the night before, in a format the AV team did not expect, with an embedded video that will not play. Version three of a keynote's deck is emailed to the client instead of you, and version two is what goes on screen.
Why speaker content is always late
Speakers are busy people doing you a favour or being paid a fee, and neither group enjoys being chased. The chasing is worse because nobody can see what is missing across the whole programme.
- Requests go in separate emails from different people, so speakers do not know the full list.
- Deadlines are stated once and forgotten.
- Content comes back through the client, your account manager and the AV company, and ends up in three places.
- Nobody checks a headshot or a slide deck until it is needed, when it is too late to ask again.
- There is no single version of each speaker's slides that the AV team can trust.
The cost of a missing bio or a wrong deck
The website and app go live with placeholder photos. The printed programme is held for one late abstract. On the day, a speaker's wrong version is on screen and they stop to apologise, which is uncomfortable for them and for the client who invited them. Panellists turn up without knowing who moderates, because the briefing never reached them.
And your team spends weeks on polite reminder emails, which is expensive work for something a system can handle.
A speaker portal with one list per speaker
- Each speaker gets a personal link to a simple portal page for this event, with no password to remember.
- The page lists exactly what you need from them, each with a deadline: bio, headshot, session details, technical needs, slides, agreement, and any consent you require.
- Uploads are checked as they arrive: headshot resolution, bio length against your limit, slide file type, and whether embedded video files are included.
- Reminders go out on the schedule you choose, only for what is still missing, and escalate to the person who invited them.
- Your team and the client's content lead see one board showing every speaker and every item.
- Slide decks are versioned. The AV team downloads the latest approved version from the same place, and anything uploaded after a cut-off is marked so the technician checks it at the speaker ready room.
- Approved bios and photos feed the event website, app and programme export, so they are not copied by hand.
| Item | Check on upload | Where it goes |
|---|---|---|
| Biography | Length against your limit | Website, app, programme |
| Headshot | Resolution and shape | Website, app, screens |
| Slides | File type, embedded media | AV team, speaker ready room |
| Speaker agreement | Signed and dated | Event record |
| Filming consent | Answer recorded | Production and client |
Content week with a board, not an inbox
Six weeks out, every speaker has their link. The board fills up as bios and photos arrive. Your coordinator looks at the red items on a Monday and makes a handful of personal calls to the few who need a human nudge. On the day before the event, the AV team has the approved deck for every session except two late changes, which are flagged. When a keynote uploads a new version on the morning, the technician is alerted rather than finding out on stage.
Is this your speaker programme?
- Bios and headshots arrive in every format and are retyped for the website.
- Speakers get separate requests from different people.
- Slide versions are emailed to several people and the wrong one is used.
- You cannot see which speakers are missing what without checking each thread.
- The printed programme waits on one or two late abstracts.