Agent Authority
Home/Toolkit/Agent Mandate

Agent Mandate

The Agent Mandate is the agent’s written grant of authority, set out line by line with the control that enforces each line. Complete one per agent, record the signature of the person whose authority covers the grant and any additional approval required by policy, and keep it versioned.

Once signed, the mandate is the record of what the company authorized the agent to do, and the source for every technical setting and for the agent’s entry in the Agent Registry. It stays internal. When the agent deals with another company, Schedule A to the Agent Transaction Addendum shares the limits that company needs to rely on, taken from this mandate.

The example column uses the Acme procurement agent from the guides. The downloads add two columns for a gap analysis: where each line’s authority comes from, and whether the system enforces it today. Every line backed only by policy, with nothing enforcing it, is a place where the agent can do more than the company approved.

DimensionWhat to decideExample: Acme procurement agentControl that enforces it
PrincipalWhich entity the agent acts forAcme Corp. only, not its subsidiariesAgent uses only Acme’s own vendor and card accounts
Approved byWho approved the deployment, under which delegation, and that person’s own limitsDirector of IT Procurement, under the delegation of authority policy ($25,000 per order; $100,000 per month)Signed, versioned mandate; the approver’s own per-transaction and period limits must cover the agent’s
Additional approvalWhether approval one level up is needed: the delegation policy requires it above an aggregate threshold, or where the agent may make payments, sign or accept nonstandard termsRequired, because the agent pays with a capped virtual card and authenticates purchase orders. Also approved by the Chief Financial Officer, under the delegation of authority policyBoth approvals recorded in the signed mandate and the Agent Registry before any credential or card is issued
Whose authority it carriesWhether the agent’s authority comes from the company or from the person who approved it, which decides what happens when that person leaves or changes rolesFrom Acme, under its delegation of authority policy, not from the approver personally. If the approver leaves or changes roles, the grant from Acme continues, but Acme pauses the agent until the required approvals are recorded again (see Review triggers)Stated in the signed mandate; Section 17(d) of the Agent Transaction Addendum tells vendors the grant continues; the [monthly] approver check under Review triggers flags each departure or role change
Business ownerWho reviews the agent’s activity and disputes what’s outside the mandateProcurement manager, with a named backupThe owner or backup reviews urgent shipment alerts immediately and other alerts on out-of-mandate actions and confirmations the same business day. The owner reviews overall activity weekly.
Notices and deadlinesWhere confirmations and notices arrive, when each deadline runs, and which events can cut off a right soonerprocurement-agents@[acme domain]. Under the sample Addendum, Acme has one business day from receipt to dispute the terms in a Confirmation Message. For goods made to Acme’s specifications or perishable goods, shipment cuts off the right to reject an action outside the Limits, even on the day of the order.Route notices to the owner and backup, track each order’s deadlines, and alert them as soon as a shipment-sensitive order is placed so they can review it before it ships.
IdentityHow the agent is identified to systems and counterpartiesIts own client ID, acme-procurement-agent-01Separate OAuth client or service identity; never an employee login. Issued only after the mandate is recorded in the Agent Registry
Authority levelHow far it may go without a person: 0 Recommend, 1 Communicate, 2 Negotiate, 3 Agree subject to confirmation, 4 Execute within limits4. Execute within limitsTools and scopes match the level: no ordering or payment tools below level 4
Subject matterWhat the agent may do, and what it may never doOrder servers and networking hardware. Never any matter that requires approval of the board, a board committee or the stockholdersOrdering scope only; category allowlist
Per-transaction limitThe most it may commit to at once$10,000 per orderLimit check in the ordering tool before the order is sent or terms are accepted; virtual card cap only as a payment backstop; vendor’s service also checks the amount granted through the token where supported
Aggregate limitThe most it may commit to over a period, in total and per counterparty$50,000 per month; $20,000 per vendor per monthOne commitment ledger checked before each order is sent, counting pending, invoiced and paid orders across all vendors and agents, with concurrent orders reserved so they can’t together pass the limit; per-vendor cap in the same check; alert at 80%; card monthly cap only as a payment backstop
CounterpartiesWhom it may deal withVendors on the approved list under a master agreementTokens bound to each vendor’s service; vendor allowlist; vendor or payee checked on each order where one service hosts several vendors
GeographyWhere it may buy, ship to or deal with counterpartiesU.S. vendors; delivery to Acme’s U.S. sites onlyVendor list and shipping addresses fixed in the ordering system
Contract termsWhich terms it may acceptMaster agreement terms only; no new click-through termsOrdering tool blocks acceptance of new terms. Procurement handles proposed changes separately
Term and recurring commitmentsThe longest commitment it may make, and whether it may start subscriptions, change plans, buy on account or credit, or commit to minimum spendNo commitment longer than 12 months. No subscriptions, plan changes, minimum-spend commitments, or purchases on account or credit termsTerm-length check and blocked-terms list in the ordering tool before the order is sent; no subscription or plan-change tools issued; ordering tool accepts only orders paid with the capped virtual card
NegotiationWhat it may offer or concedePrice and delivery date only. Price must stay within 5% of list priceOffer limits checked before the agent confirms
Signature authorityWhether it may sign documentsMay submit and authenticate purchase orders within these limits through the ordering tool. No authority to sign any other documentNo e-signature service credentials issued. The agent may authenticate, and sign or accept where the ordering tool requires it, only to submit purchase orders within these limits through the designated ordering tool. All other signature fields, typed name signing and “I agree” steps in browser, document and messaging tools blocked or routed to the procurement manager. Counterparties told in writing that the agent may submit purchase orders through the ordering tool but cannot sign any other document
PaymentsWhether and how it may move moneyMay settle its own orders only with the capped virtual card at approved vendors’ checkouts. No bank transfers, invoice payments, or other payment initiationCard restricted to approved vendors with per-transaction and monthly caps; no payment initiation or payment approval scopes
Separation of dutiesWhich related powers it must not hold togetherMay order; may not pay invoices, add vendors, change vendor bank details, or approve its own ordersNo vendor record, payment approval, or approval step permissions
Human approvalWhat must pause for a personFor otherwise permitted orders: any order above $5,000 through $10,000, the first with a vendor, or the first under the applicable Agent Transaction Addendum, even with an existing vendorApproval of the specific order, with strong sign-in, by a person whose own limit covers it: the procurement manager up to $5,000, the Director of IT Procurement above $5,000 through the agent’s $10,000 ceiling. Larger orders are blocked. The approver and the limit they acted under are recorded with the order. For an order in the Director’s approval range, a manager’s preliminary review does not release it
SubagentsWhether it may hand work to other agentsProhibitedOrchestrator and tool list block calls to other agents; token exchange disabled; no credential sharing
DurationWhen its authority endsDec. 31, 2026, end of day New York time. Record this legal end date separately from the technical shutdownAt the end date: stop new token issuance and refresh, disable the agent’s client, revoke active tokens and end sessions where the systems support it, close the virtual card, and notify vendors under their agreements. Token and card expiry alone doesn’t end access: a refresh token or client credential can obtain a new token
RevocationHow authority is withdrawn, and what happens to work in progressImmediate shut-off; unsent orders removed from the queue; sent and accepted orders identified and handled under any withdrawal, cancellation, or rejection rights; suspension notices sent promptly through the agreed channels, with notice to vendors and the card issuer within one business day or sooner if their agreements requireTested kill switch that also ends subagent credentials; prepared notice to vendors and the card issuer that the agent’s authority has ended
Review triggersWhat requires the mandate to be reviewed and approved againThe approver changes roles, leaves or has their authority reduced; or the agent’s limits, tools, credentials or underlying model changeThe officer responsible for the Agent Registry checks each approver against HR and delegation changes [monthly]; the agent stays paused until all approvals required under the delegation policy are recorded again
Counterparty noticeHow counterparties learn its limitsWritten notice in each vendor’s master agreementDesignated agent clause; the agent identifies itself
Authority or internal checkWhich limits the vendor may rely on under Schedule A and which checks are internal. Breaching an internal check alone does not give Acme a right to reject. Under Addendum section 5(d), an approval reference satisfies the approval requirement as between the parties. All other Limits still apply. Section 14 governs written confirmation, knowing use and rejection of an action outside those Limits.Limits on authority: the per-order and per-vendor limits, subject matter, contract terms, term and recurring commitments, negotiation, signature authority, payments and the human approval requirement. Internal checks: the $50,000 monthly total across all vendors, which vendors can’t see, the geography rule and the weekly activity reviewLimits on authority stated to vendors in Schedule A to the Agent Transaction Addendum, which treats approval requirements as part of the Limits; owner and backup monitor notices and act on shipment-sensitive order alerts before shipment; approval references attached only by the approval system, after the approval is recorded; internal checks enforced only in Acme’s own systems
LoggingWhat is recorded and for how longFor each transaction, keep the mandate version, credential identifiers, counterparty, order, approvals, confirmation and outcome for at least six years after the transaction, or through the applicable contract limitation period if it runs longer. Record only the input details needed to document the transaction or meet a legal obligation.Use tamper-evident logs and exclude credentials and other secrets. Redact, anonymize or delete personal details as soon as the need ends, even within six years. Preserve evidence covered by a legal hold for as long as the hold applies.

Related: Building Limits into Agent Systems · From mandate to control · Corporate Authority for Agents

Review step 3: Find the gapsLast reviewed: November 2026Template: adapt before use