Wilson by Cartage
Try Wilson →
Carrier email and shared freight inboxes

Who covers shipping when our logistics person is out?

Key Takeaways

  • Name the backup before anyone needs one. Coverage decided on the morning someone calls in sick is coverage that misses things.
  • Five items make coverage work: a shared inbox, an open-loads list, a carrier contact sheet, written approval limits for the backup and a handoff note.
  • The handoff note matters more than the backup's experience. A capable person with no context will still miss promises made last week.
  • Give the backup smaller approval limits than the regular owner, with a named person to call for anything above them.
  • Plan for the unplanned absence too. A sick day gives no time for a handoff, so the open-loads list and the shared inbox must already be current.
  • Wilson, by Cartage, is an AI logistics agent that keeps quoting, booking, tracking and exception handling moving within the company's rules, with every message and change kept in each shipment's change history, so the backup starts from the record instead of a guess.

Who should cover shipping when the logistics person is out?

The person who runs shipping at a manufacturer wakes up with a fever on a Tuesday. Three loads are scheduled to pick up that afternoon. One customer was promised a delivery appointment for Thursday, but the appointment hasn't been confirmed. A carrier emailed last night to say a truckload will be late. All of it sits in one person's inbox, and the customer service rep who is asked to "keep an eye on shipping" doesn't know any of it exists.

Shipping should be covered by a named backup who has access to the shared inbox, a current list of open loads, the carrier contacts and written approval limits, and who receives a handoff note before any planned absence. The backup doesn't have to be a logistics specialist. They do need to know what's moving, who to call and what they're allowed to decide.

Coverage fails for predictable reasons. The work lives in a personal inbox. Open loads are tracked in the regular owner's head or in a private spreadsheet. Carrier contacts are in their phone. Nobody wrote down which rates the backup can accept. And the planned handoff, if there is one, is a five-minute conversation on Friday afternoon.

What actually goes wrong during an absence

The common failures are small and expensive. A pickup isn't confirmed and the truck doesn't come. A carrier's delay notice isn't passed to the customer, who finds out when the freight doesn't arrive. A rate increase is accepted by reply because the backup didn't know it was above the usual range. A detention charge piles up because nobody told the dock a truck was coming. Industry data shows how costly waiting at the dock can be: the American Transportation Research Institute found trucks were detained at 39.3% of stops in 2023, with more than 135 million hours of detention and $3.6 billion in direct costs to carriers. A backup who doesn't know a truck is coming can't get it loaded on time.

Why one person ends up holding everything

Nobody plans for shipping to depend on one person. It happens gradually. The person who books freight is the one carriers know, so carriers email them directly. They learn which receivers need appointments and keep that in their head because it's faster than writing it down. They agree on a rate over the phone and remember it. Each habit is reasonable on its own. Together, they mean the company's freight knowledge sits in one inbox and one memory, and an absence exposes it all at once.

Planned and unplanned absences need different plans

A vacation gives time for a handoff note and a walkthrough. A sick day doesn't. The coverage plan should work for both, which means the daily habits matter more than the handoff itself. If the open-loads list and shared inbox are always current, an unplanned absence is manageable. If they're only updated before a vacation, a sick day leaves the backup starting from nothing.

Longer absences change the plan

A two-day absence can run on a handoff note and the shared inbox. A parental leave or a medical leave of several weeks can't. For longer absences, the backup needs more than temporary coverage: they need ownership. Hand over lanes formally, update the carrier contact sheet so carriers know the new main contact, and give the backup the same training a new coordinator would get. Plan for a check-in each week with the manager, so problems that build slowly, such as a carrier whose service is slipping, get noticed.

How do you set up shipping coverage step by step?

Set up coverage once, then keep it current as part of normal work. The steps below build a plan that works for a one-day absence and a two-week vacation alike.

Step 1: Name the primary and secondary backup

Pick one person as the primary backup and a second person if the first is also out. Write both names down and tell carriers and key customers who to contact. A backup can be another coordinator, a customer service rep, a purchasing buyer or a warehouse lead, as long as they have time set aside and know they're responsible.

Step 2: Move shipping email to a shared inbox

If carrier and customer emails go to one person's address, the backup can't see them. A shared inbox, or at least a shared alias that copies the backup, fixes this. Carriers should be told to use the shared address for all load messages. The carrier email and shared inbox guide covers how to set one up and keep it organized.

Step 3: Keep an open-loads list

The open-loads list shows every load that's booked but not yet closed: reference, customer, carrier, pickup date, delivery date, current status and next action. It can be a spreadsheet, a view in the ERP or a dashboard in the shipping system. The key rule is that it's updated every day, not only before a vacation.

Step 4: Build a carrier contact sheet

List every approved carrier with its dispatch email, phone number, after-hours number, tracking website, account number and the name of the usual contact. Include any notes the regular owner relies on, such as "Call before 10 a.m. for same-day pickups" or "Portal updates lag; call the terminal."

Step 5: Write the backup's approval limits

Decide what the backup can approve alone: the maximum rate per lane or per load, which carriers they can book, which accessorials they can accept and whether they can approve invoices. Anything above those limits goes to a named manager. For how to set limits that work, see negotiating freight rates within approval limits.

Step 6: Write the handoff note

Before a planned absence, the regular owner writes a handoff note covering open loads, promises made, known problems and anything due during the absence. The next section shows what it should include.

Step 7: Test the plan

Have the backup run shipping for a day while the regular owner is still in the office. Gaps show up fast: a missing login, a carrier who only calls one person's cell phone, a customer requirement nobody wrote down. Fix them before the real absence.

How much time the setup takes

The first setup takes the most effort: moving carriers to the shared inbox, building the contact sheet and agreeing on limits. After that, coverage costs only the daily habit of keeping the open-loads list current and filing documents by load. A useful rule is that if keeping the list current takes more than a few minutes a day, the list has too many columns. Status and next action are the two fields the backup needs most.

What should the handoff note include?

A good handoff note answers one question for every open load: what happens next, and who does it? It's short, specific and organized by load, not by inbox thread.

The parts of a handoff note

Section What it covers Example
Open loads Every booked load not yet delivered and invoiced, with status "PO 4471, LTL to Dayton, picked up Mon, due Thu"
Next actions What must happen on each load, and by when "Confirm Thursday delivery appointment by Wed noon"
Promises made What customers were told, and by whom "Told the customer we'd call if it slips past Thursday"
Known problems Delays, damage claims, disputed charges, missing documents "Truckload to Reno running a day late; customer informed"
Scheduled work Pickups and orders expected during the absence "Weekly replenishment ships Tuesday, same carrier as usual"
Approval limits What the backup can decide, and who to call above it "Up to the lane target; above it, call the ops manager"
Contacts Carrier and customer contacts for open issues "Carrier dispatch for the Reno load, plus terminal number"
Where things are Folders for documents, the open-loads list, the shared inbox "Rate confirmations and PODs in the shipping folder by PO"

Keep it in one place

The handoff note should live where the backup will look first, next to the open-loads list or pinned in the team channel. Email attachments get buried. Notes in a personal document can't be updated by the backup.

Write it for someone without context

The regular owner knows that "the Reno load" means a specific order with a specific problem. The backup doesn't. Use references, names and dates. "Call Mike about the thing" helps nobody.

Update it on the way back

When the regular owner returns, the backup writes a short note in reverse: what changed, what was approved, what's still open. Without it, the returning person spends a day reading the inbox to find out what happened. The same discipline applies to handing a load across shifts, as described in how to hand off a delayed shipment between shifts.

What can the backup decide, and what should wait?

The backup should be able to keep freight moving, but not to change the company's commitments. Written limits make the line clear and protect both the backup and the company.

Decisions the backup can usually make

  • Confirm pickups and delivery appointments for loads already booked.
  • Book routine loads with approved carriers at or below the lane's usual rate.
  • Tell customers about delays, using the customer's notification preference.
  • Request and file PODs, BOLs and rate confirmations.
  • Rebook a cancelled load with another approved carrier within the approval limit.

Decisions that should go to a named approver

  • Accepting a rate above the approval limit.
  • Using a carrier that isn't on the approved list.
  • Approving accessorials or extra charges outside the agreement.
  • Paying or disputing carrier invoices, unless the backup normally does this.
  • Making new commitments to a customer, such as a guaranteed delivery date.

Mistakes to avoid

  • Giving the backup the owner's full authority without training. A backup who can approve anything will approve things the owner wouldn't.
  • Giving the backup no authority at all. If every decision waits for the owner to return, freight stalls.
  • Leaving the approver unnamed. "Ask a manager" fails when three managers each assume another one is handling it.
  • Not telling carriers. If carriers keep calling the absent person's cell phone, the backup never hears about problems.
  • Forwarding instead of sharing. Auto-forwarding a personal inbox to the backup creates two copies of every thread and replies from the wrong address.

After-hours problems during an absence

Freight problems don't wait for office hours. A truck can arrive early, a driver can call about a closed gate, a carrier can cancel at 6 p.m. Decide in advance who answers after-hours calls during the absence and which problems justify a call to the approver at night. A simple rule works: anything that will miss a customer's delivery date gets a call; anything that can wait until morning gets a message.

What customers should hear during an absence

Customers don't need to know someone is on vacation. They do need consistent answers. Give the backup each key customer's notification preference: who to contact about a delay, by email or phone, and how far ahead. If the regular owner promised a call before a delivery, the backup makes that call. A customer who hears from a new name with the right information rarely minds; a customer who hears nothing does.

Coverage across modes

Coverage gets harder when the company ships in more than one mode. LTL and truckload loads move on a schedule of days. Parcel moves in volume, and problems show up as exceptions on a carrier's tracking page. Ocean and drayage loads run on longer timelines, with free time at the port and appointments at the terminal. Cross-border loads add paperwork handled by the customs broker. The handoff note should flag which open loads are in which mode, and the backup should know the one or two deadlines that matter most for each: the pickup window for LTL, the last free day for a container, the broker's document cutoff for a border crossing.

What to do when no approved carrier is available

The most stressful moment for a backup is a cancelled load with no obvious replacement. The coverage plan should include the order of carriers to call for each lane and what to do if none accepts. A backup carrier plan written in advance turns that moment into a checklist.

A coverage checklist for any absence

Run this checklist before a planned absence, and keep the daily items current so an unplanned one is covered too.

Item Daily or before absence Owner Done
All carrier and customer email goes to the shared inbox Daily Logistics lead Yes / No
Open-loads list updated with status and next action Daily Regular owner Yes / No
Documents filed by load reference Daily Regular owner Yes / No
Backup has logins for the inbox, ERP, carrier portals and shipping system Before absence IT or logistics lead Yes / No
Carrier contact sheet current, with after-hours numbers Monthly Regular owner Yes / No
Backup approval limits written and shared Before absence Manager Yes / No
Named approver for anything above the limits Before absence Manager Yes / No
Carriers and key customers told who to contact Before absence Regular owner Yes / No
Handoff note written and reviewed with the backup Before absence Regular owner Yes / No
Out-of-office reply points to the shared inbox and backup Before absence Regular owner Yes / No
Return note from the backup On return Backup Yes / No

Hypothetical example: a week of coverage

Consider a hypothetical distributor whose logistics coordinator takes a week of vacation. Before leaving, the coordinator updates the open-loads list, writes a one-page handoff note and spends an hour with the backup, a customer service rep. The backup can book routine LTL loads up to the lane target and must call the operations manager for anything else. On Wednesday, a carrier cancels a truckload pickup. The backup follows the backup carrier order in the plan, books the second carrier within the limit, tells the customer about the new pickup time and records it all on the load. When the coordinator returns, the return note lists that change, two delayed loads and one invoice held for review. The coordinator is caught up in under an hour.

Signs the coverage plan is working

A coverage plan works when the returning owner finds no surprises. Look for three signs after each absence: no pickups were missed because nobody confirmed them, no customer heard about a delay from someone other than the company, and no invoice was approved outside the limits. If one of those failed, find the gap in the plan, whether it was a missing contact, an out-of-date list or an unclear limit, and fix it before the next absence. Over time, the plan should need less explaining each time it's used.

Cross-training before it's needed

The best backup has already done the work. Rotate the backup into shipping for a few hours each month, even when nobody is out. They book a routine load, work the shared inbox for a morning and check one carrier invoice. The practice keeps logins working, shows where the documentation has fallen behind and makes the real absence feel familiar instead of stressful.

Where documents should be during an absence

A backup who can't find the rate confirmation can't check an invoice, and one who can't find the BOL can't answer a dock's question. Keep documents filed by load reference in one shared location. For a simple structure, see how to organize BOLs, PODs and freight documents.

How does Wilson, by Cartage, keep shipping covered when someone is out?

Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays freight for manufacturers and distributors, so routine work doesn't depend on one person being at their desk. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

When the logistics person is out, Wilson keeps the routine steps moving under the same rules:

  • Quotes and booking. Wilson requests quotes from the company's approved carriers, compares them on total cost and negotiates toward the company's rate targets within approval limits. Rates outside the limits go to the logistics team. It books with written acceptance and a rate confirmation, and schedules pickups.
  • Documents. Wilson generates rate confirmations, bills of lading, packing slips and pallet labels, and requests and files PODs.
  • Tracking. Wilson tracks each load with the best source available for that carrier: carrier API or EDI, GPS or ELD data where the carrier shares it, the carrier's website by PRO number, and email or phone calls when nothing else is current.
  • Exceptions. When a pickup is missed or a load is delayed or cancelled, Wilson contacts the carrier, tells the team in Slack, Microsoft Teams or email, tells the customer by email or SMS if configured, and starts rebooking from the approved carrier list automatically within the rules or after approval.
  • Invoices and payment. Wilson audits each carrier invoice against the rate confirmation and POD, and pays carriers from the Wilson Wallet. Payments above the approval limits or outside the rules wait for a person.

For the backup, the most useful part is the record. Every message, confirmation and change is kept in each shipment's change history, so the backup can open any load and see what was agreed, what happened and what's next, without searching someone else's inbox. The approval limits the company sets apply the same way whoever is covering, and Wilson books only carriers the company has approved.

Wilson replaces the TMS for freight execution and connects to the company's ERP. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope.

Teams start with assisted execution, where Wilson prepares and a person approves. Routine actions can then run automatically within the company's rules as the workflow is proven.

Pricing

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. Timing depends on scope: most teams start on a few lanes and expand from there.

FAQs

Who covers shipping when our logistics person is out?

A named backup with access to the shared inbox, a current open-loads list, the carrier contacts and written approval limits, plus a handoff note for planned absences. Wilson, by Cartage, an AI logistics agent, keeps routine quoting, booking, tracking and exceptions moving within the company's rules and records every change in each shipment's change history.

What should a shipping handoff note include?

Every open load with its status and next action, promises made to customers, known problems, work scheduled during the absence, the backup's approval limits, contacts for open issues and where documents are kept.

Should the backup have the same approval limits as the regular owner?

Usually not. Give the backup enough authority to keep routine freight moving, such as booking approved carriers at or below the lane's usual rate, and send anything above that to a named approver.

How do we cover shipping on an unplanned sick day?

Keep the open-loads list and shared inbox current every day, so the backup can start from them without a handoff. Keep the carrier contact sheet and approval limits written down in advance.

Should we forward the logistics person's email to the backup?

A shared inbox works better. Forwarding creates duplicate threads and replies from the wrong address. Ask carriers and customers to use the shared address for all load messages.

What is an open-loads list?

A list of every load that's booked but not yet closed, with the reference, customer, carrier, dates, current status and next action. It should be updated daily.

Who should be the backup for a logistics coordinator?

Anyone with time set aside and basic knowledge of the orders, such as another coordinator, a customer service rep, a buyer or a warehouse lead. What matters most is the handoff note and the written limits.

What should the backup do if a carrier cancels?

Follow the backup carrier order for that lane, book the next approved carrier within the approval limit, tell the customer if needed and record the change on the load. Anything outside the limits goes to the named approver.

How should carriers know who to contact during an absence?

Tell them before the absence, set an out-of-office reply that points to the shared inbox and the backup, and make sure the shared address is on every rate confirmation and BOL.

What should happen when the logistics person comes back?

The backup writes a short return note: what changed, what was approved, what's still open. The regular owner reads it and the change history of any load that moved, instead of reading the whole inbox.

How often should a backup practice covering shipping?

A few hours a month is enough for most teams. The backup books a routine load, works the shared inbox and checks an invoice, which keeps logins working and shows where the notes have fallen behind.

Sources

Bring the open loads from your last vacation week and see how Wilson would have kept each one moving.