Pre-event: contracts, deliverables, deadlines
The pre-event phase starts the day the speaker accepts. The first forty-eight hours after acceptance are the highest-leverage window of the whole engagement — speakers are committed, attentive, and looking for clarity. Use them well.
Within those forty-eight hours, the accepted speaker should receive: a single welcome email; a signed speaker agreement (or a sign-here link); a calendar invite for a fifteen-minute kickoff call in the next two weeks; a deadline calendar with all content deliverables and dates; a logistics intake form (dietary needs, accessibility requirements, travel preferences, accommodation preferences); and the name and contact of their single point of contact for the entire engagement.
The deliverables most conferences track:
• Talk title (final) — locked four to six weeks out
• Abstract for the public schedule — four weeks out
• Speaker bio (final) — four weeks out
• Professional headshot — four weeks out
• Slide deck (first draft) — two weeks out
• Slide deck (final) — three to five days out
• Tech rider for non-standard A/V needs — three weeks out
• Bio-and-photo release form — at acceptance
Publish this calendar to every speaker on day one. Most missed deadlines are not deliberate; they are buried in scattered emails.
Communications cadence
Speaker communications fail in two characteristic ways: too sparse (the speaker hears nothing for three weeks and panics) or too noisy (the speaker receives nine emails in a week and stops reading). The cadence that works is regular, structured, and brief.
A workable cadence:
• Kickoff call (T-8 weeks): fifteen minutes, video, one program manager and the speaker. Confirms the talk, the audience, deliverables, and answers questions. Almost every later issue is one a kickoff call could have surfaced.
• Weekly digest (T-6 to T-2): one short email per week, same day, same format. What is due this week, what is due next week, one logistics update, one calm reminder of the next major milestone.
• T-7 reminder: deck draft due, travel booked, any outstanding documents listed.
• T-2 reminder: final deck, run-of-show, greenroom location, mic check time.
• T-0 morning: a short calm message with the day-of contact, the mic-check time, and a one-line "good luck".
Keep these in a templated system so the words are consistent across speakers and across years. Personalization is for the kickoff call, not the logistical reminders.
Running this cadence by hand at scale is brittle. Purpose-built event speaker management tooling templates each touchpoint and surfaces who is behind on which deliverable in one view.
Day-of logistics
The day of the event is too late to fix anything that is broken. The job on the day is to remove friction, not to introduce it. The choreography that works:
• Greenroom open from one hour before the first session. Stocked with water, snacks, a phone-charging area, a printed run-of-show, and one named person available throughout the day to answer questions.
• Mic check thirty minutes before each speaker's session — not just at start of day. Bodies move, lavs come unclipped, batteries die.
• A standing tech runbook per stage: who switches the deck, who pulls up backup slides if the laptop fails, who triggers captioning, who hands the speaker their mic and which mic.
• A "T-five-minutes" handoff: the program manager walks the speaker to the side of stage, confirms the deck is loaded and on the correct slide, confirms the mic is hot, and hands them off to the stage manager.
• Captioning and accessibility: confirm the captioner has the speaker's name, talk title, and any specialized terminology in advance. Confirm the sign-language interpreter, if booked, has met the speaker before the session.
• A clear emergency runbook: who calls medical, who pauses the live stream, who briefs the audience if a session must be cut short.
Day-of choreography fails when speakers do not know what is happening next. Over-communicate the next five minutes, every five minutes.
Honoraria and travel reimbursement
Payment is the easiest thing to get right and the easiest thing to get publicly wrong. Speakers talk to each other. A conference with a reputation for paying within thirty days lands better speakers next year. A conference with a reputation for paying ninety days late or after follow-up loses them.
The workflow that consistently lands inside thirty days:
• Capture banking and invoicing details at the contract stage, not after the event.
• Send a templated post-event email within forty-eight hours of the speaker's session: thank you, here is the recording link when ready, here is the invoice template, here is the reimbursement form for travel.
• Process invoices in weekly batches, not as they arrive. Communicate the batch cadence to speakers so they know what to expect.
• Reimburse travel against receipts within fifteen working days. Keep a published per-diem table so speakers do not need to ask.
• Tax forms (W-9, equivalent EU forms) go in the contract package, not at payment time.
For international speakers, identify withholding obligations and currency-conversion fees at the contract stage. Surprises at payment time cost more in goodwill than they save in accounting time.
Post-event: recordings, payment, alumni network
The window immediately after the event is when most organizers go quiet — and it is precisely when speakers form their long-term opinion of the conference. The post-event work that compounds:
• Within forty-eight hours: thank-you email, payment instructions, recording timeline, NPS or one-question feedback survey.
• Within two weeks: edited talk recording delivered, with a draft social card and suggested copy for the speaker to share. Speakers do reshare when the assets are ready.
• Within thirty days: honorarium paid, travel reimbursed.
• Within sixty days: short retrospective survey — what worked, what did not, would they speak again. Use the results to refine next year's playbook.
• Ongoing: a quiet alumni list (newsletter, Slack, or LinkedIn group). Three messages a year is enough. Open the next CFS to alumni a week before public — they are your warmest pool.
A speaker who is paid on time, sees their recording shared well, and is invited back to next year's CFS becomes a multiplier — they refer other speakers and they pre-commit to future events.
Tooling: spreadsheets versus purpose-built
Spreadsheets are the right tool for managing five to ten speakers. They are cheap, transparent, and everyone can edit them. Past about ten speakers — or two simultaneous events — the cost of running operations on spreadsheets shows up as missed deadlines, duplicate emails, lost attachments, and version-mismatched run-of-show documents.
The signs you have outgrown spreadsheets:
• You maintain more than one tab per speaker.
• You routinely send the same email twice because you forgot you sent it.
• You have three "final-final" versions of the run-of-show.
• A speaker has emailed asking for an update on something you sent.
• You spend more than two hours per week on manual reminders.
What a purpose-built platform replaces, in order of value: deadline tracking with automated reminders, a single source of truth for content assets (decks, bios, headshots, contracts), reviewer scoring and decision workflow, payment status, recording delivery, and an alumni database that survives across rounds.
The cost of the tool is almost always a fraction of one staff-week per event, which is what spreadsheet operations cost at scale.
SpeakUp's conference speaker management software handles the eight-week cadence above by default — content deadlines, automated reminders, signed agreements, payment workflow, and recording delivery in one place.