Document naming conventions for transaction files.

A naming convention decides whether a file is searchable in three years. Here is a convention you can adopt whole, with the version rules.

Naming feels like tidiness and behaves like infrastructure. Nobody notices a bad name on the day the document is filed, because the person filing it just read it and knows exactly what it is. The cost lands later, when a different person opens the folder with no memory of the deal.

The three years later test

Apply one question to every name: can somebody who never worked this deal tell what this document is, when it was executed, which side it belongs to, and whether it governs, without opening it? A name that fails that test is a name that will cost somebody time during a review, a dispute, or a license audit years after the coordinator who filed it has left.

Three years is the right horizon because it is the shortest state retention period in common use. California requires three years, New York three, Texas four and Florida five, so the documents being named today will be requested by somebody with no context on the deal at some point inside that window.

Folder structure and naming solve different halves

Structure decides where a document lives. Naming decides whether it can be identified once it is there. A strict filing system filled with names like scan_0012.pdf performs the same as no system at all, because the reviewer still has to open every file in the folder to find the one they asked for.

Search is the real user

Most retrieval now happens through a search box rather than by browsing folders. That changes the economics of naming completely. A searcher typing amendment expects to see every amendment across every file in the office, correctly ordered by date, with subjects visible in the result list. That only works when the tokens in the name are the tokens people actually type.

The pattern is date, side, document type, sequence, qualifier, status. Not every element applies to every document, and the ones that apply always appear in that order.

The five tokens

Date comes first in ISO format, year then month then day, using the execution or signature date rather than the upload date. Side is a single letter, B or S, present only when a document belongs to one side. Document type is the searchable noun and should match the vocabulary people use out loud. Sequence is a zero padded number for anything that comes in a series, meaning amendments, counters and extensions. Qualifier is two or three words naming the subject, used when a document type repeats. Status closes the name with Draft, a version number, Executed, Signed or Superseded.

Rules that keep the pattern stable

Spaces rather than underscores, since every current system handles spaces and underscores make names harder to read at small sizes. No property address, because the folder carries it. No agent names or initials. No status words that expire, which rules out final, latest, new and current. Zero padded sequence numbers so 02 sorts before 10. Title case throughout, which keeps mixed capitalization from splitting search results.

Versioning is where most conventions break, because a transaction produces three different kinds of change and offices tend to treat them all the same way.

Drafts are versions

A document being negotiated inside one side carries v1, v2, v3 until it is signed. Repair requests, listing agreement drafts and unsigned addenda all behave this way. Version numbers only increase, and a version is never overwritten by a later one under the same name.

Executed is a status, not a version

Once a document is fully signed the status token becomes Executed, and the version number drops out of the name. This is what replaces the word final. There is only ever one executed copy of a given document, so the name is unambiguous by construction, and nobody has to decide whether final or final v2 is the real one.

Amendments are documents, not versions

An amendment does not create a new version of the contract. The contract keeps its name and its executed status, and the amendment arrives as a separate numbered document with its own execution date. This matters at review, because a reviewer reading a contract needs to see at a glance that three amendments follow it rather than hunting for the current combined version.

Superseded documents stay

When a document is replaced, append Superseded to its name and move it into the archive subfolder. Deleting the prior version removes evidence that can decide a dispute over what was agreed and when. The rejected counters in a negotiation chain are the clearest case, since the chain itself is what proves the sequence of offers.

A convention that lives in a training document and not in a workflow lasts about six weeks. Enforcement needs a named owner at each stage and a checkpoint where misses get caught.

Rename at upload

The person who files the document names it, at the moment of filing, while they still know what it is. This is the single rule that matters most. A name applied at upload is applied by somebody with the document open in front of them. A name applied during a cleanup two months later is applied by somebody guessing from a thumbnail.

Check at review

File review is the checkpoint. A broker or compliance reviewer working through a file for sign off is already opening every document, so catching a misnamed one costs nothing extra. Fix it then rather than logging it, because a list of naming corrections is a list nobody works through. Adopting standardized document naming at the platform level removes most of this from human hands, since the document type and date are captured at upload rather than typed.

One page, not a manual

The convention belongs on one page with the reference table above and nothing else. Ten pages of naming policy gets skimmed once. A single table pinned where coordinators can see it gets used daily and gets shown to new hires in five minutes.

Do not run a cleanup project first

Start applying the convention to new documents today and rename historical files in the order they are likely to be needed, meaning active deals first, then recent closings. Offices that decide to rename four years of archives before adopting the standard usually finish neither.

Consistent names stop being a filing nicety once a system reads them, because a predictable name is a machine readable label describing what a document is and what it satisfies.

Document to task matching

A checklist item named executed contract and a document named 2026-03-04 B Contract Executed can be matched without a human deciding they are the same thing. That is the mechanism behind checklist items marking themselves complete on upload. Inconsistent names break the match, and the task stays open next to a document that already satisfies it, which is how files end up looking incomplete when they are not.

Deadline extraction

Names carrying an ISO execution date let a system order documents on a timeline and compare that order against contract deadlines. An inspection contingency removal dated after the inspection deadline is a flag a system can raise on its own, and only if the date in the name is the execution date rather than the upload date.

Completeness checks at closing

Closing checks compare what the file contains against what a transaction of that type requires. That comparison runs on document types, so a file where every document carries a recognized type token can be checked in seconds while a file of ambiguous names has to be reviewed by hand.

Reporting across the office

Consistent naming across every file makes office wide questions answerable. How many amendments the average transaction carries, which document type most often arrives late, which office is slowest to file executed contracts. None of those are answerable when the same document goes by five different names across five coordinators.

Questions brokers ask