Can an AI-extracted document become a trusted record?
Fleetpass is a vehicle and driver document-compliance product. A fleet operator uploads a document, AI extracts what it says, the operator confirms or corrects it — and only then does it become the record that drives reminders, renewals, reporting and audit history.
The problem
A fleet’s compliance position lives in a drawer: insurance certificates, roadworthiness papers, driver licences, permits, each with its own issuer and its own expiry. The failure is rarely that nobody knew a document existed. It is that nobody knew it expired last Tuesday until a vehicle was stopped.
Extraction is the obvious lever — read the document, take the dates, drive the reminders. It is also where this kind of product usually goes wrong. An extracted expiry date that is confidently wrong is worse than no date at all, because the system will now reassure an operator on a schedule.
Verification is a product state, not a review step
So a document in Fleetpass is never in one state. It is extracted, or it is verified, and the two do not behave the same way.
- Extracted fields — document type, plate number, expiry date, issuer — are shown as proposals, attributed to the extraction, and editable in place.
- Nothing downstream reads an extracted value. Reminders, renewal scheduling, reporting and audit history all read the verified record only.
- Confirming is explicit and per-field, because operators correct one wrong date far more often than they reject a whole document.
- A field the extraction could not read is empty and marked, never guessed. An unreadable expiry date is a question for a person, not a low-confidence number.
| State | What the operator sees | What it drives |
|---|---|---|
| Uploaded | The document, and that extraction is running. | Nothing. |
| Extracted | Proposed fields, attributed and editable, with unreadable fields empty and flagged. | Nothing. This is the point of the split. |
| Verified | The confirmed record, with who confirmed it and when. | Reminders, renewals, reporting, audit history. |
| Expiring / expired | The verified record with its remaining life, and the renewal action. | Escalating reminders and the compliance view. |
What it establishes
The design claim is small and, I think, portable: an AI-extracted value can become a trusted record, but only if the product models the moment it stopped being a guess. Confidence scores do not do that job — they let a system act on its own uncertainty and describe it afterwards.
Fleetpass is in production use. It does not make a compliance determination; it records the one a responsible person made, and keeps the trail that shows when they made it.
