Check Odometer Readings Before Recording Trip Distance

1. Define the narrow desk decision

The dispatch-desk question is deliberately small: can two recorded odometer observations be linked to the same identified vehicle and the same identified movement, so their difference can be recorded as an observed distance? Start with the movement reference, not a remembered route, map display, or a number copied from another job. A movement may be a collection run, delivery leg, return leg, or another locally named movement. Give it one reference that can be read alongside the vehicle reference.

A start reading and an end reading are observations. They do not prove a planned route, an arrival event, a commercial distance, or the reason a vehicle moved. Record each as seen or reported, with its displayed value, unit, observation time, evidence source, and recorder or sender where known. Preserve the original entry even when a later review identifies a problem. A traceable correction may add context; it should not make the earlier observation disappear.

Source: BossFlow Fleet workflow scope

2. Gather the two observations before calculating

For each candidate reading, capture the same minimum facts: vehicle reference; movement reference; start or end marker; displayed value; unit; time observed or reported; evidence source; and recorder or sender if known. Evidence may be a signed desk sheet, supplied image, vehicle record, or handover note. This suggested worksheet does not rank one source as always stronger; it makes the source visible for later review.

Compare identity before arithmetic. The vehicle reference must match, unless a named verifier records why a stated match is supported by traceable evidence. The movement reference must also match. Check that both readings use the same stated unit and that their order makes sense for the movement. Do not quietly convert, infer, or fill a missing unit. If a meter changed, was replaced, reset, or its status is unknown, label that fact and leave distance unresolved until traceable evidence supports a decision.

3. Follow a concrete decision sequence

First, open the movement record and write its reference. Second, identify the vehicle attached to that movement at the time of each observation. Third, enter start and end observations separately, preserving source and time. Fourth, check whether vehicle reference, movement reference, and unit align. Fifth, note any intermediate movement, handover, meter change, unrelated use, or reading gap that could affect interpretation. Sixth, ask a named verifier to review a mismatch or uncertainty. Seventh, only when the evidence supports the link, calculate end minus start and label the result “observed odometer difference.”

This sequence is suggested internal practice, not a carrier requirement, universal industry standard, Malaysia service rule, or legal obligation. No carrier-specific example is used as a rule for another service. The sequence simply keeps a small operational fact reviewable: it shows what was observed and what remains unknown without turning an unsupported assumption into an established fact.

4. Use an adaptable internal worksheet

A suggested internal movement-reading worksheet can include: vehicle reference; movement reference; start observation; end observation; unit; start time; end time; evidence source for each observation; intermediate or unrelated movements; meter-change note; discrepancy note; named verifier; review time; and outcome. Keep the two observations in separate fields rather than replacing either one with the calculated result.

This worksheet is an adaptable internal proposal. It is not a carrier-specific form or a rule imposed on drivers, dispatchers, or customers. It does not direct meter handling, driver phone use, maintenance activity, route choice, payment treatment, or compliance decisions. Its narrow purpose is to preserve observable reading evidence and make the basis for a recorded difference clear to the next reviewer.

5. Decide from the evidence currently available

Use the table to choose the next record state. “Unresolved” is a valid operational result. It means the desk lacks a traceable basis to derive an observed difference; it does not mean staff should estimate one from a map, tracking display, or another job. If the operation records those other measures separately, they should retain their own labels and evidence.

A named verifier should record the review outcome and the evidence relied upon. If traceable evidence identifies an original entry error, retain the original entry, add a correction reference, and explain the reason. Do not overwrite a reading merely because a later number appears more convenient.

6. Fictional example / 虚构示例

Fictional example only: Northbank Parts uses vehicle reference L-17 and movement reference MV-204. A desk sheet records a start observation of 18,240 km at 08:10. An image supplied after the movement shows 18,286 km at 10:05, also labelled L-17 and km. The dispatcher records both sources, notes no reported intermediate movement, and asks verifier Mei to review the matching references. Mei records that the displayed readings and unit align. The suggested internal worksheet may then record an observed odometer difference of 46 km for MV-204.

In the same fictional setting, a later sheet lists 18,310 but names vehicle L-12. It is not added to MV-204 as an end reading merely because it is nearby in time. The worksheet records the mismatch, source, and reviewer. Likewise, if the end image has no visible unit, or the vehicle’s meter status is uncertain, the observed distance remains unresolved. This example contains no real fleet, customer, service outcome, statistic, or performance claim.

7. Five-item close check

Before closing the reading review, use the following suggested internal checklist. It is a review aid, not a carrier requirement or universal operating rule.

1. The vehicle reference is recorded for both observations and any difference has a named review note.
2. The movement reference is the same for both observations, or the readings remain separate.
3. The displayed unit is recorded and matches; no missing unit has been assumed or converted.
4. Each observation retains its time, source, and original recorded value.
5. The outcome is either an observed odometer difference with its basis or an unresolved result with the missing or conflicting fact.

8. Keep the boundary clear and close the review

This guide differs from nearby fleet topics because it concerns one evidence link: two odometer observations, one identified vehicle, and one identified movement. It does not decide whether empty repositioning was authorised, whether a driver should be reassigned, whether freight was collected, whether a passenger trip has costs to review, or whether waiting occurred. Those may be related events, but each needs a separate record and decision.

The existing AI conceptual fleet illustration is reused and labelled “Illustrative: AI concept imagery, not an actual customer fleet.” It is contextual only and supplies no evidence for a movement reading. Close the review by recording either the observed odometer difference with its basis, or an unresolved outcome with the missing or conflicting fact. Preserve original observations and the reviewer’s traceable note for a later evidence-based correction if needed.

Source: GOV.UK: writing user stories