The three-folder system that keeps client files from rotting
Naming conventions fail because they ask you to make a decision. This one removes the decision.
Every file system falls apart at the same point: the moment you are tired, late, and holding a file that does not obviously belong anywhere. Complex systems lose there. A system with three destinations does not, because with three options you are never really choosing.
The three folders
- 01_IN — everything you received. Client photos, briefs, logos, fonts, references. Read-only in spirit: you never edit anything in here, you copy it out.
- 02_WORK — everything in progress. Project files, exports you are not sure about, versions, dead ends. This folder is allowed to be a mess. That is its job.
- 03_OUT — only what you delivered. If it went to the client, it is here. If it did not, it is not.
Same three folders inside every project, forever, no exceptions and no fourth folder. The value is entirely in there being no fourth folder.
Two rules that make it hold
Date-first file names. 2026-06-21_bannerA_v3.png. Sorted by name is sorted by time, on every operating system, in every cloud drive, forever. Never final_final_v2_REAL.
Nothing leaves 02_WORK without a copy landing in 03_OUT. Send it, then copy it. Six months later when a client asks for “the one we used”, 03_OUT answers the question in ten seconds.
Good systems are not the ones with the most structure. They are the ones you still follow at 11pm on a Friday with a file you do not want to think about.
The archive step
When a project ends, zip 02_WORK and leave 01_IN and 03_OUT loose. Working files are large and you almost never open them again; source assets and deliverables are small and you open them constantly. That one step is what keeps a five-year archive navigable.