← All templates
AI Agent Register
One line per AI agent: what it does, who owns it, what it can touch, and what it may never do without a person.
For the COO, CIO or CISO. Fill it in with each team that runs an agent, then review it every quarter. · Updated November 2026
Why this matters now
- Only 21% of leaders say their organization has a mature governance model for AI agents (Deloitte, 3,235 leaders in 24 countries). [Deloitte, State of AI in the Enterprise 2026]
- In April 2026 an AI coding agent deleted a company’s production database and its backups in nine seconds, without asking first. [Euronews, 28 April 2026]
How to fill it in
- List every agent that can take an action (send, write, delete, pay), not just chat.
- Give each one a named owner. A team name is not an owner.
- Write down the access it really has today, then cut it to what the task needs.
- Mark irreversible actions (deleting, paying, emailing customers, changing permissions) as "human approval".
- If a row cannot be filled in, pause that agent until it can.
The template
The first row is an example. Replace it with your own.
Agent Short name | Task One sentence | Owner A named person | Systems and data What it can reach | Access Read / write / act | Needs human approval Actions it may not do alone | Stop switch Who can stop it, and how | Action log Where actions are recorded | Backups out of reach Yes / no | Status Pilot / live / paused / retired | Last review Date |
|---|---|---|---|---|---|---|---|---|---|---|
| Invoice matcher | Matches supplier invoices to purchase orders and flags mismatches | Head of Accounts Payable (name) | ERP invoices and POs; finance inbox | Read; write comments only | Approving or paying any invoice | Finance on-call disables the service account | ERP audit log | Yes | Live | 2026-11-01 |
Free to use and adapt inside your organization. Suggestions or corrections: hello@lumisai.space