How do you hand off a delayed shipment between shifts without losing the next action?
Key Takeaways
You hand off a delayed shipment between shifts without losing the next action by keeping everything the next person needs on the load record itself: what happened, what is confirmed, what has been tried, what the next action is, who owns it and by when. A handoff that lives in someone's head, a personal inbox or a sticky note fails as soon as that person goes home. An AI logistics agent such as Wilson, by Cartage, owns the next action on every delayed load across shifts: it keeps asking the carrier, updating the receiver and escalating within the rules, so the night shift or the next morning starts from a clear status.
- A delay is not handed off well until the next action, owner and deadline are written down.
- Confirmed facts and open questions must be kept apart.
- Every message to and from the carrier should be on the load, not in a personal mailbox.
- An agent that owns the follow-up does not go off shift.
- The handoff list should show only the loads that need a person, with the reason.
- After-hours decisions need a named approver and a rule for when to wake someone.
What does a good handoff contain?
A good handoff contains the facts, the history, the next action and the owner, for every delayed load. An AI logistics agent keeps all of this on the load record, so the handoff is the record. The table lists what the next shift needs.
| Item | Example | Why it matters |
|---|---|---|
| Load and order | PO 2291, load 21734, carrier PRO 4471-2290 | So the next person finds it at once |
| What happened | Driver out of hours at 4 p.m.; truck parked in Knoxville | The cause decides the response |
| What is confirmed | New ETA 9 a.m. tomorrow, confirmed by dispatch at 5:10 p.m. | Separates facts from guesses |
| What is open | Receiver has not confirmed a 9 a.m. slot | Shows what still needs an answer |
| What was tried | Two emails to receiver; one call, voicemail | Prevents repeating the same steps |
| Next action | Confirm receiver slot by 7 a.m. | Clear task |
| Owner | Wilson until 7 a.m.; then morning coordinator if unconfirmed | No gaps |
| Deadline | 7 a.m. | When it becomes urgent |
| Customer status | Customer told delivery moves to tomorrow morning | Avoids double or missing messages |
| Decisions pending | Approve redelivery fee if the slot moves | Shows what needs a person |
Where should the handoff live?
The handoff should live on the load record, not in a separate document. Shift notes in a spreadsheet, a chat thread or an email to the next shift are better than nothing, but they drift from the truth as soon as a carrier replies. When the record is updated by every message and action, it is always current. The next shift reads the record, not a summary written hours earlier.
Why are facts and open questions kept apart?
Facts and open questions are kept apart because the next shift acts differently on each. "ETA 9 a.m., confirmed by dispatch" can be passed to the customer. "Receiver slot not confirmed" cannot. When they are mixed, the next person may promise something that was only a guess. Wilson records each status with its source and the time it was confirmed.
How detailed should the history be?
The history should be detailed enough that someone who has never seen the load can understand it in a minute. Every message, call and status change with its time is the base. On top of that, a short current summary at the top of the record, updated by the agent, lets the next person read the situation without scrolling through every message. The detail is there when needed; the summary is what most people read.
Why does the cause of the delay matter?
The cause of the delay matters because it decides the right next action and who pays for any extra cost. A driver out of hours will move again after the rest period; the new ETA is fairly predictable. A breakdown may take an unknown time to fix and may need a new truck. A receiver that refused the load because the dock was full needs a new appointment, not a new carrier. Recording the cause also matters later, for the carrier's lane record and for checking any detention or redelivery charges on the invoice.
Why does "what was tried" matter?
"What was tried" matters because the next person will otherwise start again. They will email the same contact, call the same number and wait the same time. Seeing that two emails and a call already went to the receiver tells them to try a different contact, or to escalate. It also shows the carrier and the receiver that the company is organized.
Why do delayed shipments get lost between shifts?
Delayed shipments get lost between shifts because the work is spread across people, inboxes and phone calls, and the handoff depends on memory. An AI logistics agent removes most of these failure points by keeping the work in one place and owning the follow-up itself.
| Failure | What happens | Fix |
|---|---|---|
| Personal inbox | Carrier's reply arrives after the coordinator leaves | Carrier email goes to the agent's address and the load record |
| Verbal handoff | "Keep an eye on 21734" is forgotten | Next action written on the load |
| No owner | Two people assume the other has it | One owner per action |
| No deadline | The next step waits until someone notices | Deadline on the action |
| Guess passed as fact | New ETA from memory sent to the customer | Source and time on every status |
| Phone call not recorded | The night shift calls the same dispatcher | Call summary on the load |
How much does a lost handoff cost?
A lost handoff can cost detention, a redelivery fee, an expedited rebooking, a customer penalty and a lot of staff time the next morning. Detention alone is common and expensive across the industry: the American Transportation Research Institute found detention at 39.3% of stops in its 2023 data, with $3.6 billion in direct costs. Not all of that comes from handoffs, but a missed appointment change is one of the ways a truck ends up waiting.
What happens in a typical lost handoff?
A hypothetical lost handoff: at 4:45 p.m., a coordinator learns a truck will miss a 6 a.m. delivery. She emails the receiver to move the appointment and tells a colleague on the way out. The receiver replies at 7 p.m. offering 11 a.m. The reply goes to her inbox. The night shift does not see it. The carrier, hearing nothing, plans for 6 a.m. and arrives to find no slot. The truck waits, detention starts and the customer calls at 8 a.m. Every piece of information existed. It just was not where the next person could see it.
Why do teams with several sites have more trouble?
Teams with several sites have more trouble because handoffs cross both shifts and locations. A delay on a load from one plant may be handled by a coordinator at another, and the receiving warehouse may be in a different time zone. Each extra person and time zone adds a chance for the next action to fall through. A single load record that everyone sees, with one owner for each action, matters even more in this setup.
Why do phone calls make it worse?
Phone calls make it worse because they leave no trace unless someone writes them down. A dispatcher's promise, a receiver's new slot or a driver's location may only exist in one person's memory. Wilson can call carriers where configured and records what was said, with the time and source, on the load. When a person makes the call, a short note on the load keeps it visible.
How should the next action be set and owned?
The next action should be specific, have one owner and a deadline, and be visible on the load. An AI logistics agent can own most next actions on delayed loads: asking the carrier, asking the receiver, updating the customer, checking the new ETA. People own the decisions.
Should every delayed load have a next action?
Every delayed load should have a next action until the delay is resolved: the load delivered, the new time confirmed with everyone, or the decision made. A delayed load with no next action is a load nobody is watching. The agent should never leave a delay without one. If the next action is "wait for the truck to arrive at 10 a.m.", that is still an action, with a time to check.
What makes a next action clear?
A clear next action says what to do, with whom, by when and what result closes it. "Follow up on 21734" is not clear. "Get the receiver to confirm a slot between 9 and 11 a.m. tomorrow by 7 a.m.; if no answer, call the receiving manager" is clear. The agent can carry out clear actions without guessing.
How should deadlines be set?
Deadlines should be set from the commitment the action protects. If the receiver needs four hours' notice to move a 6 a.m. appointment, the deadline for getting a new slot is 2 a.m. at the latest, and better the evening before. If the customer must be told by the start of their business day, the deadline is that time. The agent can calculate these from the load's appointment and the receiver's rules, and escalate when a deadline is near.
Who should own the action overnight?
The agent should own routine actions overnight: following up with carriers and receivers, recording replies and updating statuses. A person should own decisions that cannot wait for morning, such as approving an expensive rebooking for a load due at 6 a.m. The rules should name that person and say what counts as urgent enough to contact them.
How should a decision handed to a person be framed?
A decision handed to a person should be framed as a choice with options and a deadline, not as a problem to research. "Carrier cancelled the 6 a.m. pickup. Backup A can pick up at 8 a.m. for $180 over limit; Backup B at noon within limit, but delivery slips a day. Customer appointment is Thursday 2 p.m. Decide by 7 a.m." The person can answer in one line.
How should ownership pass in the morning?
In the morning, the handoff list should show only the loads that need a person, with what happened overnight. A hypothetical morning list: "21734: receiver confirmed 10 a.m.; carrier confirmed; customer updated. No action needed." "21741: carrier cancelled at 1 a.m.; two backups quoted; best is $180 over limit; approval needed by 8 a.m." The morning coordinator starts with one decision instead of a pile of emails.
| Overnight event | What the agent did | Morning list shows |
|---|---|---|
| Receiver replied with a new slot | Confirmed with carrier; updated customer | Done, no action |
| Carrier sent new ETA | Recorded with source; checked appointment | Done, no action |
| Carrier cancelled | Requested quotes from approved backups | Approval needed |
| No reply from receiver | Followed up at set times | Call receiving manager at 7 a.m. |
How should a person take over from the agent?
A person takes over from the agent by opening the load, reading the history and taking the action, with the agent recording what they did. If the coordinator calls the receiver in the morning and gets a slot, a short note on the load lets the agent confirm with the carrier and update the customer. The handoff works in both directions: from person to agent at the end of the day, and from agent to person when a decision is needed.
What if the agent cannot reach anyone?
If the agent cannot reach the carrier or the receiver, it keeps trying on the schedule, records each attempt and escalates to the named person when the deadline nears. The morning list shows the attempts, so the coordinator knows to try a different contact or a different approach.
How should customers and receivers be kept informed across shifts?
Customers and receivers should be kept informed by one source, with one consistent message, regardless of who is on shift. An AI logistics agent sends updates from the facts on the load, so a customer does not get one story at 5 p.m. and another at 8 a.m.
Why does one source of updates matter?
One source of updates matters because customers lose trust when they hear different stories. If the night shift tells the receiver 10 a.m. and customer service tells the buyer "sometime tomorrow", the customer will call to sort it out. When every update comes from the same confirmed facts on the load, everyone says the same thing.
When should the customer hear about the delay?
The customer should hear when the new delivery time is confirmed, or with a short heads-up and a time for the next update if confirming will take longer. Telling a customer "it will be late" without a new time creates calls. Wilson can email or text the receiver when a load is running late, according to the company's settings.
What should the message to the customer say?
The message should say what changed, the new confirmed time or the time of the next update, and whether anything is needed from the customer. A hypothetical message: "Your order PO 2291 will arrive Thursday at 10 a.m. instead of 6 a.m. The truck was delayed by driver hours; the carrier and your receiving team have confirmed the new time." Short, factual and with one time.
What if the delay affects other loads?
Sometimes one delay affects others: a late inbound shipment holds up production, which holds up outbound orders, or a late truck on a multi-stop route makes every later stop late. The agent should flag related loads when it knows about them, such as other stops on the same truck or other orders on the same ERP order. The team decides how to handle the wider impact.
How should the receiver be handled?
The receiver should be contacted to move the appointment before the truck arrives late, not after. Many receivers need hours of notice to give a new slot. The agent should ask for a new slot as soon as the delay is confirmed and tell the carrier the answer. A missed appointment can lead to a refused delivery or detention, which is harder to fix than a moved appointment.
Should the carrier hear from one person too?
Yes. A carrier that gets questions from three people about the same load answers slowly and may give different answers to each. One owner, the agent, asking one clear question at a time gets better answers.
How should customer service be kept in the loop?
Customer service should see the same load record, so when a customer calls in the morning, the rep can give the current, confirmed status without asking logistics. This removes a common source of confusion: the night shift updated the receiver, but customer service still has yesterday's story.
How should the team review handoffs?
The team should review handoffs weekly at first: which delayed loads crossed a shift, whether any next action was missed and why. Most problems point to a rule gap, such as no after-hours approver for one region, or a receiver whose contact details are wrong. Fixing those removes repeat failures.
What about the sales team?
For key customers, the account manager may want to know about delays before the customer calls. The company can include the account manager in delay updates for certain customers. The agent sends the same facts to everyone, so the account manager and the customer hear the same thing.
How should after-hours decisions be handled?
After-hours decisions should follow written rules: what the agent can do alone, what needs a person, who that person is and how to reach them. An AI logistics agent prepares each decision so the person can make it quickly. A Cartage logistics expert is also available when a load needs extra help.
Is a Cartage expert available?
Yes. A Cartage logistics expert is one message away when a load needs judgment the team cannot give at that hour. Cartage experts monitor Wilson's actions and step in if something goes wrong. The team still owns its rules and its customer decisions; the expert helps keep the load moving until the team is back.
What can the agent do alone after hours?
The agent can do what the rules allow at any hour: follow up, record replies, update receivers and customers as configured, and rebook from approved backups within the rate limit when the rules allow automatic rebooking. It books only carriers the company allows.
What about weekends and holidays?
Weekends and holidays need the same rules, plus a calendar of which receivers and shipping sites are open. Many receivers are closed on weekends, so a Friday evening delay may push delivery to Monday, which changes the customer message and possibly the carrier's charges. The agent should know the receiving hours from the ship-to records and plan the next action accordingly.
What needs a person after hours?
A person is needed for decisions outside the rules: a rate above the limit, a carrier outside the approved list, a change that breaks a customer commitment, or a damage or safety issue. The rules should say which of these can wait until morning and which cannot.
| Decision | Can wait until morning? |
|---|---|
| Rate above limit for a load due at 6 a.m. | No |
| Rate above limit for a load due in three days | Yes |
| Customer commitment broken for a key account | Depends on the account rules |
| Carrier reports damage | Usually yes, unless safety is involved |
| No approved carrier for an early pickup | No |
How should after-hours rules be reviewed?
After-hours rules should be reviewed after the first few weeks and after any night that went badly. Look at which after-hours requests were truly urgent, which could have waited and whether any load was missed. Adjust the rules so the on-call person is contacted only when needed, and so the agent can handle more on its own within the limits.
How should the on-call person be contacted?
The on-call person should be contacted in the channel they actually check after hours, often a phone call or text, with a short summary and the decision needed. Wilson sends approval requests through the channel the company sets, with the comparison attached. The answer is recorded on the load.
How does Wilson, by Cartage, keep delayed loads moving across shifts?
Wilson, by Cartage, is an AI logistics agent that owns the follow-up on every load, including delayed ones, without going off shift. Carriers and receivers email Wilson's address on the company's domain, so replies arrive on the load record, not in a personal inbox. Wilson detects a delay, contacts the carrier, notifies the team, notifies the customer if configured and initiates rebooking from the approved carrier list when needed, automatically within the rules or with approval. For how Wilson handles carrier email across people, see who owns unanswered carrier email when a coordinator leaves.
Wilson replaces the TMS for freight execution and connects to the company's ERP. It handles LTL, FTL, ocean, drayage, parcel and cross-border freight. For the broader exception picture, see the best AI logistics software for exceptions across email and ERP.
What does a night look like with Wilson?
A hypothetical night: at 6 p.m., three loads are running late. Wilson has confirmed new ETAs with two carriers and asked the receivers for new slots. At 8 p.m., one receiver confirms a 10 a.m. slot; Wilson tells the carrier and emails the customer. At 11 p.m., the third carrier emails that the truck broke down. Wilson asks for repair time, hears "unknown", and requests quotes from approved backups for an early pickup. One is within the limit; under the rules, Wilson books it, confirms the rate confirmation and tells the shipping site. At 7 a.m., the morning list shows one load needing a person: the receiver that never replied.
What stays with the team?
The team sets the rules, names the after-hours approver and makes the decisions outside the rules. Wilson starts with assisted execution, and more routine follow-up runs on its own as the team sees the results. For the specific case of a missed pickup, see what AI logistics software should do after a carrier misses pickup.
How do teams start?
Most teams start Wilson on a few lanes and expand from there. Cartage helps map the highest-impact workflow during discovery. Lanes with early-morning deliveries or long transit across time zones are often a good start, because delays there often cross a shift.
How is Wilson priced?
Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract.
FAQs
How do you hand off a delayed shipment between shifts without losing the next action?
Keep the facts, the history, the next action, its owner and its deadline on the load record. An AI logistics agent like Wilson, by Cartage, owns the routine follow-up across shifts and hands the next shift only the loads that need a decision.
Who follows up overnight?
An AI logistics agent can follow up with carriers and receivers overnight, record replies and update customers as configured. A named person handles decisions that cannot wait until morning.
How do we stop carrier replies from landing in personal inboxes?
Have carriers email the agent's address on the company's domain. An AI logistics agent matches each reply to the load, so the next shift sees it on the record.
What should the morning handoff list show?
Only the loads that need a person, with what happened overnight and the decision needed. An AI logistics agent can produce this from the load records.
Sources
- Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai
- American Transportation Research Institute, research on truck driver detention (2023 data), September 2024: https://truckingresearch.org/2024/09/new-research-documents-substantial-financial-and-safety-impacts-from-truck-driver-detention/
If delayed loads still depend on who remembered to check before going home, book a demo to see how Wilson, the AI logistics agent by Cartage, keeps the next action moving across shifts.