PDF naming in the matter file: a scheme that survives handoffs

“final_v3_really_new.pdf” is not a scheme. It is a symptom. When associates, support staff, and external counsel use different naming logics, the wrong exhibit lands in the filing pack - or nobody finds the filed version six months later.

Good PDF names are dull and predictable. They carry matter reference, document role, and date so sorting and search work without tribal knowledge. That is organisational work, not cosmetics.

Building blocks that hold up

A durable pattern usually includes:

1. Matter or file reference (stable inside the firm).
2. Short document type from a closed list (pleading, exhibit, authority, invoice).
3. Date in ISO form YYYY-MM-DD for chronological sorting.
4. Optional: short status mark (draft, approved, filed).

Example structure: 2024-0147_Exhibit-K3_2024-11-03_filed.pdf. Avoid leading spaces, treat diacritics in portal-critical upload names only under an internal rule, and special characters that sync tools break.

What names need not do

The filename replaces neither the matter note nor version control in the DMS. It should make the right file identifiable in the right minute. Long descriptions belong in metadata or the file note, not in a 120-character name.

Separate working copies and filing copies clearly: _draft and _filed (or equivalent) stop a partner signing the draft while support sends the old version. LexLogik helps with the technical PDF chain; naming discipline remains a team rule.

Rolling out without chaos

Do not rename a thousand legacy matters retrospectively. Start with new matters and active deadline work. Publish a one-page list of allowed document types - ten to fifteen entries usually suffice. Train cover staff expressly: “What are files called when I am off sick?”

Typical pitfalls

• Mixing date formats (03/11/24 vs 2024-11-03) breaks sorting.
• Initials instead of role marks make cover arrangements unreadable.
• “new”, “old”, “corr” without a date create duplicate traps.
• Exhibit numbers in the name must match the exhibit list in the pleading.

Before sending, check the leading characters of filenames in the pack against the exhibit schedule. Five seconds that prevent embarrassing mix-ups.

Align with DMS, filing and portal rules

Check which characters your DMS, sync client, and each court or agency portal accept. Some systems truncate after 80 characters; others fail on brackets or repeated dots. Define a “portal variant” of the name: same logic, technically softened. The internal matter keeps the full scheme name; the upload copy uses the cleaned form and a pointer in the send note. That avoids twin filings with totally different meanings.

Also decide who resolves naming clashes - usually office management with a one-line escalate to the matter lead. Without that ownership, cover weeks recreate “final_new” files.

Cover weeks and naming clashes

When two people create the same exhibit on the same day, “final_new” does not win - the approved role mark in the scheme does. Support logs one line in the matter: who renames, who archives the duplicate. Partners decide only when substance differs - not for spelling variants.

A dull naming scheme survives leave and cover because it sorts without tribal knowledge. Before the next filing, check leading filename characters against the exhibit list - that is the operational test of the scheme.