Skip to main content

Verification Workbench

Verification Workbench is where humans correct what OCR and AI could not safely decide.

Verification Workbench

Design goal​

The verifier should not read the whole document from the beginning. The system should guide the user to:

  • missing required fields;
  • low-confidence fields;
  • inconsistent totals;
  • suspicious dates;
  • unknown suppliers;
  • line items that need approval or correction;
  • duplicate documents;
  • export blockers.

Work modes​

Productivity mode​

Default mode for professional verifiers. It shows:

  • next focus field;
  • confidence heatmap;
  • missing fields;
  • QA requirement;
  • productivity metrics;
  • action shortcuts.

Header mode​

Used for invoice-level data:

  • buyer and seller;
  • invoice number;
  • invoice date;
  • due date;
  • VAT number;
  • IBAN;
  • totals;
  • currency;
  • payment terms.

Lines mode​

Used for line item review:

  • description;
  • product or service code;
  • quantity;
  • unit;
  • unit price;
  • VAT rate;
  • line total;
  • cost center;
  • project;
  • approver;
  • line status.

Large documents with hundreds or thousands of lines should use paging, virtual scrolling, keyboard navigation, and bulk accept actions.

Focus mode​

Focus mode hides non-essential navigation and maximizes the document plus fields. This is the recommended mode for daily verification.

Dual monitor mode​

Planned mode for professional teams. One screen shows only the document, another shows fields or lines.

Region OCR​

Region OCR lets a verifier select an area in the document and write the result into a field. The region engine can be configured separately from full-document OCR.

Recommended use:

  • Tesseract for fast local region OCR;
  • premium AI fallback when local OCR confidence is low;
  • keep the selected region and field update in history.

Document overlay​

Recognized OCR zones should be shown on the document:

  • all recognized regions as soft rectangles;
  • focused field region highlighted stronger;
  • line item region highlighted when a line is focused;
  • low-confidence regions in warning color;
  • missing field remains unbound.

Locks and concurrency​

Enterprise verification requires locks:

  • document is locked when a verifier opens it;
  • heartbeat keeps the lock active;
  • another user sees who holds the lock;
  • takeover can require permission or reason;
  • lock events are audited.

Keyboard-first work​

Recommended shortcuts:

ActionShortcut
Next fieldAlt+N
Previous fieldAlt+P
Accept safe fieldsAlt+A
Lines modeAlt+L
Next lineAlt+ArrowDown
Previous lineAlt+ArrowUp
Accept safe linesAlt+X
SaveAlt+S
Refresh queueAlt+R
Duplicate queueAlt+D
Bulk OCR visible queueAlt+B
ApproveAlt+Enter

Verifier quality metrics​

Track:

  • documents per hour;
  • fields corrected per document;
  • lines corrected per document;
  • first-pass yield;
  • rework count;
  • hotkey usage;
  • SLA status;
  • QA sample failures;
  • average time locked.

These metrics should improve the product and team process, not become blind pressure on users.