Define the result and human decision

Delegation starts with the result you need. Describe usable materials, delivery format and quality criteria. Explain where you need to intervene: approving copy, choosing an option or confirming an external action.

For example: ‘Prepare a proposal for this customer using the attached rates. Flag missing details and leave the email ready for review.’ The person retains the offer and sending decisions while the employee organises information and prepares delivery.

Connect only what the task needs

The cable metaphor helps visualise configuration: employees connect to particular resources and actions. A connection may permit reading information while another action needs approval. iabot uses three decisions: Deny, Ask for my approval and Allow without asking.

The skill supplies the method; permission authorises the action. Email instructions do not grant a mailbox, and knowing a publishing procedure does not permit publication. Review the specific accounts and tools available to the employee.

Use clear review points

  1. Agree on the goal and authoritative sources first.
  2. Request a plan for multi-stage work or outstanding requirements.
  3. Check a sample before applying the procedure to a whole batch.
  4. Review the content and scope of approval requests.
  5. Open the deliverable and verify that it satisfies the brief before using it.

Expand autonomy from evidence

For recurring work, preserve the procedure and record needed corrections. Assess concrete quality: correct data, usable files, verifiable references and actions in the intended place. This evidence informs which parts may gain autonomy.

Keep human review where judgement matters or commitments affect the company. Recheck permissions and results when the process, application or recipient changes. Directing an AI employee means building a workflow your team understands, can review and can adjust.

Sources and documentation