Human authority

When should an AI agent need human approval?

Your team knows how to keep a workflow moving. It also needs to decide when a person must review an action before work continues. A useful approval request presents the exact action, the available evidence and the expected consequences. It should still make sense when a colleague takes over the mission.

This guide offers practical criteria for designing these decision points, sometimes called Human Gates, into workflows you build for clients.

In brief

The question and the useful result.

Question
Which action is a person approving, and when must that agreement be reviewed again?
Useful result
An approval record and a case in which the attachment changes after approval.

Human authority

Place approval where a decision is still needed

Start with the actions and their consequences. Define which cases can proceed under an existing authorisation and which need human review. For example:

  • An action falls outside the scope agreed with the client.
  • Conflicting information makes the next step unclear.
  • A business record change or an external message requires approval under the team’s rules.
  • Permissions or execution conditions have changed since the action was prepared.

Specify who can decide and what that person needs to examine. When approval is required, define an explicit waiting state if no decision arrives. An elapsed deadline should not become tacit permission by default.

Human authority

Ask for approval of an identifiable action

A question such as “Approve the next step?” leaves too much room for interpretation. Present a short decision record that answers five questions.

QuestionWhat to show
What will happen?The exact action and expected outcome.
What does it affect?The record, recipient or items involved.
Which version is being reviewed?The proposed content and any attachments.
Why is a decision needed?The applicable rule, exception or missing information.
What are the limits?The scope and conditions under which the decision remains valid.

Provide distinct responses: approve, reject or request a correction. Keep the reviewer’s identity, the date and a reference to the action they examined. Someone taking over should be able to see what was accepted without reconstructing the entire conversation.

Human authority

Example: the message is approved, then its attachment changes

In this illustrative scenario, an agent prepares a client email. A person approves its text, recipient and attachment. Before sending, the workflow replaces that attachment with another version.

The decision now needs review: did the earlier approval cover this change? If it applied to the original document, request approval of the modified action before proceeding.

Three facts need to remain distinct:

  • Mission state: the revised message is waiting for a decision.
  • Authorisation: the recorded approval applies to the previous version.
  • Outcome evidence: an approval does not establish that a message was sent.

This scenario illustrates a design approach. It does not announce a qualified email integration in DUBSAR.

Human authority

Check that approval works within the wider workflow

Review a few specific cases: the recipient changes, approval is withdrawn, the content evolves or another person takes over. In each case, the team should be able to establish which decision still applies and whether a fresh review is needed.

The useful output is a decision record: the action examined, its scope, the human choice, its conditions and what happened next. If your workflow tool already supports approval, start there and check how this information stays connected to the rest of the mission.

Human authority

Frequently asked questions

Should every action need approval?

Define decision points around the scope, consequences and client’s rules. Other actions can follow the authorisation framework established for them.

Is an agreement in a conversation enough?

You need to be able to identify the exact action and conditions accepted. If a “yes” is ambiguous or cannot be found during a handover, the decision record is insufficient.

Does approval confirm that an action succeeded?

No. The human decision records what may be done. Execution evidence is then needed to establish what actually happened.

Human authority

Where DUBSAR fits

DUBSAR is developing a foundation that connects mission state, authorisations, human decisions and execution evidence alongside existing tools. Selected workflows have been tested; end-to-end validation for B2B use is still underway. Pilots are not currently open.