The broker-compliant transaction file

Ask a broker-owner what keeps them up at night and you will rarely hear “paperwork.” You will hear recruiting, splits, a lawsuit someone mentioned at a conference. But when the letter from the real estate commission actually arrives, it does not ask about splits. It asks for files. And in that moment, everything the brokerage believes about its own diligence collapses into a single question: can you produce the file, complete, right now?

This guide is the answer to that question, written for the people responsible for it — broker-owners, managing brokers, and the compliance staff who stand between a busy office and a regulator with a checklist.

The transaction file is not a filing habit. It is a legal artifact with a specific job. In most states, license law makes the broker of record responsible for supervising the licensees who hang their licenses at the firm — their advertising, their handling of client funds, their paperwork. The agent writes the contract; the broker answers for it. That asymmetry is the whole architecture of real estate regulation, and it has a practical consequence: supervision that leaves no record is, to a regulator, supervision that never happened.

The file is the record. It is how a broker demonstrates, months or years after the fact, that the agency relationship was disclosed before advice was given, that the deposit went where the contract said it would, that the buyer saw the lead paint disclosure before signing, that the version of the contract everyone performed under was actually executed by everyone. No broker can personally witness fifteen agents running forty deals. The file is the mechanism by which supervision scales — and the evidence, later, that it did.

It is worth being blunt about the exposure. When a transaction goes wrong — a complaint, a lawsuit, an E&O claim — the file is pulled first, and it is pulled against the broker. A thin file does not merely fail to defend the agent; it affirmatively indicts the supervision. The complaint might be meritless. The missing signature page makes it look otherwise.

States differ on the precise list, and a good brokerage policy adds house requirements on top of the legal floor. But the logic of the inventory is universal: the file must contain every document that created an obligation, changed one, or settled one. Walk the deal from engagement to disbursement and the list writes itself.

The agency agreements.The listing agreement on one side, the buyer agency or buyer representation agreement on the other, plus whatever brokerage-relationship disclosure your state requires. These establish who the firm represented, on what terms, and from when — and “from when” is the part audits catch. An agency agreement dated after the offer it supposedly authorized is a document that testifies against you.

The disclosures. Agency disclosure, the property condition disclosure in the many states that require one, and — for any home built before 1978 — the federal lead-based paint disclosure and pamphlet acknowledgment. The lead paint requirement is one of the few genuinely uniform rules in this entire domain: it is federal, it applies nationwide, and the acknowledgment must show the buyer received the disclosure before becoming obligated. Where the property sits in an HOA or condominium, the resale package and its delivery record belong here too.

The contract — and every single change to it. The fully executed purchase agreement is the spine of the file, but it is almost never the whole story. A typical deal accretes counters, addenda, repair amendments, and extensions, and each one is a contract document with the same signature requirements as the original. The file must hold the complete chain, executed end to end, because the version of the deal that closed is the sum of the chain — not the document that started it. The deadlines that decide a deal live in these pages, which is one more reason the chain has to be complete.

Earnest money records.The receipt, the record of deposit into the trust or escrow account, and — if the deal died — the executed release showing where the money went and who agreed. Money is where audits get serious, and the standard of proof is documentary: not “the deposit was made” but a dated record showing when it was received and when it hit the account. The mechanics of the deposit itself are covered in our earnest money guide; the file’s job is to prove those mechanics were followed.

Inspection artifacts.The notices the buyer sent inside the window, the seller’s responses, any repair amendment, and any waiver or release of the contingency. These documents decide whether a deposit was refundable on the day the deal died — which makes them exactly the documents a dispute reaches for first.

The settlement record. The Closing Disclosure or settlement statement showing the final numbers. It is the one document that reconciles everything above — price, credits, deposits, commission — against what actually happened at the table, and its absence is among the most common holes in otherwise decent files, because it is born at the title company and nobody owns bringing it home.

Commission and disbursement records.The disbursement authorization and the record of what was paid to whom. This is the document that connects the brokerage’s money to the file that earned it — and, as we will see, the moment of disbursement is the single most important control point in the whole system.

The correspondence that changed the deal.Not every email — the file is not an archive of pleasantries. But any message that granted an extension, agreed to a repair, waived a right, or memorialized a decision is part of the deal’s legal record, and a file without it is missing terms. This is a category busy offices routinely miss, because the correspondence lives in a dozen inboxes and never announces itself as a file document.

Ask anyone who has sat through a file audit what actually gets written up, and the answer is anticlimactic. It is almost never a missing document category. It is a missing mark: the initials that never landed on page 7, the second buyer’s signature absent from one addendum out of five, the counter-offer the seller signed and the buyer — who went on to buy the house — somehow never countersigned.

The mechanism behind this failure is worth understanding, because it explains why good offices keep producing it. A contract package is not one signature event; it is dozens of them, spread across documents, days, and devices. E-signature platforms have made the problem better and subtly worse at once: better, because a well-built envelope forces every field; worse, because a document that comes back “completed” from the platform feels finished, and nobody re-reads a finished thing. The page that was scanned askew, the addendum sent outside the envelope, the counter printed and signed in a driveway — those live outside the guardrails, and they are precisely the pages that come back incomplete.

Why it matters more than it looks.An unsigned amendment is not a cosmetic defect; it is an open question about what the contract says. If the repair amendment was never fully executed, did the buyer waive the inspection contingency or not? If the counter was never countersigned, what were the terms of the deal that closed? The parties performed, so in practice a court may find a contract existed — but “a court may find” is exactly the sentence a broker’s file exists to make unnecessary. Every missing signature converts a settled fact into an arguable one, and arguable facts are what claims are made of.

The audit standard, then, is not “is the document present” but “is the document fully executed” — every signature, every initial block, every date, on every page that calls for one, for every version of every document. That standard is easy to state and brutal to verify by hand, which is why it is the standard files fail.

State license law sets a minimum period for which brokers must retain transaction records, and the periods commonly fall somewhere between three and seven years. That range is the honest answer; the useful answer is narrower and personal: know your state’s number, and know what starts the clock.Some states run the period from closing; others from the date of the last activity or, for transactions that fell through, from termination. A broker who knows “three to seven years” knows a trivia fact. A broker who knows “our number is five, measured from settlement, and dead deals count” has a retention policy.

Three points that separate real retention from a shelf of boxes. First, dead deals are files too. A terminated transaction — the one where the deposit dispute got heated before everyone signed the release — is if anything more likely to generate a complaint than a closed one, and it is subject to the same retention rules. Second, electronic storage generally satisfies the requirement in many states, subject to conditions on completeness and producibility that vary; the operational test is whether you can hand a regulator the entire file, legible and organized, within days of the request. Third, retention is a floor, not a target.The statute of limitations on the claims a file might defend against does not always match the license-law retention period, which is why many brokerages and their E&O carriers keep files longer than the legal minimum. Where the two numbers differ, the longer one is the one protecting you.

Everything else in this guide is about paper. This section is about money, and regulators treat the two very differently: recordkeeping lapses tend to draw citations, while trust account violations put the license itself in play. If a state audit has a center of gravity, it is here.

Deposit timing.States commonly require that earnest money and other client funds be deposited into the trust or escrow account promptly — many define a specific short window, measured in days from receipt or from ratification, though the exact rule varies by state and by what the contract itself says. The transaction file’s role is to prove compliance: the dated receipt, the deposit record, the ledger entry, forming an unbroken line from the buyer’s check to the account. A deposit that was in fact timely but cannot be shown to be timely is, for audit purposes, a finding.

No commingling.The universal principle, however each state words it: client funds and brokerage funds do not mix. Operating money does not sit in the trust account; client deposits do not touch the operating account; and the trust account reconciles — every client’s funds individually accounted for, the ledgers summing to the bank balance. Auditors reconcile the account against the transaction files, which means a hole in a file becomes a hole in the reconciliation. The two record systems vouch for each other, and they fail together.

Disbursement with authority. Money leaves the trust account only where the contract or a written agreement of the parties says it can — the closing, an executed release, whatever the governing documents provide. The file must hold the authority alongside the disbursement. A correctly paid release that exists only as a wire confirmation is half a record.

Demystifying the audit is worth a section, because brokerages that have never been through one tend to prepare for the wrong thing. There is no single national playbook — practices vary by state — but the shape recurs.

State auditors come for the money first and the files second.A routine examination commonly starts with the trust account: bank statements, reconciliations, ledgers. Then come the files — some pulled at random, some selected because a deposit in the account led there, some because a complaint did. The random pull is the part worth internalizing. It means the file that gets audited is not the file you would have chosen to show. Every file is the audit file; you just don’t know which one yet.

E&O carriers pull files at two moments.At underwriting, many carriers ask about the brokerage’s supervision practices — whether files are reviewed, on what schedule, against what checklist — because those practices price the risk. And at claim time, the file isthe defense. The difference between a claim that settles quietly and one that doesn’t is very often the difference between a complete file and a thin one. A brokerage’s file discipline is, functionally, part of its insurance program.

And the broker owns the finding, whoever caused it.When an agent’s file is thin, the regulatory conversation is not with the agent. License law’s supervision duty means the broker of record answers for the file — which is precisely why file compliance cannot be left as a matter of each agent’s personal organization. An office’s file quality is a distribution, and the broker is accountable for its worst tail, not its average.

Knowing what a complete file looks like is the easy half. The hard half is producing complete files at volume — across dozens of agents with different habits, hundreds of transactions a year, and documents that arrive by email, portal, and driveway. The brokerages that manage it converge on the same three mechanisms.

A checklist per file type.Not one checklist — several. A listing-side file, a buyer-side file, a dual-agency file, a lease, and a dead deal each have different required contents, and a single generic list guarantees that every file is either over-documented or under-checked. The checklist is the brokerage’s policy made operational: it turns “complete” from a judgment call into a countable state. Our transaction checklist is the deal-level version of this instinct; the compliance checklist is its broker-level sibling.

Review before disbursement. The single highest-leverage policy in broker compliance: no commission is paid until the file passes review. Leverage is the reason — the moment before disbursement is the last moment the brokerage holds something the agent wants, and therefore the last moment a missing document gets chased with any urgency. Offices that review files after closing are running a suggestion; offices that review before disbursement are running a control. Many brokerages staff this with transaction coordinators or dedicated compliance reviewers, and the policy is only as strong as their authority to actually hold a check.

Exception reports, not heroic memory.At scale, the question “which files are missing something?” must be answerable by a report, not by the compliance manager’s recall. The office needs a standing view of every open file’s gaps — the unsigned amendment, the absent settlement statement, the deposit with no receipt — ordered by how close each deal is to closing. What gets surfaced gets fixed; what lives in someone’s head gets discovered in the audit.

Where the reading becomes the bottleneck.Notice what all three mechanisms quietly assume: that someone has read the documents. A checklist can confirm a PDF named “Amendment 2” was uploaded; only reading it reveals that page three is missing the second buyer’s initials, or that the version uploaded is the unsigned draft. Human review at brokerage volume therefore becomes sampling — spot-checks, skims, trust in the file name — and sampling is exactly how the counter nobody countersigned survives to the audit. This is the layer where AI document reading genuinely changes the economics: when software reads every page of every file, the review moves from sampling to census, and the humans move from hunting for problems to ruling on the ones surfaced.

That census-not-sampling review is the compliance half of what Ratifylydoes. The paperwork gets forwarded the way it would be sent to a coordinator; the AI reads every page, extracts the parties, the price, and every date, builds the transaction from the documents, and audits the file against the brokerage’s compliance rules — the missing signature, the unexecuted amendment, the disclosure that never came back. When an amendment lands, it is re-read and the schedule re-flows; agent, client, broker, lender, and closing office see one shared live timeline, and deadlines escalate before they hit.

A human approves every call — no finding blocks a file, and no file clears review, on the software’s word alone. What changes is coverage: the review that policy says happens on every file actually happens on every page of every file, and the compliance staff spend their judgment on the exceptions instead of the reading. For a brokerage, that is the difference between believing the files are clean and being able to show it.