Six Draft and Revision Mistakes That Slow Down a Live Script
Most weak scripts fail in the revision rounds, not the first draft. Daniel Okafor walks through six common mistakes and shows how to run a cleaner draft-and-revise cycle.
Treating the first draft as the finished script
The most common mistake I see in the Drafting and Revisions module is a writer who hands over a first draft as though it were final. A first draft exists to get the shape of the segment onto paper: the opening, the order of points, the hand-off to the next item. It is not yet a script a presenter can say.
When learners treat it as finished, they defend every sentence in the feedback round, and the revision becomes an argument rather than a repair. Writers who expect to revise write faster, cut more freely and accept notes without taking them personally.
In the course we set the expectation early: the draft is round one of three. Round one fixes structure, round two fixes wording for the ear, and round three fixes timing. Knowing what each round is for keeps the whole process calm.
- Label every draft with its round number
- Decide before you write what round one must achieve
- Keep the outline beside the draft and check against it
Revising everything at once
A second mistake is answering feedback by rewriting the entire script in one sweep. Notes arrive in different kinds: a producer may question the order, a presenter may flag a tongue-twister, and the clock may show you are forty seconds long. If you change all three things together, you cannot tell which change helped.
We teach learners to sort notes into groups before touching the page. Structural notes come first, because a moved paragraph changes everything after it. Wording notes come next, and timing notes last, since cuts and additions alter the count.
Working in this order also protects the parts that were already approved. When a producer has signed off the outline, the revision should not quietly wander away from it, and a clear sequence of passes makes that easy to guarantee.
Ignoring the presenter's voice in the feedback round
Feedback from the person who will actually speak the words is the most useful note a writer receives, and also the one most often dismissed. A presenter who says a line feels awkward is rarely wrong, even when the writer cannot see why on the page.
The mistake is to defend the sentence instead of reading it aloud. In our sessions we ask every learner to read the disputed line out loud, twice, at the pace of the programme. Usually the problem is audible at once: a clause that needs a breath in the wrong place, or two similar sounds side by side.
Respect for speakers is one of our stated values, and this is where it becomes practical. A script that suits the presenter's natural phrasing will sound more confident on the day, whatever the topic.
- Read every disputed line aloud before replying
- Ask the presenter where they take a breath
- Offer two alternative wordings rather than one
Letting length drift between rounds
Writers often fix a note and, without noticing, add ten seconds. After three rounds the segment that began at ninety seconds now runs two minutes, and nobody remembers agreeing to that. Revision should never quietly change the target duration set at the briefing.
The remedy is dull but reliable: record the word count and estimated seconds at the top of every version. If a revision adds a sentence, find the sentence it replaces or mark an optional cut elsewhere. Our demonstration scripts show this habit clearly, each version carrying its running length.
This also prepares you for live conditions, where a segment may be asked to shrink at the last minute. A script whose length has been tracked from the start is far easier to trim than one that has grown unseen.
Losing track of versions and decisions
A quieter mistake is administrative. When several people comment, files multiply, and a producer approves the wrong version or a presenter rehearses an old one. The result is confusion minutes before going live, which no clever phrasing can repair.
Keep one working file, name each version plainly with its round and the date, and write a short list of what changed and why. When a note is declined, record the reason in a line. That record saves a repeated discussion later and shows reviewers that the choice was deliberate.
In the course, learners practise this with the demonstration samples, which come in several labelled versions. Comparing version one with version three teaches more about revision than any amount of advice, because you can see exactly which changes mattered.
- Name files by round and version
- Record declined notes with a one-line reason
- Archive earlier versions rather than overwriting them
Stopping revision too early or too late
The final mistake is judging when to stop. Some writers stop after one round because they are tired of the piece; others keep polishing until the segment is stiff and over-edited. Neither helps the presenter on the day.
A useful test is to ask what the next round would actually change. If the answer is only synonyms, the script is finished. If the answer is a clause nobody can say cleanly, or a transition that still jars, another round is justified.
I usually suggest a final read-through with the clock running and the presenter speaking at normal pace, then a short pause, then a last look at the opening and closing lines. Those two moments carry the most weight, and they are worth the extra few minutes.
Good drafting and revision is mostly discipline: know what each round is for, change one kind of thing at a time, listen to the presenter, track length, keep versions tidy and recognise when to stop. These habits matter more in these early autumn weeks, when new programme schedules begin and scripts are written under fresh pressure. Practise them on the demonstration samples first, and they will hold when a real segment depends on them.
