Write a speaker bio for [SPEAKER NAME] for [EVENT OR PLATFORM]. Use only the verified material below. Speaker facts and credentials: [VERIFIED BIO FACTS] Talk title, topic, and audience: [TALK AND AUDIENCE] Platform requirements: [FORMAT REQUIREMENTS] Voice examples or preferred tone: [VOICE NOTES] Required links, pronouns, and disclosures: [REQUIRED DETAILS] Choose the credentials that establish why this speaker is useful to this particular audience, not every role they have held. Open with the speaker’s current role or clearest authority, connect it to the talk’s subject, then add 1 to 2 concrete proof points such as a named organization, published work, relevant result, or prior speaking experience only if supplied. End with a human detail or current focus only when it supports the event’s tone. Do not use inflated labels such as “thought leader,” “visionary,” “renowned,” or “world-class.” Do not invent audience size, clients, awards, media appearances, degrees, revenue figures, quotations, or endorsements. Keep third person unless the format says otherwise. Avoid a chronological resume and unexplained acronyms. Produce: 1. A primary bio in the specified format. 2. A 50-word short bio. 3. A one-sentence stage introduction. 4. A fact-check list identifying any claim that needs the speaker’s approval. Before answering, verify that every credential is supported by my material and that the opening makes the speaker’s relevance to this audience clear. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [SPEAKER NAME] | Enter the speaker’s full published name. | Maya Chen |
| [EVENT OR PLATFORM] | Enter the event, podcast, conference, website, or program where the bio will appear. | Midwest Product Leaders Conference program |
| [VERIFIED BIO FACTS] | Enter confirmed roles, achievements, publications, experience, and background details. | Director of Product at Fieldnote; previously led onboarding at a 120-person SaaS company; co-hosts a monthly product-ops meetup in Chicago; BA in economics from DePaul University |
| [TALK AND AUDIENCE] | Enter the session topic, title, and the people expected to attend. | Talk: “Making Product Decisions When the Data Is Late”; audience: product managers and product operations leads |
| [FORMAT REQUIREMENTS] | Enter word count, point of view, style guide, and placement requirements. | Third person, 110 words maximum, professional but not formal |
| [VOICE NOTES] | Enter preferred tone or a short approved sample of the speaker’s writing. | Practical, candid, lightly conversational; avoids buzzwords |
| [REQUIRED DETAILS] | Enter required pronouns, links, affiliations, disclosures, and contact details. | Use she/her; include fieldnote.com; no personal contact information |
How to use
- Collect the event’s word limit, viewpoint, and editorial rules before drafting.
- Paste only credentials you can substantiate with a current résumé, site, or speaker-approved notes.
- Check that the first two sentences explain relevance to the actual session, not just seniority.
- Follow up with: “Rewrite the primary bio for an emcee to read aloud in 25 seconds.”
Variations
Podcast guest
Use this for an episode description or host introduction.
Write a podcast guest bio for [GUEST NAME] for an episode about [EPISODE TOPIC]. Use [VERIFIED FACTS], [AUDIENCE], and [HOST STYLE]. Produce a 75-word show-notes bio and a 35-word host introduction. Prioritize credentials that explain the guest’s perspective on this episode. Keep claims attributable and conversational; do not invent expertise, client names, numbers, or personal backstory. Check that the introduction is easy to say aloud and every fact is supplied. Ask up to 3 questions only if inputs are missing.
Conference program
Use this for a tightly constrained conference or workshop listing.
Write a [WORD COUNT]-word third-person conference bio for [SPEAKER] presenting [SESSION TITLE] to [AUDIENCE]. Work only from [VERIFIED CREDENTIALS] and [REQUIRED DETAILS]. Open with current role and directly connect one relevant accomplishment to the session. Use plain job titles, define unavoidable acronyms, and omit unrelated career history. Do not add awards, companies, results, or education not supplied. Return the bio and a list of claims requiring confirmation. Ask up to 3 questions only if required inputs are absent.
Speaker one-sheet
Use this when an organizer needs a longer booking profile.
Create a speaker one-sheet profile for [SPEAKER] using [VERIFIED BACKGROUND], [TALK TOPICS], [AUDIENCE FIT], and [BOOKING DETAILS]. Include a 150-word bio, three session descriptions of 40 words each, and five approved proof points. Separate verified facts from optional positioning language. Do not manufacture testimonials, press logos, audience counts, or outcomes. Flag all items that need a link or source before distribution. Ask up to 3 clarifying questions only if a required input is missing.
Tips
- Match the bio’s proof points to the session: a relevant implementation result is stronger than an unrelated senior title.
- Write the stage introduction separately because readable-on-paper bios often sound awkward aloud.
- Keep an approved fact sheet for each speaker so organizers do not reuse stale roles, company names, or accomplishments.
- If an organizer asks for superlatives, replace them with evidence such as a role, publication, or specific body of work.
FAQ
How long should a speaker bio be?
Many event programs need 75 to 125 words, while a stage introduction is often 30 to 50 words. Follow the organizer’s limit first.
Should a speaker bio include personal details?
Include them only when they are speaker-approved and reinforce the event’s tone or topic. Professional relevance should carry the bio.
Can AI make a speaker sound more credible?
It can make verified evidence easier to understand. It should not add credentials, audience figures, endorsements, or awards.