Turvo offers tags and notifications to help alert you when shipments need attention. Utilizing the #RunningLate and #ApproachingLate automatic tagging feature will help you keep on top of shipments that may be experiencing issues and understand how you or your customers may be impacted in real-time.
This article describes:
- ETAs and Pickup/Delivery scheduling times
- How Approaching late and Running late are calculated
- How Approaching late and Running late values are displayed
For information on configuring and managing rules for when these tags are applied to your shipments, see our Manage and configure #ApproachingLate and #RunningLate threshold rules article.
ETAs and Pickup/Delivery scheduling times
Within a shipment, you can schedule pickup and delivery appointment times by expanding the Route segment under the Shipment block. These scheduled times can be set as first come first served (FCFS), or by appointment (Appt).
Note: Users with Turvo Appointment Scheduling enabled for their tenant will also see the Turvo Appointment Scheduling option. See our Appointment scheduling settings in the Admin console article to learn more about enabling and utilizing Turvo Appointment Scheduling.
The type of scheduling you select coupled with the start and end times will determine when a #ApproachingLate or #RunningLate tag will be applied. If you have thresholds set, these will also affect when the tags apply.Thresholds can be set up at the tenant-level, where they will apply to all customers, or at the customer account-level, where they will be specific to that customer. You can use the two threshold levels in combination, where the tenant-level thresholds serve as your default for all customers, and account-level thresholds will apply to that specific customer only.
Important note: A customer account-level threshold will always take precedence over the tenant-level threshold if both thresholds apply to the shipment.
Note: Your tenant-level thresholds can be updated at any time without affecting your customer account-level thresholds.
Scheduling type = FCFS
If an appointment window is set for FCFS, #RunningLate and #ApproachingLate will be calculated based on the end of the window. For instance, if the FCFS window is 12pm-3pm, the shipment will not be considered late until arrival time is estimated to be after 3pm (depending on the thresholds configured for the customer on the shipment).
If there is no end time set for the window, just a start time, #RunningLate and #ApproachingLate will be calculated based on the start time.
Scheduling type = Appt
If an appointment window is set for By appointment, #RunningLate and #ApproachingLate will be calculated based on the start of the window. For instance, if the Appt window is 12pm-3pm, the shipment will be considered late if arrival time is estimated to be after 12pm (depending on the thresholds configured for the customer on the shipment).
The Appt scheduling type logic in Turvo is less of an arrival window and more of a strict appointment, similar to a doctor appointment. For instance, if you have a doctor appointment scheduled at 12pm, if you arrive at 12:15, you're considered late and may be required to reschedule.
Scheduling type = Turvo Appointment Scheduling
If an appointment window is set for Turvo Appointment Scheduling, #RunningLate and #ApproachingLate are calculated based on the start of the window.
Multiple customers on a stop
If there are multiple customers associated with a specific stop, the shipment will be marked as #ApproachingLate or #RunningLate based on the customer with the lower threshold.
For example, Customer A and Customer B are both associated with a stop. Customer A has a Running late threshold of 30 minutes, while Customer B has a Running late threshold of 60 minutes. The #RunningLate tag will be applied as soon as the shipment is at least 30 minutes delayed to the stop. This is based on Customer A's lower Running late threshold of 30 minutes.
How Approaching late and Running late are calculated
Whether or not a shipment is late is calculated by comparing the ETA to the next open stop with the appointment time on that stop.* The customer account settings for Approaching late and Running late are also taken into consideration as described above. Lastly, the two types of scheduling are also considered: By appointment and FCFS (first come, first served). Learn about how ETA is calculated.
*Note: Carriers performing shipments with LTL, Parcel, Drayage, Air, Rail, or Ocean as the mode may not be able to provide or calculate ETAs for the stops. If an ETA is not provided by the carrier or Turvo cannot calculate an ETA for the next stop, ETA to delivery will remain blank.
For example: Customer A has a Running late threshold of 30 minutes. The next open stop on the route has an appointment time of 9:00 AM - 10:00 AM with the scheduling type By appointment. Once the shipment status is En route, the ETA will be calculated. If the shipment is En route at 6:00 AM, with a drive time of 3 hours and 45 minutes to the next stop, then the ETA to that stop will be 9:45 AM.
To calculate whether or not the shipment is late, Turvo compares the ETA to the stop, 9:45 AM, with the appointment time on the stop, 9:00 AM. Since the scheduling type is By Appt, running late is based off of the appointment’s start time. The shipment is running 45 minutes late compared to the start time of the appointment, and 45 minutes is greater than Customer A's Running late threshold of 30 minutes. As a result, the shipment will be marked and tagged as #RunningLate with a late value of 45 minutes.
In this same scenario, if the scheduling type was FCFS, then Running late would be based off of the end of the appointment window, which is 10:00 AM. So, in this case, the shipment would not be marked as #RunningLate because the ETA is 9:45 AM, which is earlier than the end of the appointment window at 10:00 AM.
How Approaching late and Running late values are displayed
#ApproachingLate and #RunningLate are represented visually throughout Turvo so that you can see at a glance if a shipment is late and by how much.
When viewing a shipment, the shipment status bar shows the current status of the shipment and how late it is to the next open stop on the route. Reference the En route status highlighted in red in the screenshot below. This same value is also displayed on the shipment Route timeline based on the last location update that was received. This is visible when the Summary tab is selected on a shipment.
When viewing shipments in list view, the same value that is shown on the status bar is also displayed in the status column for that shipment. In all of these views, the shipment is running 1 day and 5 hours late.
Note: When a shipment status is At pickup or At delivery, the #ApproachingLate or #RunningLate value will show how late the shipment was when it arrived at that location. Once a stop is completed, the #ApproachingLate or #RunningLate value will then update to reflect if the shipment is late to the next stop. See the examples below to understand how information is displayed while a shipment is still in the At pickup or At delivery status.
The shipment status bar and list view Running late and Approaching late value takes into consideration the customer account threshold and will only be displayed if the shipment arrived at the stop past the acceptable late threshold.
The value shown in the Route card in the right pane uses a threshold that can be configured at an organization level. Please contact your Turvo representative to change this threshold. This value does not control #RunningLate and #ApproachingLate notifications or other workflows.
It is possible for the route card in the right pane to show the shipment is late, when the status column and status bar do not. This occurs when the customer’s account thresholds are set for a longer threshold than the route card threshold.
For example: The below shipment checked in to the pickup location before the account thresholds for #ApproachingLate and #RunningLate, but not before the card threshold. Because of this, the route card shows the shipment as 8 minutes late, while the status column and status bar do not.
Note: Even if Turvo receives additional location pings at the stop, the shipment status will not show as #ApproachingLate or #RunningLate, because it was not late when it first arrived at the location.
In the last example below, the shipment was 16 hours and 38 minutes late when it arrived at the first pickup. The ETA to the next stop is displayed in red text because it is also expected to be late, but the running late value will not be displayed for the second stop until the first stop has been completed.