Add a new ETA to the next stop by adding a load update: open the load, select Load Update, and fill in Next stop ETA (local to stop). The update saves to the load and syncs back to your TMS.
Do this in TrackFlo, not in your TMS
An update entered here goes both ways: it syncs to your TMS and it counts toward your shift scorecard and team metrics. The same update typed directly into your TMS does neither of those for you — TrackFlo can only measure work that happened in TrackFlo, so it never sees it.
This is the habit that decides whether a rollout works. When a team's numbers look low in the first few weeks, it's usually because part of the team is still updating in the TMS out of habit and getting no credit for it.
Before you start
You need a Tracker, Internal User, or Admin role to open a load page.
The update types you can pick from are set by your company, so the list on your screen may differ from the examples here.
Add the ETA
Open the load from the tracking board.
Select Load Update. The Add Load Update panel opens. If your team uses Turvo, this button is labeled Turvo Status Update and the steps are the same.
In Type of load update, choose the type that fits. For a carrier-confirmed ETA, choose ETA Confirmation if your list includes it.
If you know where the information came from, pick it in Where did you get the information? (for example, Phone Call with Driver). This field is optional.
To record the truck's current location, type the first 3 letters of the city in Current load location city, state and choose from the options. This field is optional.
In Next stop ETA (local to stop), enter the new ETA, or use a quick-fill button: Now (local to stop), In 1 Hour, or In 6 Hours.
In Latest information on the load, add a short comment, such as what the driver said. This field is required and limited to 600 characters.
Select Add Load Update at the bottom of the panel.
Wait for the status line to show Load Update: Completed. The panel closes when the update is submitted, and the update appears in the load's All Updates tab once your TMS confirms it.
TrackFlo applies the ETA to the next stop on the load that has no arrival time yet. You don't pick the stop yourself, so there is no stop selector in the form.
On a multi-stop load, that means the ETA lands on the next unarrived stop rather than the final delivery. If you meant the ETA for a later stop, record the stop you mean in the comment.
Write the comment for whoever reads it next
Two audiences see this field. The next tracker picking up the load reads it to know what's already been chased, and — depending on your company's portal settings — your customer may see it too.
What makes a comment useful is specificity about time and source: "driver says loading now, expects to roll by 3pm CT" beats "on time." The next person shouldn't have to make the same call you just made to find out what you learned.
The Where did you get the information? field is optional and worth filling in anyway. When a customer asks two weeks later why nobody caught a delay, "Phone Call with Driver" is the difference between a defensible record and a guess.
What good looks like
The status line shows Load Update: Completed, and the update appears in the load's All Updates tab with the ETA in the ETA Local column.
Watch the status line before you move on. TrackFlo saves the update only after your TMS confirms it, so navigating away from a failed update means the information you just gathered is recorded nowhere — not in TrackFlo, not in your TMS.
When it doesn't work
The status shows "Load Update: Failed"
Your TMS rejected the update, so TrackFlo did not save it. TrackFlo records an update only after your TMS confirms it, and a failed update retries a few times before it stays failed. Open Two Way Integration Status, check the Failed TMS Updates tab for the TMS response message, and retry from there. See Troubleshoot TMS sync issues.
If several updates fail at once, it's usually the integration rather than anything about the loads. Check Two Way Integration Status before retrying each one individually.
The ETA shows a different time than you entered
The ETA field is local to the stop, not local to you. A load crossing time zones shows the ETA in the destination stop's time, while other timestamps on the page use your own time zone.
This catches people out on long hauls. An ETA that looks three hours off is usually correct — it's just being shown in the receiver's clock, which is the one the receiver cares about.
The update isn't on the load yet
Updates are sent to your TMS as background tasks, so they take up to a minute to appear. If the status line still shows Load Update: Processing..., wait for it to change to Load Update: Completed before adding the update again.
Resubmitting during that minute is the usual cause of duplicate updates on a load.
