Lesson objective

Build and maintain an agent authority register that records, for every automation, its owner, its mode, its bounds, the data it touches and who can stop it, and that is changed before the agent is.

Plain-language explanation

Why this matters now

A company with one agent can keep its bounds in a single document. A company with five, some bought, some built and some switched on inside a platform it already had, needs a register: one list of every automation that acts, with its authority written down in the same shape each time.

The reason is not tidiness. It is that authority grows. CISA's announcement of its 1 May 2026 joint guidance, "Careful Adoption of Agentic Artificial Intelligence (AI) Services", names privilege creep and obscure event records among the risks of agentic AI. Both describe the same slow failure: agents that gain reach nobody decided to give them, and records that cannot show afterwards what they did. The guide is voluntary and written mainly for developers, vendors and operators, but it also recommends that organisations "account for agentic AI security in your organization's security model and risk posture." For a landscape company, the register is where that accounting happens.

Professional guidance (NIST, AI RMF 1.0, January 2023; voluntary, under revision): the framework's GOVERN function "applies to all stages" of AI risk management, and NIST says that after instituting GOVERN outcomes "most users of the AI RMF would start with the MAP function." A register is a GOVERN record that makes MAP possible: you cannot map the risks of an automation nobody has listed.

A question to sit with

If your field-service vendor switched on a new "auto-reply" feature overnight, how would anyone in your company find out, and whose job would it be to decide whether it stays on?

What goes wrong

The register lists tools, not authorities. It says "field-service platform: approved." It does not say which of the platform's automations are switched on, what each may do, or who owns each one.

Platform features escape the register. The company registers the agent it built, but not the auto-reply, auto-reschedule and auto-invoice features inside tools it already pays for. Those features act on customers just as surely.

The agent changes first and the register later, if ever. A new connection is added on a Friday to fix an urgent problem. The register is "updated when things calm down," which in a landscape company means November.

Nobody owns the stop. The register names who built the agent but not who may switch it off, or how to reach that person on a Saturday.

Seasonal turnover empties it of meaning. The named approver left in October. The register still shows her name in April, so every approval since has been given by whoever was nearby.

The practical answer

One row per automation that acts, with fixed columns. The column set below is an AI Coalition Network recommendation and matches the downloadable register template.

Column What it holds
ID and name A short identifier and a plain description, for example "A-03 Estimate booking agent"
Source Built in-house, bought, or a feature inside an existing platform, with the vendor and the setting name
Business owner The named person who answers for it, and a deputy
Qualified owner Where it touches a qualified domain: the certified applicator, the irrigation owner (licensed where the state requires), the arborist, the person who signs proposals
Purpose One sentence
Mode per verb From Lesson 1: suggest, act inside bounds, or wait for a person
Permitted, forbidden, approvals From Lesson 2, or a reference to the one-page bounds document
Systems and data Which systems it reads and writes, and which data classes must never reach it (reference to the systems map and data contracts in Module 4)
Log location Where its actions are recorded (Module 11 specifies the log)
Stop owner and method Who may stop it, how, and how that person is reached out of hours (Module 9)
Status Proposed, trial in suggest mode, live, paused or retired
Last review and next review Dates, and who reviewed
Change history Each change of authority, with the date, the approver and the reason

Find what is already switched on. Before registering anything new, walk every platform the company uses and list every setting that sends, books, reschedules, replies, invoices or posts on its own. Typical places to look in a landscape company are the CRM, the field-service platform, the texting service, the review-management tool, the accounting package and the irrigation controller management portal. Each switched-on feature becomes a row, even if the answer is to switch it off.

Change the register before the agent. The rule that makes a register real is simple: no new connection, permission, template or mode change goes live until the register row has been updated and the business owner has approved it. Emergencies happen; the emergency rule is that the change is recorded within one working day with the reason, and reviewed at the next weekly meeting. This rule is an AI Coalition Network recommendation, not a legal requirement.

Review on the landscape calendar, not the office calendar. A generic annual review misses the points where this trade changes shape.

Review point Why What to check
Before spring start-up New hires, new routes, new templates Every named person is still employed and available; every template is current; seasonal accounts are ready
After the first busy fortnight Pressure reveals shortcuts Approvals bulk-cleared? Auto-send switched on by anyone?
After any vendor update Features change without warning New automatic behaviours; changed defaults
Before winterization and closeout High-volume batches Batch limits; stop owner availability
At season end Departures Remove leavers from every role; retire unused agents

Keep it where people can find it and small enough to read. A shared document or a simple table is enough for most landscape companies. What matters is that the dispatch lead can see, in one place, which agents may touch her routes and who stops them.

Remember this

  • The register records authority, not just tools, and includes automatic features inside platforms the company already uses.
  • Every row names a business owner, a qualified owner where relevant, and a stop owner who can be reached out of hours.
  • The register changes before the agent does; emergency changes are recorded within a working day.
  • Review it at the points where a landscape season changes shape, not once a year.
  • CISA names privilege creep and obscure event records as agentic risks; the register is the company's answer to both.

Landscaping example

Marlowe Property Services, a fictional commercial grounds company, believes it runs two automations: a website booking agent and a route-drafting tool. Its operations director, Sam Oduya, starts a register and walks every platform first. He finds seven automatic behaviours. The field-service platform sends "we're on our way" texts, auto-reschedules rained-out visits to the next open day, and emails invoices on job close. The review tool auto-posts replies to five-star reviews. The irrigation controller portal applies a vendor "seasonal adjust" percentage to 41 commercial controllers each month. The two known agents make seven. The auto-reschedule feature has moved 63 visits since April without anyone approving a single one, and three HOA boards have complained about crews arriving on days they had not been told about. The controller adjustment raises the sharpest question: who decided that a vendor percentage could change watering on customer sites? Sam gives each behaviour a row. Auto-reschedule is switched to propose-only, with the dispatch lead as approver. The controller adjustment is paused and referred to the company's irrigation manager, who holds the state irrigation licence where the company works in a licensing state, for a decision on each site. The review auto-replies are switched off until the owner decides who answers public reviews and in what words. Sam sets the review calendar to spring start-up, the first busy fortnight, vendor updates, winterization and season end, and adds a line to the weekly meeting agenda: "register changes this week."

Responsible-use warning

Do not build a register that lists only the agents you built. Automatic features inside the CRM, the field-service platform, the texting service and the controller portal act on customers too and must each have a row. Do not let a change go live first and reach the register later; that ordering is exactly how authority creeps. Do not leave a leaver's name in an approver or stop-owner column over the winter.

Human-review requirement

The owner, or the operations lead the owner names, owns the register and approves every change of authority before it goes live. Each business owner confirms their rows at every review point. Qualified owners confirm the rows touching their domains: the certified applicator for anything near a pesticide decision, the irrigation owner for controllers, the person who signs proposals for pricing and commitments. The technical administrator confirms that the register matches what the systems actually allow.

Practical exercise

Use a fictional landscape company with at least three platforms.

  1. List every platform the fictional company uses: CRM, field-service, texting, review management, accounting, routing, irrigation controller portal, and any other.
  2. For each, list every behaviour that sends, books, reschedules, replies, invoices, posts or changes a setting on its own. Include vendor defaults nobody chose.
  3. Create one register row for each behaviour and each built agent, using every column in this lesson's table.
  4. Fill in the qualified owner column wherever a behaviour touches a pesticide decision, irrigation programming, tree work, pricing or a signature. If nobody fills it, write "none named" and treat that as a finding.
  5. Name a stop owner for each row, with an out-of-hours contact method.
  6. Choose two behaviours to switch off or reduce to suggest mode, and write the change-history entry for each: date, approver and reason.
  7. Write the five review points for your company's season, with a date and a reviewer for each.
  8. Write the one-sentence rule your company will follow for emergency changes, and the meeting where they will be reviewed. Then name one row you would retire at season end, and record why nobody would miss it.

Knowledge check

  1. Why must the register include automatic features inside platforms the company already uses?

    Answer guidance: Because features such as auto-reschedule, auto-reply and auto-invoice act on customers just as a built agent does. If they are not registered, nobody owns them and nobody decided they should act.

  2. What is the rule that makes a register real rather than decorative?

    Answer guidance: No new connection, permission, template or mode change goes live until the register row has been updated and the business owner has approved it. Emergency changes are recorded within one working day and reviewed.

  3. Which two agentic risks named by CISA does the register address?

    Answer guidance: Privilege creep, because every change of authority must be approved and recorded, and obscure event records, because each row points to where the agent's actions are logged.

  4. Why review the register at points in the landscape season rather than once a year?

    Answer guidance: Because the company changes shape at spring start-up, in the first busy weeks, before winterization and at season end, when people leave and batches run. Those are the moments when named people go missing and shortcuts appear.

Sources and further reading