My twins are nine years old and deeply curious about computers. A few years ago, one of them wandered into my office while I was on a call, poked around my desktop, and dragged a folder of client proofs into the trash. Then emptied it. I found out twenty minutes later when I went to pull the files. I had them restored from my local backup in ninety seconds. The client never knew. That near-miss is why I’m going to spend the next thousand words convincing you to take file management as seriously as you take lighting.

Most photographers treat their filing system like a junk drawer. Folders named “shoot2,” “FINALS,” “FINALS_v2,” and “ACTUALLY_FINAL” scattered across a desktop. It feels harmless until a drive fails, a client emails asking for the raw of a specific frame three years later, or someone small and curious empties your trash.

Why Your OS Can’t Save You

Here’s what’s actually happening when files get corrupted or lost. Operating systems use a file allocation table to track where data lives on a drive. When you delete a file, the OS doesn’t immediately wipe the data. It just marks that space as available and removes the pointer. Until something writes over it, the file is technically recoverable. That’s the good news. The bad news is that SSDs, which most of us are using now, use a process called TRIM that actively clears deleted data to maintain performance. On an SSD with TRIM enabled, deleted files can be gone within seconds. No recovery software will bring them back. This is why a backup strategy based on “I’ll just undo it” is not a strategy. It’s a prayer.

Card corruption works differently. A memory card mid-write is vulnerable to any interruption, whether it’s a power hiccup, pulling the card too early, or a card that’s simply degrading. The file gets written partially, the header breaks, and your software can’t read it. This is recoverable sometimes, with tools like Disk Drill or PhotoRec, but “sometimes” is not a word you want to stake a client’s wedding on.

The Naming Convention That Actually Scales

I’ve used the same naming convention since around 2010 and it has never failed me. Every file follows this structure: YYYYMMDD_ClientName_JobCode_SequenceNumber. A commercial shoot for a restaurant client in March looks like this: 20240315_MarketStreetBistro_COM047_0001.ARW. The job code is my internal reference that links back to my invoicing system in HoneyBook.

Why date first? Because every operating system sorts alphabetically by default, and leading with the date means your folders sort chronologically without any extra effort. Client name second means a search for any variation of that client name across an entire hard drive returns every file from every shoot. Sequence number last, padded to four digits, means files sort correctly whether you have 12 frames or 1,200.

I use Adobe Bridge for batch renaming during ingest. It takes about four minutes per card. That four minutes, compounded across every shoot for the rest of your career, is the difference between a professional archive and a digital attic.

The 3-2-1 Rule, Made Specific

You’ve probably heard of the 3-2-1 backup rule: three copies, on two different media types, with one offsite. Here’s what it looks like in practice at my studio in San Francisco.

Copy one lives on my primary working drive, a Samsung T7 Shield 4TB at around $230. Copy two goes immediately to a local NAS, specifically a Synology DS223 with two 8TB WD Red Plus drives in a mirrored RAID 1 configuration. Total cost around $480 for the enclosure and $180 per drive. Copy three is cloud backup through Backblaze B2, which runs me about $6 a month for roughly 800GB of active client work. The moment a card is in the reader, Lightroom Classic ingests to the primary drive and I manually copy to the NAS before I pull the card. The cloud sync runs overnight.

I test every drive the first Sunday of every month. Plug it in, spot-check three random folders, verify file integrity with a checksum tool. Takes twenty minutes. I’ve caught two drives showing early failure signs over the past four years. Both times I replaced them before losing anything.

Folder Architecture That Survives Handoffs

Here’s my top-level folder structure: Clients / Year / ClientName_JobCode / and then four subfolders inside every job: RAW, Exports, Selects, and Delivery. RAW never gets touched after ingest. Exports is where I put full-res TIFFs and JPEGs after editing. Selects holds the Lightroom catalog smart previews and any curated subsets. Delivery is what the client actually receives, and it’s a mirror of whatever file structure I agreed to in the contract.

This matters for client handoffs because you will eventually have a client ask for raw files, ask for a re-export at a different resolution, or come back two years later needing a file for a new campaign. With this structure I can fulfill any of those requests in under five minutes. Without it, I’ve seen photographers spend an hour hunting through nested folders trying to find the original before a client gets frustrated and questions their professionalism. Clients notice response time. They remember it.

Before You Touch a Card

The single habit that protects more photographers than any other is this: do not format a card until you have verified that both local copies exist and at least one cloud sync has completed. Not before the sync starts. After it completes. It sounds obvious. It’s not obvious at 11pm when you’re exhausted from a twelve-hour shoot and just want to clear your cards for tomorrow. Put a physical rubber band around every card you haven’t verified yet. It sounds analog and slightly ridiculous. It works.

A reliable file system isn’t glamorous work. Nobody hires you because of your folder structure. But they will stop hiring you because of its absence, the first time you can’t deliver a file, can’t find a frame, or lose something that can’t be re-shot.

Build the system once. Run it every time. The cost of not doing so always arrives at the worst possible moment.