Systems & SOPs · Template · Published Nov 2, 2026

Law Firm File Naming Conventions: A Template

Every firm has a folder that contains a file called something like Final_FINAL_v3_revised_JS.docx. Nobody knows if it is the signed version, the filed version or the one somebody started editing on Friday. A naming convention will not fix every filing problem, but it fixes that one, and it costs nothing but agreement.

Law firm file naming conventions work when they are short and fixed: start with the date in year-month-day order so files sort correctly, then the matter number, a document type code, a short description and a status suffix such as signed or filed. Avoid characters that OneDrive and SharePoint reject, write the rules down, and check new files weekly.

Key takeaways

  • Put the date first, year-month-day, so files sort in order.
  • Use the matter number, not the client's name, in the file name.
  • A short list of document type codes beats free text.
  • Mark status with suffixes: draft, signed, filed.
  • Avoid characters cloud storage rejects: " * : < > ? / \ |.

A naming convention is one of the smallest procedures in our SOP set and one of the most used. It applies whether your files live in a practice management system, in SharePoint as described in our Microsoft 365 guide, or in Google Drive as in our Google Workspace guide. Immigration firms will want the more specific version for forms and evidence that we publish separately.

What pattern should law firm file naming conventions follow?

One fixed order, used for every file: date, matter number, document type, short description, status. Dates go first in year-month-day order, the ISO 8601 format, because that is the only order in which alphabetical sorting is also chronological. The matter number ties the file to the matter even if it is moved or attached to an email. Using the number rather than the client's name also keeps names out of file listings that may be shared or synced.

The naming pattern, with examples
PartFormatExample
DateYYYY-MM-DD2026-11-04
Matter numberAs in your case system2026-0418
Type codeFrom the code listCORR
DescriptionTwo to five words, hyphenatedopposing-counsel-discovery-letter
Statusdraft, signed, filed (optional)signed
Full nameParts joined by underscores2026-11-04_2026-0418_CORR_opposing-counsel-discovery-letter_signed.pdf
Add naming to your procedure set

The free Deadline Rescue Kit includes the procedure format this convention slots into. Metadata only.

Get the free Template Library

Which document type codes work?

A short list, ten or so, that everyone can remember: CORR for correspondence, PLD for pleadings and filings, ORD for court orders, EVD for evidence and exhibits, FIN for financial documents, ID for identity documents, AGR for agreements, NOTE for internal notes, INV for invoices, and FORM for completed government forms. Resist adding codes for every situation. When something does not fit, the description carries the detail. Put the list at the top of the procedure and in the shared drive's root folder.

One file, named once, found forever Law firm file naming conventions in order: the date in year-month-day form, the matter number, a document type code, a short hyphenated description, and a status suffix such as signed or filed. One file, named once, found forever DateYYYY-MM-DDMatter numbernot the nameType codefrom the listDescriptionshort, hyphenatedStatusdraft, signed, filed Same order, every file, every person
The pattern, left to right. Same order, every file, every person

Which rules prevent the usual mess?

Five rules cover most of it. Never use "final" in a file name; use the status suffix, because there is always another final. Keep versions with v01, v02 during drafting, and drop the version once a document is signed or filed. Use hyphens within parts and underscores between them, and no other punctuation. Avoid the characters Microsoft says OneDrive and SharePoint do not allow in file names, namely " * : < > ? / \ |, plus leading or trailing spaces; some organizations also reject # and %. And keep names short enough to survive deep folder paths, since apps differ in how long a full path can be.

How do you get people to use it?

Make the convention easy and checked. Put two or three real examples at the top of the procedure, since people copy examples rather than rules. Rename incoming scans and email attachments at the moment they are saved to the matter, not later. Include a quick check in the weekly review: five recent files, are they named correctly? When someone gets it wrong, fix the file and show them, without ceremony. Within a month, the convention is habit, and the "which version is this?" conversation stops.

Where we stand FirmFooting builds operational systems. We are not a law firm and do not give legal advice. Systems track, surface and route work; the attorney owns the law, the official docket and every judgment. We work with matter numbers and metadata only, never privileged content. Each system supplements, never replaces, the firm's official docketing and the attorney's own record of critical dates. Nothing here is legal advice.

Where to go next

  • Law Firm SOPs

    Where the convention lives.

  • Microsoft 365 for Small Firms

    Folder structure.

  • Google Workspace for Law Firms

    Drive structure.

  • Systems & SOPs hub

    Every systems brief.

End the "which version is this?" conversation

Get the free Deadline Rescue Kit, or book the free audit. A diagnosis, not a pitch.

Frequently asked questions

What is a good file naming convention for a law firm?

Date in year-month-day order, matter number, a document type code, a short description and an optional status such as signed or filed, joined by underscores.

Should law firm file names include the client's name?

Using the matter number instead keeps names out of file listings that may be shared or synced, while still tying the file to the matter.

Which characters should not be used in file names?

Microsoft says OneDrive and SharePoint do not allow " * : < > ? / \ | or leading and trailing spaces, and some organizations also reject # and %.

Should file names include the word final?

No. Use a status suffix such as signed or filed instead, because drafts called final multiply.

Sources

  1. Microsoft Support, restrictions and limitations in OneDrive and SharePoint. support.microsoft.com
  2. ISO, ISO 8601 date and time format. iso.org