Hi @tanyamain , thanks for confirming the details.
The odometer entered during a pre-start inspection is saved with that inspection record, which is why it appears on the Inspection Report. It does not automatically update the asset's underlying odometer or the Current Odometer value used by Work Order Management.
For untracked assets, you can manually update the odometer from the asset record:
Assets > select the asset > Usage > Odometer
This should be maintained manually at a cadence that works for your operation. For example, you could update it whenever a pre-start inspection is completed or whenever the operator provides a new verified reading. Keeping this value current is important because distance-based maintenance schedules rely on the asset-level odometer, not the odometer stored on an inspection.
You can also manually enter or update the odometer reading on a work order when recording maintenance activity. That reading is part of the work-order history and should reflect the odometer at the time the work was performed.
If the Current Odometer field remains blank after updating the asset record, that would need to be investigated separately as a Work Order Management synchronization or maintenance-calculation issue.
The inspection odometer remains available on the inspection record and report:
https://support.geotab.com/help/mygeotab/maintenance-and-diagnostics/work-order-management/asset-inspections
Work orders can be edited here:
https://support.geotab.com/help/mygeotab/maintenance-and-diagnostics/work-order-management/work-orders
Hope that helps!
Eishi FUN