How do you set a buying mandate for an AI advertising agent?

A buying mandate defines the five constraints an AI buying agent operates within: permitted publisher categories, authorised price range, maximum volume commitment, brand safety parameters, and the conditions that require human escalation before the agent can proceed.

Buying mandate: ** The human-defined set of constraints within which an AI buying agent is permitted to operate autonomously; actions within the mandate can be taken without per-action human approval; actions outside the mandate trigger escalation.

Escalation trigger: ** A condition that causes the agent to pause and request human approval before proceeding; typically defined as specific thresholds on price, volume, publisher type, or deal structure.

Mandate ceiling: ** The maximum commitment the agent is permitted to make without human approval; anything above the ceiling in price, volume, or risk requires escalation regardless of whether other mandate conditions are met.

Proving period: ** The initial operating phase during which the agent runs under tight mandate constraints and demonstrates reliable behaviour before the mandate is expanded.

The five components of a buying mandate

A complete buying mandate defines five things. Publisher permissions: which categories of publisher the agent is authorised to buy from (and which it must avoid). Price range: the minimum and maximum CPM or deal price the agent can agree to without escalation. Volume commitment: the maximum total inventory volume the agent can commit to in a given period. Brand safety constraints: the content categories, audience types, and adjacencies that must be excluded. Escalation triggers: the specific conditions that override the mandate and require human sign-off before the agent acts.

Each component needs to be specific enough to be machine-executable. "Premium publishers" is not a mandate-ready specification; "publishers in IAB category tiers 1 and 2 with a declared audience of 500,000+ monthly uniques and a verified direct deal relationship with Alkimi" is.

How to set the mandate for a new agent deployment

Start conservative. The first mandate should be narrow: a small number of permitted publisher categories, a low price ceiling, a low volume cap, and a short escalation trigger list that catches most decisions. The goal is to run the agent within tight bounds while building the track record that justifies expanding them.

Set the escalation triggers broadly at first. If the agent escalates frequently, that is information about where the mandate needs refinement, not a failure state. Frequent escalation in the first month is better than infrequent escalation that masks deals the human operator would have rejected.

Document the mandate formally before the agent goes live. The mandate document should be version-controlled, reviewed by the relevant budget owner and brand safety lead, and signed off before the agent starts negotiating. This is the record the team refers to when reviewing the agent's deal history.

Common mandate-setting mistakes

The most common mistake is setting the mandate to match current human buying behaviour exactly. Human buying processes include implicit judgements, relationship factors, and contextual calls that are difficult to codify. A mandate that tries to replicate all of these becomes too complex to be useful and too rigid to let the agent operate effectively.

A better approach: identify the three to five criteria that matter most for a successful deal, build those into the mandate explicitly, and let the agent escalate on everything else during the proving period. As the human operator reviews escalations, they learn which criteria are actually decision-relevant and can refine the mandate accordingly.

The second common mistake is setting the volume cap too high in the proving period. If the agent can commit to large volumes before the team has confidence in its judgement, one poor decision can create a significant liability. Start with a volume cap that limits exposure to an amount the team is comfortable writing off if the agent makes an error.

When to expand the mandate

Mandate expansion should be triggered by evidence, not time. The questions to ask before expanding are: has the agent made decisions at the mandate boundaries that the human operator would have made the same way? Have the agent's escalated decisions been approved at a high rate? Has the agent flagged any decisions that the human operator was glad to have reviewed?

If the answers are consistently yes, the mandate is ready to expand in the relevant dimensions. If the escalation rate is low but the approved rate is also low (the agent is escalating things the team is rejecting), the mandate needs recalibration before expansion.

Frequently asked questions

Who should own the buying mandate?

The mandate should be owned by the person responsible for the campaign budget, typically the client lead or trading director. Brand safety constraints should be signed off by the brand safety team. The mandate is a cross-functional document, not a technology team artefact.

How often should the mandate be reviewed?

At minimum, the mandate should be reviewed monthly during the proving period and quarterly once the agent is operating at stage four or five autonomy. It should also be reviewed after any significant deal that required escalation or produced an unexpected outcome.

Can a single agent operate under multiple mandates?

Yes. An agent can hold different mandates for different advertiser relationships or campaign types, provided the platform supports mandate segmentation. Each mandate governs the agent's behaviour for that specific scope.