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 role who belongs to a team assigned to at least one work queue. Supervisors can work the same loop.
1. Open your queue
Open Reviews in the sidebar. As an operator you land on My work queues, which lists the queues your team is assigned to, each with its open count and how much of it is cleared. Select a queue's Open queue card. The workstream claims the next matching document for you and opens it. Supervisors open a queue from the Work queues tab and pick a document from its list.
The bar across the top shows done today, your pace and left in queue, with the percentage of the queue cleared. Your claim on the document lasts 10 minutes and renews for as long as the document stays open.
2. Read what the machine flagged
Flagged fields are the ones the Extract stage was not sure of. Each one carries a ⚠ mark, and every group shows how many flagged fields it holds. Press ⌥↓ and ⌥↑ to step between flagged fields, or ⌥⇧F to hide everything else. A failed cross-field rule shows as a validation error, and ⌥E jumps to the next one.
Moving to a field highlights the region of the page its value was read from. If nothing highlights, the value has no recorded location. Press ⌥D, or hold ⌥ and drag, to draw a box around the right text and fill the field from it.
3. Correct the value
Start typing to replace the value, then press Enter to commit it and move to the next flagged field. If the extracted value is already right, ⌥Y confirms it as-is. Backspace marks the field as not present in the document, and ⌥R reverts to the extracted value. To use text from the page, select it and press Enter.
The original extracted value is never overwritten. It is kept beside your correction, along with who made it, when, and the field's confidence at the time. ⌥M adds a note, which a verifier sees next to your change.
Keyboard shortcuts
Keys are shown for macOS. On Windows and Linux, ⌥ is Alt and ⌘ is Ctrl. The Keyboard shortcuts button in the workstream's top bar lists every binding.
| Key | Action |
|---|---|
⌥↓ / ⌥↑ | Next / previous flagged field |
Tab / ⇧ Tab | Next / previous field |
Enter | Edit, commit, confirm and move to the next flagged field |
⌥Y | Confirm the value as-is |
⌥R | Revert to the extracted value |
⌥D | Draw a box on the page to fill the field |
⌘S | Save without leaving the document |
⌘ Enter | Save and move to the next document |
⌥K | Park: route to a supervisor |
⌥S | Skip: leave it for later |
[ / ] | Switch queue |
⌥[ | Re-open the document you just left |
Esc | Release the document and leave the workstream |
4. Submit
When every flagged field is dealt with, press ⌘ Enter. Your corrections are saved and the next document opens. What happens to the one you submitted depends on the review coverage a supervisor sets for you on the Operators tab:
- Not sampled: it is marked Corrected. Once every document its job is holding for review is cleared, the job resumes and delivers to its destination.
- Sampled: it moves to the Verifier queue. Someone other than you checks your changes and confirms or amends them. It does not come back to you.
Sampling applies only if you are marked Needs review. Otherwise every submission is marked Corrected directly.
When to park instead of correct
Park (⌥K) when the answer is not on the page and you cannot settle it yourself, for example when a vendor has to confirm a PO number or finance has to decide whether an unbudgeted line is approved. Choose a reason: Ambiguous, Illegible, Missing page(s), Wrong document for this queue, Duplicate of another item, or Other with a note. Parking routes the document to a supervisor with your reason attached, releases your claim, and takes the document out of your queue.
Skip (⌥S) means "not now". It also asks for a reason, but the document stays in the queue for anyone to pick up, including you on a later pass. Nobody is notified.
A guessed value is worse than a parked document. Unless your submission is sampled for verification, the guess goes to the destination as if a person had confirmed it.