Manual Review
This chapter was written from the product's source code and has not yet been checked by a person on a running Cogneris. If what you see on screen differs, the screen is right — please tell your Cogneris contact so the chapter can be corrected.
Stops the process and puts each of its documents in a review queue, until a person approves or rejects them. Optionally, it lets a process through without a person when every field the AI read is confident enough and nothing else needs a human eye.
| Palette | Nodes › Manual Review |
| Outputs | One: once the review is approved, the run continues along every link of that output. A rejection does not take an output — see Approval and rejection. Before this version the editor also showed Alternative; a link still on it shows Alternative not routed and must move to the output before a new version is published. |
| Content status | From source; not observed (workflow-fe f88c5c1, workflow-be 6703373, 2026-10-22) |
When to use it
- After the phases whose results a person must confirm — typically Extraction, Cross-check, Facematch or a REST consultation.
- Before a phase that must only act on confirmed data, such as Generate document or Send.
The Document intake with review, Identity verification and Business onboarding workflow templates include this phase. Who reviews what is set up separately: see Organize human review.
What happens in a run
- The audit is gathered. The phase collects the output of every phase completed before it (classification, extraction, cross-check, face match and so on), so the review screen can show everything the AI produced in one place.
- Every document gets a type. A document that reached the review without a type (no Classification, Zero Shot, or Extraction with Detect document type ran before) is classified once, so that it lands in the right queue. An image that cannot be identified but contains a face is typed
selfie. If classification fails, the document stays untyped and the review screen shows its file name. - Fraud verdicts are read. For documents checked by the fraud pass, the graded verdict is fetched, so that a suspect document lands in the fraud queue rather than in its type's queue.
- Automatic approval is tried, only when Skip review when every field is confident is on — see Automatic approval.
- One review item per document is created, with the status pending. Documents that failed in an earlier phase are left out. If every document failed earlier, the failed documents are put in review instead, so a person sees what happened; the review never passes on its own.
- The process waits for the review, and its status in the Document Center becomes awaiting review.
A process with no documents at all completes the phase without waiting.
When the classification service refuses temporarily while checking an image for a face (step 2), the phase is run again after 30 seconds, then 2 minutes; after that it waits for review with that document untyped.
Review queues
Each document waits in exactly one queue:
| Queue | Holds |
|---|---|
| One queue per document type | Documents of that type. The type is compared ignoring case and surrounding spaces. |
| Unidentified | Documents that reached review without an identified type. |
| Fraud review | Documents the fraud pass flagged. |
| Face conference | Selfies, for the face comparison. |
The queues are not configured in the phase. An administrator assigns reviewers to them in Administration › Review Queues; a reviewer with no queue sees all of them. See Organize human review.
Automatic approval
With Skip review when every field is confident on, the process is approved without a person only when all of the following hold. If any does not, it goes to review as usual.
- It is not a correction round (a process resubmitted after a rejection).
- It has documents, and none failed in an earlier phase.
- No phase whose result only a person can judge completed before the review: Facematch, Cross-check, Signature validation, or a REST integration that publishes its answer for the review screen.
- An Extraction or Zero Shot phase ran before it.
- No document has a fraud signal or was blocked by the fraud pass.
- No document is a selfie, and every document has an identified type.
- Every field extracted on every document carries a confidence, and the lowest of them is at or above Minimum confidence (%). A field the AI did not find counts as confidence 0.
An automatically approved process still records one review item per document, approved with no reviewer and a note giving the lowest confidence and the threshold. The step's output says it was approved automatically.
Approval and rejection
- Approved (every document decided and none rejected, or approved as a whole): the phase completes and the run continues to every phase connected to it, whichever output the connection was drawn from.
- Rejected: the run does not continue. A process from the Portal goes back to its requester; a process started inside Workflow ends as failed (
manual_review_rejected). See Organize human review.
Configuration
| Field | What it does | Required | Format / values | Default | Validation messages |
|---|---|---|---|---|---|
| Description | Name shown on the node. | No | Text | Manual Review | — |
| Skip review when every field is confident | Turns automatic approval on. The panel explains: When every field the AI extracted on every document is at or above this confidence, the process is approved without a person. Fraud signals, selfies, unidentified documents, correction rounds and face match, KYB, cross-check or signature checks always go to review. | No | On / off | Off | — |
| Minimum confidence (%) | The lowest field confidence that still allows automatic approval. Shown only when the option above is on. | Yes, when shown | Whole number from 1 to 100; other values are rounded and brought into range; an empty or invalid entry reverts to the previous value | 95 | — |
Settings the panel does not show are kept when you change these (for example keys added earlier by hand).
Common problems
| Message | Cause | What to do |
|---|---|---|
| A process waits in review although Skip review when every field is confident is on | One of the conditions of Automatic approval was not met — most often a field below the threshold, a field without confidence, a selfie, or a cross-check or facematch before the review. | Expected. Lower the threshold only if the risk is acceptable. |
| A phase connected to Alternative runs after an approval | A version published earlier keeps running every link it has. | Connect the link to the output and publish again; a rejection stops the run, so it cannot take a path of its own. |
| A document waits in Unidentified | No phase gave it a type and the classification at review time did not identify it. | Add a Classification or Zero Shot phase, or let a reviewer classify it. |
Related
- Organize human review — queues, reviewers, returning a process to its requester.
- Cross-check, Facematch, Signature validation — their results always need a person.
- Extraction, Zero Shot — provide the field confidences.
- Design and publish a workflow
Last reviewed 2026-10-22 · Version 1.0.0 · Owner: product-documentation