What if my ETA changes?

The percentage you see next to "On schedule" in your tracking module is our calculated probability that the vehicle arrives within four hours of the stated time. 85% confidence means: of 100 similar shipments at this point in transit, about 85 arrived within the 4-hour delivery window. Confidence isn't a guarantee — it's our honest read of the variables we can see (driver pace, remaining miles, weather forecasts, traffic patterns, hours-of-service status). It updates every 30 minutes.

Five biggest causes, roughly: weather (~40% of all ETA changes — storms slow everyone down), traffic and construction (~25% — especially urban approach segments near pickup or delivery), mechanical (~15% — the truck or trailer needing service), driver hours-of-service limits (~10% — federal regs cap drivers at 11 driving hours per 14-hour day, so when a driver "runs out of hours" they have to stop), and other (~10% — state inspections, fuel stops, customer rescheduling). Of these, only mechanical issues let us route around the problem by reassigning the load.

For shifts under two hours, we update your portal in real-time without notifying you — these are within the original confidence window, so they're not surprises. For shifts over two hours, you get an SMS the moment we know. For shifts over six hours, we call you personally before sending the SMS, because that's the level of change that affects your day. Email goes out for every change, regardless of size.

You can adjust your delivery window (a wider window often improves the next ETA), swap your delivery contact (if you can't be there, who can?), or reschedule entirely. Rescheduling is free within 24 hours of pickup if conditions warrant. We do not penalize you for being flexible — flexibility usually helps the whole trip stay on track.

Any time the change feels off, even if our notification says it's within tolerance. Your gut about your own schedule is often better than our model. We never mind the call — and a five-minute conversation often catches an issue our automated system would have flagged six hours later.