---
name: speaker-management
description: Handles speaker recruiting and speaker management for B2B events, webinars and user conferences. Shortlists speakers from a candidate list, writes invitation emails including asks to customer speakers, builds a speaker tracker with deadlines for bios, headshots, slides, rehearsals and approvals, writes deadline reminders, and produces a speaker briefing pack covering audience, format, AV, timing and do's and don'ts. Use for speaker outreach, inviting customer speakers, chasing speaker deliverables, speaker reminders or speaker kits.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: content-and-speakers
  source: https://eventmarketingsoftware.com/skills/speaker-management
---

# Speaker Management

Runs the speaker side of an event from invite to show day: who to ask, how to ask, what you need from each speaker and by when, the reminders that get it in, and the briefing pack that makes speakers good on stage. It's built for the reality of chasing dozens of people for bios, headshots and slides.

## Intake

If the user has an `event-context.md` file, read it first and don't ask for anything it already answers (company, audience, tone, sender names).

Ask for whatever is missing in ONE message:

1. Event name, format (conference, user conference, webinar series, field event), dates, location or platform, audience (roles, level).
2. What you need help with: recruiting, invites, tracker and reminders, briefing pack, or all of it.
3. Speakers or candidates: a list with name, title, company, type (internal, customer, partner, external expert), session, status, and what's been received. CSV, sheet or paste.
4. Deadlines: confirmation, bio and headshot, session title and abstract final, slides draft, slides final, rehearsal or tech check, legal or brand review, travel booking.
5. What you offer speakers: pass, travel, hotel, honorarium, promotion, recording, coaching. Say "none" if none.
6. Sender for each email type (event lead, account owner for customer speakers, executive sponsor).
7. Session formats and lengths, AV setup, slide template and ratio, recording and release terms.

Work with partial data and use placeholders like `[SLIDES DUE DATE]` instead of inventing.

## Data sources (connectors optional)

- If a Google Sheets connector is available, read the speaker sheet and offer to write the tracker to a new tab. Never overwrite the source.
- If a Slack connector is available, you may draft an internal update listing overdue items by owner. Post only after a clear yes.
- If a HubSpot or Salesforce connector is available, you may read account owners and open opportunities for customer speakers. Don't write to the CRM.
- Otherwise, work from an uploaded CSV or XLSX or a pasted table and return Markdown plus a downloadable CSV tracker.
- Never require a paid service. Don't fetch speakers' websites or profiles.

Sample tracker for testing: [assets/sample-speakers.csv](assets/sample-speakers.csv).

## Method

1. **Recruit (if asked).** Shortlist candidates by fit with the audience, a story or evidence they own, a mix of perspectives (customers, practitioners, partners, internal), and speaking experience where it matters (keynotes). Note gaps the lineup has (no customer, all one region, all vendors). Never infer protected traits from names or photos.
2. **Invite.** Use [references/email-templates.md](references/email-templates.md). Every invite says: why them specifically, the audience, format and length, date and time with time zone, what you'll provide, what you need and by when, and a clear yes or no ask. Customer invites come from or are cc'd to the account owner, lead with what's in it for the customer (visibility, peer recognition, a platform for their team's work, a chance to shape the roadmap), and mention approvals their company may need.
3. **Build the tracker.** One row per speaker per session. Deliverable columns hold `Received`, `Overdue`, `Pending` or `N/A`. Compute overdue from today's date and the deadlines. Add an owner per speaker (who chases).
4. **Set the reminder cadence.** For each deliverable: a heads-up about 7 days before the deadline, a reminder 1 to 2 days before, and an overdue nudge 1 to 2 business days after, then escalate to the owner for a personal call. Don't send reminders for items already received. Group a speaker's open items into one email.
5. **Write reminders.** Short, specific, one action, easy link to upload, the exact spec (bio length, headshot size and format, slide template). Thank them for what's in.
6. **Write the briefing pack** from [references/briefing-pack.md](references/briefing-pack.md): audience, format, timing, AV, slides, rehearsal, day-of logistics, recording and release, promotion, do's and don'ts, contacts.
7. **Status report.** Counts by deliverable (received, pending, overdue), speakers at risk (2 or more overdue items, or no confirmation), and next actions by owner.

Domain rules that matter:
- Ask for bios at a fixed length (e.g. 50 words, third person) and headshots in a fixed spec so they don't all need editing.
- Customer speakers often need internal approval (legal, comms) for logos, numbers and quotes. Build that time into deadlines.
- Lock slide deadlines early enough for a review pass and AV loading; ask the user for their buffer.
- Product pitches from external speakers break trust with the audience; the briefing pack says so plainly.
- Record what each speaker agreed to (recording, release, promotion) in the tracker.

## Output templates

**1. Speaker tracker** (also as CSV):

| Speaker | Company | Type | Session | Owner | Confirmed | Bio | Headshot | Title and abstract | Slides draft | Slides final | Rehearsal | Release signed | Travel | Next action | Next action date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|

**2. Reminder schedule:**

| Date | Speaker | Items | Email | Sender |
|---|---|---|---|---|

**3. Emails** (invite, customer invite, confirmation, reminders, overdue nudge, thank you), each with subject, preview text and body.

**4. Briefing pack** (headings in the reference).

**5. Status report:** counts by deliverable, at-risk speakers, actions by owner.

## Validation checklist

- [ ] Every speaker in the input appears in the tracker exactly once per session.
- [ ] Overdue status is computed against today's date and the stated deadlines.
- [ ] No reminders scheduled for items already received.
- [ ] Each speaker gets at most one reminder email per send date, grouping their open items.
- [ ] Customer invites go from or cc the account owner and mention internal approvals.
- [ ] Every email has one clear action and the exact spec where relevant.
- [ ] No invented perks, deadlines or session details; placeholders are listed.
- [ ] House style: contractions, plain words, no hype, no dashes as punctuation.

## Approval gates

- Return all emails as drafts. Never send email, post to Slack or write to a sheet or CRM without showing the content and getting a clear yes.
- For customer speakers, recommend the account owner approves the invite before it goes.

## Privacy

- Speaker trackers hold personal data (phone numbers, travel details, dietary or accessibility needs). Keep them in the user's tools and share only what each person needs.
- Don't put personal notes (availability reasons, travel) in public agenda exports or Slack channels.
- Publish only the bio, title and headshot each speaker approved.

## Related skills

session-abstract-writer (helping speakers write submissions), cfp-review-scorer (choosing them), agenda-builder (scheduling them), event-social-kit (speaker promo kits), webinar-run-sheet (rehearsal and run sheet for webinars).
