How to Name Legal Documents Consistently

Open any long-running case folder and you will find the archaeology of a dozen busy days: final, final_v2, final_FINAL, scan, scan_new, and a document simply called order. Each name made sense to the person who typed it and to no one afterwards. When a colleague has to file at short notice, or when a matter is handed over, these names cost real time and occasionally cause real errors, such as serving a draft that was never approved. A shared naming convention is the cheapest document-management system a practice can adopt.

Understand why loose names fail

The problem with final_v3 is not that it is untidy; it is that it makes a claim it cannot support. It does not say what the document is, which matter it belongs to, when it was created, or whether anyone approved it. Worse, words like final and approved assert a status that may be untrue, inviting exactly the mistake of treating a draft as settled. Good naming removes assertions the file cannot back up.

Decide the elements every name should carry

A workable convention encodes a few facts in a fixed order so that names sort and scan sensibly. Most practices need some combination of:

• Date, written so files sort chronologically, such as year-month-day at the front.
• Document type: order, plaint, reply, agreement, letter.
• The matter or a short party reference, so a file is recognisable out of its folder.
• A true status: draft, executed, filed.

Kept short and consistent, these turn an opaque filename into a one-line description of the document.

Keep status words honest

The most useful discipline is to reserve loaded words for facts. Do not label a document filed until it has actually been filed, or approved until someone with authority has approved it. A name that overstates status is more dangerous than a vague one, because it invites reliance. When in doubt, name the document by what it verifiably is, and let the index or the workflow record what has happened to it.

Test the pattern on real documents

Before circulating a convention, run it against a few genuine files: a court order, a client letter, a draft pleading, a scanned exhibit. If any of them produces an awkward or ambiguous name, adjust the pattern now rather than after the team has adopted it. Check that names remain readable on a phone screen, where much filing and forwarding actually happens, and that they do not rely on characters some systems mishandle.

Account for scans and regional-language files

Scanned and photographed documents arrive with meaningless camera names, and regional-language files may carry titles in a script the folder does not sort cleanly. Rename these to the convention as they enter the file, using the document's real date and type rather than the device's. Where the content is locked in an image, a quick text extraction helps you read the parties and date so the name reflects the document rather than a guess.

Publish it and rename the working set

A convention that lives in one person's head is not a convention. Write it down in a few lines, share it with everyone who touches the files, and apply it first to the active working set rather than attempting the whole archive at once. Consistency going forward matters more than a perfect retrospective cleanup.

Naming is a small habit, but it is the layer everything else, indexing, search, handover, rests on. Get it right and the file stays legible long after the day that produced it is forgotten.