Who follows up on late loads overnight and on weekends?

Key Takeaways

Most freight teams have no one assigned to late loads after hours. The work waits until the next shift, and the delay grows while nobody asks the carrier.
Three things must keep happening outside business hours: carrier follow-up, a new ETA with a reason, and notifications to the people who depend on the load.
Night and weekend escalation rules should be narrow. Wake a person only for decisions that can't wait, such as rebooking above a cost limit or a load that misses a receiving window.
Wilson, by Cartage, is an AI logistics agent that follows up with carriers, gets the new ETA and reason, notifies the right people and escalates under the company's rules, including overnight and on weekends.

Who should own a late load at 2 a.m. on a Saturday?

Someone, or something, has to own the carrier follow-up on a late load outside business hours, because the carrier's day doesn't stop when the office closes. In most manufacturing and distribution teams, that owner is undefined: the coordinator who booked the load has gone home, the on-call phone is for emergencies, and the late load sits until Monday morning.

A truck that slipped Friday night shows up Monday as a missed delivery appointment or a customer asking why nobody called. The problem wasn't the delay. It was the hours in which nobody asked the carrier what happened.

For food and beverage shippers the gap is wider. Plants and distribution centers often run more than one shift, retail receiving windows are tight, and temperature-controlled loads can't sit at a dock while someone waits for the office to open.

What has to keep happening when the office is closed?

Three tasks can't pause after hours: carrier follow-up, a new ETA with a reason, and notifications. Everything else can usually wait for the next business day.

Carrier follow-up. When a load misses a check-in, a tracking update or an appointment, someone has to contact the carrier's dispatcher or driver. A check call (a status call to the carrier or driver) at 11 p.m. often finds a truck that is two hours late, not lost.
A new ETA (estimated time of arrival) and the reason. "Running late" isn't enough. The receiving team needs a time, and the logistics team needs a reason: driver hours, a breakdown, weather, a late departure from the previous stop. The reason decides whether this is a one-off or a pattern.
Notifications. The receiving dock, the customer service lead and, where configured, the consignee (the party receiving the load) need the new ETA before they find out from an empty dock.

Which escalation rules should you set for nights and weekends?

Set rules that separate what can be handled and logged from what needs a person now. Most after-hours exceptions only need follow-up and an update. A few need a decision, and those are the only ones that should page someone.

Situation after hours	Default handling	Escalate to on-call person when
Load running late, new ETA still inside the delivery window	Follow up, record ETA and reason, notify per rules	Not needed
New ETA misses the delivery appointment	Notify receiving and customer service	The customer or plant has to decide whether to accept a later slot
Carrier doesn’t respond to follow-up	Retry on the next channel at the set frequency	No reply after the number of attempts your SOP allows
Carrier says the truck won’t make it	Initiate rebooking from approved carriers	Rebooking exceeds the cost threshold or needs approval
No approved carrier accepts	Stop and record every attempt	Always

A few practical rules make this table work:

Write down the follow-up frequency. For example, a carrier that misses a tracking update gets a call at the next check interval, and again after that until it answers. The SOP (standard operating procedure) should say how many attempts come before a person is involved.
Name the on-call person and the channel. A Slack or Microsoft Teams alert to a channel nobody watches on Sunday isn’t an escalation.
Set the cost threshold before the weekend, not during it. A rebooking decision at 3 a.m. goes better when the limit is already approved.

For a wider view of who owns which exception, see the freight exception responsibility matrix.

What does after-hours coverage look like at a food and beverage shipper?

One food and beverage company uses Wilson to cover the dispatch follow-up its team can't staff at night and on weekends. Wilson sent 7,000+ emails and touched 1,600+ unique trips for this company. That works out to 8–10 hours of dispatch labor covered every day, including overnight and weekend hours that are the hardest to staff.

The work Wilson took off the team's plate is the same work described above: chasing carriers for late reasons, collecting PODs (proof of delivery, the signed record that a load arrived) and running detention checks.

The point isn't the email count on its own. It's where the hours fall. Overnight and weekend dispatch is the follow-up that usually waits for morning, and it's the part of the day this company found hardest to staff. Covering it means the work above keeps moving between shifts instead of piling up for the next one.

How does Wilson handle a late load after hours?

Wilson, by Cartage, follows the same steps at night that it follows during the day: it checks the load, contacts the carrier, gets the new ETA and reason, notifies the people set to be notified, and escalates when the rules require a person. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Tracking. Wilson uses the best source available for each load: the carrier’s API, GPS or ELD (electronic logging device) data from the truck, or the carrier’s website by PRO number. When none of those exist, Wilson emails or calls the carrier.
Follow-up. Wilson calls carriers and drivers for check calls and ETA follow-ups, and follows up by email and text. If a carrier doesn’t respond, Wilson calls. The frequency is set in the company’s SOP, and call transcripts are saved on the order.
Notifications. The team hears about late loads in Slack or Microsoft Teams. The shipper and the consignee can get updates by email, or SMS for the consignee. Each company chooses who’s notified and how.
Rebooking. If a carrier can’t make it, Wilson initiates rebooking from the approved carrier list. That rebooking runs automatically or waits for approval, depending on the company’s rules.
Escalation. Wilson escalates to the team when a carrier can’t confirm, no approved carrier accepts or a decision exceeds the approval rules.

Every message, confirmation and change is recorded in the shipment’s change history. Wilson starts with assisted execution, and the company decides which actions need approval, so night and weekend handling can begin conservative and expand as the team trusts it. For more on routing unanswered messages, see who escalates unanswered carrier messages.

How do you know after-hours coverage is working?

Measure the time from the exception to the notification on loads that slip outside business hours, and compare it with how those loads ran before. If Monday still starts with a pile of unexplained delays, the coverage isn't working. If it starts with a list of late loads that already have a new ETA, a reason and a record of who was told, it is.

Pick one lane that often runs overnight, write the escalation rules for it, and see how Wilson would cover that lane's weekend exceptions with our team.

Sources