Show
Emcee Script
Write the links, not the speech
An emcee script written as continuous prose gets abandoned ten minutes in. What the host actually needs is a set of blocks they can pick up, say, and put down — because the running order will change, and it will change while they are standing on stage.
The short answer
An emcee script (MC script, host script) is a set of spoken blocks tied to the running order: an opening, an introduction and a handover for each segment, housekeeping, filler, and a close. It is written in spoken language, in blocks that work in any order, because the one certainty is that the schedule will move.
The blocks
| Block | What it does | Length |
|---|---|---|
| Pre-show | Welcome, seats, silence phones, start time | Short, repeatable |
| Opening | Welcome, what today is, why it matters | Keep it brief |
| Housekeeping | Exits, toilets, wifi, breaks, photography, hashtag | Once, early |
| Introduction | One per speaker | Two or three sentences |
| Handover | Thanks the last speaker, sets up the next | One or two lines |
| Q&A management | How to ask, time limits, wrapping up | Short |
| Break and return | Where to go, exact return time | State the time twice |
| Filler | For the gaps. The most useful block | Several options |
| Close | Thanks, next steps, survey, exit | Short |
Point
Write the filler block before anything else. Something will run late, a laptop will not connect, a speaker will be in the corridor. The host standing in silence is what the room remembers. Give them three things they can say for two minutes each.
Note
Introductions are two or three sentences, not a biography. Name, why this person is talking about this subject, and the title of the talk. A full CV read aloud flattens the energy before the speaker has said a word.
Writing for the mouth, not the page
- Short sentences. If the host has to take a breath mid-clause, it is too long
- Write contractions — people say "we're", not "we are"
- Spell out numbers and times as they are spoken
- Mark the words to stress in bold
- Write phonetic spellings for names on the line where they appear
- Never make a joke mandatory. Offer it; let the host decide
- Large type, one block per page, generous margins
- Page numbers, because pages get dropped
Point
Put the phonetic spelling next to the name, every time it appears. Not in an appendix, not in a briefing email. On the line the host is reading. Getting a speaker's name wrong on stage is the one error the whole room notices.
Note
Confirm pronunciation with the person, not with a colleague. Ask at the same time you collect their bio, and write it the way the host would sound it out.
Making the script survive changes
- 01
Number the blocks, do not paginate the show
Blocks can be reordered. A continuous script cannot.
- 02
Keep each block independent
No block should depend on a line from the block before it.
- 03
Mark which blocks can be cut
Decide in advance what goes when you are running late. Not on stage.
- 04
Agree a signal system
Five minutes, wrap up, stretch, stop. Rehearse the signals with the host.
- 05
Name one person who makes the call
The host should look at exactly one person for timing decisions.
- 06
Print it, and have a spare
Tablets dim, lock and run out of battery. Paper does not.
Point
Decide in advance which blocks get cut when you overrun. If nobody has decided, the host cuts the wrong thing — usually the close, which is the only part with the call to action in it.
Note
The host and the technical cue document are not the same thing. The host needs words; the crew needs cues. Keep them as separate documents that refer to the same numbered items (see run of show).
Names, sponsors, and the things that cause complaints
- Every name spelled and sounded out, confirmed with the person
- Job titles and organisation names confirmed — people notice demotions
- Sponsor mentions listed with exact wording and where each one belongs
- How many times each sponsor is mentioned — it is a deliverable; count it
- Any legally required announcement (recording, photography, safety)
- Accessibility announcements — captions, quiet room, step-free routes
- Nothing written that assumes an attendee's background
- An agreed line for a no-show speaker
- An agreed line for an evacuation, written by whoever is responsible for safety
Point
Sponsor mentions are contractual deliverables. If the package promised three on-stage mentions, write three and count them during the show. Nobody will remind you, and the shortfall surfaces at renewal (see sponsorship packages).
Note
Write the evacuation line, and do not improvise it. It should be agreed with whoever is responsible for safety at the venue, and it should be at the front of the script where the host can find it without searching.
Briefing the host
- Send the script with enough time to read it aloud, not the night before
- Walk the room together — where they stand, where the clock is, where the signaller stands
- Test the microphone they will use
- Agree what they may improvise and what is fixed wording
- Tell them who to look at for timing
- Give them the speaker list with photos so they can recognise people
- Tell them what to do if a speaker does not appear
- Water, on stage, where they can reach it
Point
A host who has read the script aloud once performs differently from one who has only read it. Build that into the schedule — it takes twenty minutes and it is the highest-return rehearsal you can run.
Key takeaways
- Write blocks, not continuous prose. The running order will change while the host is on stage.
- Write the filler block first. Silence during a gap is what the room remembers.
- Introductions are two or three sentences, not a biography.
- Put the phonetic spelling on the line where the name appears, every time.
- Decide in advance which blocks get cut when you overrun, or the host will cut the close.
- Count sponsor mentions during the show. They are contractual deliverables.
FAQ
Frequently asked questions
A pre-show block, an opening, housekeeping, one introduction and one handover per segment, Q&A management, break and return announcements, filler, and a close. Write it as independent numbered blocks rather than continuous prose, because the running order will change — often while the host is already on stage.
Two or three sentences: the name, why this person is talking about this subject, and the title of the talk. A full biography read aloud flattens the room's energy before the speaker has said a word. If the speaker's credentials matter, put them in the programme, not in the introduction.
Write for the mouth. Short sentences, contractions, numbers and times spelled as spoken, stressed words in bold, large type, one block per page, and page numbers because pages get dropped. Put phonetic spellings next to each name on the line where it appears — not in an appendix. Getting a speaker's name wrong on stage is the one error the whole room notices.
Follow a decision made in advance. Mark which blocks can be cut before the day, and agree a signal system with one named person who makes timing calls. If nobody has decided, the host cuts the wrong thing — usually the close, which is the only part containing the call to action.
A filler block with several two-minute options for gaps, an agreed line for a speaker who does not appear, and an evacuation announcement written with whoever is responsible for safety at the venue. Keep the evacuation line at the front of the script so the host can find it without searching, and do not leave it to improvisation.