Imagine the same supplier quote coming back for a third pass. The unit price is clear. The number of units in a carton is not. Each pass produces a tidier summary, with the same little gap where the comparison needs an answer.
We would rather see that gap arrive on somebody’s desk than watch another polished version circulate. If an automation cannot finish, its next owner should receive the missing field and the source together.
Here is a fictional rehearsal, not a description of a deployed system. A quote shows $72 per carton, but the carton quantity is unreadable. The comparison needs a price per unit. Without the quantity, dividing $72 by an assumed pack size would manufacture the answer.
For this rehearsal, set a limit of three extraction attempts against the same source version. That is a test rule, not a recommended number for every workflow. Count the initial attempt. After the third unresolved result, stop the extraction and create a review task. Do not submit an order, substitute zero or mark the comparison complete.
The handoff should contain enough evidence to avoid a fourth person starting from scratch:
Quote reference: fictional Q-17, page 2
Source version: scan received Monday, 10:00
Supported amount: $72 per carton
Unresolved field: units per carton
Attempts used: 3, including the initial attempt
Next owner: purchasing reviewer
Needed answer: confirmed carton quantity, with its source
Permitted next step: review or request a clearer quote
Now test the stopping point. Feed the same unreadable fixture through the rehearsal again. The expected result is one open review task with the original source attached, not another attempt or a completed per-unit price. Check the attempt count as well as the final status. A workflow that says “needs review” but keeps trying in the background has not stopped.
If a clearer quote arrives, keep its new version separate. The reviewer can decide whether it supplies the missing quantity and whether another extraction is appropriate. A new file should not silently erase the history of the unresolved one.
Our earlier free note explains why the missing charge should remain visible: https://www.rebuildshow.com/p/leave-the-freight-cell-blank
Before rehearsing one automated task, write its stopping rule and the evidence its next owner will receive. Then use an unresolved fixture to check that the handoff actually happens.
The Rebuild Editorial


