What Should a Call for Speakers Include? A Template for Organisers

TL;DR
- A call for speakers states the theme, the audience, the session types and lengths, what to send, the deadline, how proposals are scored, what speakers receive and when they will hear back.
- Write the scoring criteria before the call opens, and publish them.
- Work back from the date your speaker brief goes out; most calls open 18 to 24 weeks before the event.
- Say plainly what speakers get, even if it is nothing.
- Answer everyone, including the people you decline.
A call for speakers is an open invitation for people to propose themselves as presenters at your event. This guide answers one question: what should a call for speakers include? It gives a template you can copy, a timeline worked back from the day, a scoring method and the reply that closes the loop. I have hosted more than 800 events, and the speakers a call brings in are the ones I end up introducing.

What should a call for speakers include?
A call for speakers should include the theme, the audience, the session types and lengths, what to send, the deadline, how proposals will be scored, what speakers receive and when they will hear back. Fill each of these in before you publish.
- Event. Name, date, venue, expected delegates, and who they are: roles, seniority, what they already know. Your conference theme goes here as one sentence, plus three to five topics you want and one you do not.
- Session types and lengths. Mercian 26, a UK library conference, listed its formats as 15-minute table discussions, 20-minute presentations and 60-minute workshops, with the time being the total.
- What to send. A title, a description, what a delegate will be able to do afterwards, format and length, a short biography, a link to something they have given before, and access needs.
- The deadline. Date, time and time zone, then the date decisions go out and the date the programme is published.
- How you choose. The criteria, who reads the proposals, and what you will decline.
- What speakers get. Tickets, travel, a fee or nothing, and whether the session is recorded.
- Their data. The ICO says to tell people why you use their details, your lawful basis and how long you will keep them. The page was under review in November 2026.
- A named contact. One person, with an email address.
PyCon US 2026 asks for the audience level, what attendees will know afterwards, and a timed outline. It also asks applicants to say how they would cut a 45-minute talk to 30. Copy that last one. It saves you a second round of emails.
When should a call for speakers open and close?
A call for speakers should open about five months before the event and stay open for four to six weeks. Sched recommends five to seven months out, with a window of four to six weeks. Sessionize says organisers on its platform open on average 156 days ahead and keep the call open for 59 days.
A real timeline shows the gaps. This is the UKOUG DISCOVER 2026 call, read in November 2026, with my arithmetic against the event date of 23 November.
| Stage | Date in 2026 | Gap |
|---|---|---|
| Call opens | 22 June | 154 days before the event |
| Call closes | 2 August | 41 days open |
| Speakers notified | 21 August | 19 days after closing |
| Programme published | 2 September | 12 days after notification |
Mercian’s call, for a conference on 9 September, closed on 8 June, 93 days ahead. It also ran speaker briefing events in May, which lowers the cost of applying for first-timers.
Work back from the speaker brief
The easiest way to set the dates is to start from the day the speaker brief goes out. The brief belongs six to eight weeks before the event, so take eight weeks as the latest.
Every figure below is my arithmetic from the ranges above, not a published rule.
- Brief out: 8 weeks before the event.
- Speakers confirmed: 10 weeks before, so notify two weeks earlier, at 12 weeks.
- Review takes two to six weeks, so the call closes 14 to 18 weeks out.
- The window runs four to six weeks, so it opens 18 to 24 weeks out.
Anything tighter than 18 weeks squeezes the review or the window, and the review is the part that suffers.
How should you choose between proposals?
Score every proposal against criteria you wrote before the call opened, with more than one reviewer, and keep a written note of each score. Sessionboard, a vendor, advises writing the criteria first so a decision survives a declined applicant asking why.
KubeCon + CloudNativeCon, whose 2026 North America reviewer guidelines I read in November 2026, scores content, originality, relevance, the speaker, and whether the session is a product pitch. Reviewers must leave a comment on every proposal, and the highest-scored 30% go to track chairs.
Three rules carry over to a small event:
- Hide names in the first round. PyCon does not show author details to reviewers in its first round.
- Decline the sales pitch in writing. Sched lists self-promotion, vague proposals and repeated topics as the usual mistakes.
- Balance the day, not just the scores. Three top-scoring talks on the same subject make a flat afternoon. I have watched the energy in a room dip after lunch, around 1:30pm, and a heavy session there needs a lighter one beside it.
Check the shortlist against your agenda template before you accept anyone.
What should a call for speakers include about fees and tickets?
A call for speakers should say exactly what an accepted speaker receives, including when that is nothing. The Women in Publishing Summit offers a small honorarium and a free ticket, and tells anyone seeking a large fee to look elsewhere. UKOUG gives up to two complimentary tickets where a customer speaks, and other speakers buy standard tickets.
State travel, accommodation, a speaker dinner and recording terms in the same place. Sessionize lists these as incentives that help speakers who could not otherwise attend. PyCon offers travel grants to people who need them. A plain “no fee, but a ticket” is easier to accept than a surprise in the contract.
The reply that closes the loop
Every applicant should hear from you, on a date you gave them in the call. Sched suggests templates for confirmation and rejection, and a window of 1 to 2 weeks for accepted speakers to confirm.
- Accepted. The session title as you will print it, the slot length, the date to confirm by, and when the speaker brief follows. Ask for a reply, so silence is not an answer.
- Reserve. Say they are a reserve, until when, and what happens if a slot opens.
- Declined. Say it early, give one reason from your criteria, and thank them. The KubeCon guidance asks for constructive notes because applicants range from a vice president to a student.
Do not announce the programme before the reserves know where they stand. Retitle weak submissions as part of the same pass, using the advice on session titles.
When is it worth hiring a conference host for this?
Running the call is a desk job, and you can do it yourself with a form, a spreadsheet and two reviewers. I add nothing to the scoring, and I would not pretend otherwise.
The point where it helps is the programme you build from the shortlist. I read the agenda for the energy curve: the cold 9am open, the slump after lunch and the awkward gap before networking. I can tell you which sessions to move, where a short opener belongs and how to link two speakers who disagree. I can also use RoomReader, my live Q&A software, so questions come from every delegate and not the three people at the front.
Before you get in touch, have to hand the accepted sessions with their lengths, the date, the room size and the running order as it stands. If you want one person to read the programme and run the day, send me the agenda or check availability at hello@conferencehost.uk or on 07596 851647. I am a conference host and I am happy to start from a rough list.
17:00Close
Send me your agenda. I’ll show you where the room comes alive.
A fixed price, a free planning call, and a reply within one working day.


