Speaker Application Form Template

A call-for-proposals form that collects program-ready assets — attendee-facing abstract, format, level, bio, and headshot — in one submission.

Free · copies into your editor in one click
Live preview — try it, nothing is saved

Our call for proposals is open. Write your abstract for the people who will sit in the room — if we accept your talk, that text goes straight into the program.

Exactly as it should appear in the program.

150–200 words, written for attendees: what they will learn and why it matters to them.

Third person, around 75 words — this also goes in the program as written.

Optional now, required if accepted — square crops work best.

Every conference organizer knows the post-acceptance scramble: chasing speakers for bios, headshots, and a usable description weeks after saying yes. This call-for-proposals form ends the scramble by collecting program-ready assets at submission time — and its central trick improves the talks themselves.

Why these fields. The abstract instruction is the trick: "written for attendees — if accepted, this text goes straight into the program." That single sentence transforms submissions. Speakers stop writing to impress reviewers ("a deep exploration of the paradigm...") and start writing to attract an audience, which is precisely the skill that predicts a good talk. The length cap keeps every proposal readable in one sitting. Format and audience level are program-construction data — a schedule is a portfolio, and committees need to balance keynotes against lightning talks and beginner sessions against advanced ones, not just pick ten favorites. The given-before question de-risks honestly: new talks aren't penalized, but a committee pairing a brand-new talk with a big room can plan a rehearsal — while "many times" plus a recording link is a known quantity. Bio and headshot arrive with the proposal because collecting them now, when speakers are motivated, costs nothing — and collecting them later costs three emails each.

What we left out. Travel, dietary, and AV logistics — that's an accepted-speakers form, and mixing it into the CFP presumes acceptance awkwardly. Full slide decks — talks evolve until the week before; a past recording says more anyway. Speaker fees — discuss directly where relevant; a form field flattens a nuanced conversation.

Who uses this. Conference program committees running annual CFPs, meetup organizers filling quarterly calendars, companies collecting internal tech-talk and all-hands proposals, and university series inviting outside lecturers.

Make it yours. Set the CFP deadline as a close date — the fairest CFPs close at a public timestamp, no exceptions, and the closed message can name the announcement date. For review, export proposals as CSV; many committees read abstracts blind on the first pass (ignore the name and bio columns) and rank before revealing who wrote what — the columns make that trivially easy. If your event has tracks, add a dropdown and use the Logic panel for track-specific questions.

Program quality begins here. The abstract-for-attendees framing means that by the time your committee meets, half the program copy is already written and every proposal has been forced through one audience-first rewrite. That's a better program before a single vote is cast.

Frequently asked questions

Why collect bios and headshots at proposal time?

Because chasing accepted speakers for assets is every organizer’s least favorite month. Collected now, the program page can go live the day decisions are announced.

How do committees review blind?

Export proposals as CSV and hide the name and bio columns on the first reading pass. Rank abstracts on merit, then reveal identities for the final balance check.

When does the CFP close?

Set a close date in Settings and the form shuts itself at that moment. Public, uniform deadlines protect the committee from a week of "just one more day" emails.

Can we accept proposals for multiple tracks?

Add a track dropdown and, if tracks need different questions, logic rules per track. The CSV export then splits cleanly by track for parallel review.