Lesson objective

Identify the acts a brokerage automation must never perform, explain who owns each, and design what the automation may do around each instead.

Plain-language explanation

Why this matters now

Lessons 1 to 3 built a way to decide how much an automation may do. This lesson fixes the acts where that is already decided: the automation prepares, and a named person acts. Each needs a licence, belongs to a principal, rests on a legally required consent, or can move money or rights beyond recall.

Four of this module's sources show why these acts stay personal.

  • Law / rule (South Carolina, S.C. Code §40-57-820, effective 21 May 2024; binds South Carolina brokers, salespersons and property managers): a licensee is responsible for work product produced with the assistance of AI, and a violation committed through such programs "will be treated as if the violation was committed directly by the licensee." Automating an act does not move it away from the licensee. Other states have no such statute on record here, but their licence laws still place the act on the licensee.
  • Professional guidance (California DRE, Real Estate Bulletin, Winter 2026, explaining binding California law): only licensees may perform licensed activities, and using AI to conduct licensed activity "may be equivalent to asking an unlicensed assistant to do licensed activity." DRE states that use of an AI tool will not excuse a violation (citing Business and Professions Code §10176), that AI-generated advertising must still meet the §10140.6 disclosure requirements, and that from 1 January 2026 §10140.8 applies to digitally altered images, including AI-created or AI-enhanced changes. It warns that AI-generated legal explanations or contract language may lead to the unauthorised practice of law, a crime under §§6125-6126, and should not replace advice from an attorney.
  • Law / rule (Texas, 22 Texas Administrative Code §537.11; binds Texas real estate license holders): a license holder may not practise law, give legal advice or opinions on the legal effect of contract forms, and may not draft or recommend language for a contract form "defining or affecting the principals' rights, obligations or remedies", "including escalation, appraisal, or contingency clauses." The license holder may explain the meaning of informational items or choices in a form without giving legal advice. Adding informational items to an authorised form is not the practice of law, and neither is adding or striking language when a principal specifically instructs it in writing, provided the change is made conspicuous. When a transaction involves unusual matters an attorney should review, the license holder must advise the principals to consult one. The rule does not mention AI: treating clause language an automation drafts as covered by the drafting prohibition is this programme's application of the rule to a new tool. Other states set their own unauthorised-practice boundaries.
  • Law / rule (federal, FCC Declaratory Ruling FCC 24-17, released 8 February 2024 and effective on release; a binding interpretation of the Telephone Consumer Protection Act): the TCPA's restrictions on "artificial or prerecorded voice" encompass "current AI technologies that generate human voices." Callers "must obtain prior express consent from the called party before making a call that utilizes artificial or prerecorded voice simulated or generated through AI technology", and voice cloning falls within the prohibition. The TCPA "does not allow for any carve out of technologies that purport to provide the equivalent of a live agent." Such messages must identify the responsible entity and, where they advertise or are telemarketing, offer the specified opt-out methods. Telemarketing calls need prior express written consent under 47 CFR 64.1200(a)(2)-(3). Whether the ruling reaches a particular AI voice agent that is not delivering an artificial or prerecorded voice message is a question for counsel. Level 4 covered consent for voice agents; here the point is that the call is never the automation's decision.

A question to sit with

If an automation assembled a counter-offer, a buyer's agent reviewed it on a phone for twenty seconds and pressed send, who would the commission say negotiated it?

What goes wrong

The automation performs the act. If a platform lets the automation sign, publish or call, eventually it will, on a run nobody watched.

The licensee releases what the automation assembled without reading it. Every field is filled, the button says "send", and the licensee's act shrinks to a formality. The law still treats it as the licensee's act, and South Carolina's statute says so in terms.

Contract language is treated as text. An automation that fills informational blanks in a form gets extended to "suggest an escalation clause" or "tidy up the contingency". In Texas that is language a license holder may not draft, and in any state it can be the practice of law.

A rental decision is treated as a workflow step. A screening tool returns a score and the automation sends the approval or denial. The decision belongs to the housing provider, and the notices that follow it carry their own legal duties.

A voice is treated as a message. An automation that sends reminder texts is extended to "call the lead with our AI assistant". A call with an AI-generated voice needs the consent the TCPA requires, and a product that sounds like a live agent gets no carve-out.

Money is treated as a document. An automation that relays closing documents is extended to "send the wire instructions from the title company". Module 06 designs that boundary; no automation sends, changes or confirms payment instructions.

The practical answer

Adopt the never list. The list below is an AI Coalition Network recommendation for this level. It is not a list of legal prohibitions on software. It is the set of acts this programme treats as always belonging to a named person, because the law, the client relationship or the consequences make them personal.

Never goes to an automation Who performs or decides it What the automation may do instead
Signing or negotiating a contract The principals sign; the licensee negotiates for the client Summarise terms, compare offers side by side, list open questions
Drafting language that defines the parties' rights An attorney; in Texas, license holders may not draft it Flag that a clause request needs an attorney or the principal's own written instruction
Publishing advertising no licensee approved The licensee, under the broker's supervision Draft copy and check it against the listing file for the licensee's review
Deciding a rental application The housing provider, or its property manager Assemble the file against the provider's written criteria for a person to decide
Choosing which consumers see a housing ad or listing The licensee and broker, within fair housing law Nothing on audience selection by protected characteristic or proxy (Module 08)
Placing an AI-voice call without the consent the rules require The brokerage, only with recorded consent and counsel's view Check the consent record and route to a person to call
Sending, changing or confirming payment instructions The closing or settlement agent, verified by people out of band Remind parties to verify by phone with a known number (Module 06)
Setting compensation or price terms The licensee and client together Show the terms the client already agreed, never propose or change them

Eight rows: a named person owns each act, and the automation only prepares.

Enforce the list in three places. Writing it down is not enough.

  1. In the register. Every entry lists these acts under prohibited actions wherever the platform could technically perform them.
  2. In the configuration. Remove the capability, not just the intention: no stored signatures or signing rights on the automation identity, no publishing rights to portals, social accounts or the website, no outbound calling with a synthetic voice, no send rights on anything carrying bank details, no write access to compensation fields.
  3. In the review. The quarterly reconciliation from Lesson 3 checks specifically for these capabilities appearing on any automation identity.

Make the licensee's review real. Where an automation prepares something a licensee will send, sign or rely on, design the hand-off so the licensee sees what matters rather than a button. For a listing description, that means the facts the draft asserts, each tied to the field or document it came from, and anything the automation could not confirm. DRE's guidance is that licensees relying on AI for listing descriptions, emails or ads must independently verify factual claims. An AI output is never proof: check a room count or rule citation against its source.

Keep contract work on the right side of the line. An automation may fill informational items and pull agreed dates and names into a promulgated or brokerage form. When a client asks for special language, it flags the request and stops. The licensee tells the client that such language comes from the client in writing or from an attorney, and advises an attorney where the matter is unusual. In Texas, where §537.11 also requires reproduced TREC forms to match TREC's published text and format, no automation should reflow or edit the form itself.

Treat "it only prepares" as a claim to test. Ask whether a hurried person could mistake the output for the finished act. If so, mark drafts as drafts, keep them out of outward channels, and make the person perform the act in a separate step.

Remember this

  • Eight acts never go to an automation: signing or negotiating, drafting rights-defining language, publishing unreviewed advertising, deciding rental applications, choosing ad audiences, AI-voice calls without required consent, payment instructions and setting compensation or price terms.
  • South Carolina treats a violation committed through AI as the licensee's own; California DRE says an AI tool will not excuse a violation.
  • Texas bars license holders from drafting rights-defining clauses, including escalation, appraisal and contingency clauses.
  • FCC 24-17 brings AI-generated voices under the TCPA's consent rules, with no carve-out for tools that sound like a live agent.
  • Enforce the list in the register, in the configuration and in the quarterly review.

Real estate example

Copperline Properties, the fictional brokerage from Lesson 1, now has a Texas office. Its technology owner, Hugo Ferris, proposes an "offer desk" automation for buyer agents: read a buyer client's notes, fill the TREC-promulgated contract form, add any special provisions the client mentions, send it for e-signature, then place an AI-voice call to the listing agent announcing the offer. The Texas office's designated broker, Mei Okafor, asks for a never-list review before anything is built. The review finds four problems. Adding special provisions would mean the automation drafts language affecting the principals' rights, which §537.11 bars license holders from doing, and one client note asked for "an escalation clause up to $15,000 over the best offer". Sending for signature is the principal's act. Negotiating the offer is the licensee's act. And the voice call would use a synthetic voice to a number with no consent record. The redesign keeps the useful part. The automation fills the informational blanks from the buyer agreement and the client's written notes into the form without changing its text or layout, lists every blank it could not fill, and flags any requested clause language. In its first week it flags the escalation request; the buyer's agent, Luis Farah, tells the client that clause language must come from the client in writing or from an attorney, and recommends an attorney. Luis reviews each filled form against his notes, sends it for signature himself, and phones the listing agent himself. Hugo removes the voice-calling integration and the e-signature send right from the automation identity, and the register entry lists all four acts under prohibited actions.

Responsible-use warning

Do not let an automation identity hold signing or send-for-signature rights, publishing rights, synthetic-voice calling, send rights on messages carrying bank details or write access to compensation fields, even if nobody plans to use them. Intentions change on a busy weekend and configurations outlast the people who set them. Equally, do not let a licensee's act shrink to a button: a filled contract or a drafted advertisement is still the licensee's work, and in South Carolina the statute says a violation through AI is the licensee's own.

Human-review requirement

Each act on the never list has an owner: the principals for signatures, the licensee for negotiation and advertising under the supervising broker, an attorney for rights-defining language, the housing provider for rental decisions, the licensee and broker for audience choices, the brokerage with counsel for any AI-voice calling, the closing or settlement agent for payment instructions, and licensee and client for terms. Each checks that no automation can perform the act and that what it prepares shows sources and gaps, not just a send button.

Practical exercise

Use a fictional brokerage, or your own with nothing confidential.

  1. Copy the eight rows of the never-list table and write, for each, the role in your brokerage that performs or decides that act.
  2. For each row, list any automation or platform that could technically perform the act today, including signing rights, publishing rights, calling features and access to compensation fields.
  3. For each capability you find, write the configuration change that removes it and who will confirm the change.
  4. Choose one document an automation prepares for a licensee to send or sign, such as a listing description or a filled purchase contract form.
  5. Design the first screen the licensee sees, listing the facts or blanks they must check and the source record for each.
  6. Write the "could a hurried person mistake this for the finished act?" test for that document and describe how drafts will be marked.
  7. Write the message your automation shows when a client asks for special contract language, and check that it neither drafts the language nor discourages the client from using an attorney.
  8. Identify your state's rule on licensees and contract drafting, and note where it differs from Texas's §537.11.
  9. Add the never list to the prohibited actions field of one register entry.
  10. Name who checks automation identities for never-list capabilities each quarter, and what they do if they find one.

Knowledge check

  1. Which eight acts does this lesson say never go to an automation?

    Answer guidance: Signing or negotiating a contract, drafting rights-defining language, publishing unreviewed advertising, deciding a rental application, choosing who sees a housing ad, AI-voice calls without required consent, sending or changing payment instructions, and setting compensation or price terms.

  2. What does Texas rule §537.11 bar license holders from drafting, and what may they still do?

    Answer guidance: Language defining or affecting the principals' rights, obligations or remedies, including escalation, appraisal or contingency clauses. They may explain informational items and choices without legal advice, and add or strike language on a principal's specific written instruction, made conspicuous.

  3. What did the FCC confirm in its February 2024 declaratory ruling about AI-generated voices?

    Answer guidance: That the TCPA's artificial or prerecorded voice restrictions cover current AI technologies that generate human voices, so such calls need the called party's prior express consent, with no carve-out for tools that purport to be the equivalent of a live agent.

  4. In which three places does this lesson say the never list must be enforced?

    Answer guidance: In the register entry's prohibited actions, in the configuration by removing the capability from the automation identity, and in the quarterly reconciliation that checks every automation identity for those capabilities.

Sources and further reading