The Folder Templates and Naming Rules We Teach From
A look at the working tools behind our folder structures and naming module: the template tree, the naming pattern and the checks we use to keep both usable on real shoots.
Priya Raman · · 6 minutes to read
Why we start with a template tree
Every learner in the folder structures and naming module begins with the same thing: a blank project drive and a template tree. The tree is deliberately plain. It has a top level for the project, then numbered branches for source footage, audio, graphics, project files, exports and documents. The numbers matter because they keep the branches in a fixed order in any file browser, whether someone opens the drive on a laptop, an edit suite or a shared server. We rely on a template rather than a lecture because people remember a structure they have handled. In the first session each learner copies the tree, fills it with a handful of sample clips and then breaks it on purpose by adding a folder where it does not belong. Seeing how quickly a clean tree drifts teaches more than any rule about discipline.
The tree we hand out is an original worked example, not a standard borrowed from anywhere. It is meant to be cut down or extended. A documentary team shooting over several seasons will keep a different set of branches from a two-day corporate crew, and the module spends time on deciding which branches earn their place. A branch that nobody can describe in one sentence usually gets merged into another.
- Numbered top-level branches keep the order fixed in any browser
- Each branch must be describable in a single sentence
- The template is trimmed to fit the shoot, never copied blindly
The naming pattern and what each part does
Our naming pattern is built from short parts separated by underscores: a project code, a date, a shoot or scene label, a description and a version number. Each part answers a question someone will ask later. Which job is this from? When was it shot? Which scene? What is in it? Which revision is it? When all five are present, a file can be understood from its name alone, even when it has been copied out of its folder and sent in an email. We teach the order as well as the parts. Putting the date in year-month-day form means a plain alphabetical sort is also a chronological one, which saves many hours of scrolling. Learners write names for a set of imaginary clips, then swap with a partner who tries to guess the content from the name. Where the guess fails, the name is rewritten.
We keep names short enough to survive the path limits of older systems and avoid spaces and special characters. Those two habits remove a surprising number of failed transfers and broken links in editing projects. We also ask learners to agree the pattern once, write it down on a single page, and keep that page in the project root where every newcomer will see it.
- Project code, date, scene, description and version in that order
- Year-month-day dates so alphabetical order is chronological
- No spaces or special characters in any file name
Materials we use in the exercises
The exercises use a small sample project drive that learners can reproduce on their own machine. It holds short placeholder clips, a few project files, some exported cuts and a documents folder with a call sheet and a shot list. None of it is precious, which is the point: learners can rename, move and delete freely and then reset the drive to try a different structure. Beside the drive we use a one-page naming sheet and a simple spreadsheet that maps old file names to new ones. The spreadsheet is the quiet hero of the module. Before any renaming happens, the old name and the proposed new name sit side by side, so the change can be reviewed and, if necessary, reversed. Bulk renaming tools are shown, but only after the mapping exists.
We deliberately keep the tooling modest. A learner who understands the structure can apply it in any editing application or file manager they already use, and a method that depends on one piece of software becomes a problem the day the team changes tools. Where a tool is mentioned, it is described by what it does rather than recommended by name.
Checks that keep the system honest
A structure is only useful if people keep following it, so the module ends with a set of checks rather than a set of rules. The first is a five-minute drive walk: open the project, look at the top level and ask whether a stranger could find the final export without help. The second is a naming scan, sorting a folder alphabetically and reading down the list to see whether the order tells a coherent story. The third check is the handover test. A learner gives the drive to a colleague with no explanation and asks them to locate a particular clip, the current cut and the project file. If the colleague hesitates, the structure has a gap, and we fix the gap rather than add a longer instruction document. Instructions that need explaining are usually a sign that the structure itself is unclear.
We encourage teams to repeat these checks at natural pauses, such as the end of a shoot or before an edit begins. The checks take minutes, and they catch drift while it is still a handful of misplaced files rather than a library nobody trusts.
- Five-minute drive walk at the top level
- Alphabetical naming scan of each folder
- Handover test with a colleague who has no briefing
Adapting the method to your own shoots
Once the template and the pattern are familiar, the last part of the module is adaptation. Learners take a recent or upcoming shoot of their own and sketch the tree it would need. A single-camera interview series, a multi-day event and a short drama each ask for different branches, and the sketch is where those differences show up. We ask for the sketch on paper first, before anyone touches a drive. We also talk about what to leave alone. Existing projects with a long history do not need to be rebuilt in a weekend, and forcing a new structure onto old material often creates more confusion than it removes. A sensible route is to apply the new method to every project from now on and bring older work across only when it is reopened.
Instructors review each sketch and comment on clarity, depth and naming, but the choices stay with the learner. The aim is a structure the whole team understands and will actually use, not a perfect one that lives in a document nobody opens.
The tools behind this module are modest on purpose: a template tree, a five-part naming pattern, a mapping spreadsheet and a few quick checks. None of them depends on a particular application, and all of them can be adapted to a different kind of shoot. If a colleague can open your drive cold and find the current cut within a minute, the method is doing its job.
Send us a message
- Call us
- (505) 214-0873
- By email
- [email protected]