Speaker Bio Template: Short, Medium and Long Versions

Attendees use speaker bios to decide which session to attend, and moderators read them aloud to introduce a speaker. A bio that does both jobs answers three questions quickly: who is this person, what do they actually do, and why should I listen to them on this topic.

Organizers get the opposite: a copied LinkedIn summary in first person, a 600-word CV, or a single line with no organization. A shared speaker bio template fixes that by telling every speaker the same structure and length.

• Name, current role and organization
• The experience that qualifies them for this session, stated specifically
• One or two concrete achievements: projects, programs, publications or results
• A connection to the audience: the sector, region or problem they share with attendees
• Optional: one human detail, such as where they are based or an outside interest
• Optional for long bios: where to find their work

Just as important is what to leave out. A program bio is not a CV, and attendees skim past anything that does not help them decide.

• Full employment history; keep only the roles that explain the session
• Lists of every award, membership or certification
• Self-descriptions such as passionate, visionary or thought leader
• Product names or sales claims, unless the session is sponsored and labeled as such
• Personal contact details; link to a professional profile or website instead

Send all three templates to every confirmed speaker and ask for each length. Writing the short version is hardest, so having the speaker do it avoids your team cutting the long one badly.

[FULL NAME] is [JOB TITLE] at [ORGANIZATION], where [HE / SHE / THEY] [ONE-PHRASE DESCRIPTION OF THE WORK].

[FULL NAME] is [JOB TITLE] at [ORGANIZATION], where [HE / SHE / THEY] leads [AREA OF RESPONSIBILITY]. Over [NUMBER] years in [FIELD], [FIRST NAME] has [MOST RELEVANT ACHIEVEMENT]. [HIS / HER / THEIR] work focuses on [TOPIC CONNECTED TO THE SESSION], and [HE / SHE / THEY] regularly [ADVISES / WRITES / TEACHES] on [SUBJECT].

[FULL NAME] is [JOB TITLE] at [ORGANIZATION], where [HE / SHE / THEY] [DESCRIPTION OF ROLE AND TEAM].

Before joining [ORGANIZATION], [FIRST NAME] [PREVIOUS ROLE OR EXPERIENCE]. [HE / SHE / THEY] [ACHIEVEMENT 1] and [ACHIEVEMENT 2].

[FIRST NAME] [CREDENTIAL, PUBLICATION, BOARD ROLE OR AWARD RELEVANT TO THE AUDIENCE]. [HE / SHE / THEY] [HOLDS DEGREE / CERTIFICATION] from [INSTITUTION].

Based in [CITY], [FIRST NAME] [ONE HUMAN DETAIL]. Find [HIS / HER / THEIR] work at [WEBSITE OR PROFILE].

The examples below describe fictional speakers and organizations. Use them to show presenters the tone and level of detail you expect.

[FICTIONAL EXAMPLE] Jordan Avery is director of member programs at a regional facilities management association, where Jordan runs education for more than [NUMBER] member organizations.

[FICTIONAL EXAMPLE] Sam Okafor is head of operations at [EXAMPLE MANUFACTURING CO.], where Sam leads maintenance planning across three plants. Over 15 years in manufacturing operations, Sam has moved the company's plants from reactive repairs to a planned maintenance program. Sam's work focuses on scheduling and spare-parts planning, and Sam regularly mentors new maintenance supervisors through a regional apprenticeship scheme.

[FICTIONAL EXAMPLE] Riley Chen is chief operating officer of [EXAMPLE HEALTH NETWORK], where Riley oversees facilities, supply chain and patient transport for a network of community hospitals and clinics.

Before joining [EXAMPLE HEALTH NETWORK], Riley spent a decade in hospital construction project management, delivering new wards and outpatient centers while existing services stayed open. Riley led the network's move to a single maintenance and asset system and set up its first shared procurement team.

Riley serves on the facilities committee of a regional healthcare association and writes a monthly column on hospital operations for [EXAMPLE TRADE PUBLICATION]. Riley holds a degree in civil engineering from [EXAMPLE UNIVERSITY].

Based in [CITY], Riley coaches a youth rowing team at weekends. Find Riley's articles at [WEBSITE].

The headshot is often the first thing attendees see on a session page or in the event app. Ask for it at the same time as the bio, with clear guidance, so you are not cropping holiday photos the night before the program goes live.

• A recent photo, head and shoulders, facing the camera
• Plain or softly blurred background, with even light on the face
• High resolution: a square image of at least 800 by 800 pixels works for most sites and apps
• JPG or PNG, with the file named after the speaker, such as firstname-lastname.jpg
• No logos, text, filters or other people in the frame
• Leave space around the head, because many sites and apps crop to a circle

Consistency matters as much as quality. A speaker page where some photos are tight studio portraits and others are wide outdoor shots looks unfinished. Crop every headshot to the same shape and framing before publishing, and keep the originals so you can re-crop for print, slides and social posts. If a speaker sends a group photo or a logo instead, ask again rather than cropping it yourself, and use your placeholder image until the right file arrives.

1. 1

   Ask at Acceptance

   Ask for bios and headshots in the acceptance email, with the deadline written into the speaker agreement. If you ran a call for speakers, you may already have a short bio from the proposal.

2. 2

   Give the Template and Limits

   Send the three templates, the word limits and the headshot guidance together. Tell speakers you will write in third person and may edit for length and consistency.

3. 3

   Use One Collection Point

   Collect everything through one form or profile per speaker, not attachments in email threads. Let speakers update their own profile so late job changes do not depend on your team.

4. 4

   Edit for Consistency

   Read every bio before publishing. Fix person, tense and length, remove sales language, and check names and organizations against the speaker's agreement.

5. 5

   Chase the Gaps

   Track who is missing a bio or photo and send a short reminder each week. Keep a placeholder image ready so a missing photo does not delay the program.

For panels, collect a bio from every panelist and the moderator, using the medium template, and publish them in the order they will sit on stage. With more than a handful of speakers, a speaker management tool that lets speakers edit their own profiles saves most of this chasing.

Once bios and headshots are in, publish them with the sessions they belong to; see how a conference agenda builder connects speakers to the program.