Most editors clean up their drives the same way amateur productions handle gear: only when something breaks. The drive fills up mid-export, or a project will not open, or a client asks for an old job and nothing can be found. Then comes a frantic afternoon of triage.

There is a better way, and it takes 30 minutes a month.

Treat It Like a Camera Check

A first AC checks the camera every morning before the first take. Not because something is wrong, but because the cost of finding a problem at 6 a.m. is roughly zero, and the cost of finding it at noon is the entire afternoon. The check is cheap insurance. It is also a craft signal. The people who do it are the people you want on your set.

A monthly drive audit is the editing equivalent. It is not a chore. It is a professional practice. The editors who do it have predictable storage costs, fast project lookups, clean archives, and almost never get caught by a full drive on a deadline day. The editors who skip it spend three times as long fighting their own infrastructure when it eventually breaks.

Pick a date. The first Tuesday of every month is what I use. Thirty minutes. Same time every month. Make it boring and repeatable.

The 30-Minute Checklist

Run through this in order. Do not skip steps even if you think you do not need them. The whole point is the ritual.

Minute 0-5: Capacity check

Open Disk Utility or your storage tool of choice. Write down the current free space on each working drive and each archive drive. Compare to last month's number. If a drive dropped more than 20 percent in a month, that is your signal to dig in.

Note any drive that is below 15 percent free. At 10 percent free, SSDs start slowing down due to write amplification, and Premiere's cache behavior gets unpredictable. You want a buffer.

Minute 5-10: Project inventory

List every active project on every working drive. Mark each one as one of three states: in progress, delivered awaiting cleanup, or stale.

Stale means the project has not been touched in 30 days and is not waiting on anything. These are the projects you forgot about. They are also the easiest cleanup wins because there is no risk of needing the source files imminently.

Minute 10-20: Cleanup pass

For every project marked "delivered awaiting cleanup" that delivered more than 5 business days ago, run the cleanup. Identify unused media, delete it from the working drive, archive a lean version to long-term storage.

For every "stale" project, decide: archive it or delete it. There is no third option. A project that has been stale for 30 days is either worth keeping forever or worth letting go. Hedging is how drives fill up.

This is the slowest step. It is also where almost all the value comes from. If you only have 10 minutes one month, spend them here.

Minute 20-25: Backup and integrity check

Confirm your backup ran in the last week. Open one random archived project from six months ago. Make sure it actually opens, the media is online, and nothing is corrupted. Bit rot is real on long-term storage, and the worst time to find out your archives are broken is when a client wants something from one of them.

If a project will not open, do not panic, but do put it on a fix list. You found the problem on a quiet Tuesday instead of in front of a client.

Minute 25-30: Log it

Write down what you did. A single line per drive in a running text file is enough. Date, free space before and after, projects touched, anything notable.

This log is your early warning system. If you can see that a drive lost 200 GB a month for three months, you can predict the full date and act before it happens. Without the log, you are flying blind.

What This Saves You

A monthly audit prevents the three most common storage disasters: the full-drive emergency on a deadline day, the lost-archive panic when an old client returns, and the slow-Premiere problem nobody can diagnose because the working SSD is silently choking on a 98 percent full disk.

It also gives you real numbers. You stop guessing about how much storage you need. You start knowing. The calculator becomes a planning tool instead of a vague reference, because you can plug in actual usage trends from your audit log.

Over a year, 12 audits add up to 6 hours. A single full-drive emergency typically costs 4 to 8 hours of recovery work. Do the math. The audit pays for itself the first time it prevents one disaster.

Why Most Editors Skip This

Two reasons. First, it does not feel urgent. Nothing is on fire, so the brain says it can wait. The same thing happens with backups, until the day it does not.

Second, the cleanup step is hard to do right. Identifying genuinely unused media across multiple projects on a drive is the kind of cross-referencing nobody wants to do by hand. So editors either skip it, do it badly, or accidentally delete something that turns out to matter.

This is the part I would automate before anything else. The audit framework is the human ritual. The unused-media identification is the part a computer should handle.

The Actionable Step

Open your calendar. Create a recurring event: "Drive audit, 30 minutes, first Tuesday of the month." Starting next month. Add a note with the checklist above.

Then, before your first audit, set up the audit log. A single text file. One line per drive per month. That is the entire system.

The Tool That Helps the Hardest 10 Minutes

When you get to the cleanup step and need to identify what is actually safe to delete, Clip Sweeper does the cross-project reference analysis automatically. The audit is the ritual. The tool just makes the hardest 10 minutes of it tractable.