When a verification solution is bought, the first thing done is distributing readers to the field. That is necessary but not sufficient on its own: the device gives an answer, and where that answer goes is a separate design job.
Whose reading is it
Every reader needs an owner. If it is not known who used the device, the result belongs to nobody and provides no ground in a dispute. Permissions come from the same place: some teams only read, some flag results, some open campaigns.
A reading with no owner is a reading that did not happen.
Getting the record to the centre
The field is often where coverage is weakest: a warehouse, a customs yard, a rural dealer. If a reading cannot be sent at that moment it must accumulate on the device and transfer by itself when a connection returns. Otherwise the most critical readings are the ones that are lost.
What the report should show
- Reading density: how much checking was done in which region.
- Negative result rate: comparison by region and by dealer.
- Repeating points: continuous negative results coming from the same place.
The third is the most valuable. A single negative reading is an incident; dozens from the same point is a pattern, and a pattern directs your inspection plan.
How many devices
The first instinct is to give everyone a device; what works in practice is counting the points where a reading is actually taken. How often does a regional manager meet the product, how many shipments enter which warehouse — those numbers give you the device count. A device nobody uses is in a drawer by the end of the first month.
Who holds the device matters, but so does who is accountable for it, in writing. An unowned device goes missing, and a missing device is not only lost hardware — it is the lost verification at that point.
How long training takes
The reading step is simple and takes minutes to learn. What takes time is not the reading but what the result means: when to release the product, when to open a record, when to escalate. Split the training across those three thresholds and one shift is enough.
Where staff turnover is high, training cannot be a one-off. Showing the steps in sequence on the device's own screen makes it repeatable; someone who joins today can take a reading on their first day.
When there is no connection
The field is not always in coverage. In a warehouse basement, a customs yard or open country, the connection drops. Recording the reading there and then and sending it when the connection returns is the most practical way to build trust in the field: staff do not wait, and work does not stop.
A verification step that is not used in the field counts as never deployed.