GoScript
Back to Blog
GoScript Journal

Shot Numbering to Track Cuts in Scripts

·6 min read·GoScript Team /Product

Why count shots

Long videos can have dozens or hundreds of cuts. Without clear shot numbers, editors and writers waste time pointing to 'that one clip' in reviews. A format library should define how to number shots for each project type. For example, a documentary crew can number shots in order from start to end with no gaps. This makes it simple to say 'fix shot 24' and have both people look at the same cut.

Choosing a numbering style

There are a few common styles: simple numbers, scene-based numbers, or numbers with letters. A simple sequence works well for short clips. Scene-based numbers work well for films with many acts. For a tutorial series, scene 1 shots could be 1.01, 1.02 to show their order. A format library should pick one style per project type and state it clearly.

Linking numbers to script lines

Shot numbers only help if they appear in the right places. Put the number next to the visual cue and next to the cut point in the script. For example, a product demo can list 'SHOT 05: show close-up of button' in the visuals column. This links the written line to the video cut without extra notes. When numbers stay in sync, edits go faster and reviews take less time.

If you cannot point to a number, you will point to a guess.

Handling inserts and changes

Edits often add or remove shots late in a project. A format library should say how to handle this. One option is to keep original numbers and add letters for inserts, like 12a. Another option is to renumber after major cuts. For a news package with tight time limits, many crews renumber after each edit pass to keep a clean list. The choice depends on the team, but it must be written down and followed.

Key takeaways

  • Define one shot numbering style per project type in your format library for consistent use.
  • Put shot numbers next to visual cues so writers and editors see the same cut point.
  • Choose a clear rule for inserts, like adding letters or renumbering after major edits.
  • Use numbers in reviews to cut back on vague notes and speed up fixes.

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