Lesson objective

Write an agent authority register entry that names the trigger, permitted tools, stop conditions, blast radius and responsible licensee before an automation is connected to a live brokerage system.

Plain-language explanation

Why this matters now

Lessons 1 and 2 produced two decisions for each automation: the rung it runs on, and the tools and reach it gets. Decisions that live in a meeting, an email thread or a vendor's settings screen drift. An administrator widens a scope to fix a problem on a busy weekend. A new team leader assumes the automation was approved for their team because it runs for the team next door. The integrator leaves and nobody knows what the rules were.

The fix is unglamorous: write the authority down, in one place, before the automation is connected to anything live, and treat any change to what it may do as a change to that written entry first.

No regulator defines which brokerage tasks an automation may perform, and none prescribes a register. The register in this lesson is an AI Coalition Network recommendation. It is built to serve duties that do exist.

  • Law / rule (South Carolina, S.C. Code §40-57-820, effective 21 May 2024; binds persons licensed under Title 40, Chapter 57, meaning brokers, salespersons and property managers): a licensee is responsible for "any and all work product produced by him or with the assistance of artificial intelligence, machine learning, or similar programs," and a violation of the chapter committed through these programs "will be treated as if the violation was committed directly by the licensee." It is one of very few state real estate statutes that names AI. It applies in South Carolina only, but it states plainly where responsibility lands, and a register should make the same point everywhere: every automation's output has a named licensee who owns it.
  • Professional guidance (California DRE, Real Estate Bulletin, Winter 2026): DRE's best practices include written broker policies and training on AI use, human review of outputs before publication, and keeping records of how AI outputs were reviewed. It states that if an AI tool generates inaccurate information, misleading advertising or improper communications, responsibility rests with the licensee and responsible broker, not the technology provider. These best practices are recommendations; the binding duties are the California statutes and regulations the article cites.
  • Professional guidance (NIST, AI RMF 1.0, January 2023; voluntary): the Core has four functions, GOVERN, MAP, MEASURE and MANAGE. GOVERN "applies to all stages", and NIST states that after instituting GOVERN outcomes "most users of the AI RMF would start with the MAP function". A register entry is a practical way to map one automation before it runs.
  • Professional guidance (CISA and partners, May 2026; voluntary): CISA recommends organisations "account for agentic AI security in your organization's security model and risk posture", and names obscure event records as a risk. The register is where the brokerage's security programme learns an automation exists.

A question to sit with

If your integrator resigned tomorrow, could anyone in the brokerage say, from a document, exactly what each running automation may do, for which agents and clients, which licensee owns what it produces, and what makes it stop?

What goes wrong

The configuration is the only record. What an automation may do is whatever the platform currently allows. Nobody can tell whether the current setting is the one the broker approved.

The trigger is vague. "Runs when leads come in" turns out to mean any message in a shared inbox, including a cooperating agent's reply, a seller's email about a repair and a tenant's maintenance request.

No licensee owns the output. The register names the person who built the automation but not the licensee whose work product it produces. In South Carolina the statute supplies the answer anyway; elsewhere, supervision duties do. The register should not leave it to be discovered.

There is no stop condition. The automation keeps going when its input is garbled, when a listing is withdrawn, when the same enquiry arrives twice, or when the owning agent is on leave and nobody releases its drafts.

Blast radius is never estimated. Nobody asked how many clients, records, outside parties or consumer contacts one bad day could touch, so nobody noticed it was all of them.

Approval by the wrong person. The entry is signed by the person who wanted the automation, not by the supervising broker.

The practical answer

Keep one register for the brokerage, one entry per automation. The fields below are this programme's template. The downloadable agent authority register for this level follows them.

Field What to write Example (fictional)
Name and ID A plain name and a unique ID AUT-007 New-lead tagging, Eastgate team
Automation owner Named person and deputy Marketing lead; deputy the operations coordinator
Output owner The licensee who owns what it produces Eastgate team leader for tags and drafts
Supervising broker The broker accountable for supervision Designated broker
Purpose One sentence Tag new portal leads by type and price band and draft a first reply
Rung 0 to 3 from Lesson 1, and who chose it Rung 2 tagging; rung 1 drafts
Trigger The exact event that starts a run New lead record created in the Eastgate pipeline from a listed portal source
Inputs read Systems and records it reads That lead record; the brokerage's active listing records
Permitted tools Every tool and action, by name Read one lead; set two tags; save one draft note
Prohibited actions What it must not do even if able Send, text, call, delete, export, reassign, book showings
Gate Where a licensee decides, and who Assigned agent reviews and sends each draft
Stop conditions Events that halt it See the list below
Blast radius The most one bad day could touch See the estimate below
Manual fallback How the work is done if it stops Team leader tags and answers by hand from the same pipeline
Log location Where every action is recorded The automation's action log (Module 11)
Approvals Names and date Automation owner, output owner, supervising broker, technology owner
Review date When the entry is re-checked Six months, or on any platform change

Name the trigger precisely. A good trigger names the source, the event and a filter. "A new lead record is created in the Eastgate pipeline from one of the three listed portal sources" is testable. "When leads come in" is not.

Write stop conditions a system can detect. Every entry carries at least these five, adapted to the automation:

  1. The input cannot be read or does not match the expected form.
  2. The same input has already been processed.
  3. The listing, transaction or client is closed, withdrawn or not within the automation's scope.
  4. The number of runs in a set period exceeds a written ceiling.
  5. A named person has pressed stop (Module 13 designs the stop and the return to manual).

When a stop condition fires, the automation halts and tells the automation owner. It does not guess.

Estimate the blast radius in four dimensions. Blast radius is the most that one bad day of runs, before anyone notices, could affect. Write a number for each.

Dimension The question AUT-007 estimate
Clients and agents How many clients or agents' pipelines can it touch? One team of 6 agents
Records How many records could one day of bad runs change? Up to 120: a ceiling of 20 runs a day per agent across 6 agents, one tag set and one draft per run
Outside parties Who outside the brokerage could see or receive the effect? None; drafts go nowhere without a licensee's release
Money and consumer contact Could it move money, commit a client or contact a consumer? No

A blast radius of one team, 120 internal records, no outside party and no consumer contact is a small, recoverable failure. If the same table showed every agent's clients, the MLS and outbound texting, the design would go back to Lesson 2.

Get the right signatures. This programme recommends four approvals: the automation owner, who answers for how it runs; the output owner, the licensee who answers for the work it produces; the supervising broker, who answers for supervision under your state's licence law; and the technology owner, who confirms the configuration matches the entry. None of these approvals moves any duty to the tool or the vendor. DRE says as much for California: responsibility for an AI tool's inaccurate or misleading output rests with the licensee and responsible broker.

Change the entry before the configuration. Any change to trigger, tools, scope, rung or stop conditions is an amendment to the entry, approved the same way, and only then applied. Keep old versions. The live configuration should always be something the current entry permits.

Remember this

  • No regulator defines which tasks an automation may do; the register is this programme's recommendation, built to serve duties that already bind.
  • South Carolina makes the licensee responsible for AI-assisted work product; every register entry should name the licensee who owns the output.
  • The core fields are trigger, permitted tools, prohibited actions, gate, stop conditions and blast radius, plus named owners and the supervising broker.
  • Stop conditions are detectable events; a stopped automation halts and tells a person.
  • Change the entry first and the configuration second, and reconcile the two every quarter.

Real estate example

Larkfield Realty Group is a fictional 90-agent brokerage with offices in two states, one of them South Carolina. Its transaction services manager, Tomas Adair, built an automation that reads executed contracts uploaded to the transaction system and creates a task list of dates for the transaction coordinator. It ran for six weeks on the Columbia office's files, set up by an outside integrator, with no written entry. Before extending it, the broker-in-charge, Grace Nwosu, asks for a register entry. Writing it exposes three problems. First, the trigger is "any new PDF in a transaction folder", so it also read inspection reports and a lender's letter and created 27 junk tasks. Tomas rewrites it as "a document tagged Executed Contract by a coordinator in a listed office's transaction file". Second, there are no stop conditions: when the system re-uploaded a batch of files, the automation duplicated 48 task lists. The entry adds five stop conditions, including a duplicate check and a ceiling of 15 runs a day per office. Third, the blast radius table shows the integrator connected it with an account that reaches both offices and can send task reminders to clients by email. The first estimate reads: 2 offices, up to 30 task lists a day (15 runs in each of 2 offices), outside parties including buyers and sellers, no money. Grace sends it back. The approved entry scopes it to the Columbia office, internal tasks only, 15 runs a day, so the estimate becomes 1 office, up to 15 task lists, no outside party and no money. The entry names the listing or buyer's agent on each file as output owner, because under South Carolina's statute the licensee answers for AI-assisted work product, and Grace signs as supervising broker.

Responsible-use warning

Do not let the register describe what the automation already does. An entry written from the live configuration simply blesses whatever the integrator set up, including the excessive reach Lesson 2 warns about. Write the entry from what the task needs, compare the configuration with it, and change the configuration to match. And never extend an automation to another office or team by editing a setting; that is an amendment, with the new output owner and the supervising broker signing it.

Human-review requirement

The automation owner drafts and maintains the entry. The licensee who owns the output approves the purpose, gate and fallback for their clients. The supervising, designated or responsible broker approves the entry as part of supervising the tools licensees use, as your state's licence law defines that duty. The technology owner confirms the live configuration matches and reconciles it each quarter. Every approval is recorded by name and date, and no approval transfers responsibility to a vendor or the tool.

Practical exercise

Use a fictional automation, or one running in your own brokerage with nothing confidential.

  1. Fill in every field of the register template in this lesson for that automation, including automation owner, output owner and supervising broker.
  2. Rewrite the trigger until it names a source, an event and a filter a system can test.
  3. List every permitted tool by name, then list the prohibited actions the platform would technically allow.
  4. Write at least five stop conditions, and say who is told when each fires and how.
  5. Estimate the blast radius in the four dimensions and show the arithmetic for the records figure.
  6. Describe the manual fallback in enough detail that a new transaction coordinator or assistant could follow it.
  7. Name the four approvers this lesson recommends and state which licence law in your state defines the supervising broker's duty.
  8. Compare the entry with the automation's actual configuration, or with the vendor's defaults, and list every difference to be removed or approved.
  9. Read the entry to a team leader, or imagine doing so, and record their answers to "Would you know if this stopped?" and "Would your team know how to do the work without it?"
  10. Set a review date and describe the quarterly reconciliation that will compare live permissions with this entry, naming who performs it.

Knowledge check

  1. Which fields does this lesson say an agent authority register entry must contain?

    Answer guidance: Name and ID, automation owner, output owner licensee, supervising broker, purpose, rung, a precise trigger, inputs, permitted tools by name, prohibited actions, the gate, stop conditions, blast radius, manual fallback, log location, approvals and a review date.

  2. What does South Carolina Code §40-57-820 say, and whom does it bind?

    Answer guidance: A licensee is responsible for all work product produced by him or with the assistance of AI or similar programs, and a violation committed through them is treated as committed by the licensee. It binds South Carolina brokers, salespersons and property managers.

  3. In what four dimensions is blast radius estimated in this lesson?

    Answer guidance: The clients or agents' pipelines it can touch, the records one bad day could change, the outside parties who could see or receive the effect, and whether it could move money, commit a client or contact a consumer.

  4. What is the correct order when an automation's scope needs to change?

    Answer guidance: Amend the register entry first, have the same named owners and the supervising broker approve it, and only then change the configuration, keeping the old version so the live setup is always something the current entry permits.

Sources and further reading