Depending on the size of your operation, you’ll have people to help you manage all your shooting material, or it will be up to you. Either way, these principles should be useful. You’ll end up with a lot of material, especially if you’re shooting anything feature-length. It’s imperative to come up with an organizational scheme and system that you’ve test and that you’ll stick to. As a fun primer on why organization is so essential, let’s take a look at the high end scale to better understand the concept of workflow, pre through post production:
We’ve covered some folder structure best practices for on-set. Now let’s turn to a post structure that will accommodate a variety of asset organization. This is a difficult thing to teach, because it’s going to vary widely depending on the scale of the project you’re involved in and the preferences of the post supervisor. I like to teach a system that takes the best practices from the pro world and incorporates them into something you can use on the smallest of projects.
First, for the main directory, I prefer starting directory names with the date in YearMonthDay format (e.g. 20200314 for March 14, 2020) as it makes alphabetical organization simple. Sort by name and everything flows chronologically. Feel free to add hyphens to improve legibility if you find it necessary (I.e. 2020-03-14), but you’ll get used to them not being there.
Inside that folder, contents can vary, but here’s a good, general-purpose folder structure for a project that you’ll handle on your own, but that’s also navigable in a professional post production environment:
There are many folders which will be added to this basic outline, but it’s a good starting place and it’s logical enough that, even after archival, the project can be understood. I often like to add a “MM” folder for media managed ‘trims’ if I’m not archiving an entire project’s media. I use uppercase for my default structure simply because it’s easy to see what folders I add to it, but it’s not essential. If working in a collaborative environment, sometimes it’s nice to set up “To” and “From” folders for passing a project between artists. Most of these folder names should makes sense, but here are a couple clarifications:
This directory should hold only the final files delivered to client or broadcaster. The “Master” folder holds the highest quality “original”.
“Renders” means exported video that is not generated during production and is only a portion of a final product. I’ll use this folder for VFX renders, color renders, time-lapse renders, etc.
This folder exists so you don’t have to delete anything, but you have a place to put it when you *think* you no longer need it. It’s basically a recycle bin.
BTS is a place to put behind-the-scenes material if you have someone doing EPK. PRODUCTION is a way to stipulate media created during production. Inside, all the transcodes from production can live by date, straight from the DIT production drive, and on a smaller project, camera originals can live there as well. If you’re thinking that the “Video” folder may seem far too general an organization scheme to edit from, that’s because your footage is much better sorted for editing in the NLE than in a file browser; we’ll get to that shortly. You could have additional folders inside “Video” for other sources of video, like stock assets.
Posthaste is a piece of software that can speed up your workflow by generating these folders with the push of a button.
This is a cool application that gets your bin into the NLE (if you’re using Adobe) and keeps the hard drive folders and the imported bins in sync.
The above-mentioned structure actually works quite well in an NLE as well, but, as mentioned, the video organizational side will potentially be much more intense. Keeping the directory structures parallel is a great organizational tactic if you’re disciplined enough to stay on top of it.
Assistants set up bins and metadata, specifically syncing audio, adding scene and take info based on production’s reports and script, and assemble multi-cam sequences. Every production will be different and every editor will have different preferences. A common method is based on scene/take organizational structure since scenes are the building blocks of the narrative and you have a script as your outline (in scripted material). Check with editorial post supervisor. Do they want reel names assigned? ReelID comes with R3D and Arri files but not often with consumer formats, and it can really complicate the conforming process later on.
Features can be edited in a variety of ways. I’ve seen editors cut an entire feature-length project in a single timeline. It’s more common, however, to use the historical standard of “reels” to break up the edit. A standard feature-length projects typically has 5 to 6 “reels”. This means you might have each of those ‘reels’ as a separate AVID bin, each bin containing a sequence for that reel. AVID bins can be accessed by multiple users simultaneously, somewhat similar to Resolve’s collaborative projects. In Premiere, project files are opened on at a time, so it’s common to have each ‘reel’ as its own project as well as a master project to combine them all.
Here are key takeaways: Keep your timelines (AKA “sequences”) organized and duplicate them, incrementing version numbers or dates as you go. I like to use “v07” for versioning; others keep the current cut in a separate bin titled “current” but I like the versioning method best as it gives you a historical order of the cuts. This level of minutia in naming may sound silly, but it makes it easy for someone else (or YOU down the road) to know you’re accessing the latest changes. Make sure it’s easy to find the latest cut.
NEVER LABEL ANYTHING AS “FINAL”. Instead, use version numbers.
The “archive” idea can work in a bin as it does with the folder structure. On a feature, one timeline might represent a “reel’s” worth of time. On a reality show, a timeline may be one scene. Inside those timelines, some editors will use color coding to represent different beats within the story and have an easy visual of how lengths compare. On a smaller project, one timeline may represent the entire piece.
Oftentimes for unscripted work it’s easier to cut all the scenes down and figure out how they will interplay as you craft the narrative. In these cases, organizing via metadata is the most sane approach. In scripted work, scene bins can be auto-generated from metadata as well or manually populated. Having a dedicated folder for each scene can be invaluable on a feature film.
This is the term used to describe the good stuff that’s most likely to make final cut. It’s very helpful to establish a means of rating clips, so you can separate your “selects”, or best shots from the garbage. Some editors like having a ‘stringout’ of these selects to pick from. While these can be laid out in a timeline, again, utilizing metadata and smart bins is arguably the more modern approach.
Here’s a look at a feature film bin structure setup in an NLE:
Similar to how the file explorer structure sometimes uses “to” and “from” folders to see how, for example, color files might be delivered pre-color to the colorist and received post-color from the colorist, there are frequently bins in the NLE for the different hands the media will pass through. As you can see above, assistants will often have their own bins for sync, for example.
Subclips are a very handy organizational tool. These are portions of a clip that exist as their own clips. Resolve, fortunately, allows you to change the in and out points of these clips after the fact if required. In and out points on the source media, then Alt+B to create the subclip, and right-click should you need to edit it later:
Duration markers are simply markers that define a range, rather than a point in time. Similar to subclips, these allow you to define portions within a clip that you want to work with later. They are easily searchable and modifiable as well.