Turvo status updates
Updated today
If your team uses Turvo, the load page shows a Turvo Status Update button in place of the standard Load Update button. It sends one combined status update to Turvo: the load status, the stop event, the time, the current location, and a comment in a single submission.
This is the whole tracking update in one form. On other TMS setups the status change and the load update are separate actions; here they're the same submission, so the status you choose and the comment you write go out together.
Fields on the form
Field | What you enter |
|---|---|
Load Status | Choose one: Covered, Dispatched, At pickup, Picked up, En route, At delivery, Delivered, Route complete. |
Stop | Shown and required only for the statuses At pickup, Picked up, At delivery, and Delivered. The list starts with -- Select a stop --. |
Update Time (local to the update location) | The time as it appears at the update location, not your own time zone. TrackFlo converts it to UTC. A time more than five minutes in the future is rejected. |
Comment (optional) | Maximum 600 characters. |
Current Location (city, state) | Defaults from the selected stop when available, and can be overridden. |
Update Time is local to where the update happened, not to you. A driver arriving at 2pm at a facility two time zones away is 2pm in this field. Entering your own clock time puts the event hours from where it belongs, and those times are what dwell and on-time performance are measured from.
Override Current Location when the truck isn't where the stop is. En route updates are the common case — the default comes from the selected stop, which isn't where the driver actually is.
Email section
The email section is shown unless your team's load update style is Without Email. It contains Send email update?, Add myself as CC, Add Emails, Add Carrier Account Manager, Add Customer Account Manager, and Email addresses (separate with comma).
Those account manager shortcuts are the reason to use this section rather than typing addresses. When a status change is something the account owner would want to hear about directly — a load going late, a problem at a facility — one checkbox beats remembering who covers the account.
Manage Issue section
The section contains Manage Issue?, Manage Issue Type, Follow Up Time, Follow Up Date & Time (which will overwrite Follow Up Time), Set to Now (my timezone), and Set to Tomorrow at 7am.
This is how you clear a load from your active work without pretending it's finished — you've dealt with it for now, and it comes back at the follow-up time. Set that time for when you'd actually want to know, not for the end of your shift, or you're handing the load to the next person with no warning.
Set to Tomorrow at 7am is the right button for anything that can't progress overnight.
Select Send Turvo Status Update to submit the form.
What is sent to Turvo
The update to Turvo carries five things:
The load status.
The selected stop, only for the statuses At pickup, Picked up, At delivery, and Delivered.
The update time, converted to UTC.
The current location.
The comment.
Every update is marked with TrackFlo as the tracking source. The email fields are not sent to Turvo; they control who in your team gets the email update.
The Manage Issue settings stay in TrackFlo too — a follow-up time is a note to your own team about when to look again, and Turvo never sees it.
Status and stop rules
A delivery status is blocked on a pickup stop, and a pickup status is blocked on a delivery stop. For At pickup, Picked up, At delivery, or Delivered, choose a stop of the matching type before you submit.
On a multi-stop load this is worth reading twice. The stop picker is how Turvo knows which leg the event belongs to, and the wrong stop puts an arrival on the wrong facility.
When an update fails
A failed update is one your TMS (transportation management system) rejected or that never reached it.
Open Two Way Integration Status and check the Failed TMS Updates tab. Each failed row shows its Status, TMS Response Code, and TMS Response Message, and has a Retry Update action. See Troubleshoot TMS sync issues for the full failure modes.
Because status and comment go out together here, a rejected update means neither was recorded. Retry rather than assuming the comment landed.