How a Presenter Introduction Gets Written, From Guest Notes to Final Line
A look at the working steps behind a short presenter introduction: what we collect about the guest, how the draft is built, and how it is checked before anyone says it aloud.
It starts with the guest, not the sentence
When a presenter introduction lands on my desk, I resist the urge to write the first line. The first hour goes to reading what the guest has actually said and done: a short biography supplied by the guest, the title of the talk or conversation, and anything the producer has noted about why this person is on the programme at all. Only then do I know what the introduction has to accomplish.
Most weak introductions fail here. They are written from a general idea of the guest and then padded with praise. A good one is built on three or four verified facts that the audience can use to understand why the next ten minutes matter. In our course, learners practise this stage first, using the short demonstration profiles, because everything downstream depends on it.
I keep a single page for each introduction, with the guest's name, the correct pronunciation, the topic and the audience on it. That page stays beside the script until the segment airs.
- Guest name and confirmed pronunciation
- Role or connection to the topic
- The one reason the audience should listen
- Target length in seconds
Checking facts before they become spoken words
A printed error can be corrected quietly. A spoken error cannot. Once a presenter says a wrong title or a misplaced affiliation on a live programme, the guest hears it, the audience hears it, and nobody can take it back. For that reason I treat every factual claim in an introduction as something that needs a source I can point to.
In practice this means asking the guest or their representative to confirm the wording of their own description. I send the proposed line back and ask a simple question: is this how you would like to be introduced? People are generally generous about this, and they often shorten what I had planned to say.
Rebecca Alvarez teaches this research habit in the interview module, and I lean on her checklist myself. Accuracy comes first, and elegance is added only to what has been confirmed.
Shaping the draft for one voice
With the facts settled, I write for a specific presenter. Each person has a natural pace, favourite phrasings and words that trip them up. A line that reads well on paper may be awkward in someone's mouth, so I ask the presenter for a recent recording or sit in on a rehearsal when I can.
The structure is usually simple: a welcome, a single sentence placing the topic, the guest's name delivered clearly, and a handoff that gives the guest an easy first question. I keep sentences short and put the name late enough that the audience is listening when it arrives.
I read every draft aloud, at the speed the presenter would use, and mark the places where I run out of breath. Those marks tell me where a sentence is too long. Cutting there almost always improves the whole passage.
- Short sentences with one idea each
- The guest's name placed where it can be heard
- A handoff that invites the first answer
Counting seconds against the running order
An introduction has a slot, and the slot is rarely generous. A producer may allow twenty seconds, or forty, depending on the rundown. I convert the draft to time by speaking it with a stopwatch and then comparing that against a plain word count, so that I learn each presenter's real rate rather than relying on a generic figure.
If the draft runs long, I cut in a fixed order: decorative phrases first, then secondary credentials, and only last the core reason the guest is there. I also mark one optional sentence that the presenter can drop on the day if the programme is running behind.
This is where Daniel Okafor's timing module and the introduction work overlap in the course. A line that is correct but ten seconds too long is still a problem for the people running the studio.
Revision rounds and the producer's eye
The first draft goes to the producer with a short note explaining the choices I made and what I could not confirm. Producers see the whole programme and know things I do not: that the previous segment ended on a joke, or that the guest is nervous. Their comments usually change the tone more than the content.
I ask for notes in one round where possible, then revise once, and keep a clean copy marked with the version. Too many small changes late in the day cause confusion about which page the presenter is holding.
Learners follow this same loop in the drafting module, using the demonstration scripts, so that the habit of tracking versions and recording decisions is in place before they ever work on something live.
- One consolidated round of notes
- A clearly labelled final version
- A record of what was confirmed and by whom
What the presenter receives on the day
The finished page is deliberately plain: large type, generous spacing, the guest's name written once in bold with a phonetic note beside it, and the optional cut marked in the margin. Nothing on it should require interpretation under studio lights.
I try to be reachable shortly before the segment in case a fact changes. Occasionally a guest has altered a title at the last minute, and a quick message is the difference between a correct introduction and an awkward one.
After the programme I ask the presenter what felt natural and what did not. Those remarks go into my notes for the next script, and they are the most useful teaching material I have.
An introduction is short, but the work behind it is not: gathering facts, confirming them with the guest, writing for one voice, timing it against the rundown and revising once with the producer. None of these steps is complicated, yet skipping any of them shows on air. If you practise the sequence on small examples first, it becomes routine by the time the segment is live.
