Review queue
The Review Queue in the web portal collects the items that need a person's judgement: documents a driver uploaded and confirmed, odometer, pump and document readings the system could not confirm, and refuels where the driver's and the merchant's pump readings disagree.
Overview#
The queue has three tabs, Documents, OCR Corrections and Pump Discrepancies, each with a count of open items. Each tab can be exported to Excel. A decided item leaves its tab, but an item can come back: a document returns when the driver confirms its fields again, and a pump discrepancy reopens when new readings are paired for the same refuel and still disagree. The odometer review list for flagged odometer readings is a separate page; see Review flagged odometer readings.
Documents tab#
Lists documents waiting for verification, that is documents whose fields the driver has confirmed after upload; see Document field extraction.
- Columns: Type, Owner, Vehicle, Uploaded, Expires and Extraction.
- Filters: Document type, a box where the document type's code is typed, and urgency: Expiring soon (within 30 days) or Expired.
- Detail: the uploaded pages, the extracted fields, and a Plate mismatch detected: warning when the plate read from a vehicle document did not match the driver's vehicles.
| Decision | Effect |
|---|---|
| Verify Document | The document becomes verified and leaves the queue |
| Edit Fields and Verify | Offered when the document has extracted fields. The reviewer corrects field values, then verifies with Save and Verify |
| Reject Document | A reason is required. The document becomes rejected and its uploaded pages are removed (the record stays) |
For a driver's own document, the driver is notified of the outcome; a rejection carries the reason and a link to upload again.
OCR Corrections tab#
Lists readings the AI check sent to a person:
- the AI could not read the photo, or returned no value or low confidence;
- a pump photo whose litres, unit price and total do not add up, which lowers the AI's confidence and so usually sends the reading here;
- an odometer the driver typed on the order that disagrees with the AI reading, or that the AI could not check.
The tab covers odometer, pump and document-field readings. Its columns are Image, Driver, Context, OCR Value and Captured. To see one driver's items, pick the driver in the Top Drivers by OCR Corrections (last 30 days) summary at the bottom of the tab.
The detail page shows:
- the source image, the context, when it was captured, and the Confidence reported by the phone's on-device reading;
- the OCR value and the AI value, with the AI's reasoning (LLM Reasoning) and, for odometers, the numbers it ruled out (Rejected Candidates);
- for a pump photo, the litres, unit price and total it read, marked cross-check OK or liters × price ≠ total;
- for an odometer the driver typed, User vs LLM reconciliation: the typed value, the AI value, the divergence, the tolerance used, and a badge with the outcome.
The reviewer enters the Corrected value and clicks Commit Correction. The value becomes the final reading and is written back: an odometer correction goes to the vehicle's verified odometer, a pump correction sets that side's pump reading on the order, and a document-field correction updates that field on the document. When the value cannot be applied (an odometer that is not a number, or one the odometer rules refuse), nothing is saved and the page shows "Failed to apply OCR correction to downstream entity.". How the AI check reaches these outcomes is on Odometer and pump photo readings.
Pump Discrepancies tab#
A pump discrepancy is raised when the driver's and the merchant's pump readings for the same refuel have both been accepted and differ by more than the company's pump tolerance: the larger of a fixed amount (0.5 L by default) and a percentage of the larger reading (1% by default). If newer readings for that refuel later fall within tolerance, an open discrepancy is resolved automatically.
The tab lists Order, Driver, Store, both photos, Driver (L), Merchant (L), Delta (L) and Flagged. To see one store's or one driver's items, pick it in the Top Stores by Discrepancy Delta (30 days) or Top Drivers by Discrepancy Delta (30 days) summary at the bottom of the tab.
The detail page shows both readings, both pump images, the delta and the tolerance used.
| Decision | Effect |
|---|---|
| Confirm Driver Reading | Resolved; the driver's reading is recorded as accurate and the merchant's as inaccurate |
| Confirm Merchant Reading | Resolved the other way round |
| Dismiss (tolerable variance) | Dismissed; a reason is required |
The decision is recorded on the discrepancy; it does not change the order's quantity or amount.
Notifications#
| Event | Who is notified |
|---|---|
| A reading is sent to the OCR Corrections tab | The company's users who can review OCR submissions, plus its Tenant Owner, Tenant Admin and Tenant Supervisor; never drivers |
| A pump discrepancy is raised or reopened | The same users; never the driver or the merchant |
| A driver's document is verified or rejected | The driver |
Permissions#
| Action | Tenant Admin | Tenant Supervisor | Other roles |
|---|---|---|---|
| Open the queue and decide items | Yes | Yes | No |
Acting needs the permission to review OCR submissions. Reviewers see only their own company's items.