Back to Blog
GoScript Journal

Adding Timecodes and B-Roll Notes to Video Scripts

·7 min read·GoScript Team /Editorial

The short answer

A timecode marks a moment on the timeline, and a b-roll note describes the footage you want at that moment. Adding both to a script turns the words into a plan a crew can actually execute. The page stops being only a reading script and starts working as a production document.

You do not need frame accuracy for every line. Rough marks in minutes and seconds are enough to guide a shoot and speed up the edit later. Start loose and tighten the marks as the video moves closer to production day.

Keep the notes close to the lines they belong to. A timecode floating far from its scene forces the reader to hunt, which defeats the purpose of adding it.

Why timecodes help

Timecodes give everyone one shared reference. Instead of saying the part after the intro, you point to a specific mark and the whole team knows exactly where to look on the timeline.

During editing, a timecode lets a cutter jump straight to a beat without scrubbing the entire file. That saves minutes on every pass through the timeline, and those minutes add up across a long project.

Keep the format fixed, such as hours, minutes, and seconds, and never mix styles inside one script. A single format stops the reader from guessing and makes the marks searchable.

Writing b-roll notes that get used

Good b-roll notes describe the shot rather than the feeling. Write a close-up of hands typing instead of something dynamic here, because the crew cannot film a mood or a vague intention.

Add the source when you know it, such as archive, screen capture, or shot on location. The crew can then gather the right material without a follow-up call the night before the shoot.

Mark optional shots so the director can drop them when the schedule runs short. A labeled optional shot is easier to cut than a surprise conversation on set.

A timecode tells the crew when, and a b-roll note tells them what. Together they remove guesswork.

Keeping notes from bloating the script

The script is a reading document first. Too many production notes make it hard to read aloud, and the narrator is reading the same page you are. Keep the narration clear of clutter.

Push long shot lists into an appendix or a linked sheet and keep only the key note inside the script. The crew still has the detail, and the page stays readable for everyone else.

Use a consistent marker, such as a bracketed label, so notes stand apart from spoken lines at a glance. The reader should never confuse an instruction for a line to read.

Matching notes to the edit

Timecodes and b-roll notes do most of their work in the edit, long after the shoot is over. The cutter opens the script, reads the marks, and pulls footage in the order the page lays out.

Keep each note specific enough to act on alone. A cutter working at night should not need to call you to understand what a note means or where a shot came from.

When you change a timecode after a rough cut, tell the editor in the same file. Stale marks in a script are worse than no marks at all.

A clean set of notes also lets two editors share the work without stepping on each other. Both people read the same timecodes and the same b-roll references, so their cuts line up. That shared language keeps a shared edit from turning into a negotiation over every clip. Write the notes as if a stranger will read them alone, because sometimes a stranger does.

Key takeaways

  • Timecodes create a shared reference point for every beat.
  • B-roll notes should describe the shot and its source.
  • Keep one timecode format across the whole script.
  • Move long shot lists into an appendix.
  • Mark optional shots so they can be cut later.

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel