The paper waybill, replaced: trips, odometer and offline entry

The paper waybill has one great virtue: it works without electricity. Everything else about it is a liability. It is filled in from memory, it is legible to its author and to nobody else, its arithmetic is done by the same person whose numbers are being checked, and it reaches the office weeks after the fact.

Replacing it is not about digitising the form. It is about changing which fields a human is asked for.

What a trip record actually needs

Five things, and they take under a minute on a phone:

• Date, and departure and arrival times;
• Driver — implicit, because the driver is the one holding the phone;
• Vehicle, chosen from the fleet rather than typed;
• Route — where from, where to;
• Odometer at start and at end.

Notice what is not on the list: distance. Kilometres are calculated from the two odometer readings, never entered. This is the single most important design decision in the whole record, and it is worth being explicit about why.

Derived mileage cannot lie to you quietly

When distance is a typed field, it is an independent number that has to agree with the odometer, and nothing forces it to. Any disagreement is invisible until someone sits down with a calculator, which in practice is never. When distance is derived, there is only one place a mistake can live — the odometer reading — and a wrong odometer reading announces itself immediately, because the next trip starts somewhere else.

That continuity is the check paper cannot perform. Every trip should begin where the previous one for that vehicle ended. A gap means a trip was never recorded. A reading lower than the one before it means either a typo or something that needs a conversation. Neither is discoverable in a stack of handwritten forms.

Offline is not a feature, it is the condition

Field crews work where the signal ends. A tool that requires connectivity to accept an entry gets abandoned in its first week, and what replaces it is the same paper form with an extra step of resentment attached.

So the driver app stores the entry on the phone and syncs it by itself when the vehicle returns to coverage. The driver does not need to know whether they were online; they need to know the trip is recorded. Nothing is lost in a dead zone, and — this is the part that matters for data quality — nothing has to be held in someone's head until the evening.

Data entered at the moment of the trip is a record. Data entered a week later is a reconstruction. Offline capture is what moves a month from the second category into the first, and every downstream report inherits that difference.

What the office gets instead of a folder

The same entries, immediately, as structured rows: per-vehicle distance and cost, per-driver days and trips, a refuelling log with the odometer at each pump. Nobody retypes anything, so nobody introduces a second generation of errors, and the month closes when the last trip syncs rather than when the last folder arrives.

Being straight about the legal side

This is a management record, not a state electronic waybill. If your accounting or your contracts require the paper document, keep issuing it — the trip records will match it, and they will be ready weeks earlier. What changes is that the operational truth stops living exclusively in a glovebox.

How to switch without losing the month

Do not migrate history. Take today's odometer reading on each vehicle as the starting point, and from tomorrow drivers log trips from the phone. Close the paper month the way you always have — for the last time. Your first full report comes out for the following month and is internally consistent from its first line.

The temptation to "just enter the last six months first" has killed more rollouts than any technical problem. It is weeks of work, the data is reconstructed from memory anyway, and the team burns out before it sees a single useful report.

Depot 17 gives drivers an app that records trips offline and gives the office reports built from those records. Register your organisation and start with tomorrow's odometer.