Repeat deliveries and waiting vehicles consume capacity before they appear as a clear line item.
THE FIRE
A missed handover, unclear layout or unavailable receiving point can send a vehicle back to the same route while crews and equipment wait.
THE BLUEPRINT
1. Record the reason for the repeat movement or waiting period.
2. Link it to the affected workfront, route and responsible decision.
3. Fix the upstream condition and check whether the repeat event disappears.
THE METRIC
Measure repeat trips, waiting hours, kilometres, additional fuel and verified causes. Avoid double-counting costs that are already included elsewhere.
Download the OperatorOS Field Execution Pack: https://operatorosglobal.odoo.com/web/content/694?download=true
Put this into practice
Use the delivery coordinator to connect every repeat attempt to its original delivery and verified reason.
Do not count the original journey as additional distance when calculating the effect of a repeat attempt.
Begin with one example using Delivery ID, Attempt number, Reason, Additional distance km, Additional hours. Give the record a stable identifier and connect any unresolved issue to an owner and next action. Ask the receiving reviewer to explain the decision the record supports before expanding the process.
For a step-by-step routine, use the Track delivery failures guide alongside the Repeat delivery causes template.