The Tools Behind a Clean Programme Transition
A look at the rundown, the link ledger and the spoken read-through that Daniel Okafor relies on when joining one live segment to the next without a jarring gap.
Why transitions need their own tools
A live programme is a chain of separate pieces, and the weakest part of any chain is the join. Writers tend to spend their care on the segments themselves and treat the link as an afterthought, a sentence or two typed at the end. On air, that sentence carries a lot of weight. It has to close one topic, open another and keep the viewer oriented while cameras, graphics and guests change around the presenter.
Because a link is so short, it is easy to judge by feel alone. I prefer a small set of fixed materials that make the judgment repeatable. They do not write the link for you. They show you where the gap is, how long it will last on air and whether the presenter can actually say the words in one breath. This article walks through the three I return to most often in the course.
None of them is exotic. All are things a producer will recognise on a desk, and that is deliberate. A method that only works in a classroom will not survive the pressure of a real running order, so every tool here is chosen because it holds up when the schedule moves.
The rundown sheet as the working document
The rundown is the first thing I open. It lists each segment in order with its running time, its topic and who is speaking. For link writing, I add two columns of my own: what the audience has just heard, and what they need to know before the next piece begins. Filling those columns forces a decision about the link's real job.
Often the answer is smaller than expected. A link between a talk on regional pottery and an interview about school music does not need to pretend the two subjects are related. It needs to release the first topic cleanly and prepare a fresh question for the second. Seeing both ends on one page makes that honest, modest approach easy to spot.
I also mark any segment whose length is uncertain. If a guest might run long, the link after it must be able to shrink. Noting that on the rundown, before a word is drafted, saves a rewrite later and keeps the whole team looking at the same facts.
Learners in the course practise this with a rundown they build themselves, then swap with a partner who has to explain each join back to them.
- Add a column for what the audience has just heard
- Add a column for what they need before the next piece
- Flag any segment with an uncertain length
A link ledger for wording and reuse
The second tool is a plain list I call the link ledger. For each join I record the draft wording, its spoken length in seconds and a note on what it hands over. It looks dull, and it is the most useful page in the folder, because patterns appear when links sit side by side.
You notice that three links in a row begin with the same phrase, or that every handover leans on a question the presenter then answers. Repetition that is invisible in a single script becomes obvious in the ledger. Fixing it is usually a matter of changing the opening word or letting one link simply state the next topic and stop.
The ledger also gives you spare material. For each important join I write a long version and a short version, side by side, so that a producer who needs to cut can choose without asking me. Having both ready is what separates a flexible script from a fragile one, and it costs only a few extra minutes at drafting time.
- Record wording, seconds and what each link hands over
- Write a long and a short version of key joins
The spoken read-through
The third method needs no paper at all. I read every link aloud, at the pace the presenter would use, with a stopwatch running. Silent reading hides awkward sounds, stacked consonants and sentences that demand more breath than a person has. Aloud, they announce themselves immediately.
I listen for three things. First, whether the link finishes in the time the rundown allows. Second, whether any phrase makes me hesitate, since a writer who stumbles will be joined by the presenter. Third, whether the last words land on something the next segment can pick up, so the handover feels like a hand passed rather than dropped.
In class we do this in pairs, one reading and one timing, and then switch. People are often surprised how many sentences they cut once they hear themselves say them. The exercise is not about performance. It is a check that the words belong to a mouth, and that the join will hold under live conditions where there is no second take.
Using the three together for these autumn weeks
As the new season of programming begins, many productions return with fresh running orders and unfamiliar guests, which is exactly when joins go wrong. The rundown shows the shape, the ledger keeps the wording consistent and the read-through proves it can be said. Used in that order, they take perhaps half an hour for a typical programme.
I would not claim they remove every risk. A guest who overruns or a graphic that fails will still test a link. What the tools give you is a script that already has a shorter option ready, wording that has been spoken at least once and a clear idea of what each join is for.
That preparation is calm work, done at a desk, and it pays off precisely when the studio is not calm. It is the difference between improvising a bridge under pressure and choosing between two bridges you built earlier, with the time to build them properly.
Starting small with your own rundown
If you want to try this, take any programme you know well, even a short one, and write out its running order. Choose a single join and fill the two extra columns. Then draft a long and a short link, read both aloud against a stopwatch and note what you changed.
Do not aim for elegance on the first attempt. The point is to see the join as a piece of work with its own length and its own job, rather than a sentence squeezed in at the end. Once that habit forms, the rest of the method follows naturally.
The Programme Transitions module in the curriculum builds on exactly these steps, with demonstration scripts you can mark up and revise. You will practise on neutral educational and cultural topics, so the focus stays on the craft of the join and not on the subject matter around it.
A good transition is rarely clever. It is short, spoken aloud before it is trusted, and built from materials any producer would recognise: a rundown, a ledger of wording and a stopwatch. Use them in that order, keep a shorter version of every important join and let the presenter hear the words before the programme does. The gap between topics then becomes a quiet, ordinary moment instead of a risk.
