How Rosa's Documentary Team Stopped Losing Clips in Their Own Folders
A short story about Rosa, a documentary producer whose shared drive grew faster than anyone could follow, and the folder and naming rules her team settled on over a few weeks.
Daniel Whitfield · · 6 minutes to read
A drive that nobody trusted
Rosa runs a small documentary team that shoots interviews and landscape material across several states. When she first wrote to us, the shared drive held about two years of work, and every person on the team kept their own idea of where things belonged. Rough cuts lived beside raw cards, exports sat in folders named after a mood rather than a project, and two editors had each built their own copy of the same interview selects.
She did not describe it as a crisis. It was more a steady loss of confidence. Before every edit session someone spent the first hour asking the others where a clip was, and more than once a finished sequence was rebuilt from material that turned out to be an older ingest.
I joined her first call as the instructor handling this module. Before suggesting anything, I asked her to describe how a single shoot day travels from the camera card to the final export, because folder rules only work when they follow that path.
Starting from the shoot day, not the folder tree
Most people begin by sketching a tree of folders. Rosa's team did the same, and their first draft had seventeen top-level folders. We set it aside and walked through one actual shoot day instead: cards offloaded in the evening, a second copy made, selects pulled the next morning, then a rough assembly.
Each step produced files that someone later had to find. Writing those steps down on a single page showed which stages needed a home of their own and which were being given a folder out of habit. The seventeen folders collapsed into five, each matching a stage in the life of a clip.
This is the principle we teach in the module: a structure should describe where a file is in its life, not who made it or how it felt to the person who saved it. Once the team agreed on that sentence, most of the arguments about placement ended.
- Offload and backup
- Selects and working media
- Project files
- Exports and deliverables
Naming rules the team could say out loud
Naming took longer than the structure. Rosa's editors liked descriptive names, and descriptive names are exactly what stop sorting from working. We agreed on a short pattern that put the project code first, then the shoot date written year-month-day, then the subject, then a three-digit sequence number.
The test we used was simple: could a new editor read a filename aloud over the phone and be understood? Names with spaces, brackets and the words final or new failed that test and were dropped. A version marker such as v02 was allowed only on project files and exports, never on camera originals, which keep the name the camera gave them plus a prefix.
Rosa kept a one-page card pinned beside every edit station with the pattern and three examples. She told me the card did more than any long document would have, because nobody had to open anything to check the rule.
The first two weeks of using it
The team did not rename two years of footage on day one, and I advised against it. Old projects stayed as they were, with a short note in each top-level folder saying which convention it followed. Only new shoots used the new structure from the start.
The first week was uneven. One editor kept saving exports to the desktop, and a second shoot day was offloaded with the date written in the wrong order. Rosa handled both without drama: she fixed the files, then asked what had made the rule hard to follow at that moment. In one case the answer was that the offload folder was buried three levels down, so we moved it closer to the top.
By the second week, the question of where something lived had mostly disappeared from the team's chat. The folders had started to behave like a map rather than a puzzle, and that was the outcome the module is built to reach.
What we left alone on purpose
It would have been easy to keep adding rules, and Rosa was tempted to. She asked about colour labels, about a naming scheme for audio stems, about how to record which clips had been cleared for broadcast. Those are real questions, but they belong to other parts of the programme, such as metadata and version tracking, and we deliberately did not stretch the folder rules to cover them.
A structure that tries to carry everything becomes a structure nobody can remember. We kept hers to what a folder and a filename can honestly do: place a file in its stage and identify it uniquely. Everything else we noted on a list for later.
She also chose not to rename her oldest footage at all. That was her call, and a sensible one, since the material was already backed up and rarely opened.
What you can take from Rosa's case
Rosa's team did not need a clever system. They needed one that matched how footage actually moves through their week, and one rule per decision that anyone could recall without looking. The worked example in this module follows the same logic, and you are encouraged to adapt it to your own shoots rather than copy it.
If you are about to design your own, start with a single shoot day on paper. List every file it produces, say who needs it next, and only then draw folders. Test your naming pattern by reading a few names aloud. Adopt the structure for new work first and leave the archive alone until you have lived with the rules for a while.
- Map one real shoot day before drawing any folders
- Give each stage of a clip's life one home
- Test names by reading them aloud
- Apply new rules to new work first
Rosa's story is ordinary, which is why it is useful. No dramatic rescue was involved, only a team agreeing on where a file belongs and what to call it. The folder and naming module walks you through the same decisions with a worked example you can adapt. Take your time with the first shoot day, keep the rules short, and let the structure settle before you ask more of it.
Send us a message
- Call us
- (505) 214-0873
- By email
- [email protected]