Speaker Program Description: What Planners Want + Examples

The reason most people never get booked isn't the pitching. It's the nothing to send.

October 04, 2026

Somebody asks you, "So what do you speak about?"

And you've got... a vibe. A topic. "Leadership, mostly. And culture. Kind of resilience too."

That's the moment a lot of speaking careers stall out, and it's not because you aren't good at what you do. It's because there's nothing to send. I call it the nothing to send, and it costs people more bookings than bad pitching ever will.

The thing you send is called a program description. After 400+ keynotes for companies like Google, Amazon, Visa and McDonald's, I can tell you it's the most underrated document in speaking.

What is a speaker program description? It's the written description of your keynote or workshop that event planners, bureaus and conference committees read to decide whether to book you. A good one answers four questions a planner asks in about a minute: Is this for my people? What will they walk away with? Why this speaker? Can I paste it straight into my event materials? Most speakers keep a long version and a 150 word version.

Who actually reads your program description?

An event planner with 40 speaker options and a meeting in an hour. A conference committee skimming a stack of submissions. The person at an association who has to forward you to their boss with a one line note.

None of them are going to watch your reel first. They're going to read this, and then copy it into the event page, the email to attendees and the internal approval request. If it's vague, you're out. If it's clear, you're in the next round.

What do event planners look for in a program description?

Proof that their people will walk away with something specific. In Talent Bureau's 2025 national event survey of 250 professionals, 57% said a clear outline of learning outcomes was what they relied on most when deciding whether to attend a session. Fewer than a quarter cared about a speaker's social following or media appearances. (CSAE)

So the planner is really reading for four things.

Is this for my people? They want to see their audience in the first few lines. Job titles, situations, the problem those people are living with. Not "anyone who wants to grow."
What will they walk away with? Outcomes, not features. And named ideas read like something worth paying for. "Learn to communicate better" reads like a blog post.
Why this speaker? The credentials that matter to this room, plus the lived experience behind the talk. Not your whole résumé.
Can I paste it? Third person, clean, ready to drop into their materials without a rewrite.

What does a strong program description sound like?

Here's the opening of the sample we use inside Build Your Keynote. Maya Torres is a fictional speaker, but read it the way a planner would.

THE RECALIBRATION
Why Your Greatest Asset Is the Career Crisis You Have Been Avoiding

Every organization has them. High performers who have quietly stopped performing. Not because they lost their edge, but because they are running on a version of themselves that expired two roles ago. The meetings feel heavier. The wins feel emptier. And the question they will not ask out loud is: "Is this still what I want?"

Look at what's not in there. Maya's name. Her title. Her years of experience. That first paragraph is entirely about the planner's people, and by the time Maya shows up, the planner is already nodding. That's the move most people miss, because most people start with themselves.

The rest of the sample, who it's for, why Maya, the named takeaways and the 150 word version, is built with the same discipline. The full thing, both lengths, lives inside Build Your Keynote.

What should a program description title look like?

Short and ownable, with a subtitle that makes the promise plain. "The Recalibration" on its own is a mystery. With the subtitle under it, a planner knows exactly what they're buying. If another speaker in your field could use your title without changing a word, it's a topic, not a title.

What's the difference between a weak and a strong program description?

Usually it's one shift: from describing a job to describing a problem. Picture a bookkeeper who wants to speak to small business owners. (She's hypothetical.)

Same person. Same expertise. The first one describes a job. The second one describes a problem a planner's audience actually has, and a person who's obviously solved it. Only one of those gets forwarded.

How do you know if your program description is working?

Read yours and answer these honestly.

Is your first sentence about the audience, or about you?
Could another speaker in your field use your title without changing a word?
Can a planner tell who it's for in one line?
Are your takeaways named ideas, or verbs like "learn," "discover" and "explore"?
Could a planner paste it into their materials as is?

If two or more of those went the wrong way, the problem usually isn't the writing. It's what's underneath it.

Why do most program descriptions sound the same?

Because people write them before they know what their talk is actually about.

They write "resilience" because they haven't found the root under it yet. Then they polish the sentences, and they end up with a nicely written description of a talk that could belong to anybody. You can't read the label from inside the jar.

This is also where ChatGPT lets people down. Hand it a topic and ask for a program description and it'll give you exactly that: polished, organized and generic.

"AI is great at organizing what you give it. It's terrible at noticing what you left out."

Antonio Neves

The good stuff is almost always in what you left out, because it felt too obvious to mention.

Should a program description be in first or third person?

Third person. Planners paste it straight into their materials, so write it the way they'd introduce you to their own audience. Your website can have a first person version if you want one, but the one you send should be third.

Where will you use your program description?

Your website speaking page. The one page you send when someone asks what you speak about. Conference applications and calls for proposals. Directory listings. And the emails you send to the people who already know you when you start telling them you do this now. I walk through that part in how to become a paid keynote speaker. And if the talk behind the description doesn't exist yet, start with the three act keynote speech outline.

Build yours from your own words

Build Your Keynote is an app built on the process behind my 400+ keynotes. Eight sections, asked one at a time. You answer in your own words, and when an answer is thin, it asks about the specific thing you said instead of moving you along, the same way I would in a 1:1. Out of that come your core insights, your program description in both lengths, and a three act keynote outline.

To be clear, it doesn't invent a talk for you. Every word starts as something you said, which is exactly why it won't sound like everybody else's. The first section is free. No card.

Already sure? Get the full process.

FAQ

What is a speaker program description?

The written description of your keynote or workshop that event planners, bureaus and conference committees use to decide whether to book you.

How long should a keynote description be?

Have two versions. A full one of 500 to 750 words for your website and serious inquiries, and a 150 word version for emails, forms and listings.

What's the difference between an abstract, a program description and a one sheet?

An abstract is a short summary, usually for a call for proposals. A program description is the fuller description of your talk. A one sheet is one page that combines your short description, bio, photo, takeaways and contact info.

Should a program description be in first or third person?

Third person, so a planner can paste it directly into event materials.

Can ChatGPT write my program description?

It can polish one. It can't figure out what your talk is actually about. Hand it a topic and you'll get a well organized, generic description. The thinking has to come first.

Antonio Neves has delivered 400+ keynotes for organizations including Google, Amazon, Visa and McDonald's. He's a former journalist with NBC, PBS and Nickelodeon, a Columbia Journalism School graduate, and the creator of Build Your Keynote.