A naming convention nobody has time to follow.
Every firm has a file-naming standard, written down somewhere, ignored by Wednesday. Not because anyone disagrees with it, but because following it means renaming "scan_0473.pdf" and "IMG_4471.pdf" one file at a time, at intake, while three other matters are also due. Below is a practical convention worth adopting, the honest reason it keeps slipping, and what finally makes it stick.
General information for legal professionals. This is not legal advice. Read the full disclaimer.
You already know why naming matters. A clean, consistent name means finding the 2020 tax return in two seconds instead of opening nine PDFs. It lets an associate pick up a colleague's matter without a tour. It keeps a production free of duplicates and gaps. The problem was never the convention. The problem is the hundred small acts of discipline it takes to apply one, every day, under deadline.
A convention worth adopting
The details matter less than the consistency. A standard that holds up across firms uses a leading date, then who and what, then a version. The components, in order:
- Date first, in ISO format.
YYYY-MM-DD(orYYYYMMDD) at the front of the name so the folder sorts itself chronologically. "2024-03-14" sorts correctly; "3-14-24" does not, and "March 14" sorts alphabetically into nonsense. - Client or matter identifier. A short, stable token for the matter, so a file is self-identifying even when it's pulled out of its folder and emailed.
- Document type, then a short description. "Tax-Return," "Bank-Statement," "Decree," "Demand," followed by just enough to disambiguate (the year, the account's last four, the provider).
- An explicit version, never a vague one.
_v1,_v2,_v3-FINAL, not "new," "updated," or the dreaded "final-final-USE-THIS." - No spaces or special characters. Use hyphens or underscores. Spaces, slashes, and ampersands break links, scripts, and the occasional upload, and they make a file harder to handle in bulk.
So a messy intake of scan_002.pdf becomes 2024-04-30_Doe_Bank-Statement_Wells-8821.pdf, and a year of those sorts itself into a record you can read down a folder.
Folders the names live in
A naming convention works best inside a matter-centric folder structure your whole firm shares: one folder per matter, with the same predictable subfolders inside every one (pleadings, discovery, correspondence, client documents, court orders). The names and the folders serve the same goal: any file's identity and home should be obvious without anyone having to ask. Pick one structure, write it down, and make it the path of least resistance rather than a rule people route around.
Why the standard keeps slipping
A naming convention is only as good as the discipline to follow it on the worst day: the day a client emails forty unlabeled PDFs an hour before a filing. That's exactly when the careful name gets skipped, the file gets dropped in as document(3).pdf, and the convention quietly dies one shortcut at a time. The cost isn't abstract. It's the twenty minutes someone loses next month hunting for that file, the duplicate that surfaces in a production, the associate onboarding into a folder no one curated. Multiply it across every matter and the tax is real. It lands hardest on your busiest people.
What finally makes it stick
A convention sticks when following it stops being a chore. That is what DilloLex is built to do.
You drop the client's files into the matter folder exactly as you do today. The appliance reads each one, in English and Spanish, identifies what it actually is, and proposes a clean name in your firm's convention, with the source line shown so your staff can verify the date, party, and amount at a glance. Nothing is renamed without a person approving it. The classifier is configured to your folder structure and naming conventions during onboarding, so it fits your firm's vocabulary rather than guessing from generic patterns.
The result is the convention you already wrote down, finally followed on every file, including the forty that landed an hour before the deadline. Your staff reviews names instead of inventing them, and the folder stays readable without anyone spending an evening on it.
The same discipline, downstream
Consistent names are not the end; they are what makes everything downstream fast. Once every document is identified and named, the appliance can organize the matter, surface the PII to redact, and assemble the work product the matter needs: the financial production behind an NRCP 16.2 disclosure, the records and bills in a PI demand package, a Bates stamped production. The clean name at intake is the first domino.
Common questions
What is the best file-naming convention for a law firm?
A consistent one, applied firm-wide. A standard that holds up is a leading ISO date (YYYY-MM-DD), then a short client or matter identifier, then the document type and a brief description, then an explicit version, with hyphens or underscores instead of spaces. The exact tokens matter less than everyone using the same ones.
Should the date go first in a legal file name?
Usually yes. Putting the date first, in ISO format, makes a folder sort itself chronologically, which is how legal files are most often read: in the order events happened. Use a leading date unless your matter is better organized by document type, in which case lead with type and keep the date right behind it.
What date format should legal files use?
ISO 8601: YYYY-MM-DD or YYYYMMDD. It sorts correctly as text, avoids the US/international ambiguity of formats like 03-04-2024, and stays unambiguous when a file is pulled out of its folder.
Should I use spaces in file names?
Better not to. Spaces and special characters (slashes, ampersands, colons) can break links, scripts, and some uploads, and they make files harder to handle in bulk. Use hyphens or underscores to separate the parts of the name.
How should drafts and versions be named?
With an explicit version token, never a vague word. Use _v1, _v2, _v3-FINAL so the latest is obvious and the history is preserved. Avoid "new," "updated," and "final" used as if they were versions, they stop meaning anything by the third draft.
A note on accuracy
This guide is general information for legal professionals. It is not legal advice, it does not create an attorney-client relationship, and it does not address the records-retention, confidentiality, or e-discovery requirements of any specific matter, court, or jurisdiction. Confirm your firm's retention schedule and any applicable rules before adopting a file-management practice. DilloLex proposes names and organization for your staff to review and approve; nothing is renamed without a person's sign-off. Every output is intended for review as decision support; the supervising attorney is responsible for reviewing, verifying, and approving all work product and for all professional and ethical obligations to clients.