30 Prompts for Speaker Bios and Session Intros

Nineteen of the 48 speaker bios sent to Axis Robotics Summit arrived copied from a 2019 conference page, complete with a job title the speaker had already left. With 22 sessions and a printed programme going to press in nine days, there is no time to chase each one by hand. The 30 prompts below take a speaker from a messy intake form to a 25-word listing, a 60-word programme entry and a 120-word stage intro. Work in that order. For formatting rules that keep 48 records consistent, see our structure and output format guide.

Collect Facts Before You Write a Word

Ask every speaker for the same eleven fields, in the same order, in one form. Anything you cannot source goes in a “to confirm” column rather than into the draft. The most common failure at this summit is not bad writing; it is a confident sentence built on a title from three years ago. Two sessions run in parallel at all times, so a bio that arrives late still has to match the printed programme.

The Prompt Set, From Intake to Intro

Pass 1: Intake and Raw Material

  1. Turns a rambling email into the eleven fields you actually need.
    Extract speaker facts from this email into 11 fields: full name, current title, organisation, city, topic, one result with a number, previous role, published work, languages, accessibility needs, preferred name. Leave a field blank rather than guessing.
  2. Builds the intake form question set so late speakers send usable material.
    Write 11 intake questions for a robotics conference speaker, ordered from easy to specific. Each question must be answerable in one line. Add a note on which three fields speakers most often get wrong, and why.
  3. Pulls the one quantified result out of a long career summary.
    Read this career summary and find every claim with a number. Keep the three strongest, flag the ones without a source, and rewrite each kept claim as a single sentence a programme editor could print.
  4. Normalises job titles that arrive in five different formats.
    Normalise these 12 job titles to one style: title case, no internal acronyms, seniority word first, department last. Show original and normalised side by side in plain text, and flag any title that is ambiguous without a department.
  5. Checks a bio claim against the speaker’s own public profile.
    Compare the claim "led the largest warehouse robotics deployment in Europe" with the profile text I paste. Say whether the profile supports it, partly supports it, or contradicts it. If it is unsupported, suggest a defensible rewrite at the same length.
  6. Writes the pronunciation and credit lines before the intro is recorded.
    From this name and affiliation, produce a pronunciation line in plain syllables, a preferred short form for the stage, a one-line affiliation credit, and a note on any honorific the speaker uses. Flag anything I must confirm with the speaker.

Pass 2: Three Bio Lengths

  1. Writes the 25-word listing that fits a grid cell.
    Write a 25-word speaker listing for the programme grid: name, role, organisation, and the one thing they will talk about. No adjectives about the person. Count the words and show the count.
  2. Writes the 60-word programme entry with one concrete result.
    Write a 60-word bio for the programme: current role, one quantified result, and the session topic. Third person, no "passionate", no "thought leader", no list of three adjectives. One sentence may be long, the rest short.
  3. Writes the 120-word version for the website, with a clear ending.
    Expand this 60-word bio to 120 words for the session page. Add the speaker's relevant prior work and one line on who in the audience should attend. End on the session, not on the person's hobby. Keep every existing fact unchanged.
  4. Produces a first-person variant for the session page without changing the facts.
    Rewrite this third-person bio in first person for a speaker who prefers it. Keep all facts, drop all hype, and keep it under 70 words. Do not add opinions the speaker has not expressed in the source text.
  5. Strips the phrases that make every conference bio sound the same.
    Find cliches in this bio: passionate, thought leader, seasoned, visionary, at the forefront, unique perspective. Replace each with a fact or delete it. Show a before-and-after word count and keep the meaning intact.
  6. Rebuilds a stale bio from a session abstract and a recent talk transcript.
    Using only this abstract and transcript, write a 60-word bio. No claims about reputation, only what the person built, measured or published. If the source does not support a claim, leave it out and list what I should ask the speaker.

Pass 3: Intros That Read Aloud

  1. Writes a 60-second stage intro timed for a slow read.
    Write a 60-second stage intro, about 130 words, for a speaker on warehouse robotics. Open with the session problem, give two credentials, then the talk title. Short sentences, no subordinate clauses longer than 12 words, no jokes.
  2. Cuts an intro that runs long without losing the credential.
    This intro runs 95 seconds. Cut it to 60 without removing the speaker's name, role, or the talk title. Show what you removed and why. Keep the opening problem sentence intact.
  3. Adds stage directions a host can follow while reading.
    Add stage directions to this intro in square brackets: when to wait for applause, when to indicate the screen, when to hand over. Maximum four directions. Write them as actions, not as notes to self.
  4. Writes the intro for a panel rather than a single talk.
    Write a 90-word panel intro for four speakers on robot safety standards. Introduce the topic first, then each panelist in eight words or fewer, then the moderator. Do not read their full bios aloud.
  5. Prepares a swap script for a speaker who cancels on the day.
    Write two versions of the same 60-second intro: one assuming the speaker appears, one assuming a replacement with a different employer. Keep the session framing identical so the host can switch without rewriting. Mark the two variable lines.
  6. Rewrites an intro written for the page so it works in the ear.
    Turn this written bio into spoken intro copy. Break any sentence over 18 words, spell out numbers under twenty, replace semicolons with full stops, and remove parenthetical asides. Keep it under 130 words.

Pass 4: Moderator Questions

  1. Writes an opening question that cannot be answered with a company pitch.
    Write one opening question for a robotics panel that cannot be answered with a product pitch. It must ask for a specific decision the speaker made in the last 12 months and the trade-off behind it. Under 25 words.
  2. Builds a question ladder from safe to uncomfortable.
    Build six moderator questions on automation and warehouse jobs, ordered from factual to uncomfortable. Each must be answerable in 90 seconds. Add the follow-up you would use if the panelist dodges.
  3. Writes a question that puts two panelists in productive disagreement.
    Two panelists disagree on whether safety standards slow deployment. Write the question that surfaces the disagreement without ambushing either one, plus a follow-up that asks each to name the evidence behind their position.
  4. Prepares the audience question that always comes up, with a good answer.
    List the four questions this audience will ask in Q and A, based on the session topic and the room mix. For each, write a 30-word moderator prompt that redirects it to the right panelist.
  5. Balances a panel where one speaker dominates.
    Write three moderation moves for a panel where one speaker takes 60 percent of the airtime: a redirect phrase, a direct invitation by name, and a closing round. Keep each under 20 words and neutral in tone.
  6. Writes the closing question that lands the session.
    Write a final question for the panel that asks each speaker for one thing the audience should do in the next 30 days. It must produce a concrete answer, not a summary. Add a 20-word closing line for the moderator.

Pass 5: Consistency and Final Checks

  1. Checks 48 bios for the same six errors.
    Review these bios for six errors: title mismatch, organisation renamed, unexplained acronym, missing result, inconsistent date format, and a claim that duplicates another speaker's. Output a list of name plus issue, nothing else.
  2. Fits a bio into the printed programme’s character limit.
    Cut this 60-word bio to 240 characters including spaces without losing the role, the organisation or the session topic. Show the count and list what was dropped. If it cannot fit, say which fact should move to the app.
  3. Checks that the bio, the abstract and the session title agree.
    Compare the bio, abstract and session title for this speaker. Flag any mismatch in seniority, topic scope or claimed outcome. State which document should change, not just that they differ.
  4. Runs a sensitivity pass on claims about employers and clients.
    Review this bio for claims that need employer permission: client names, deployment figures, security work. Mark each as safe, needs permission, or remove. Give a replacement sentence for anything marked remove.
  5. Versions every bio so the printed programme and the app cannot diverge.
    Design a version log for 48 speaker bios with fields for length, channel, last edit, approver and approval date. Add the rule for which version wins when the app and the printed programme disagree.
  6. Runs the final read-aloud pass across all 22 session intros.
    Check these intros for repeated opening words, names that appear twice, and titles that are read out in full. List the fixes, then rewrite the three weakest openings so each starts differently.

One Voice Across 48 Bios

Decide the house style once: third person, present tense, current role first, one number per bio, no exclamation marks. Put that in a two-line note at the top of the shared document so a late contributor cannot invent a different one. The stage intro is the exception; it may use the second person and should sound like speech. Read every intro out loud before it goes in the run of show, and cut anything you stumble over.

Bonus: Small Moves That Save the Day

Ask for the preferred name, not the legal one. Half the pronunciation problems at a 48-speaker event start there. Record the speaker saying their own name. A ten-second voice note beats any phonetic spelling you invent. Keep a swap paragraph ready. Sessions move; a host reading a stale intro on stage is the one error the audience always notices. Run the self-critique pass on the 120-word bios only. The short ones have no room for a second opinion, and our self-critique prompt is a fast way to catch a claim the speaker cannot defend.

Sources & Notes

Axis Robotics Summit, its 48 speakers and 22 sessions are fictional examples. Real events should confirm every bio, title and claim with the speaker in writing before print, and keep that approval on file. Pronunciations vary by person and by language, so never rely on a generated phonetic spelling alone. Avoid publishing accessibility needs or personal contact details collected during intake; those fields belong in the operations file, not the programme.

声明:1.本站所有文章,如无特殊说明或标注,均为本站原创发布。本网站中【文本生成/文生图】使用了DeeSseek人工智能生成内容技术, 算法来源说明:本网站未自行开发、训练或部署深度合成算法,所使用的人工智能算法来自:DeepSeek、Chatgpt、Google Gemini。 2.为了网站加载速度优化,本站预览图片进行压缩处理,所以有些不是太清晰,并不影响AI提示词生图、AI设计等内容。3.任何个人或组织,在未征得本站同意时,禁止复制、盗用、采集、发布本站内容到任何网站、书籍等各类媒体平台。如若本站内容侵犯了原著者的合法权益,可联系我们进行处理。--GUUNN.COM