Fleet records and operating demand · Lesson 4

Data ownership and the exception register

6 min read

Lesson objectives

  • Resolve an operational conflict without erasing the original value or bypassing the decision owner
Reading tools

Fleet data do not improve merely by assigning someone to 'clean the spreadsheet'. Give each critical field a source of record, owner, update cadence and validation rule. Vehicle ID comes from the documented asset register, open defects from the workshop log, and actual trip time from operating evidence; none of these sources is infallible. When two records conflict, retain both values with source and observation time, display any provisional operating value with confidence and reason, and refer the disagreement to the field owner. An analyst must not overwrite a workshop defect because the dispatch export was downloaded later; the relevant facts are event time and evidence of defect closure. Distinguish event time from entry time. A repair from yesterday may be entered today yet still precede a defect that occurred this morning.

A data exception is a work record, not an anonymous error bin. It needs a unique number, affected vehicle or duty, conflict type, effect on a specific decision, priority, investigation owner, due time and reviewable closure evidence. Classify impact before priority: a missing vehicle ID blocks asset reconciliation; missing payload rating blocks a load assignment; inconsistent fuel quantity may block a reliable cost report without necessarily grounding an otherwise safe vehicle. An open safety defect requires a separate operational decision from data correction: keep the vehicle out of dispatch until the authorized owner reviews repair evidence. 'Close the ticket' must not mean deleting the old row. Link closure to the corrected value, its source and approver, while preserving the prior value in the audit trail. If proof cannot be obtained before departure, escalate the job or use another vehicle instead of labelling an estimate as confirmed.

Solution: the download time of the dispatch export does not prove its 'ready' label reflects the later event. The tyre defect occurred at 13:30 and remains open in the workshop log; an unsupported email establishes neither repair nor closure inspection. Open safety exception S1 with T8, defect, event time, both sources, workshop owner, a deadline before release, and the operational effect 'do not assign'. Request the repair order and return-to-service check. If unavailable by departure, revise the job or find another suitable vehicle; the smaller alternative cannot carry a load above its rating. Preserve the old 'ready' value as an outdated indicator instead of deleting it. Open separate measurement exception F1 for the nine-litre difference between 65 and 56, attaching the receipt, odometer and fueling time. Hold that transaction out of a settled fuel-cost figure until reconciled; the difference alone is not a mechanical grounding reason for T8. If an original receipt proves 65 litres and 56 was a transcription error, set the operating value to 65 while retaining 56 and the correction trail. If proof remains absent, show the difference as unresolved in the report. Both exceptions need owners and closure, but their immediate operational decisions differ because the evidence affects safety differently.

Prevent recurrence with a narrow update rule: a new open-defect message from the workshop reaches the assignment screen before dispatch authorization, and lifting the hold requires repair-order ID, closure check and the name of the release approver. Test two cases: a new defect after dispatch's last refresh, and a properly verified closure after a defect. The first should block release; the second should allow reassessment. Do not route every alert to one generic decision. A disputed fuel quantity goes to the analysis owner; the defect decision belongs to maintenance and safety. In a weekly review, show open exceptions by decision impact, their age, and closures lacking a document. A closure without evidence is a control failure, not a success. Retain the reason for each exception even after correcting its number, because a recurring input error may need a process repair.

Lesson summary

Resolve an operational conflict without erasing the original value or bypassing the decision owner