Use file names that survive real collaboration

final_FINAL_v2_reallyfinal.pdf is not a joke because people are careless. It is what happens when a team has no shared rule for naming, review, approval, and archive copies. Each person adds a word that makes sense in the moment, then the folder becomes a pile of near-duplicates that nobody wants to delete.

The cost appears later. You send the wrong contract, quote an old policy, attach the pre-signature version, or spend ten minutes opening files just to find the one that changed yesterday. A naming convention is a small piece of operational infrastructure. It lets ordinary folders, search results, email attachments, and portal uploads stay understandable.

Put dates in the order computers sort

Use ISO date prefixes: year, month, day. 2026-08-10 sorts correctly as text, so alphabetical order and chronological order agree. 10-08-2026 and 08-10-2026 are ambiguous across countries, and month names sort alphabetically rather than by calendar order.

Put the date at the start when the date is the main way you find the file: statements, minutes, signed forms, submissions, invoices, and dated evidence. A folder full of 2026-07-31-bank-statement.pdf and 2026-08-31-bank-statement.pdf will arrange itself without you switching views or trusting the file system's modified date. Modified dates change when files are copied, downloaded, or touched by software; the date in the name records the document's intended date.

For undated working drafts, use the date of the draft or review cycle. The point is not to encode every fact into the name. The point is to put the most useful sorting fact where every tool can see it.

Use a consistent field order

Pick a field order and keep it. A practical pattern is date, subject, document type, version: 2026-08-10-smith-tenancy-agreement-v03.pdf. For a business folder you might add a client or project code: 2026-08-10-acme-proposal-v02.pdf. For personal records, a shorter subject may be enough.

Keep each field short and predictable. tenancy-agreement is better than flat paperwork new one Rahul edits because the same phrase can be reused next time. Document type matters because a folder may contain a proposal, agreement, invoice, receipt, and correspondence for the same subject on the same day.

Avoid spaces and characters that break links, scripts, and command-line tools. Hyphens or underscores are safer than spaces. Avoid slashes, colons, question marks, ampersands, emoji, and smart punctuation. They may work on your laptop but break in a portal, a shared drive, a ZIP file, or a shell command. Keep names short enough that the whole path remains manageable; deeply nested folders plus long file names can hit path limits or become unreadable in dialogs.

Make version numbers sort properly

Use zero-padded version numbers: v01, v02, v03. Without padding, some systems place v10 before v2, which is exactly the confusion the convention is meant to prevent. Put the version near the end so related documents still group by date and subject.

Borrow the idea of semantic versioning, but adapt it to documents. A major revision changes the substance: a new price, a changed clause, a different scope, a replaced calculation, or a new approval round. A minor correction fixes spelling, formatting, page numbering, or a typo that does not change meaning. You might express that as v03 for major working versions and v03-1 for a minor correction, or keep a simple v04 every time anything changes. The exact scheme matters less than everyone knowing what a version bump means.

Do not use final as a version number. If a document is approved, mark the authoritative copy with a status word such as signed, submitted, or approved: 2026-08-10-smith-tenancy-agreement-signed.pdf. Keep the last draft as a draft. The signed copy is a different state, not just a more emotional version of final.

Archive superseded copies instead of deleting them

Deleting old versions feels tidy until someone asks what changed. Move superseded copies into an archive or superseded folder and keep the same names. If a file was sent externally, store the sent copy exactly as sent. That lets you answer later questions without relying on memory.

Mark the authoritative copy in one obvious place. That might be a folder named current, a file suffix such as approved, or a short index note in the folder. Avoid having two files that both claim to be current. If two people exchange files, agree who owns the authoritative copy after each review round.

A content hash helps when names lie. Two files can have different names and the same bytes, or the same name and different bytes. Use the PDF fingerprint tool to calculate a hash for each copy. If the hashes match, the files are byte-for-byte identical. If they differ, use compare PDFs to inspect whether the change is visible text, layout, metadata, or something else.

Agree the convention with other people

A convention followed by one person is just a habit. If you exchange files with a client, broker, accountant, designer, landlord, or colleague, write the pattern in one sentence and share examples. Please use YYYY-MM-DD-subject-type-vNN.pdf is enough for many small workflows.

Be realistic. Some portals rename uploads. Some counterparties will send scan.pdf no matter what you ask. Rename incoming files when you save them, but keep the original if the original name is evidence. If a document's page order is part of the version, fix that before naming the authoritative copy; the organize pages tool can put pages in the intended order before the file enters your version history.

The best convention is boring. It should be easy to type, easy to read over the phone, and understandable six months later when you are no longer thinking about the project.

A short checklist

• Start names with YYYY-MM-DD when date order matters.
• Use a stable field order such as date, subject, document type, version.
• Use v01, v02, and v03, not final or unpadded numbers.
• Avoid spaces and punctuation that break links, portals, and command-line tools.
• Mark the authoritative copy and archive superseded ones.
• Use a fingerprint when two copies have different names and you need to know whether the bytes are identical.