The designated broker's job just got harder. Here's what's actually changed, and what the job needs now.
Every designated broker we've talked to in the last twelve months has said some version of the same thing: the job is harder than it used to be, and it's harder in a way that a bigger commission check doesn't offset.
Between the two of us, we've been on both sides of the desk. Sarah is a designated broker in Arizona running an active brokerage; Mike has spent his career building products that sit on top of professional workflows. We agree on the diagnosis: the supervisory burden has grown faster than the tools brokers have to meet it, and the gap is now big enough to worry about.
What's changed
The old shape of the DB job, sign the file, spot-check the paperwork, coach the agent who asked a question, assumed that the number of things a broker was accountable for was bounded. That assumption doesn't hold anymore.
Three shifts have compressed the timeline.
The settlement changed the paperwork. The NAR settlement pushed buyer representation into the transaction as a signed document required before showings. In Arizona that's the Buyer-Broker Exclusive Employment Agreement, a form that most agents had rarely used before 2024 and that now has to be executed correctly on every buyer transaction. Getting it wrong isn't a technicality; it's an exposure.
The forms got denser. The AAR pushes revisions every 12–18 months. Line-level language on the Residential Resale Purchase Contract, the Additional Clause Addendum, the SPDS, the Cure Period Notice, all of it drifts under agents' feet. The DB is the one accountable for keeping the team current on those changes, and the changes don't stop.
The class-action climate raised the stakes. Deals that would have quietly closed and been forgotten five years ago are now the substrate for aggregated litigation. Boilerplate you thought was defensive posture can become a piece of evidence.
None of these are new problems. What's new is the density of them. A DB supervising twenty agents across sixty active transactions is running quality control on hundreds of documents a month, in a regulatory environment that keeps rewriting the rules.
What the statute actually asks for
A.R.S. § 32-2151.01 is worth reading. It puts the burden squarely on the designated broker to establish written policies, train agents on those policies, maintain records, and reasonably supervise licensed activity. "Reasonably" is the operative word, and it's the word most brokers we know are quietly worried about.
Most brokerages we've talked to know they're behind. The policy manual either doesn't exist or is a Word document from 2019 with someone else's brokerage name still in the footer. Training is happening, but it's happening in a Slack channel, or an ad-hoc mentor conversation, or an email thread that got archived, not in a system that can produce a record when ADRE or a plaintiff's attorney asks. Record-keeping is a filing convention, not an active practice.
That gap between "we know what our policy is" and "we can prove we trained the team on it" is the supervisory exposure. Every DB knows it. Almost none of them have a good answer.
What actually helps
The instinct, honestly, is to add headcount. Hire a compliance officer. Split the supervisory role between two people. That works for the largest brokerages, and it's an expensive answer that doesn't scale down.
The other instinct is to add another AI chatbot to the agents' toolbelt. That doesn't work at all. A general assistant that summarizes emails and rewrites listing descriptions has zero effect on the supervisory position. Worse: an unsupervised chatbot answering compliance questions is a new source of exposure, the DB is now on the hook for the answer their agent got from a tool the DB didn't audit.
What actually helps is a system that captures the DB's guidance once and delivers it consistently across the team. Concretely, three properties matter.
First: every answer traces to a source. When an agent asks whether a Cure Period Notice or an Amendment is the right instrument, the answer cites the specific line of the specific document. The DB can audit any answer their team got and confirm it matches brokerage policy.
Second: institutional knowledge accumulates. The way a designated broker phrases the earnest-money-non-refundable question, the specific line reference, the caveats they include, the interaction with the SPDS timeline, becomes a curated piece of the corpus. Six months later, when a new agent asks the same question at 9 PM on a Sunday, they get the DB's exact answer, not a fresh guess.
Third: the audit trail is native. Every question, every answer, every document generated is logged and inspectable. If an agent got it wrong, the DB can see where the reasoning went sideways and correct upstream. If the agent got it right, the DB has a record they can produce.
That combination; grounded knowledge, curated by the DB, auditable across the team, is not a chatbot. It's a supervisory posture aid. It doesn't replace the DB's judgment; it operationalizes it.
Where this goes
The supervisory burden isn't going to lighten. AAR will keep revising forms. NAR will keep settling class actions. Arizona will keep updating statute. Every additional obligation lands on the DB's desk.
What can change is the ratio between how much a broker is accountable for and how much visibility they have into whether the team is meeting it. Right now, for most brokerages, that ratio is quietly getting worse every quarter.
It doesn't have to. That's the job the next generation of tools should be built to do.
— Sarah Richardson (CEO) & Mike McGowan (CRO), reTEQ
