Sort driver messages: failed deliveries, delays, breakdowns

Fields

• Load or stop status from the TMS
• Driver's message

Questions

1. What is the driver reporting in this message? Choice

   Read the message with the load status. When the message reports more than one event, pick the first that applies in this order: accident or incident, breakdown, load problem, delivery or collection failed, hours running out, waiting at a site, running late, paperwork problem, on schedule, not about the load.

   • On schedule A routine update: arrived, loaded, delivered or on the way, with nothing wrong.
   • Running late Will be late for or miss an appointment or delivery slot, from traffic, weather, a closure or an earlier delay.
   • Waiting at a site At a shipper's or receiver's site, waiting to load or unload.
   • Delivery or collection failed Could not complete a delivery or collection at a stop, including a refusal by the receiver.
   • Breakdown A fault with the truck, van or trailer, including tyres.
   • Accident or incident A collision, an injury, a theft, a threat, or damage to property.
   • Load problem Goods short, damaged, wrong, shifted, or with a seal problem, found at loading or on the road.
   • Paperwork problem Documents missing or wrong, or a POD the receiver will not sign.
   • Hours running out The driver says their legal driving time is close to running out.
   • Not about the load Pay, time off or another matter that is not about a load or delivery.

2. Why does the driver say the delivery or collection could not be completed? Choice

   Judge from what the driver says happened, not from any code in the load status. When more than one reason is given, pick the one that stopped the delivery first.

   • No failed delivery The message reports no failed delivery or collection.
   • Nobody to receive it Nobody answered or was there to receive, and there was no safe place.
   • Business closed The premises were shut.
   • Access problem A locked gate, a missing entry code, a closed road or nowhere to stop or unload.
   • Address problem The address was wrong, incomplete or could not be found.
   • Refused The receiver refused all or part of the delivery.
   • Unsafe to deliver A dog, a threat, the weather or the site made it unsafe.
   • Out of time The driver ran out of time or capacity on the run.
   • Goods too damaged The goods were too damaged to hand over.

3. Does the driver's message suggest a load or delivery will arrive later than planned? Yes / No

   Count delays, waits, breakdowns, failed deliveries that need a new attempt, and knock-on delays to later stops. Yes: At least one load or delivery will be later than planned. No: Nothing in the message suggests a delay.

4. Does the driver's message mention an injury, a crash, an unsafe load, a spill, a fire or danger to the driver? Yes / No

   This sends the message to a person on the safety line at once. It never replaces a call to the emergency services. Yes: The message mentions any of these. No: The message mentions none of these.

5. Does the driver need something from dispatch to carry on or finish the job? Yes / No

   Count a request for instructions, a code, a contact, a new appointment, authorisation, recovery or a replacement vehicle. Yes: The driver asks for or clearly needs something from dispatch. No: The message is information only.

6. Should the shipper, receiver or recipient be told about what the driver reports? Yes / No

   Count anything that changes when or whether the goods arrive, or that needs the customer to do something. Yes: The customer should be told. No: Nothing in the message affects the customer.

7. Could the customer fix the problem the driver reports by giving information, such as an entry code, a corrected address or a safe place? Yes / No

   Yes: The problem would be solved by information or a choice the customer can give. No: The problem is not one the customer can fix with information, or the message reports no problem.

8. Does the driver mention arrival, appointment or waiting times at a site? Yes / No

   Count clock times, appointment times and how long the driver has waited at a site. Code reads the times from the TMS; this only flags the message for billing. Read the driver's message only; the load status times come from the TMS. A delay on the road, or a slot at a later stop, is not a time at a site. Yes: The message mentions at least one of these times at a site. No: The message mentions no such time.

9. Which extra charge to the customer does the driver's message support, if any? Choice

   Judge from what happened, not from whether the customer will be billed; billing decides that with the TMS times.

   • None The message supports no extra charge.
   • Waiting time Waiting at a site to load or unload beyond the appointment.
   • Layover An overnight wait before loading or unloading.
   • Unloading help The driver had to pay for unloading help.
   • Truck ordered, not used The load was cancelled or not ready when the truck arrived.
   • Extra stop An unplanned stop was added to the run.
   • Redelivery A failed delivery needs a second attempt.

10. Is the driver's message clear enough to tell what happened? Yes / No

    Shorthand, abbreviations and poor spelling are normal and still readable. Yes: The message can be read and says what happened. No: The message is garbled, cut off, or too short to tell what happened, such as "ok" or "call me".

Lens columns

event, event_probability, failed_delivery_reason, failed_delivery_reason_probability, eta_affected, eta_affected_probability, safety_concern, safety_concern_probability, needs_action, needs_action_probability, tell_customer, tell_customer_probability, customer_can_fix, customer_can_fix_probability, time_at_facility_mentioned, time_at_facility_mentioned_probability, accessorial, accessorial_probability, text_judgeable, text_judgeable_probability