A file naming rule is a fixed pattern for every script filename. It usually lists the project, the episode, the version, and the date in that order. The pattern turns a folder of mystery files into a list anyone can read.
A predictable name lets anyone find the right file without opening five of them to check. That small habit saves the minutes you would otherwise lose every time someone asks for the latest draft.
Agree on the pattern before a project starts, not after the first mix-up wastes an afternoon and leaves two people editing the wrong file.
Put the project and episode first so related files sort together in a folder. Add a version number and a date so the newest draft always wins when someone sorts by name.
Use a date format that sorts correctly, such as year, month, then day. Month names and slashes break sorting in most file browsers, which hides the newest file somewhere in the middle.
Avoid spaces and special characters that trip up upload tools and shared links, because a broken link stalls a review and sends someone hunting through chat history.
Number versions in a straight line, such as v01, v02, and v03. Skip words like final and final-final because they lie the moment a producer asks for one more change.
When a version is approved, mark it locked and stop editing it. New work continues in the next number so the approved file stays honest about what it contains.
Keep one folder for drafts and one for locked versions, so the right file is always obvious at a glance and nobody opens a half-finished page by mistake.
A filename is the first instruction you give your editor, so make it a clear one.
Dates written several ways look alike when you scan fast. Pick one format and hold it across the whole project so the list stays sortable from start to finish.
Deep folder nesting hides the files people need most. A flat folder with strong names often beats a maze of subfolders that nobody can remember.
Renaming shared files breaks links that other people already have. Lock the names once a file leaves your hands and starts moving through the team.
A naming pattern proves its worth over a full season, not a single file. Twenty episodes with the same structure sort into a clean list that anyone can scan.
Include the episode number early so the folder order matches the release order. The editor then finds episode twelve where they expect it to be.
When you archive a finished season, keep the locked versions and the naming pattern intact. A tidy archive makes a future re-edit far less painful.
A naming pattern fails quietly when one person breaks it. A single file called draft two new final undoes the order of twenty tidy names and sends the newest version somewhere unpredictable. Watch for those breaks during a season and rename on the spot rather than waiting for a cleanup day. A folder kept tidy week by week never needs a heroic rescue at the end. Build the check into your publishing routine so a bad name never survives a single day, and finding any script in the archive takes seconds instead of a long hunt.
A two column script puts visuals and audio side by side, while a single column script keeps one flow. Here is how to choose the right layout.
Marking visual and audio columns inside a script keeps shots and narration aligned, so your edit team knows what to cut before shooting starts.
Adding timecodes and b-roll notes to video scripts turns a rough draft into a shooting plan that both camera and edit crews can follow on the day.
Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.
Analyze a Channel