Setting Up a Matter Naming Convention

The same dispute is filed under the client's name in one associate's folder, the opposing party's name in another's, the case number in the accounts file, and "the property matter" in everyone's WhatsApp. When it is time to find the papers, or hand the matter to a colleague, half an hour goes to working out that these are all the same thing. Naming is not clerical trivia. In a chamber that runs dozens of matters, the naming convention is the index to everything, and an inconsistent one quietly taxes every search, every handover, and every audit.

Choose an identifier that never changes

The anchor of any convention is a stable identifier that survives everything the matter will throw at it. Party names change, causes get renamed, the same client brings ten matters, so none of those can be the primary key. Assign each matter a short unique code at intake, a running number, perhaps prefixed by year, and let that code be the one thing that never varies. Everything else about the matter can shift; the code is the constant that ties the file, the tasks, the calendar entries, and the correspondence together.

Pair the code with a name humans can read

A bare code is reliable but unusable; nobody remembers that 2026-041 is the tenancy dispute. Pair the stable code with a short, readable title that tells a person what the matter is, and fix the order of its parts so titles sort predictably. A workable shape is code, then client, then a two- or three-word descriptor:

• 2026-041 Mehta – Andheri tenancy eviction
• 2026-042 Sharma Exports – supply contract dispute

The code makes it findable by machine; the title makes it recognisable by people. Both matter, and keeping them together in a fixed order is what makes a folder list scannable.

Test the name everywhere it will live

A convention that reads well in a folder can break in a calendar or a message thread. Before adopting it, run a sample name through every place a matter's name appears, filenames, task lists, calendar entries, email subjects, billing, and check it stays legible and sortable in each. Watch for length limits, characters a filesystem rejects, and titles that truncate to something ambiguous. A name is only as good as its behaviour in the worst-behaved system that has to hold it.

Decide the hard cases in advance

Every convention meets edge cases, and unresolved edge cases are where inconsistency creeps back in. Write down the answers before they arise:

• Confidential matters where the party name should not appear in a title.
• Two clients with the same surname.
• A matter that spawns related matters or appeals.
• Transfers between forums, where the case number changes but the matter does not.

Documenting these once means everyone handles them the same way, instead of each person inventing a fix that the next person will not recognise.

Give someone ownership of consistency

A convention with no owner drifts within weeks. As soon as one person under pressure names a file their own way, the discipline starts to erode. Name a single person responsible for enforcing the standard, catching duplicates, merging inconsistent labels, and applying the code at intake before a matter acquires informal names. In a shared matter workspace, such as Juniorlawyer, the identifier can be attached once at intake and carried automatically wherever the matter appears, which removes most of the chance for drift.

Publish examples and keep them visible

People follow a convention they can copy, not one they have to interpret from a rulebook. Put a handful of worked examples where the team sees them, covering the ordinary case and the awkward ones, and keep them current as new situations are decided. The goal is that naming a new matter correctly is the path of least resistance, so that consistency happens by default rather than by constant correction.