A real estate filing system that survives an audit.

Most brokerage filing systems are built forward from habit. Here is one built backward from what an auditor actually asks for.

Forward design starts with whoever set up the drive first and grows by accretion. Someone adds a folder for inspections, someone else adds one for repairs, a third person starts putting repair addenda in the contract folder because that felt right at the time. Nothing is wrong on any single day, and after two years nobody can find a lead paint disclosure without opening four folders.

Backward design starts from the request list. A state commission audit follows a predictable order, and the order is worth memorizing because it tells you what to optimize for.

The order requests arrive in

First comes a list of transactions closed in the review period, usually pulled by date range and office. The list itself is a test. A brokerage that cannot produce a clean transaction register in an afternoon has already told the reviewer something about how the rest of the review will go.

Second comes a sample of files pulled from that list, typically ten to thirty deals chosen by the reviewer rather than by the office. Sampling is the reason consistency beats perfection. One immaculate file and nine improvised ones score worse than ten files that are merely complete, because the reviewer expands the sample when the first pulls come back thin.

Third comes specific documents inside those files. The contract with every amendment, the agency disclosures with dates, the earnest money receipt matched to a deposit, the commission disbursement authorization matched to the settlement statement. Fourth comes the supervision layer, meaning evidence that a broker reviewed the file rather than simply storing it.

What that implies for structure

Three design rules fall out of the request order. Categories must match the way documents are requested, not the way they arrive. Every file must carry the same categories whether or not each one is populated, so an empty folder becomes visible evidence rather than a silent gap. And retrieval time is the metric that matters, because a reviewer who waits twenty minutes for a disclosure starts wondering what else is slow.

The structure below is one worked example, shown in full. It splits by transaction, then by document category, with side handled at the transaction level rather than as a folder layer.

Why side lives in the transaction, not the folders

Brokerages that represent both sides sometimes build parallel buyer and seller trees inside one deal. That doubles the categories and creates an argument every time a document belongs to both sides, which the contract and the settlement statement always do. Cleaner to keep one file per transaction, record the represented side in the file header, and open a second transaction record when the office holds both sides under an intermediary or dual agency arrangement that requires separate handling.

Numbered prefixes are doing real work

The two digit prefixes force sort order to match review order in every operating system and every document system, without anyone having to configure a custom sort. They also make verbal reference precise. Asking a coordinator to check 05 for the deposit confirmation removes a step that a phrase like the earnest money folder does not.

Depth stops at two levels

Only 01 Contract carries subfolders, because it is the only category that reliably holds enough documents to need them. Three levels of nesting looks organized and performs badly. Every extra level is another place to misfile and another click during a review, and past two levels people start guessing.

The summary folder earns its place

A one page term sheet at the top of the file gives a reviewer, a covering coordinator or a broker on vacation the governing terms without reading the chain. Price, effective date, key deadlines, parties, commission split and the current status. It takes five minutes to produce at acceptance and saves the same hour every time somebody new touches the file.

Structure decides where a document lives. Naming decides whether anyone finds it once it is there. The two have to be designed together, since a strict tree filled with names like scan_004.pdf performs no better than a flat drive.

The pattern that holds up

Date first in ISO order, then document type, then a qualifier, then version if one is needed. So 2026-03-04 Contract Executed, or 2026-03-11 Amendment 02 Repair Credit, or 2026-03-06 Disclosure Lead Paint Signed. Date first sorts chronologically by default, which is the order a reviewer reads a file in.

Avoid initials, personal shorthand and status words that go stale. Final, latest and new are the three worst tokens in any brokerage drive, because there is always a later final. Version numbers are unambiguous and initials tell a reviewer nothing about the document. Solid document management for brokerages applies the pattern at upload so it does not depend on whoever is filing that day.

What goes in the name and what does not

The property address does not belong in the file name. It is already in the folder name, and repeating it makes every name long enough to truncate in list views. Agent names do not belong there either. What belongs is date, type, qualifier and version, in that order, every time.

Not everything in a transaction file carries the same weight. Sorting the required from the discretionary tells you where to spend effort when a backlog needs triage and what to check before a file is marked closed.

Required means findable in minutes

The executed contract, every amendment, the agency disclosures, the representation agreements, the statutory property disclosures, the earnest money record, the settlement statement and the commission disbursement authorization. These are the documents a reviewer asks for by name, and each one has to be complete rather than merely present. A contract missing the initials page is a missing contract for audit purposes.

Discretionary means useful, not defensive

Inspection reports, vendor invoices, showing feedback, scheduling threads and marketing material. Keep them because they help the next person, and keep them out of the categories a reviewer reads first. Correspondence is the category that swallows files if nobody sets a rule, so the rule is simple. Written communication that changes an obligation gets filed. Everything else does not.

Empty is a finding, missing is a bigger one

A category folder that exists and sits empty tells a reviewer the office knows what belongs there and this deal did not generate it. A category that does not exist at all reads as a system that never asked the question. Build the full tree on every file, including the categories that will stay empty on most deals.

An office in one state runs one rule set. Add a second state and the retention clock, the required forms and the supervision evidence all change, while the people filing the documents mostly do not.

Keep the tree, vary the contents

The structure should be identical across every office. What varies is which documents populate 07 Compliance and how long the whole file is held. Standard categories with state specific contents give a regional broker one mental model instead of four, and give a reviewer in any state the layout they were promised.

Retention runs per office

Retention is set by the state where the transaction occurred, not where the brokerage is headquartered. California requires three years, Texas four, Florida five and New York three, so a file in a five state operation can hold anything from three to seven years depending on where the property sits. Verify each period with the state commission before writing policy, because the rules change and several states run a longer clock on trust account records than on transaction files. The practical answer for most multi-state offices is to set the retention policy to the longest applicable period and apply it everywhere, since the cost of extra storage is smaller than the cost of tracking five clocks.

State specific forms live in one place

Intermediary consent in Texas, transfer disclosure in California, agency form timing in New York, property condition requirements in Florida. Put every state specific item in 07 Compliance rather than scattering them into whichever category they resemble, and maintain a one page checklist per office naming exactly what 07 must contain for that state.

Access follows office

Coordinators should see their office by default and other offices by exception. This is a filing decision as much as a permissions decision, since a drive where everyone sees everything eventually becomes a drive where anyone can move anything.

No office rebuilds four years of files at once. Triage in order, and accept that the oldest material may never be restructured beyond being findable.

The triage order

Start with active transactions. Every deal currently in flight moves into the new tree as it progresses, which costs almost nothing because the documents are arriving anyway. Second, files closed inside the last twelve months, since these are the most likely to be sampled and the most likely to generate a question. Third, anything already flagged by a prior audit, a complaint or a legal hold, regardless of age. Fourth, the remaining files inside the retention window, worked backward from most recent. Fifth, everything past retention, which gets a disposition decision rather than a migration.

Move, then improve

Two passes beat one perfect pass. First pass gets every document into the right category folder with whatever name it already has. Second pass renames to the standard. Splitting the work this way means the file is navigable after the first pass, which is the pass most offices actually finish.

Record what cannot be fixed

Some old files are missing documents that no longer exist anywhere. Note the gap in the summary folder with the date it was identified and what was done to look. A documented gap with a search record reads very differently to a reviewer than a silent hole, and the note takes two minutes.

Freeze the old drive

Once migration starts, make the old location read only. A live legacy drive and a new tree running side by side produce two partial files per deal, which is worse than the mess being replaced. Read only forces every new document into the new system on day one.

Questions brokers ask