GoScript
Back to Blog
GoScript Journal

Format Naming Rules for a Shared Script Library

·6 min read·GoScript Team /Product

Setting a fixed name for each part

The quickest way to avoid confusion in a shared script is to assign one fixed name to each part of a video. A format library should list names like intro, body, and outro with a short reason for each. For example, a local news team can call its lead block 'open' and keep that name for every weekday clip. This habit saves time when people search for specific parts across hundreds of files.

Rules for numbers and labels

Names work best when they follow a few clear rules. Use plain words, keep them short, and avoid mixing languages in the same folder. For a cooking show, a team could use 'step01', 'step02', and 'step03' to mark recipe parts. These labels make it easy to sort files by order without reading full scripts. The goal is not to invent new terms but to pick a few and use them every time.

Keeping names the same over time

A format library only helps if people do not change names on a whim. Pick names once, write them down, and point new team members to that list. If a name no longer fits, replace it in the list first and update old files in a set batch. This keeps old links working when possible and stops small edits from creating new names. Over a few months, a stable list becomes second nature for the whole team.

Pick three names, write them down, and use them for one month before adding more.

Handling special cases

Not every video fits a basic set of names. A live event may need a 'break' or 'ad' block that does not appear in scripted films. A format library should allow a small set of extra names but not an open list. For example, a sports crew can allow 'replay' and 'stat' blocks only when needed. This keeps rare cases clear without letting every clip get its own name.

Key takeaways

  • Assign fixed names to parts and write the list in one place for all team members to see.
  • Follow simple rules for numbers and labels to keep files in order without extra reading.
  • Keep names stable by updating the list before changing files in bulk or over time.
  • Allow only a few special names to handle rare cases without breaking the pattern.

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