← All posts

Review

Why a review queue beats a higher threshold

Raising the threshold feels safe and quietly drops good data. Routing the uncertain fields to a person keeps both accuracy and coverage.

·

4 min read

The first instinct when a wrong value slips through is to raise the confidence threshold. It works, and it costs you: every good field just under the new line is now sent back to the start.

Thresholds decide where a field goes

In Tolva a threshold doesn’t delete anything. Fields at or above it are returned as final; fields below it go to a review queue with the page region they came from. A person confirms or corrects them in seconds, and the corrected value is returned through the same webhook.

Setting it per field

Since r2.4 you can set thresholds per field. A total on an invoice can demand 0.97 while a free-text note accepts 0.8, so the queue holds only the fields where a mistake is expensive.

How to pick the number

  1. Start every field at 0.9.

  2. Watch the queue for a week.

  3. Lower the threshold for fields whose queued values were nearly always right.

The confidence is calibrated, so the share of the queue that needed no change tells you how far to move.