How to Write a Speaker Proposal That Review Committees Say Yes To

A strong speaker proposal does three jobs in a few hundred words: it shows the selection committee that your session fits their audience, it promises specific outcomes, and it proves you are the right person to deliver them. If you get those three things onto the page clearly, you are already ahead of a large share of the submissions in the pile.

This guide walks you through how to write a speaker proposal from the first read of the call to the final proofread. You will get a fill-in conference proposal template, a worked speaker abstract example with three learning objectives, and a checklist to run before you hit submit.

What reviewers are actually scoring

Most selection committees are volunteers or program staff reading dozens or hundreds of submissions on a deadline. Many use a simple rubric. The wording varies, but the criteria tend to cluster around the same questions:

• Fit: Does this session match the conference theme, tracks, and audience level?
• Value: Will attendees leave with something they can use on Monday morning?
• Clarity: Can a reviewer understand the session in one quick read?
• Credibility: Has the speaker done the thing they are teaching?
• Originality: Does this add a fresh angle to the program, or repeat a session they already have?

Write every section of your proposal with those five questions in view. When a sentence does not help answer one of them, cut it.

Step 1: Read the call for proposals twice

The first read is for the basics: deadline, session formats, length, submission link, and whether the event is paid, unpaid, or covers travel. The second read is for signals. Look for:

• The theme and tracks. Borrow their language where it honestly fits your talk.
• The audience description. Job titles, experience level, and sector tell you which examples to use.
• Stated priorities. Phrases like "practical takeaways," "diverse perspectives," or "case studies preferred" are direct instructions.
• Form fields and limits. Open the actual application form early. Word and character limits shape everything you write.

If you are still hunting for calls worth reading, start with our guide on where to find calls for speakers or browse the open calls for speakers directory.

Step 2: Pick one audience problem and one promise

The most common reason proposals get passed over is vagueness. "Leadership in a changing world" could be about anything. Narrow your session to a single problem your audience has and a single promise about what changes for them.

Try completing this sentence before you write the abstract:

[Audience] struggles with [specific problem]. After this session, they will be able to [concrete outcome].

For example: "Mid-level engineering managers struggle to give feedback that changes behavior. After this session, they will be able to run a 15-minute feedback conversation using a repeatable structure." That sentence becomes the spine of your title, abstract, and objectives.

Step 3: Write a specific, searchable title

Your title appears in the program, the app, and the reviewer spreadsheet. It needs to be clear at a glance. Good session titles usually combine a hook with a plain-language description of the content.

• Weak: "The Future of Work"
• Stronger: "The 15-Minute Feedback Conversation: A Repeatable Script for Engineering Managers"

Check the form for a title character limit. Some events cap titles at 60 or 100 characters, and a cut-off title looks careless.

Step 4: Draft the abstract using a simple structure

A reliable abstract structure has four moves:

1. The problem. One or two sentences naming the tension your audience feels.
2. The approach. What you will teach, show, or walk through, and why it works.
3. The format. How the session runs: case study, live demo, workshop exercise, panel discussion.
4. The outcome. What attendees leave with, stated concretely.

Keep sentences short. Use the audience's vocabulary. Include one real detail from your own work, such as a project, a number you can verify, or a before-and-after example, because specifics signal credibility faster than adjectives.

Step 5: Write measurable learning objectives

Learning objectives matter most at education, association, and higher-ed conferences, and many continuing-education credit programs require them. Each objective should start with an observable verb and describe something attendees can do after the session.

Use verbs like	Avoid vague verbs like
Identify, compare, apply, build, evaluate, draft, prioritize	Understand, learn about, appreciate, be aware of, explore

Three objectives is the common default. Make each one distinct: one for recognizing the problem, one for applying the method, and one for a next step or tool they can take home.

A fill-in conference proposal template

Use this template as a starting draft. Replace every bracket, then trim to fit the form's limits.

Session title: [Hook]: [Plain description of what attendees get] for [audience]

Format and length: [Keynote / breakout / workshop / panel], [minutes]

Target audience: [Job roles], [experience level], [sector]

Abstract: [Audience] face [specific problem], which leads to [cost or consequence]. In this [format], [your name] shares [method, framework, or case study] drawn from [your relevant experience]. Attendees will [interactive element: work through, practice, see a live demo of] [specific activity]. They will leave with [concrete takeaway: template, checklist, script, plan].

Learning objectives: By the end of this session, participants will be able to:

1. [Verb] [what] [in what context].
2. [Verb] [what] [using which method].
3. [Verb] [what] [as a next step].

Why this session, why now: [One or two sentences connecting your topic to the conference theme or a current shift in the field.]

Speaker bio (third person): [Name] is a [role] who [relevant accomplishment]. [One line on the experience that qualifies them for this topic.]

For the bio section, our guide on how to write a speaker bio has 50-, 100-, and 150-word examples you can model.

Speaker abstract example with learning objectives

Here is a worked example for a fictional speaker submitting a 45-minute breakout session to a regional higher-education technology conference. The details are illustrative.

Title: Office Hours Nobody Attends: Redesigning Student Support for Online Courses

Format: 45-minute breakout with a hands-on redesign exercise

Audience: Faculty, instructional designers, and program coordinators who support online or hybrid courses

Abstract: Many online instructors hold weekly office hours and watch the video room stay empty, while the same students later report feeling unsupported. The problem is usually in the design of the support, since students often do not know what office hours are for or feel their question is too small to bring. In this session, an instructional designer who has rebuilt support models for several online programs walks through three low-cost changes: renaming and reframing office hours, adding short asynchronous check-ins, and building "question on-ramps" into weekly assignments. Participants will spend 15 minutes redesigning the support plan for one of their own courses using a one-page worksheet, then compare approaches with a partner. Everyone leaves with the worksheet, sample announcement language, and a simple way to track whether the changes increase student contact.

Learning objectives: By the end of this session, participants will be able to:

1. Identify at least two design barriers that keep online students from using office hours in their own courses.
2. Apply three low-cost support strategies to redesign the student support plan for one course.
3. Build a simple tracking method to measure student contact before and after the redesign.

Notice what this example does. The title names a pain the audience recognizes instantly. The abstract states the problem, gives a reason for it, names specific methods, describes the interactive portion with a time estimate, and ends with tangible takeaways. Each objective starts with a measurable verb and maps to a part of the session.

Step 6: Tailor each submission

You can reuse a core talk across many events. What changes is the framing. For each call, adjust:

• The title to echo the theme or track name where it genuinely fits.
• The examples to match the audience's sector. A healthcare audience wants healthcare cases.
• The format description to match the session types they list.
• The "why now" line to connect with the event's stated focus for this year.

Keep a talk library: one master version of each signature talk, plus notes on which variations you have submitted where. That record makes the tenth submission much faster than the first.

Step 7: Answer every field with care

Application forms often include fields beyond the abstract. Common ones include:

• Short summary for the program (often 50 words or 300 characters)
• Audience level dropdown (beginner, intermediate, advanced)
• Previous speaking experience or links to recordings
• Diversity, accessibility, or AV requirements
• Co-presenter details
• Whether you are willing to speak without an honorarium

Treat each field as part of the proposal. A thoughtful 50-word summary often ends up as the public description, so it deserves the same polish as the abstract. For guidance on how Worth the Pitch handles tricky forms, see drafting proposals and what happens when a form cannot be read.

Common mistakes that sink good proposals

Leading with your résumé

Reviewers care about attendee outcomes first. Put your credentials in the bio and keep the abstract focused on the session.

Promising too much

A 45-minute breakout cannot cover "everything you need to know about AI strategy." Narrow scope reads as expertise.

Ignoring the theme

If the conference theme is "Building Resilient Teams," a proposal that never connects to resilience will score low on fit, however good it is.

Missing the deadline by a day

Many calls close at a specific time zone's midnight. Submit at least a day early so a form glitch does not cost you the slot.

Sales pitches

Most conferences reject sessions that read like product demos. Teach the method. Interested attendees will find your offer.

Pre-submission checklist

• Title is specific, under the character limit, and names the audience or outcome.
• Abstract states a problem, an approach, a format, and a concrete takeaway.
• Three learning objectives, each starting with a measurable verb.
• Language mirrors the conference theme where it honestly fits.
• Every required field is answered and within limits.
• Bio is in third person and matches the length requested.
• Headshot meets the requested size and format.
• You saved a copy of everything you submitted, with the date.

After you submit

Record the submission, the decision date, and a follow-up date. If you hear nothing a week or two after the announced decision date, a short, polite check-in is appropriate. When you are accepted, confirm quickly and ask about AV, recording rights, and travel details. When you are declined, ask whether reviewer feedback is available, since some committees share scores.

Worth the Pitch sets a follow-up reminder automatically when you mark a proposal submitted. You can read more in pipeline and follow-ups, and see how acceptances turn into paid work in how to get paid speaking gigs.

Bringing it together

Writing a speaker proposal gets easier with repetition. Read the call closely, commit to one audience problem and one promise, write a clear title, structure your abstract around problem, approach, format, and outcome, and finish with three measurable learning objectives. Then tailor, check every field, and track what you sent.

If you want to spend less time on the mechanics and more time on the talk itself, the speaker proposal generator handles the first draft of every field so you can focus your energy on editing and on finding the next call worth your pitch.