guide to naming short-form edit versions so midnight revisions stop looping

# The Night I Lost Three Hours to “Final_Final_v3_ReallyFinal.mp4”

It was 2 AM. I was staring at two video files on my desktop: `short_v2_final_rev.mov` and `short_v2_final_rev_NEW.mov`. I had no memory of which one I’d sent to the client. My heart sank. I’d just promised them the “locked” version an hour ago. I had to open both, scrub through, compare timecodes—a brutal, sleepy-eyed archaeology dig on my own stupidity. That was the night I declared war on my own file names.

**I used to think** that as a solo editor, my system only had to make sense to me. Chaos was a private tax. **I was wrong.** The moment you send a file to *anyone*—a client, a collaborator, even your future self at 2 AM—that private chaos becomes a public liability. Your file name is the only message in the bottle.

## The “Creative” Naming System That Wasn’t

My old method was a festival of adjectives. `short_epic_draft.mp4`. `short_banger_final.mov`. What does “banger” mean? Is it better than “epic”? Is it a different cut, or did I just like the music more that day? **This broke** every single time I had to go back and find a specific take or revert a change. My project folders looked like the notebook of a mad poet, utterly useless for finding anything.

The embarrassment wasn’t just internal. I once sent a client `project_awesome_final.mov`. They replied, “Great, but can we see the *awesome* version?” They were joking. I wanted to crawl into a hole. My “creative” naming had created confusion and made me look unserious.

## The Switch: Code, Not Poetry

I stopped trying to be clever. I realized file names aren’t titles; they are **coordinates**. They need to tell you, at a glance, exactly *what* the thing is and *where* it sits in the process.

Here’s the blunt system I built from the ashes of that 2 AM panic:

**`[ProjectID]_[VersionDescriptor]_[CreatorInitials]_[YYYYMMDD].mov`**

Let’s break that down with the soul of a tired practitioner, not a textbook: * **ProjectID:** A short, consistent slug. `BakeryAd_30s`. Not `ThatBreadAd`. * **VersionDescriptor:** This is the critical field. I use a strict vocabulary: * `v1_rough` – First assembly. Sent for story approval. * `v2_review` – Has basic graphics, sound bed. Sent for feedback. * `v3_rev1` – First round of revisions applied. * `v3_rev2` – Second round on the same base version. * `v4_final` – Approved picture lock. No more changes to cut. * `v4_final_master` – Color, sound mix, titles baked in. This is the deliverable. * **CreatorInitials:** `_JB`. When you work alone, this feels silly. Until you send a file to a client and they send back notes on `_JB`’s file. It’s a tiny flag in the ground. * **Date:** `_20231027`. The ultimate truth-teller. `v3_rev1_20231027` is objectively older than `v3_rev1_20231028`. No more guessing.

**What actually happened** when I forced this on myself? The midnight revisions stopped looping. I could look at a folder and *instantly* know the timeline. `BakeryAd_30s_v2_review_JB_20231027.mov` is clearly the file the client saw on October 27th. Their notes apply to it. My next file will be `BakeryAd_30s_v3_rev1_JB_20231028.mov`.

## The One Realization That Cut My Revision Time in Half

**The file name is the first piece of client communication.**

When you send `Client_v8_FINALFINAL.mov`, you’re telling them the process is messy and their feedback might be lost in the sauce. When you send `ClientAd_v4_final_JB_20231027.mov`, you’re telling them this is a specific, dated milestone. It frames the conversation. It makes notes actionable. It builds trust because it demonstrates a process.

I now spend zero mental energy wondering what file is what. That time—hours a week, I’m not exaggerating—goes back into the edit. The outcome was a massive reduction in workload and cognitive drain. The chaos is gone. At 2 AM now, the only thing I’m looking for is my pillow.