Most file organization systems start well and quietly fall apart within a few months — not because the initial idea was bad, but because it wasn't built to survive the mess of everyday use. A system that actually holds up is usually simpler than people expect, and consistency matters more than cleverness.
Fewer, broader folders beat many narrow ones
A deeply nested folder structure (Documents > Work > 2026 > Q2 > Projects > ClientA > Contracts > Signed) is exhausting to navigate and easy to file things into the wrong branch of. A flatter structure with a handful of broad top-level categories, relying more on clear file naming than folder depth to add specificity, tends to survive daily use far better — it's faster to file something correctly when there are fewer decisions to make about where it goes.
A naming convention that sorts itself
Starting filenames with a date in YYYY-MM-DD format (rather than MM-DD-YYYY or a written-out month) makes files sort chronologically by default in any file browser, without needing to manually organize by date. Following the date with a short, specific description — 2026-06-29-client-contract-signed.pdf rather than just contract-final-v2.pdf — makes files identifiable from the name alone, without needing to open each one to check what it actually is.
The "final" and "v2" trap
Filenames like final, final-v2, and final-FINAL are a near-universal sign of a naming convention that's broken down under real use — usually because there wasn't a clear system for versioning to begin with. A consistent version number or date in every filename (v3, or a date-based name that updates each time) avoids this ambiguity entirely, since it's always clear which one is actually the most recent without relying on the word "final" to mean anything reliable.
Bundling related files together
For a set of files that belong together — all the documents for one project, or every receipt for one trip — bundling them into a single archive keeps them from getting scattered across a folder over time, and makes the whole set easy to move, back up, or share as one unit rather than several loose files that are easy to lose track of.
Periodic cleanup, not constant maintenance
A system that requires constant, careful maintenance to stay organized usually doesn't survive busy periods. A better approach: file things reasonably well as you go (following a simple, consistent convention), and set aside a short, periodic cleanup pass — monthly or quarterly — to catch anything that slipped through, rather than expecting perfection in the moment.
When it's time to archive a completed project or a batch of related files together, Create Archive bundles them into a single ZIP. If a project's documents are spread across several separate PDFs that belong together, Merge PDF can consolidate them into one file first.