---
title: "Human-in-the-loop review | Skills We Assign For | Azendo"
description: "Human-in-the-loop design — routing thresholds, interface, feedback, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/human-in-the-loop-review/"
---

[Skills](https://azendo.co/skills/) Automation platforms 

# Human-in-the-loop review.

Human-in-the-loop review routes cases an automated system cannot handle confidently to a person, whose decision completes the process and can be fed back as training data.

## Where Human-in-the-loop review fits on a long engagement.

Full automation of ambiguous work is usually the wrong target. A system handling eighty percent confidently and routing the rest to a person delivers most of the value at a fraction of the risk, and it degrades gracefully rather than failing silently on the hard cases.

The routing threshold is a business decision with a cost on each side. Set too high, people review cases the system would have handled correctly; too low, errors reach production. It should be set from the relative cost of a review versus an error, not from a default.

## What an assigned team does with Human-in-the-loop review.

The review interface determines whether the model works. A reviewer who has to open three systems to make a decision is slow and inconsistent; one shown the document, the extracted values and the specific uncertainty is fast and accurate.

Designing that properly is interface work rather than automation work, and it is scoped with [outsource ux design](https://azendo.co/services/ux-ui-design/) alongside the automation capacity.

## What we use Human-in-the-loop review for.

* Confident cases automated, the rest routed Most of the value with none of the silent-failure risk.
* Thresholds set from relative cost Review cost weighed against error cost rather than a default confidence level.
* Decisions fed back as training data Reviewer judgements improving the model rather than being discarded.

## How Human-in-the-loop review capacity is assigned.

Review workflow design is assigned across automation and design capacity, since the reviewer interface decides whether the model works.

## Service lines it sits in

* [AI automation engineering](https://azendo.co/services/ai-automation-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in automation platforms

* [n8n — skill we assign for](https://azendo.co/skills/n8n/)
* [Make — skill we assign for](https://azendo.co/skills/make/)
* [Zapier — skill we assign for](https://azendo.co/skills/zapier/)
* [Power Automate — skill we assign for](https://azendo.co/skills/power-automate/)
* [UiPath — skill we assign for](https://azendo.co/skills/uipath/)
* [Automation Anywhere — skill we assign for](https://azendo.co/skills/automation-anywhere/)
* [Blue Prism — skill we assign for](https://azendo.co/skills/blue-prism/)
* [Workato — skill we assign for](https://azendo.co/skills/workato/)

## Tell us what your roadmap needs Human-in-the-loop review for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)