Human-in-the-loop review,built into the pipeline.
Not a bolted-on task list: documents park at verify nodes inside the running pipeline, reviewers decide with full context, and the flow resumes automatically. Automation for the confident cases, judgment for the rest.
Park, decide, resume.
Review is a pipeline stage, not an afterthought.
Verify nodes
You place review gates in the pipeline and define what parks: failed validations, low confidence, business rules, samples.
3-pane workspace
Queue, record editor and page viewer with highlighted source regions: the reviewer sees claim and evidence together.
Automatic resume
Accept or reject resumes the document through the running pipeline; no manual re-submission, no lost state.
Review that survives operations.
The hard part of human review is not the UI, it is the lifecycle: reviewer edits must survive pipeline restarts and redeployments, decisions must be auditable, and the queue must stay meaningful as volume grows.
MiruIQ persists review state independently of pipeline runs: edits carry forward across stops and redeployments, every decision is recorded with who and when, and reviewer field definitions come from the verify configuration, so the queue shows exactly the fields that matter for the decision.
Human review questions
What operations teams ask about built-in review.
Rules you define at verify nodes: failed validation checks (totals that do not add up, missing required fields), extraction confidence below a threshold, cross-document inconsistencies, specific document types, amount limits, or random sampling for quality control. Everything else flows through untouched.
Three panes: the queue of parked documents, the extracted record as an editable form, and the original page with the source region of each field highlighted (OCR-snapped boxes, zoom, brightness and inversion controls for bad scans). The reviewer verifies against the document, corrects if needed, and accepts or rejects.
It survives. Review items and reviewer edits are persisted independently of the pipeline run, and carry forward when the pipeline restarts or is redeployed. A half-reviewed queue on Friday is the same queue on Monday, even if the pipeline was updated over the weekend.
See it on your own documents.
The 14-day free trial covers 200 documents: enough to define your schemas, run real files and measure the results before anyone calls you.