All insights

Which AI actions need a human sign-off?

Decide where an AI workflow can prepare work, where it can act, and who owns a consequential decision.

A fingertip hovers above a violet approval button.

The practical takeawayPut approval at the point where a draft becomes an external action or a change of record.

  1. Map the action
  2. Assign the decision
  3. Test the handoff

Consider a dealership inquiry about a vehicle advertised online. AI can summarize the shopper's question, find the relevant listing, and prepare a reply. Sending a message that promises a particular price or says the vehicle is on hold changes the conversation. Your team now has a commitment to honor. Drawing the line between preparation and action lets you give people real help while keeping decisions with the right person.

Describe the verb, the destination, and the consequence

Walk through one task with the person who does it. Write a verb beside each step: read, classify, draft, update, send, approve. Add the destination. Drafting a note in a private workspace differs from writing a value into a customer record that another team treats as final. The same sentence has different consequences in those two places.

For each step ask what happens if the answer is wrong, who notices, and how the team can undo it. An internal summary is easy to edit. A customer who receives an inaccurate appointment or offer may already have rearranged their day. A change that can technically be reversed can still cause real work for the person on the other end.

Give the reviewer something they can decide

A confirmation box that says “Proceed?” provides little help. Show the proposed action in plain language, the intended recipient or record, the source facts, and the exact content that will be sent or changed. Give the reviewer a clear option to edit, return it for clarification, or decline. A person who cannot see the underlying evidence is being asked to guess with extra steps.

In the dealership example, put the shopper's requested model next to the listing the assistant matched. Show when availability was last checked and leave the final customer message editable. If the listing changed or the match is uncertain, the sales representative can call the inventory owner. That intervention is valuable precisely because it happens before the shopper receives a promise.

Test delays, retries, and a change of mind

Human review introduces time. The request may wait overnight, the source may change, or someone may already have handled it by phone. Decide when an approval expires and what should happen if the draft changes after approval. For an externally visible action, a material edit deserves a fresh look at the final version.

Consider two staff members opening the same request. The system should identify when someone has already acted. A retry after a network interruption should check whether the message or update went through before attempting it again. Test those conditions with internal recipients and practice records. A demo that only tests one uninterrupted click leaves a common source of duplicate work unexplored.

Make the queue part of someone's job

Name the role that owns pending approvals and who covers an absence. Show the age of the oldest item. A workflow that saves writing time can still slow down a team if requests pile up unseen. Start with a manageable set of tasks and observe when staff actually open the queue during their day.

Review a sample of edits together. If staff repeatedly replace a greeting, that is a writing adjustment. If staff repeatedly correct the product, recipient, or commitment, keep the approval and investigate the underlying information. Removing a review step should follow evidence that the action is predictable, bounded, and easy to recover from.

A decision your team can document today

Choose one task and finish this sentence in your operating notes: “The assistant may prepare this material using these sources. This role checks these facts and takes this action when satisfied.” Add what happens if nobody approves it. For the inventory inquiry, the default could be that the draft stays in the queue and the customer receives no unverified offer. The team now has a concrete boundary to test, explain to a new colleague, and revisit as the workflow matures.

Ask someone from the next shift to find that rule and explain what happens to a waiting draft. Their answer will show whether ownership is clear when the usual reviewer is away.

Sources & further reading