← Back to all postsMay 29, 2026

Before using an AI agent, define the work you are delegating

An AI agent needs a defined job and clear limits. Decide what it may read, change and send before connecting it to business systems.

A coordinator delegates a bounded task while retaining the approval record.

Before connecting an AI agent to business systems, write down the job you are delegating. Define what it may read, what it may change and when it must ask a person.

An agent that can take actions needs more than a good prompt. The business needs a way to check its work, handle exceptions and stop the process when something goes wrong.

Begin with a narrow task you understand well enough to supervise.

Describe a finished piece of work

“Help with sales” leaves too much open. A clearer task might be to prepare a summary of an incoming enquiry for the office coordinator to review.

Specify the information the summary should contain, how it handles missing details and where the draft belongs. A summary should not silently become permission to send a quote or promise an appointment.

That is a hypothetical first task for a local service business. The useful boundary is that a person can check the output before the next customer-facing action.

Separate information from instructions

An enquiry, attachment or web page can provide facts relevant to the work. It should not be allowed to expand what the agent is authorised to do.

For example, a message requesting a different payment destination needs the business's normal verification process. The fact that an agent can read the message does not make the request trustworthy.

Define which sources are approved for facts such as service scope, prices and policies. If those sources disagree or omit an important detail, route the uncertainty to the person responsible.

Limit the actions available

Give the workflow only the access its current task requires. A draft-preparation trial may not need permission to send email, change customer records or spend money.

Keep consequential actions behind an explicit approval step. Define what a person is approving so a broad instruction does not quietly become permission for a new kind of change.

When a task fails, the agent should leave a useful record and alert the right person. It should not keep repeating an action when it is unclear whether the first attempt succeeded.

Prepare a delegation brief

Before a live trial, agree:

  • Task: the specific work and its stopping point.
  • Information: approved sources and how missing details are handled.
  • Access: systems it can read and actions it can take.
  • Approval: decisions that remain with a person.
  • Exceptions: what requires escalation instead of a guess.
  • Records: what is logged without collecting unnecessary sensitive details.
  • Review: how the business will assess quality, effort and failures.

Have the people handling the real work review the brief. They may recognise an exception that a polished demo never encounters.

Test the boundaries as well as the normal task

Use safe representative examples, including incomplete, duplicate and contradictory requests. Confirm that the process stops or asks for help where the brief says it should.

Check the work needed to review and maintain it. A workflow that needs constant correction may need a smaller scope or a different method.

A successful trial gives you evidence about that defined task. Review any proposed expansion separately before granting more access.

For help scoping a supervised workflow, tell us what you want to delegate and what must remain under your control.

Free rank audit