Conference speaker briefing checklist and template

A conference speaker briefing should tell the speaker who is in the room, what their session needs to deliver, how much time they have, and exactly what happens before they walk on stage. Put arrival, preparation deadlines, production details, accessibility arrangements and an emergency contact in the same brief, then ask the speaker to confirm the decisions that affect delivery.

You've booked someone with the right experience. Their title looks good on the event page. Now you need them to give the session your ticket buyers paid for. That's where a proper brief earns its place. "Please send your slides and arrive early" leaves rather a lot to chance.

This checklist covers the work after a speaker is confirmed. We'll go through the content, timing, technical checks and handoffs, then give you a copyable template and a worked example. The timings and deadlines in the example are planning choices for a fictional conference, not industry standards.

Give each speaker one useful brief

The first thing you want to do is separate the speaker's instructions from your team's entire production plan. A speaker needs to know where to report, which file to deliver and what the host will do. They don't need to hunt through catering notes, sponsor furniture orders and every microphone change in the building.

Keep the decisions in one current document. You can send reminders and calendar invitations, but each should point back to that brief. Put a version date, an owner and the session name at the top. If something changes, make the change visible and tell the people whose work it affects.

Your speaker agreement and your briefing do different jobs. The agreement records the booking and accepted terms. The brief explains how to deliver those commitments at this event. Use our speaker agreement template for the booking conversation, then bring the agreed session length, preparation obligations and recording permissions into the practical instructions.

Don't use a briefing email to quietly add another workshop, a promotional video or wider recording rights. If the request changes the booking, resolve it through the agreed change process first. Otherwise your speaker may arrive believing they've accepted one job while the crew is preparing for another.

Assign one person to collect replies and settle questions. That person doesn't have to know every technical answer. They do need to get it from production and return a definite answer to the speaker. Sending someone around five departments is an easy way to leave an important question unresolved.

Check that every pending item has a clear deadline before the next dependent task. If the microphone choice changes, tell the speaker before they rehearse with a different setup at home.

Explain who bought a ticket and why

"Our audience is business professionals" doesn't help a speaker prepare. Tell them what delegates do, how much they already know, and which decision brought them to the conference. An experienced audience may need evidence and tradeoffs. Beginners may need a clear explanation before the example means anything.

Use information you actually have. Ticket categories, registration answers and conversations with buyers can help you describe the room. Keep estimates labelled as estimates. Don't tell a speaker that everyone manages a large budget because a few attendees have impressive job titles. That assumption can make the whole session miss.

Give the session one main outcome in plain words. "Delegates should be able to compare two options for opening a second location" is useful. "Inspire entrepreneurial excellence" isn't. Ask the speaker what they will show, what question they will answer and what delegates should be able to do afterwards.

Tell them what comes before and after their session. If the previous speaker explains the basics, this speaker can start further ahead. If another session covers implementation, agree the boundary. You don't want ticket buyers sitting through the same introduction twice while the practical question never gets answered.

Be direct about sales pitches. Explain whether a company introduction, product demonstration or closing invitation is allowed, and how much room it gets. Sponsored sessions need a clear description too. A sponsor relationship doesn't automatically tell the speaker what attendees have been promised or what the moderator should allow.

If you are still shaping the whole programme, our paid conference planning guide covers the decisions around audience, programme and budget. Here, the job is narrower. Make sure this confirmed session delivers its part of the promise, rather than reopening the whole conference around one person's favourite talk.

Spell out the session clock

Give the speaker separate times for arrival, technical check, waiting backstage, introduction, presentation, questions and leaving the stage. "Your slot is at ten" can mean a dozen different things. State whether that's the moment the host begins speaking or the moment the speaker takes the microphone.

A programme slot is not necessarily speaking time. Introductions, questions, applause and transitions all consume it. If you allocate thirty minutes to the session but expect a two minute introduction and seven minutes of questions, don't also ask for a thirty minute presentation. The arithmetic has to work before rehearsal.

Write the end time as well as the duration. A speaker who starts late should know whether they still get their full talk or must finish at the original deadline. Decide that policy with production. Don't leave a moderator to negotiate it in front of an audience waiting for lunch.

Agree the timing signals. Say who gives them, where they appear and what each means. A visible five minute warning only helps if the speaker understands whether five minutes remain in the talk or in the whole session. Rehearse the final signal and the moderator's closing intervention.

Ask for a shorter version before event day. The speaker can identify an optional example or discussion that can go while preserving the main lesson. Give them the minimum useful delivery time and agree who can activate that version. Rushing every sentence usually damages the session more than removing one planned section.

Keep the speaker's timing consistent with the crew schedule. Our event run of show template covers cues, owners and recovery decisions across the event. Your briefing should contain the speaker's part of that plan, including the handover to the next session and who decides when it changes.

Review the outline against the ticket promise

Before approving the content, read the session description on the event page beside the speaker's outline. Does the talk answer the question you advertised? If buyers expect a practical comparison, check that the speaker shows the criteria and a decision. A long personal introduction followed by general encouragement won't fulfil that promise, however confident the delivery. Give feedback while there is still time to change the structure. Tell the speaker which part already works, where the promised answer is missing and what you'd like them to add or cut.

Ask about the evidence behind examples. A speaker can describe their own experience without presenting it as a universal result. If they make broader claims, ask for the original source and enough context for delegates to judge it. Check whether any client names, screenshots or figures need permission before appearing publicly. Keep that review proportionate to the session. You're checking that the audience receives a useful, credible answer; you don't need to turn every practical talk into an academic paper. The moderator should also know where an example has a limitation worth exploring during questions.

Set deadlines that leave time to fix things

Start with the dates your production team actually needs, then work backwards. The final deck deadline should leave time to open the file, test media, check accessibility and correct problems. Receiving it moments before the session starts gives you a file, but it doesn't give you a reliable presentation.

Ask for the approved title, short description, biography, name pronunciation and any resources delegates need. Collect the session outline before the finished slides when content direction is still open. It's much easier to redirect a talk about the wrong problem before someone has built a polished deck around it.

Specify the submission route and file naming. Tell the speaker which formats production accepts and how to deliver linked media or supporting files. Ask them to identify anything requiring internet access, special software or their own device. Your technician shouldn't discover a live demonstration when the first slide appears.

Treat the final deadline as a controlled handover. Production confirms that it received and tested the approved version. A replacement file needs an explicit acknowledgement, not a hopeful message in a different chat. Record which version will play so the speaker and slide operator don't rehearse different decks.

Build a reminder around the missing decision, not around sending more email. "We still need to confirm whether your demonstration requires venue internet" is easier to act on than "Just checking in." If the deadline passes, tell the speaker what production can still support and ask for the simplest workable alternative.

Brief production on the actual presentation

Confirm who supplies the laptop, who advances slides and what the speaker can see on stage. A confidence monitor is a screen facing the speaker that shows their slides or notes. If you don't have one, say so early. Someone relying on detailed notes needs a different preparation plan.

Check the microphone arrangement with the speaker and technician. A handheld microphone occupies a hand. A clip microphone needs somewhere suitable to attach it. A seated conversation may require different positions from a standing talk. Ask what the speaker needs to deliver comfortably, then confirm what the venue can provide.

For video, request the actual file and test it through the event's playback system. Microsoft explains the differences between embedded and linked files in its PowerPoint video guidance. Linked files can break; testing the full presentation on the machine that will run it is still necessary.

Tell the technician which slide starts a video, whether it includes sound and what the speaker will say before playback. Agree a fallback sentence if it fails. The audience doesn't need to watch several people troubleshoot a laptop while the session clock keeps running.

For a live demonstration, identify every dependency. That might include a login, a specific browser, access to a website and a stable connection. Ask for a prepared alternative that teaches the same point if the demonstration fails. Test using the event setup rather than assuming a successful office rehearsal settles it.

Do not promise a technician can recreate a complicated setup without seeing it. Bring unusual requirements into the first production conversation, including instruments, audience voting, multiple presenters or moving between positions. Confirm any extra equipment and labour with the person controlling that budget before you tell the speaker it's arranged.

Make access part of the briefing

Ask speakers privately about access and support requirements early enough to arrange them. Give them a named contact and explain how to raise a new need later. They should not have to disclose personal information to the whole crew just to establish whether they can reach the stage.

The ACM SIGACCESS accessible conference guide covers presenter access, adjustable speaking positions and support during sessions. Check the route to the actual speaking position, not only the venue entrance. Share the practical arrangement with staff who need to deliver it while limiting personal details to those who need them.

Give speakers concrete presentation instructions. W3C's accessible presentations checklist recommends describing relevant visual information, using microphones and providing accessible materials. Translate that into the session plan. Ask the speaker to explain the point of a chart aloud, caption video and supply materials through your agreed route.

Coordinate with captioners and interpreters when they are part of the event. Ask what advance material and terminology they need, who will provide it and when. Give them approved names and session titles. A slide deadline that works for the video technician may still be too late for another person's preparation.

Explain the audience question process. If questions use a roaming microphone, the moderator should wait for it before taking the question. If someone cannot use that route, provide the alternative you've arranged. Speakers should repeat or summarise questions when needed, so the answer makes sense to everyone following the session.

Ask speakers to check that handouts and exercises work beyond the projected screen. A tiny worksheet shown on a slide is a weak substitute for a usable copy. Decide how attendees access the material and how any requested alternative reaches them. Give the speaker instructions your team can actually fulfil.

Rehearse the handoffs, not only the talk

A rehearsal should test the moments where responsibilities change. Can the host pronounce the name? Can the speaker hear the introduction from backstage? Who signals the entrance? Does the microphone work at the speaking position? Does the deck begin on the right slide? Those small details determine whether the opening feels settled.

TED's speaker preparation guide emphasises rehearsal, staying in contact and allowing time to fit microphones. Its format has its own rules; borrow the practical discipline without pretending your conference needs the same talk format or preparation schedule. Rehearsal should fit your event and the speaker's confirmed role.

Run the opening, a representative slide sequence, any media, the timing warning and the close. Then test the transition into questions and off the stage. Ask the speaker to practise the fallback for a failed demonstration. A person who has said that sentence once is less likely to freeze when they need it.

Record unresolved issues with an owner and a deadline. "Sound needs checking" isn't a complete outcome. Identify which input failed, who will fix it and when another test happens. Don't mark a session ready because the speaker attended rehearsal if the part that failed is still unresolved.

Give the moderator their own copy of the relevant brief. They need the approved introduction, session purpose, boundaries, opening question and closing instruction. Agree how they interrupt an overrun or redirect a sales pitch. The speaker should know that intervention is coming before the moderator uses it in public.

Make arrival easy enough to follow under pressure

Send arrival instructions that work for someone who has never visited the venue. Give the entrance name, meeting point and contact number, and explain whether the speaker should bring identification or use a separate registration route. If a car drops them at the public entrance but production expects them at a loading door, fix the instruction before it becomes a phone call during another session. Check that the person meeting them will actually be available at that time. A named contact who is already operating the stage cannot also leave to collect someone outside.

Explain the practical arrangements around waiting and leaving. Where can the speaker keep a bag? Is there drinking water? Can they use a quiet space before the session? What food have you arranged, and when can they get it? Give answers that match the venue and confirmed hospitality, then ask about anything still outstanding. These details help speakers focus, but they also protect the schedule. A speaker wandering off to buy food because nobody explained the arrangement is harder to find when you need to fit a microphone or approve a timing change.

Adjust the brief for panels and remote speakers

A panel needs a shared discussion brief and individual instructions. Agree the question it will answer, the opening format and how the moderator distributes speaking time. Ask panellists for examples they can discuss, rather than demanding identical scripts. The point is a useful conversation, not several short speeches stacked together.

Tell each panellist who else is joining and whether their introduction will happen before or during the discussion. Confirm seating, microphones and how audience questions enter. Give the moderator permission to redirect repetition and bring quieter speakers in. A question list alone doesn't tell anyone how the discussion will run.

For remote speakers, include the joining link privately, the correct timezone, the early connection time and a backup contact route. Decide who shares the slides. Test the speaker's sound and connection, then explain what they should do if the connection drops. The room host needs that same recovery instruction.

W3C's working guidance on accessible remote meetings distinguishes platform capabilities, prepared content and how hosts use the tools. Check all three in your rehearsal. A remote speaker showing a slide doesn't establish that attendees can access its contents, hear questions from the room or follow the captions you've arranged.

If the audience includes remote delegates too, test what they receive during questions and transitions. The speaker may hear the room perfectly while the stream carries only the stage microphone. Put someone on the remote side of rehearsal and ask them to report what they can hear and follow.

A conference speaker briefing template you can copy

Use the following fields as the starting point for your brief. Replace every bracket with a confirmed instruction or mark it as pending with a named owner. Delete sections that don't apply. Send the speaker the finished version, not a worksheet that asks them to guess how your event operates.

Event and responsibility

• Event name, date and location: [confirmed details, including timezone].

• Brief version and owner: [date, name, email and event day phone].

• Session: [approved title, room and format].

• Speaker: [preferred name, role and pronunciation].

• Moderator or host: [name and preparation contact].

• Current booking terms: [reference to the agreed document; approved changes].

Audience and content

• Who is attending: [roles, experience and relevant context based on available information].

• Why this session matters: [the delegate problem it addresses].

• Intended takeaway: [what attendees should understand or be able to do].

• Content boundary: [what this session covers; topics other sessions handle].

• Evidence and examples: [agreed examples; sources or permissions still needed].

• Commercial content: [permitted introduction, demonstration or invitation and any limit].

Preparation and production

• Outline and materials: [specific deliverables, submission route and deadlines].

• Final deck: [formats, file naming, version and replacement approval process].

• Playback: [event laptop or speaker device; slide operator; video and sound cues].

• Speaking position: [microphone, lectern or seating, notes display and entrance route].

• Internet or special equipment: [confirmed provision; dependencies and approved fallback].

• Rehearsal: [time, location or link; who attends; what will be tested].

• Access arrangements: [private contact; confirmed practical support; materials process].

Event day and questions

• Arrival and check in: [time, entrance, contact and meeting point].

• Technical check and waiting location: [time, place and who collects the speaker].

• Session clock: [introduction, talk, questions, close and stage clear times].

• Timing signals: [who gives each warning; what it means; closing intervention].

• Questions: [moderator, microphone or submission route and backup opening question].

• Short version: [approved reduced talk; optional material to omit; decision owner].

• After the session: [exit route, microphone return and any agreed attendee interaction].

Recording and confirmation

• Recording status: [what the agreed booking allows; practical filming instructions].

• Materials for distribution: [approved files, recipient group and delivery owner].

• Restricted content: [practical instruction for any material excluded from recording or sharing].

• Changes and emergencies: [contact, decision route and how a revised brief is confirmed].

• Speaker reply required: [confirm timings, content plan, file requirements and outstanding questions by date].

Keep sensitive contact and access information out of documents shared with delegates. Give each crew member the instructions they need through the event's normal production process. Your speaker can have one concise brief while the organiser maintains the fuller record of decisions behind it.

A worked example with a session that fits

Let's make the timing real. This fictional conference is for independent retailers considering another shop. The session is called "Choosing your second location" and runs on 20 May 2027 in the main room. The public programme allocates 10:00 to 10:35. Every time below is local venue time.

The organiser asks the speaker to compare two possible locations using a worked example and explain the questions delegates should ask before committing. The audience already knows basic budgeting. The previous session covers financing, so this talk won't repeat loan options. The next session is a workshop using the same location comparison.

The organiser's approved plan gives the host 10:00 to 10:02 for the introduction. The speaker presents from 10:02 to 10:24. Questions run from 10:24 to 10:31, followed by a one minute closing summary. The stage clears from 10:32 to 10:35. That's twenty two minutes of presentation inside a thirty five minute slot.

The speaker sends an outline by 29 April, the draft materials by 6 May and the final deck by 13 May. Production tests the deck and confirms acceptance, leaving time for a correction. Any later replacement needs the production lead's acknowledgement before it becomes the playback version.

Rehearsal happens on 19 May at 16:00 in the main room. The host, speaker, moderator and technician run the opening, sample slides, warnings, questions and exit. The speaker uses the event laptop and advances slides with the tested remote. A prepared slide sequence replaces the planned demonstration if internet access fails.

On event day, the speaker reports to the agreed entrance at 08:45. The liaison meets them for the technical check at 09:00, then confirms where they can wait. At 09:45 they return to the waiting point. The technician fits the microphone and the stage manager gives the entrance cue after the introduction.

The five minute warning appears at 10:19, with a final one minute warning at 10:23. Both refer to presentation time. At 10:24 the moderator takes over for questions. If there are none immediately, the moderator asks which location assumption the audience should test first, using the question agreed in rehearsal.

Suppose an earlier session means this presentation can only begin at 10:06. The production lead keeps the original end time and activates the approved eighteen minute version. The speaker omits an optional four minute example, finishing at 10:24. Questions and the stage clearance stay as planned. Nobody has to invent the cut on stage.

The organiser records the change, tells the host and technician, and checks the speaker has understood it. If the delay becomes larger, this particular recovery plan no longer fits. The production lead needs a new decision based on the programme and attendee commitments, rather than demanding an ever faster version of the talk.

Keep last minute changes controlled

Speakers sometimes discover an error after submitting the final deck. Let them flag it, but distinguish a factual correction from a new presentation. Ask what changes, why it matters and whether it affects timing, media or approved distribution. Production can then test the actual replacement instead of guessing from its filename.

If a speaker becomes unavailable, follow the booking's change process and the organiser's contingency plan. A replacement speaker needs a new briefing and a tested delivery plan. Don't assume they can use someone else's slides or agree to the same recording arrangements. Tell delegates about material programme changes through the appropriate event communication.

Keep recording instructions aligned with the permission already agreed. A crew note should explain what to capture and what must be excluded. If a speaker introduces restricted material late, settle the permitted handling before it appears. The production lead and editor need the same instruction, including any restriction on distributing slides.

When the brief is ready, ask for a reply that confirms the decisions rather than simply asking whether the speaker received it. They should acknowledge the presentation length, arrival time, production arrangement and any unresolved requirement. If their assistant manages travel but the speaker controls content, route those questions to the right person. An assistant confirming the hotel doesn't establish that the speaker has accepted a shorter talk. Record the reply where the session owner can find it and follow up on anything left open.

After the session, record what actually happened. Was the approved deck used? Were promised resources delivered? Did a particular handoff fail? Use those answers to improve your next brief. Keep the review specific enough to change a working instruction rather than writing that communication should be better next time.

If delegates are promised a worksheet or recording, confirm who sends it and which version is approved. The speaker may supply the file, but the organiser still needs to check the promised delivery happens. Put that task beside the session follow up, with a recipient group and an owner. Otherwise a useful takeaway can disappear once everyone leaves the venue.

A good conference speaker briefing makes the next action obvious. Your speaker should know what to prepare and when to arrive, while the crew and moderator have the instructions to run the session and finish on time. Confirm those decisions before event day, rehearse the awkward moments, and give the session a fair chance to deliver what your ticket buyers came for.