Skip to main content

How do we get an AI agent approved in a large organisation?

An agent is approved when someone with authority signs a scope: owner, purpose, data, systems, budget and a review date. The path, and how to shorten it.

Product
Novie Control
Format
Guide
Reading time
5 min
Published
2 October 2026
Updated
21 October 2026
In short

An AI agent is approved in a large organisation when a person with the authority to accept its risk signs a written scope. The scope says who owns the agent, what it does, which data and systems it reaches, what it may spend, and when the approval is reviewed. Agents stall when nobody knows who that person is. Name the approver and the scope template first, and run the security, privacy and finance reviews in parallel against the same document.

What an approval is.

An approval is a statement about a capability at a point in time. It says that this agent, using this model and these tools, may reach this data and take these actions, within this budget, owned by this person, until this date. When any of those change, the statement no longer describes the agent, and the approval should come back for review.

Most approvals fail that test. They are a signature on a demo, given once, with no scope written down. The agent then changes underneath the signature: the model is upgraded, a tool is added, the data it reaches grows. Nobody approved what it does today.

TakeawayAn approval describes one agent at one point in time, and it stops describing the agent when the model, tools, data, budget or owner change.

Why it matters now.

Agents are arriving faster than the approval paths for them. Deloitte's State of AI in the Enterprise 2026 found 74 percent of organisations expect to be using AI agents by 2027 and 21 percent have a mature governance model for them. In KPMG's Q2 2026 AI Pulse Survey, 53 percent of large US enterprises had agents deployed, and 18 percent were orchestrating several agents across workflows.

Deloitte, State of AI in the Enterprise 2026.

The wait is measured. In AvePoint's 2026 survey of 750 IT, security and AI leaders, 86.9 percent of organisations had delayed AI deployments, by an average of almost six months, mostly because data security and governance were not ready.

AvePoint survey of 750 IT, security and AI leaders, 2026.

Regulators expect the approval to mean something. APRA's letter to industry of 30 April 2026 asks for human involvement in high-risk decisions, controls over agentic and autonomous workflows, and an inventory of AI tooling and use cases. In New Zealand, the FMA's August 2026 review of AI in financial advice recorded record-keeping and audit trails as a significant barrier to adoption.

Singapore has gone furthest. Its agentic AI governance framework sets out what any organisation deploying agents should bound, own and control before and after an agent goes live.

TakeawayAgents are arriving faster than the paths to approve them, and most organisations are waiting months on reviews.

Who has to say yes.

  • The business owner, who answers for the outcome and owns the agent once it runs.
  • Security, for the systems the agent can reach and the credentials it holds.
  • Privacy, for any personal information in what the agent reads or writes.
  • The data owner, for each class of data the agent uses.
  • Finance, for the budget the agent draws on and its cap.
  • Risk or compliance, in regulated work, for the decisions the agent informs or makes.

One of them has the final say. Write down who, by risk tier, before the first agent arrives. An agent that needs six approvals and has no final approver waits for the slowest of them.

TakeawaySix functions review an agent, so write down which of them has the final say for each risk tier before the first agent arrives.

The approval pack.

  1. Purpose: the business outcome, in one sentence, and how it will be measured.
  2. Owner: the person accountable, by name.
  3. Model and tools: which model the agent runs on and which tools or APIs it can call.
  4. Data: the classes of data it can read and write, including personal information.
  5. Actions: what it can change in which systems, and which actions need a person to confirm.
  6. Budget: what it may spend per run and per month, and what happens at the cap.
  7. Record: what is logged, where, and for how long, so the question of what it did last month has an answer.
  8. Stop: how it is paused, and who can do it.
  9. Review: the date the approval expires, and the changes that bring it back early.

TakeawayOne written scope covering purpose, owner, model, tools, data, actions, budget, record, stop and review gives every reviewer the same facts.

Why approvals take months.

  • The reviews run one after another, each waiting for the last.
  • There is no template, so every reviewer asks for the same facts in a different form.
  • The scope is open, so each reviewer imagines the worst case and asks for controls against it.
  • Every agent is treated as new, including the tenth agent of a pattern already approved nine times.

TakeawayReviews run in sequence, there is no template, the scope is open and every agent is treated as new.

How to make it weeks.

  1. One intake, one pack. Every reviewer reads the same document.
  2. Parallel review, with a fixed window for each reviewer to object.
  3. Risk tiers. An agent that reads internal documents and drafts replies for a person to send is a different tier from one that changes customer records.
  4. Approved patterns. Once a pattern is approved, the next agent built on it inherits the controls and needs a lighter review.
  5. Approvals with expiry. A dated approval is easier to give than a permanent one.

TakeawayOne pack, parallel review, risk tiers, approved patterns and dated approvals cut the wait from months to weeks.

When the approval should come back.

The model behind the agent changes. A tool is added. It reaches new data. It runs over its cap. Its owner leaves. Each of these is a change to the statement the approver signed, and each should reopen it automatically, rather than waiting for someone to notice.

TakeawayAny change to what the approver signed should reopen the approval automatically.

How Novie Control does it.

Novie ControlAvailable now

Governance and accountability.

Give every workload a named owner, a budget and clear boundaries.

1,284

calls governed today.

Sources

  1. Deloitte, Business and IT leaders report AI agents are scaling faster than their guardrails (24 April 2026)
  2. KPMG, AI Quarterly Pulse Survey Q2 2026 (24 June 2026)
  3. AvePoint, The State of AI 2026: Scaling Trust, Control, and Readiness in the Agentic Era (2026)
  4. APRA, Letter to Industry on Artificial Intelligence (30 April 2026)
  5. Financial Markets Authority, Thematic review on artificial intelligence in financial advice: engagement overview (August 2026)

Other articles

Frequently asked questions

How do we get an AI agent approved in a large organisation?

Name the person with final authority for each risk tier, write one approval pack covering owner, purpose, model and tools, data, actions, budget, record, stop and review date, and run the security, privacy and finance reviews in parallel against it.

Who should approve an AI agent?

The business owner answers for it, with security, privacy, the data owner, finance and, in regulated work, risk or compliance reviewing their parts. One person has the final say for each risk tier, decided before the first agent arrives.

How long should an AI agent approval take?

Weeks for a new pattern and days for an agent built on an approved one. Months usually means sequential reviews, no template and an open scope.

When does an AI agent need re-approval?

When its model changes, a tool is added, it reaches new data, it exceeds its budget, or its owner leaves. Each changes what was approved, so each should reopen the approval automatically.

Build the intelligenceyour organisation compounds.