Filename patterns per document type

Step by step — set up the convention

1. Pick the client-code list. 3–6 uppercase chars per client. Save the master list as `clients.txt` at the top of your file store.
2. Pick the document-type prefixes (INV, CONTRACT, PROPOSAL, DELIVERABLE, RECEIPT, INTERNAL). Keep the list short and stable.
3. Set up the folder structure. `Clients/{ClientCode}/{YYYY}/{type-folder}/` — folder for categorical context, filename for specifics.
4. Retroactively rename a sample folder using PowerRename / Finder rename. Validate it sorts as expected before committing across all files.
5. Document the convention in a single page in your team wiki or shared note. New hires onboard against the same convention.

Folder structure that pairs with the filename convention

Filenames carry the specifics; folders carry the categorical context. The pattern I have seen scale to dozens of clients and hundreds of projects is: `Clients/{ClientCode}/{Year}/{TypeFolder}/{filename}`. Each level adds a single dimension of context. ClientCode at the top makes the file store organised around the customer relationship. Year underneath gives natural archive boundaries (close the year, archive its folder). TypeFolder (contracts, invoices, proposals, deliverables) groups documents by what they are.

Avoid deeper nesting than four levels (Clients/{Code}/{Year}/{Type}/{file}). More levels add cognitive load when navigating manually; the filename should carry the rest. Avoid "Old" / "New" / "Final" folders — categorical, not chronological, and they accumulate ambiguous content. Use date-prefixed filenames so chronology is visible in the filename itself.

Retention rules per document type

Different document types have different retention requirements. Tax-relevant documents (invoices, receipts, 1099s) retain at least 7 years per IRS guidance. Contracts retain at least the contract term plus the local statute-of-limitations period (typically 4–6 years). Marketing PDFs (one-pagers, brochures) retain only as long as they are current; archive obsolete versions. Personnel records retain per FLSA and state law (typically 4 years minimum). Encode the retention rule in the folder structure (a `Tax/` folder retained 7 years; a `Marketing/` folder culled annually) so the rule is enforced by where the file lives, not by ongoing human discipline.

Convention drift and how to prevent it

Naming conventions drift naturally over time as people forget the exact pattern, new team members improvise variations, and one-off exceptions become precedents. Three habits keep conventions consistent. First, document the convention in one page and pin it where new hires will see it. Second, audit a sample of files quarterly — pick 20 recent files and check each follows the pattern; if more than two deviate, refresh the team on the convention. Third, build the convention into your client-onboarding template: every new project gets a folder structured correctly from day one, so there is no opportunity for ad-hoc naming to take hold. Convention discipline compounds; convention drift compounds too. Catch it early.

One last note on filename length. Some file systems and cloud sync services cap filename length at 255 characters; very long client names plus long project slugs plus version codes plus extensions can hit this. Keep individual filenames under 120 characters as a safe budget. If your slug pattern keeps producing longer names, abbreviate the client code further or trim the project slug. Hitting the file-system limit at the wrong moment (sync failure during a deadline) is the kind of preventable problem that lingers in collective memory for years.

Related reading

• Small-business PDF tools: the wider free-tool stack.
• PDF for freelancers: client-folder organisation for solo work.
• PDF metadata editor: keep file metadata aligned with the filename.
• PDF to PDF/A: long-term archive format for retained files.
• PDF for accountants: retention rules per document class.

FAQ

Why date-prefix the filename instead of sorting by file-modified-date?

Three reasons. First, the date in the filename is the document date (when the invoice was issued, when the contract was signed), not the file-system date (which changes every time the file is touched or moved between systems). Second, lexicographic sort on YYYYMMDD always produces chronological order in any file manager, on any OS, without sort-by-date configuration. Third, the date is visible at a glance when scanning a folder, no hovering or column toggling needed. Use YYYYMMDD specifically (not DD-MM-YYYY or MM-DD-YYYY) — only YYYYMMDD lexically sorts to chronological order.

What client code should I use — full name, abbreviation, or internal ID?

A 3–6 character uppercase abbreviation works best. "ACME" for Acme Corp, "RKLAB" for RK Labs, "SMTHASSOC" for Smith & Associates. Long enough to be unambiguous in a list of 50 clients; short enough to keep filenames manageable. Keep a master list (a single text file or spreadsheet) of client-to-code mappings to avoid drift. Avoid using internal CRM IDs as the client code — they are not human-readable and you may move CRMs. Avoid full client names — they break sort and make filenames unwieldy.

Should the version number be in the filename or in the file content?

Both, but the filename version is what your file manager shows. v1, v2, v3 for major drafts; "v3-final" or "v3-signed" for the version that ended a thread. Avoid "FINAL" / "FINAL2" / "FINAL_REALLY" — they fail at scale. The file content can repeat the version (in a footer or metadata) so it travels with the file even when renamed. For team collaboration, also include initials of the last editor in the filename: `20260520-ACME-CONTRACT-MSA-v3-rk.pdf` — the "rk" makes ownership of the latest version obvious.

How do folder structure and filenames work together?

Folders carry the categorical context (which client, which year), filenames carry the specifics (which document, which date, which version). Pattern: `Clients/ACME/2026/contracts/20260520-ACME-CONTRACT-MSA-v2.pdf`. The filename is meaningful when copied out of the folder; the folder structure adds discoverability when browsing. Avoid deep nesting (more than 4 folders deep gets slow to navigate). Avoid folder names like "Final" / "Old" — categorical not chronological.

How do I retroactively rename a folder of badly-named PDFs?

Bulk rename tools handle this efficiently. macOS: Finder → Select files → right-click → Rename. Windows: PowerToys PowerRename. Linux: `rename` command. Define a pattern (e.g. extract date from PDF metadata, append client code based on folder, suffix v1). For per-file context that bulk tools cannot infer (a particular invoice number, a specific version number), do those manually after the bulk rename. Pattern: spend an hour now to clean up 200 files; the time pays back in faster retrieval for years.

Citations

1. ISO 8601 — Date and time format standard (YYYY-MM-DD) used in lexically-sortable filenames.
2. ISO 19005 — "PDF/A" — long-term archival format for retained documents.
3. IRS Publication 583 — record-retention recommendations for small business.