Correct a document in review
Clear a low-confidence extraction from a work queue — claim, correct, submit — and understand what the system records while you do it.
Anyone with the Operator designation and at least one queue assigned. Supervisors can do everything below as well.
1. Open your queue
From Exceptions, your work queues are listed with a live count and your progress against each. Click Continue on a queue you are part-way through, or Start on a fresh one.
Opening a queue puts your pace and what is left in it at the top — the two numbers that tell you whether to keep going.
2. Read what the machine flagged
The workstream hands you the next matching document and focuses the first flagged field. Flagged fields are the only ones you are asked to look at — everything else already passed. The trigger chips at the top tell you why the document is here.
Selecting a field scrolls and highlights the region of the page the value was read from. If nothing highlights, the value was auto-filled from a lookup rather than read from the document.
3. Correct the value
Type the correct value, or click the right region on the page to re-anchor. The original value is never overwritten in the record — it is kept alongside your correction in the field ledger.
Confirming an unreadable PO number and moving to the next flagged field, keyboard only. Hosted externally.
Keyboard shortcuts
| Key | Action |
|---|---|
Tab | Next flagged field |
⇧ Tab | Previous flagged field |
Enter | Accept the field and advance |
⌘ Enter | Submit the document |
P | Park — waiting on an external answer |
S | Skip — hand to another operator |
Esc | Release the claim without saving |
4. Submit
Submitting closes every exception on the document. What happens next depends on your coverage:
- No coverage rule matched — the document delivers to its destination immediately.
- A coverage rule matched — it goes to a verifier as a second pass. You will see it again only if the verifier rejects it.
When to park instead of correct
Park when the answer is not on the page and not in the system — a vendor has to confirm a PO number, or finance has to decide whether an unbudgeted line is approved. Parking keeps the document in your queue with a visible reason and stops the clock on handling time, so parked work does not distort your team's throughput numbers.
Corrections train the next model revision. A guessed value is worse than a parked document, because it teaches the wrong answer and ships bad data downstream.