Speakers and moderators
Event speaker confirmation tracker
The programme has twenty slots and the secretariat has a dozen email threads, and nobody can say who has really confirmed.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Track each speaker with one status from a short agreed list, a named owner, the date of the last contact and the next follow-up date. Count a speaker as confirmed only when the speaker has replied in writing to the agreed terms.
Keep the tracker as the single source for the programme, the slide deadline plan and the decision log. A speaker on a verbal maybe is shown as pending.
Agree the status words first
If two people use confirmed to mean different things, the tracker misleads. Agree the meaning of each status once and write it at the top of the sheet.
Keep the list short. More than six statuses invites argument about which one applies.
| Status | Meaning |
|---|---|
| Shortlisted | Approved by the programme owner, not yet contacted. |
| Invited | Invitation sent, no reply. |
| In discussion | Speaker has asked questions or proposed changes. |
| Confirmed | Speaker has replied in writing to the terms sent. |
| Declined | Speaker has said no, with date. |
| Withdrawn | Was confirmed, later pulled out. Trigger the backup speaker plan. |
Columns that earn their place
- Speaker and organisation as they will appear in print.
- Session title and slot.
- Status and the date it last changed.
- Owner on the organiser side who is chasing.
- Next follow-up date.
- Terms confirmed: recording, logistics form, biography and slides received yes or no.
- Notes for decisions, for example a request to change the session.
Rhythm for follow-up
- Review the tracker at the same time each week with the programme lead.
- Chase every Invited and In discussion line that has passed its follow-up date.
- Move a line to Declined after the agreed number of chases and a final note, not silently.
- Update the programme draft only from Confirmed lines.
- Freeze the confirmed list when the programme goes to print and log any later change as a decision.
Who sees it
The programme lead, secretariat and speaker liaison edit it. The committee sees a summary. Share the full sheet with suppliers only if a competent person confirms that the contents are appropriate for them.
Worked example · Fictional example
A tracker before and after a weekly review
Fictional organisation and figures, for illustration only.
A fictional association's tracker shows 20 slots: 11 Confirmed, 4 In discussion, 3 Invited, 1 Declined and 1 Withdrawn. The weekly review finds that two In discussion speakers have not been chased for twelve days.
The liaison chases both the same day. One confirms in writing and the other asks to shift to the afternoon. The programme lead logs the swap as a decision and activates the backup plan for the slot that was withdrawn.
Use this yourself
Speaker confirmation tracker
Copy into a spreadsheet. Fill in only what has been confirmed in writing.
| Speaker and organisation | Session and slot | Status | Last contact | Owner | Next follow-up | Terms and materials received |
|---|---|---|---|---|---|---|
| Shortlisted / Invited / In discussion / Confirmed / Declined / Withdrawn | recording / logistics / biography / slides | |||||
Handle it in-house, or bring in help?
Your team can usually handle this when
- Fewer than about ten speakers and one person owning the programme.
- Invitations go through a single channel.
- The committee accepts the status words as written.
Outside planning help earns its fee when
- Several people issue invitations through their own contacts.
- Slots keep moving as speakers ask for changes.
- The committee needs reliable weekly numbers and nobody has time to chase.
Want someone to keep the speaker list honest?
A conference project lead can run the weekly confirmation review, chase open lines, update the tracker and flag when a slot has no confirmed speaker. Who is invited and what is offered stay with your programme owner and committee.
Questions organisers ask
What counts as confirmed?
A written reply from the speaker, or an authorised assistant, accepting the terms sent. A verbal agreement is recorded as In discussion until the speaker replies.
How often should we update it?
Weekly for most events, and more often in the final weeks. Use the same day and the same people each time.
Should sponsors or committee members see it?
Share a summary. Ask your data protection owner before sharing contact details beyond those who need them.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.