Human in the loop: where people should decide in an automated process
SynaptaGrid8 min read
In short
Human in the loop means an automated process pauses at chosen points for a person to review, correct or decide before it continues. It is worth using where a wrong result is costly, where judgment is needed, or where a rule or regulation requires a person to be accountable. It is not worth using for every step: a person who approves everything stops reading. A good design lets the machine do the checks it can do, shows the person only what needs a decision, records who decided and what they saw, and says what happens when nobody answers. “Human on the loop” is a lighter version in which a person monitors the process and steps in when something looks wrong.
In the loop, on the loop, out of the loop
The phrase covers three arrangements. Choosing between them is the first design decision.
| Option | What the person does | When it fits |
|---|---|---|
| In the loop | The process waits for the person’s decision at a defined step | A wrong result is costly or irreversible, or someone must be accountable |
| On the loop | The process runs; the person watches and can stop or correct it | Mistakes are cheap to undo and volume is high |
| Out of the loop | The process runs without a person at any step | The rule is fully defined and the result is easy to verify |
Where a person decides
Where to put the human step
- Before something that is hard to undo
- Paying money, sending a message to a customer, deleting records, changing a contract.
- Where judgment beats a rule
- An exception to a policy, a borderline case, a request that the rules did not foresee.
- Where accountability is required
- A signature, a sign-off or an approval that an auditor will ask about.
- After an AI step
- When a model drafts, checks or summarises something, a person reviews the result before it is used.
The old way and the new way
The table compares an automation with no person in it, or a person added by email, with a human step built into the process.
- Review
- The old way: An email asking someone to look, with no record of the answer
- The new way: A task for named approvers, with the decision saved on the record
- What the person sees
- The old way: Everything, so they stop reading
- The new way: The result of the step and only what needs a decision
- A model’s output
- The old way: Used straight away
- The new way: Reviewed by a person before it is used
- Nobody answers
- The old way: The request waits indefinitely
- The new way: A rule for who decides, and what happens next
- Evidence
- The old way: Search inboxes
- The new way: A run history with each step and who decided
Common mistakes
- Approval fatigue
- If a person approves a hundred items a day, they approve without reading. Send them only what needs a decision.
- Showing a bare yes or no
- Show the person what the step produced and what it was based on, or they cannot judge it.
- No rule for silence
- Decide who decides when the named person is away, and what happens if no one answers.
- The loop without a record
- A decision that is not saved cannot be explained later.
How we decided
In SynaptaGrid Automation a step can ask a person, and the person is chosen by one of seven approver rules: one person, a list of people, a role, a quorum, weighted votes, any of a group, or all of a group. The decision is saved on the record, and the run history shows each step.
A step can also use AI to draft, check or summarise, with a person approving the result. We have run this in workspaces of our own. We have not measured the cost of AI steps, and this guide says nothing about it.
We chose to make the human step a first-class step with a stated rule for who decides, not a free-form message. The cost is that a very informal check needs to be set up as a step. The benefit is that every human decision has an owner and a record.
The person can complete the review in the Automation screens, or from an AI assistant connected to the workspace: in our live run in November the assistant listed the signed-in person’s open task and recorded the decision with a reason code, under the person. We ran this in Claude only.
Standards and accepted practice behind this
These are the practices the guide rests on. We align with them. This page does not claim a certification.
- Meaningful human oversight
- A person who can understand what they are deciding, and who is able to change the outcome, not only to confirm it.
- Source: EU AI Act (Regulation 2024/1689), Article 14: human oversight (opens in a new tab)
- Segregation of duties
- The person who starts a process is not the only person who approves it.
- Source: NIST glossary: separation of duty (opens in a new tab)
- Audit trail
- Each decision records who decided, when and on what information.
- Source: NIST glossary: audit trail (opens in a new tab)
- Risk-based review
- Put people where the cost of a wrong result is highest, not everywhere.
Where SynaptaGrid fits
SynaptaGrid Automation runs processes in which checks run first and a person or a group decides at the steps you choose. The supplier approval example on the site was built and run in our own workspace.
Use it where a process mixes automatic checks with a decision that needs a named person.
Frequently asked questions
- What does human in the loop mean?
- It means an automated process pauses at chosen points for a person to review, correct or decide before it continues.
- What is the difference between human in the loop and human on the loop?
- In the loop, the process waits for the person at a defined step. On the loop, the process runs and the person monitors it and steps in when something looks wrong.
- When should a person be in the loop?
- Where a wrong result is costly or hard to undo, where judgment is needed, where accountability is required, and after an AI step whose output will be used.
- What happens if nobody answers?
- The process should have a rule for it: who else decides, and what happens next. A step that waits for whoever sees it can wait forever.
SynaptaGrid
Put a person where it matters
Walk through one process and choose which steps need a decision.