When to route to review

Which conditions set NeedsReview — low confidence, readings that disagree, a missing required field, a failed rule — and how to route on them.

A production document extraction workflow should not treat every successful parse as sufficiently trustworthy.

Review triggers

Review should be triggered when:

  • validation rules fail
  • confidence is weak or inconsistent
  • evidence cannot be grounded in the source document
  • a field conflicts with another field in the same document
  • OCR or model output appears fabricated or suspicious

Result contract

The NeedsReview flag is the product-level signal for this. It gives applications a clear decision point before entering downstream business logic.