How to Organize Work Documents as PDF (Folders, Names, Versions)
Last updated
The problem with work PDFs isn't usually the PDFs themselves. It's the trail: thirty files with similar names in a downloads folder, versions that don't line up, finals that aren't final, drafts that look identical to deliverables. The format is fine; the convention around the format is what falls apart.
A working convention is short — a folder structure, a naming pattern, and a habit about where finals go. Once it's in place, finding 'the contract we sent in March' takes ten seconds rather than ten minutes, and version conflicts mostly stop happening.
This guide describes the convention we've watched small teams adopt and stick with. It's not the only convention that works; it's one that's robust enough to survive a busy quarter without falling apart.
Step by step
- 1
Pick a top-level folder layout once
Clients/ContractName/, Internal/, Templates/, Archive/. Four folders cover most of it. Don't nest more than two levels deep at first — depth gets you lost.
- 2
Standardize the filename pattern
ClientName_DocType_vN_YYYY-MM-DD.pdf reads cleanly in any file browser. Date last so files sort chronologically; version inline so you can spot the latest at a glance.
- 3
Separate /drafts and /final inside each project
Drafts go in the project's /drafts subfolder; finals get renamed to FINAL and moved to /final or /deliverables. The /final folder should only contain shipped versions.
- 4
Use Merge PDF to consolidate at handoff
When a deliverable is actually three PDFs (proposal + terms + pricing), merge them into one for delivery and keep the source files in the project folder. The recipient gets one clean file.
- 5
Compress and re-name only at delivery
Compress PDF for the outgoing copy; keep the uncompressed source. The delivered file goes in /final/, the source stays in /drafts/. They're different artifacts.
- 6
Archive completed projects on a schedule
Move closed projects to /Archive/ quarterly. Active folders stay scannable; the archive is searchable when you need to find something later.
Tips
- Avoid spaces in filenames if you can — underscores or hyphens are easier in URLs, email forwards and shell commands.
- Date format YYYY-MM-DD sorts chronologically in any tool. 5/29/26 doesn't.
- Don't put version numbers in the FINAL filename. FINAL is FINAL. If something changes after, it's FINAL-2 — and that's a flag the process broke down.
- Don't fear the rename. A clear filename is worth a minute of work, especially before sending.
- Keep a one-line index file (README.txt) in big projects listing what's in each subfolder. Helps the future-you who comes back six months later.
Try it on your phone
On a phone, organization gets harder because filename editing is fiddly. The PDF Editor app lets you rename, tag and file PDFs from mobile so files arriving on the phone don't pile up unnamed in the Downloads folder.
