Work from the review queue
- Open Review & QC → Extraction review. Filter by document class, priority or result state and open a record you are authorised to review.
- Compare the original with extracted text or JSON and the field panel. Locate the source for each unresolved value.
- Correct and save an incorrect value, accept a supported value or reject it for resolution. Check required blanks, dates, identifiers and deterministic business checks.
- Resolve structured-component decisions, secondary labels, redaction issues and other blocking checks. An accepted empty required field must still block completion.
- Choose Finish review when ready. Field-level decisions alone do not complete document-level review.
- Follow any indexing, sampled QC or output eligibility action shown, then continue to the next document.
Choose the queue, narrow results by class or priority, and use Review next document or the row Review link. The example contains two fictional records awaiting review. Counts describe the loaded queue.
Understand indexing
Indexing requires the appropriate published policy and current source/schema/value bindings. A proposal approval is different from a confirmed indexing effect. Look for the recorded receipt.
If a published indexing policy is missing or revoked, ask an authorised administrator to resolve that blocker. Repeating field acceptance will not create the missing policy. Changed source versions or stale target revisions can invalidate an otherwise valid proposal.
Use quality control
QC selection is fixed against the job manifest under the configured sampling policy. Selection does not mean a pass. Compare the selected source/output and record a source-bound pass or fail.
A failed sample follows the exception and release gates. Do not retry simply to draw a different, favourable sample. Work allocation and supervisor permissions govern claims, handoffs and deadlines.
Keep decisions attributable
Permissions and current assignments determine which actions you may perform. Narrow exact-source field acceptance may occur in eligible reviewer journeys, but it is not unrestricted background document approval. Other fields and consequential stages retain their independent gates.
Verify document completion
- Confirm source version and class before field review.
- Check each critical value, type and supporting text/region. Record genuinely absent values rather than guessing.
- Save corrections and use Finish review; read remaining blockers.
- Confirm resulting state, index receipt and any QC/output action before continuing.