Full Inventory or Targeted Spot Check: Which Asset Review Fits Your Drive
Two ways to review a production drive, a complete inventory and a sampled spot check, compared on effort, findings and risk, with a clear recommendation for most small teams.
Priya Raman · · 6 minutes to read
Two ways to start an asset review
Most teams that ask for an asset review have the same picture in mind: a shared drive that grew shot by shot, with several people saving files in their own way. Before anything is reorganised, someone has to look at what is actually there. In the Asset Review and Audit module we teach two ways of doing that, and in these autumn weeks, when many productions close out their summer shoots, the question of which one to use comes up constantly.
The first is a full inventory. Every clip, project file and export on the drive is listed, with its size, date, location and apparent purpose. The second is a targeted spot check. You choose a handful of recent projects, review them closely, and use what you find to judge the state of the rest.
Neither approach is clever. Both need the same prerequisite we ask of every learner: access to a sample project drive, so the habits are practised on real material rather than on a diagram.
What a full inventory involves
A full inventory means walking the whole drive in a fixed order and recording what you meet. The usual output is a spreadsheet with one row per file or per folder, depending on how large the library is. Columns typically cover the path, the format, the size, the last modified date, and a short note on what the item seems to be: raw footage, a project file, an intermediate render or a final export.
In the course we show how to build this list with the tools you already have, without special software. The point is that the list exists in one place, so duplicates, orphaned files and missing exports become visible as patterns rather than as hunches.
The cost is time. A drive with several years of work can take days to catalogue properly, and the person doing it needs to understand the team's old conventions well enough to label things correctly.
- Complete picture of duplicates and gaps
- Gives a baseline for later reviews
- Slow on large or badly labelled drives
- Needs someone who knows the history
What a targeted spot check involves
A spot check starts from a sample. You pick three to five projects, ideally a mix: one recent and well kept, one older, one that was rushed, and one that someone remembers as a problem. Each is reviewed in depth, checking that the raw footage, project file and final export all exist, that names follow some logic, and that the delivered version can be identified without asking anyone.
Because the scope is small, the review can be done in a day or two, and the findings are specific enough to act on. You also learn how the habits differ between editors, which is often more useful than a raw count of files.
The weakness is coverage. A spot check can miss a forgotten folder of unlabelled camera cards or a second drive that nobody mentions, and it says little about material outside the sample.
Comparing effort, findings and risk
On effort, the spot check wins clearly: a fraction of the hours, and a result you can read in one sitting. On completeness the inventory wins, since nothing is left to inference. On risk, the comparison depends on what you fear. If the worry is losing a specific final export, a spot check of the relevant projects answers it quickly. If the worry is that the drive is full of unknown duplicates, only an inventory shows the real scale.
There is also a difference in what the team learns. A full inventory tends to produce a document that one person understands and others file away. A spot check, because it walks through real projects, usually produces conversations about why a file was named a certain way, and those conversations are where agreement on a new convention starts.
Cost matters too. Scope for any hands-on file handling is agreed separately, so a smaller first review keeps that decision small.
Our recommendation for most teams
For most small and mid-sized production teams, we recommend starting with a spot check and growing it into an inventory only where the findings justify it. Begin with the sample projects, write down the problems that repeat, and then inventory the areas where those problems cluster, such as the drive holding the oldest raw footage.
This staged route keeps the first review short enough that it actually gets done. It also stops the common failure in which a team commits to a full catalogue, loses momentum halfway, and ends up with a half-finished spreadsheet that nobody trusts.
The exception is a drive about to be archived or handed to another team. There, an inventory is worth the time, because the next owner will have no one to ask about what each folder holds.
- Start with three to five sample projects
- Record repeating problems, not single ones
- Inventory only where the findings point
- Inventory fully before any archive handover
Working it into your routine
Whichever method you choose, the review should not be a one-off. Teams that keep their libraries in order tend to repeat a light version of the spot check at the close of each project: confirm the final export is where it should be, confirm the project file opens, confirm the names follow the agreed pattern. It takes minutes, and it prevents the slow build-up that makes a large review necessary in the first place.
In the module, learners practise this on their sample drive and write a one-page summary of what they found: duplicates, gaps, and the two or three risks that matter most. That summary is the document you carry into the next stage, whether that is designing a folder structure or setting permissions.
Keep the summary short and dated, and store it beside the drive it describes.
A full inventory gives certainty and a spot check gives speed. For most teams the sensible order is the spot check first, followed by a targeted inventory where problems cluster, and a complete inventory only before an archive handover. Whichever you pick, write the findings down in a short summary stored beside the drive, so the next review starts from facts rather than memory.
Send us a message
- Call us
- (505) 214-0873
- By email
- [email protected]