Fixing a Mistaken Collection Using Multi-Leg
If a driver accidentally marks a vehicle as collected - even if they didn’t physically load it - Blink treats that event as final. This is because our platform is designed to treat the driver’s actions as the source of truth. We do not erase or overwrite these events.
🚨 Why Doesn’t Blink Allow Overwrites?
-
Driver authority is critical: Our system is built with chain-of-responsibility in mind. If a driver says they’ve collected something, the platform records that as fact.
-
Data integrity: Once scanned, photos, timestamps, and GPS events are logged. Editing or removing these would compromise trust and traceability.
-
Training issue: Drivers must only collect vehicles they are truly taking.
✅ Best Practice: Multi-Leg the Item Back to Its Original Location
The cleanest and most accountable fix is to use the multi-leg tool to send the vehicle back to where it was mistakenly collected from. Here's how to do it:
🔁 Multi-Legging the Booking
-
Locate the run where the mistaken collection was recorded.
-
Select the three vertical dots and multi-leg option on that leg of the run.
-
Enter the original location (where the vehicle was incorrectly collected from).
-
This will:
-
Replace the current delivery address with the original location (as if "returning" the vehicle).
-
Add a new leg automatically from the incorrect collect address to the intended delivery address to be allocated.
-
This keeps your audit trail intact, shows the full journey of the vehicle, and avoids any confusion for downstream processes like billing, proof of delivery, or reporting.
