The Client Data Your Brokerage Owns but Cannot See

Somewhere in your brokerage right now, a buyer's pre-approval letter is sitting in an agent's personal Gmail account. A signed contract is in a photo roll on someone's phone. An earnest money wire confirmation lives in a text thread. None of this happened because anyone was careless. It happened because it was the path of least resistance, and nobody ever decided otherwise.

That last part is the point. In most brokerages, the location of client and transaction data was never decided. It accumulated. And what accumulates by default is not neutral — it is a set of liabilities the brokerage owns whether it acknowledges them or not.

The Quiet Default Every Brokerage Inherits

Real estate has a structural quirk that most industries do not: the people doing the client-facing work are usually independent contractors who arrived with their own phone, their own email address, and their own habits. The brokerage supplies the license umbrella, the brand, and the split. The agent supplies everything else — including, by default, the place where the deal file actually lives.

So the working record of a transaction ends up distributed across personal inboxes, personal cloud drives, phone cameras, and message threads. It works, in the sense that deals close. But "it works" and "it is governed" are very different statements, and the difference only becomes visible at the worst possible moments: a dispute, a departure, a lost device, a records request.

You Carry the Liability Either Way

Here is the sobering asymmetry. The broker of record is responsible for supervision and for maintaining transaction records — that responsibility does not shrink because the records are inconvenient to reach. When a commission dispute surfaces, when a buyer alleges a disclosure failure two years after closing, when a regulator asks for a complete file, the answer "the agent had it in their personal inbox and they've since left" does not transfer the obligation. It just means you hold the liability without holding the data.

Client financial documents raise the stakes further. Pre-approval letters, bank statements, lease applications with Social Security numbers — these routinely flow through email during a transaction. If they flow through accounts the brokerage cannot secure, cannot audit, and cannot revoke, then the brokerage's real security posture is whatever the least careful agent's personal password habits are. That is not an insult to agents. It is simply what the architecture implies.

Three Questions That Reveal Where You Stand

You do not need an audit to locate yourself. Three honest questions will do it:

1. If an agent resigned this afternoon, could you produce the complete file — every email, document, and version — for each of their active transactions by tomorrow morning?
2. For the inboxes where client financial documents arrive, do you know who can access them, whether a second factor protects them, and whether any forwarding rules exist that you did not create?
3. If a phone with client documents on it were lost tonight, is there anything you could actually do about it, or would you simply hope?

If the honest answer to any of these is "no" or "hope," the issue is not effort or diligence. It is that no infrastructure exists for diligence to act through.

Offboarding Is Where the Gap Becomes Real

Agent departures are normal in this business — to a competitor, to a new market, out of the industry. The question is what leaves with them. When the working record lives in personal accounts, the answer is: everything. The conversation history with the lender, the amended contract versions, the inspection negotiation, the client's documents. The brokerage keeps whatever fragments happened to be forwarded along the way.

There is a quieter risk on the same coin. Departure should end access — to shared drives, to the transaction pipeline, to anything carrying client data. In an ungoverned setup, nobody can say with confidence what a former agent can still open, because access was never granted deliberately in the first place. You cannot revoke what you never issued.

What Governed Infrastructure Actually Means

The fix is not a policy memo asking agents to be careful. Policy without infrastructure is a wish. Governed infrastructure rests on three plain ideas:

One identity per person, issued by the brokerage

Every agent and staff member works from an account on the brokerage's own domain — email, calendar, documents, Teams — created by the brokerage and secured to its standards, including multi-factor authentication that is on because the organization requires it, not because each individual remembered to enable it.

Access follows role, not tenure or memory

Agents see their transactions. Transaction coordinators see the files they coordinate. The broker can reach everything their supervisory duty covers. Access is granted deliberately when someone joins or changes roles — which means it can be reviewed, and it can be removed.

Departure is a switch, not a negotiation

When someone leaves, one action disables the identity. Email stops, document access stops, sign-ins on personal devices stop. The deal files stay exactly where they were, because they were never in the agent's personal accounts to begin with. Offboarding becomes an administrative step instead of a recovery project.

A Governance Decision, Not an IT Purchase

It is tempting to file all of this under technology and defer it the way one defers a software evaluation. That framing is wrong. Buying a tool is an IT decision. Deciding that your brokerage — not the personal accounts of whoever happens to work there this year — is the custodian of its client records is a governance decision. The technology is just how the decision gets enforced day after day, without depending on anyone's memory.

This is also why it is worth having someone accountable for running it. A Microsoft 365 foundation on your own domain provides the identity, email, and document layer; the discipline comes from someone provisioning accounts, enforcing access, and executing offboarding every time. That is the role Genesis AI plays for brokerages — managed infrastructure as an ongoing operational function rather than a one-time setup project.

But whether or not you ever hire anyone, ask the three questions above this week. The brokerages that handle this well are not the ones with the biggest budgets. They are the ones that made the decision on a calm Tuesday, instead of discovering it had been made for them on a bad one.