Three weeks before a major financial services summit, an event director discovered that the keynote speaker had built their entire talk around a specific AI product the host company had quietly pivoted away from. The speaker had no idea. Nobody had told them. The briefing sent over was a PDF of the event schedule and a note about parking.
That kind of mismatch is avoidable, and briefing an AI speaker properly is the single most valuable thing an event planner can do between signing the contract and showtime.
AI topics move faster than any other subject on the conference circuit right now. A talk that was fresh and accurate in January can feel dated by June. The speaker you booked for their expertise in AI agents may arrive prepared to discuss a landscape that shifted in the weeks before your event. Your job as the planner is to give them enough context to course-correct and personalize.
Here is how to do it right.
Why AI Speakers Need More Prep Than Most
A traditional keynote speaker in, say, leadership or resilience has material they have refined over years. It does not change much between bookings. An AI speaker's core expertise is current events. The subject matter evolves weekly, which means each engagement requires genuine recalibration, not a name swap in the deck.
There are also organizational landmines specific to AI topics. Many companies have internal AI initiatives they cannot discuss publicly, specific vendors they are committed to (or departing from), employee anxieties about automation they do not want stirred up, and regulatory environments they are navigating carefully. A speaker who does not know any of this will walk into the room blind.
In our experience, the briefing call is often where the real engagement begins. The contract handles the fee and the logistics. The briefing handles the quality of what actually happens on stage.
When to Start the Briefing Process
The timeline matters. Here is a practical schedule:
6-8 weeks out: Send the initial briefing document. This gives the speaker time to integrate your context into their content development rather than bolting it on at the last minute. At this stage, focus on audience profile, organizational context, and topic parameters.
3-4 weeks out: Schedule the pre-event call. By now the speaker should have a draft structure. This is when you walk through it together and surface anything that needs adjustment.
1 week out: Send the final logistics brief. Green room location, who greets them on arrival, A/V contact, run-of-show, session time with buffer.
Day of: Confirm the tech setup in person or over text. This is not the time for surprises.
A speaker who receives the briefing document two days before the event will give you a polished version of their standard talk. A speaker who receives it six weeks out will give you something genuinely customized.
The Briefing Document Template
Send this as a Word document or Google Doc with editable sections. Not a PDF. The speaker may want to annotate it.
AI SPEAKER BRIEFING: [EVENT NAME]
Event Basics
- Event name and organizing body
- Date, city, venue name
- Session date, time, and duration (be specific: "45 minutes including 10-minute Q&A")
- Format: keynote, panel, fireside chat, workshop
Audience Profile
- Attendee roles and seniority (e.g., "primarily VPs and Directors of IT, with some C-suite")
- Industry or sector
- Estimated room size
- AI familiarity level: beginner, informed, technical practitioner
- What they came to this conference hoping to get (if you know it)
Organizational Context (For corporate events and private conferences)
- Company name and industry
- Current AI initiatives or products, if speakable
- Any AI tools or vendors currently in use
- Topics or products that are off-limits
- Internal announcements expected around the event date
Conference Context (For multi-speaker events)
- Event theme or tagline
- Speakers appearing before and after this session
- Have other speakers addressed similar AI topics? What was covered?
- Any conference narrative or thread the organizer wants reinforced
Key Messages (Optional but useful)
- Two or three points you want the audience to walk away with
- Any organizational initiatives this talk should support
Technical and Demo Requirements
- Is a live AI demo expected? If so, will there be guaranteed internet access?
- Clicker preference (most speakers have their own)
- Confidence monitor availability
- Will slides be pre-loaded or does the speaker use their own machine?
- On-site A/V contact name and cell number
Audience Sensitivities
- Any known concerns about AI job displacement among this audience?
- Has the organization had recent layoffs? Public AI controversies?
- Are there pending regulatory or legal matters that should shape the framing?
Logistics
- Speaker arrival time (typically 90 minutes before session for tech check)
- Green room or backstage holding area location
- Who will escort the speaker from arrival to stage?
- On-site contact name and mobile number
- Post-event obligations (book signing, executive dinner, photo op)
The Pre-Event Call: What to Actually Cover
The briefing document sets the stage. The call is where you have a real conversation.
Block 45 minutes. Do not squeeze it into 20. A good pre-event call covers:
Opening with context, not logistics. Start with the audience. Describe who will be in that room in human terms. What are they worried about? What do they already know? What do they wish they knew? A speaker who understands the room emotionally, not just demographically, will calibrate their delivery differently.
Walking through the speaker's planned structure. Ask them to talk you through their current draft. Listen for places where their framing might land awkwardly with your specific audience. An approach that works for a startup crowd may need adjustment for a regulated financial institution.
Flagging the landmines explicitly. Do not leave this to the document. Say it out loud: "A significant portion of our audience is anxious about AI replacing their roles, so we'd prefer the talk not open with displacement scenarios." Speakers appreciate the directness. They would rather hear it from you than read it in a post-event survey.
Confirming the demo plan and the backup plan. If there is a live AI demo, have the backup conversation now, not backstage. What does the speaker do if the demo fails? What does the slide deck look like without the live element? The best AI speakers have this figured out before they arrive.
Asking what the speaker needs from you. This question surfaces requests that might otherwise turn into friction on event day. Many experienced speakers have specific preferences about green room setup, pre-talk quiet time, or how they like to be introduced. Ask early.
What Backstage Actually Looks Like (And Why It Matters)
Most event planners have never stood in the green room with a speaker in the 20 minutes before their session. The atmosphere is specific, and understanding it helps you plan the briefing process.
Speakers at mid-to-large conferences are typically escorted from a holding area to the wings about 10 minutes before their session. That final stretch is not the time for new information. A stage manager is counting down. The speaker is in a mental zone. Last-minute updates (the previous session ran long, a specific topic just came up in a panel) can disrupt that state unless delivered cleanly and concisely.
This is why everything important should surface in the briefing document and the pre-event call, not in the green room. The green room conversation should be warm-up, not briefing. If you find yourself needing to give your speaker crucial context backstage, the briefing process did not work.
Crimson Speakers coaches speakers on how to absorb and use briefing documents effectively, which is one reason the bureau model can be worth the cost for complex events. You are not just booking a speaker. You are booking a speaker who has been prepared to receive your context.
Common Briefing Mistakes That Hurt Talks
Sending the briefing too late. A speaker who receives context a week out can personalize their delivery. They cannot meaningfully rebuild their content.
Describing the audience by job title instead of mindset. "500 CMOs" tells a speaker almost nothing. "500 CMOs who are being asked by their boards to show AI ROI within 18 months and are mostly terrified" tells them everything.
Skipping the off-limits conversation. Speakers are professionals. They can handle hearing that specific vendors, topics, or framings are off the table. What they cannot handle is finding out mid-Q&A when an audience member asks why the speaker just praised a competitor.
Forgetting to share what other speakers will say. At a multi-day conference, redundancy is the enemy of the attendee experience. If two speakers each spend 20 minutes explaining what a large language model is, you have wasted audience patience. Share the lineup and the topics so speakers can differentiate.
Not telling them about the room setup. An AI speaker planning an intimate fireside framing will land differently if they walk out to a 3,000-person theater with a single podium at the far end. Room setup shapes everything from pacing to audience interaction.
One Final Principle
Treat the briefing like onboarding, not a formality. The speakers worth booking at the level you are operating have other options. When you give them what they need to do their best work, they deliver accordingly. When you send a parking PDF and call it a briefing, you get a generic version of a talk they have given 40 times.
Crimson Speakers makes the briefing template and the pre-event call part of every engagement because the quality of the briefing directly predicts the quality of the talk. Use the template above, adapt it to your event, and send it early. Your audience will never know the difference, but they will feel it.
Looking for AI speakers who know how to use a briefing? Browse the roster at crimsonspeakers.com and reach out to discuss your event. The bureau is always free to event organizers.