Reconcile the vehicle register before planning
6 min read
Lesson objectives
- Create an auditable asset register and exception list from conflicting exports
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A fleet decision begins by defining the unit of analysis: one physical vehicle with a stable identifier, not one spreadsheet row or a plate number that may change. When merging dispatch and workshop exports, use a documented vehicle identification number or asset ID as the primary key, while retaining the plate and operating number as updateable fields. Two rows do not mean two vehicles if they share that key. Conversely, similar models or missing plates are not sufficient grounds to merge different vehicles. A usable register records vehicle class, capacity, odometer, availability status, observation date and source. These fields support a review of actual use and suitability: the job can be compared with the vehicle's size, distance and fuel use. Before calculating a fleet measure, count unique vehicles, distinguish active from out of service, and attach a date to each value. An uncertain value remains an exception with an owner and due date; it must not silently become zero or an estimate in a report.
Reconcile in four passes. First, normalize fields without overwriting originals: trim identifiers, put dates into one format, and retain raw values for audit. Second, separate identity conflicts from status conflicts. One vehicle identification number across two sources becomes one asset record, but 'available' in one source and 'in workshop' in another require comparison of update times and evidence of return to service. Third, test odometer plausibility. Do not automatically choose the largest reading: the latest entry may be a typing error, while a lower reading might follow a documented meter replacement. Request evidence such as a dated work order or meter image when the sequence reverses without explanation. Fourth, classify every exception and state its operational consequence. An unresolved identity conflict prevents a reliable count; missing capacity blocks a payload assignment; absent repair closure prevents release of a held vehicle. This turns the register into an auditable decision aid rather than a cosmetically clean list.
Solution: V100 appears twice, so the three dispatch rows represent only two physical vehicles, V100 and V200. Preserve both V100 readings of 48,200 and 48,250 km with their source dates, but do not infer a 50 km trip from their difference: both rows have the same date and no time. The workshop's 13 October open brake defect is newer than dispatch's 12 October 'available' label and concerns a safety-critical system. Hold V100 from assignment and request documented repair and closure inspection before changing its status. For V200, the documented 31,600 km reading and closed work order support return to service, but neither proves payload capacity. The asset register therefore contains two vehicles, one held and one preliminary candidate. Do not approve the requested assignment until V200's required capacity is verified against an approved specification and the pre-trip check is complete. Record two exceptions: missing capacity for the asset-data owner and V100 repair evidence for the workshop owner. If later evidence shows V200's capacity is below the job's payload, the feasible shortlist is empty; escalate for a different vehicle or schedule rather than waiving the constraint.
After building the register, test it with two different questions. Does the team know which physical assets exist? And does it know which asset can be assigned to this particular job now? The first answer may confidently be 'two vehicles' from the two IDs, while the second may be 'none confirmed' because a capacity card is missing or a defect is open. Do not replace that distinction with a single yes/no readiness field; show asset status, its date and the job constraint. Apply freshness appropriate to today's decision. A month-old odometer may suffice for an inventory view but not for scheduling service near a mileage threshold, so request a new reading before scheduling. Test key completeness too: if a third row lacks a vehicle ID, do not assume it is another V100 because its plate looks similar. Put it in identity verification until an asset document arrives. Each exception states its decision effect and deadline so dispatch knows what may proceed and what must wait.
Lesson summary
Create an auditable asset register and exception list from conflicting exports