Home›AI Agency Academy›Lesson 09
Module 03 · Lesson 09

Give the agent one accountable job

Write an agent contract that makes its purpose, limits, and owner inspectable.

Last updated August 5, 2026•15–25 minutes•Free AI agent course
What you will learn

Write the agent contract

You will be able to write a one-page agent contract before configuring an agent, so everyone can see what it is meant to do and what it must not do.

Why this matters

Good agent work is useful before it is impressive.

‘Answer leads’ is not a job. An accountable job identifies who arrives, what starts the work, what good looks like, which actions are allowed, what is out of bounds, and who receives the exception.

Field note 09

Connect the trigger, context, action, owner, and measure

Connect the trigger, context, action, owner, and measure
Connect the trigger, context, action, owner, and measure
Core concepts

The language that keeps the work clear.

JobA narrow outcome the agent is responsible for supporting.
TriggerThe approved event that starts the agent, such as a new form, inbound message, or unassigned request.
ContextThe permitted information the agent can use and the source that owns each fact.
Acceptance conditionThe observable condition that shows the job is complete or needs a human handoff.
The practical method

How to write the agent contract

Write the trigger

Use a specific event rather than ‘whenever needed.’

Name the user and result

State whose request the agent supports and the useful outcome they should reach.

Set allowed actions

List the exact questions, records, messages, or recommendations the agent may create.

Define failure and ownership

Describe when it stops, who receives the case, and how the owner knows what happened.

Worked example

Worked case: give the agent one accountable job

A B2B software company uses an agent for inbound demo requests. Its contract says: when a new demo form arrives with a work email, summarize the stated problem, ask only for the missing qualification field approved by sales, create a CRM task for the regional owner, and send the approved acknowledgement.

It may not quote custom prices, promise product capability, or change account data. If a request concerns security, procurement, or an existing customer incident, it routes the conversation to the named team without improvising.

The acceptance condition is a complete record, clear owner, appropriate acknowledgement, and no unresolved high-risk issue.

Build it in practice

Complete the working artifact

Job: [one outcome]. Trigger: [event]. User: [person]. Permitted context: [sources]. Allowed actions: [list]. Never do: [list]. Handoff owner: [role]. Done means: [condition].
Practice

Before you move on

  • Write one agent contract on a single page.
  • Ask the operating owner to identify one unsafe ambiguity.
  • Remove any action you cannot explain or measure.
  • The job is narrow and outcome-led.
  • Permitted context and tools are named.
  • Prohibited actions are explicit.
  • A handoff owner and completion condition exist.

Lesson progress

Finished this lesson?

Save your place on this device so it is easy to pick up where you left off.

Not marked complete yet.