​What One Changed Plan Can Tell You About Your TMS

Two connecting flights have just been canceled at the same airport. The woman at gate 14 gets a push notification with a new flight, a new gate, and a meal voucher she didn’t have to ask for but will absolutely use. Over at gate 22, a man on his way to a wedding gets a text telling him to “see an agent,” and a line at the counter that is at least forty people long. Next time either of them books a ticket, they’ll remember which kind of rebooking experience they had.

You can judge a TMS the same way. When shipments run on schedule, cost and service metrics may look good, until a changed delivery date or rejected tender reveals system limits. In this article, learn how to trace a recent plan change to see whether your team can support the response your operation needs, and identify where manual work slows them down.

Heading Into 2027, There May Be Less Room to Recover

The September 2026 C.H. Robinson North American freight market update predicts that 2027 spot-market truckload cost per mile will rise about 10% for dry van and flatbed and 11% for refrigerated freight, in a market with “less excess capacity available to absorb sudden changes in freight demand.” Long hauls will feel it most. In August 2026, the average weekly route-failure rate was 8.5% for shipments over 600 miles, compared with 3.6% for shipments under 400 miles. Route guide failures peaked at 7.5% the week of July 4th.

For a changed load, that leaves less room to recover. A rejected tender can push a shipment further down the routing guide or onto the spot market, where the report expects the steepest increases, especially in the first half of 2027, as trucking capacity continues to shrink.

Trace One Changed Load From First Signal to Freight Bill

If you lead transportation or freight operations, start with a recent shipment-plan change that could happen again. Trace what happened from the first signal through the final bill.

Take, for example, the journey of a dry van from a Columbus distribution center (DC) to a grocery customer’s DC in Dallas, a distance of about 1,000 miles. On the Friday before the week of July 4th, the customer asks to move the delivery appointment from Thursday to Wednesday. This means pickup in Columbus moves from Tuesday to Monday.

Log a row each time the load changes hands, with timestamps from your TMS audit log, tender history, email thread, and dock appointment log. Here’s what it looks like for our hypothetical load:

Time	What happened	How long it waited
Fri 4:10 p.m.	Customer emails the account manager requesting change	N/A
Mon 9:25 a.m.	Planner finds the forwarded email	65 hrs
Mon 11:50 a.m.	Planner rebuilds the load and tenders it	2 hrs 25 min
Mon 12:40 p.m.	Primary carrier rejects	50 min
Mon 1:25 p.m.	Second carrier declines	45 min
Mon 2:05 p.m.	Third carrier declines	40 min
Mon 2:50 p.m.	Fourth carrier on the guide accepts	45 min

 

Signal: Transportation Receives the Change Late

The customer emailed the change on Friday, but because the request was done manually, transportation didn’t see it until Monday morning. By then, the email had been forwarded three times and buried in a thread titled RE: RE: FW: quick question.

Shipment changes can arrive through EDI, portals, email, and the occasional phone call. When an EDI feed or a portal is connected to the TMS, updates can flow into your systems automatically, but an email or a call usually depends on someone capturing the new date in the TMS. Until then, the TMS can’t act on the change.

If transportation teams had received the change earlier on Friday, the primary carrier would have had more time to check for and reserve Monday availability. Instead, they had only a few hours to rebuild the load and secure a carrier for the new pickup time. The realities of those last-minute changes during a holiday week led to more delays and, ultimately, higher costs.

For your load, ask:

Did the TMS learn about the change as an order update, or as an email, call, or portal message that someone retyped?

How many hours passed between the customer’s decision and the first replanning action, and where did the change wait?

Replan: A Planner Rebuilds the Load by Hand

Moving the pickup earlier by one day means the Columbus DC has to load the trailer on Monday, and the Dallas DC has to book a Wednesday dock appointment to receive the load. Only then can the tender go back out to a carrier, now on much shorter notice.

Manhattan ActiveTransportation’s continuous optimization capability can recalculate the shipment plan after a delivery date change. The planner can then review the new cost and confirm whether the customer’s Dallas DC can still receive the load on Wednesday.

In this example, the planner rebuilt the load manually and sent a new tender; that took about two and a half hours. If your records show a long gap between the customer’s change and the new tender, ask:

When the date changed, did the TMS rebuild the plan automatically, or did someone rebuild it in a spreadsheet?

Could the planner see, in one place, how the change affected cost, the dock appointment, and the delivery date promised to the customer?

Recovery: The Load Goes Back Out to Carriers

The primary carrier originally planned a Tuesday pickup, but in a holiday week they don’t have an available truck near the Columbus DC on Monday. The team tenders the load to backup carriers one at a time, moving down the routing guide until the fourth carrier accepts. But it’s at a rate much closer to the spot-market price than the contract rate.

Each step further down the guide can push costs higher, and each rejection eats into an already short pickup window. For a benchmark, C.H. Robinson’s route-guide depth metric tracks how far shippers will go into their backup-carrier list after the awarded carrier rejects the tender. A depth of 1.0 is perfect; the average across North American shipments in August 2026 was 1.35.

Pull your tender history and ask:

How many carriers deep did you have to go in the routing guide, and how often does that lane end up on spot when capacity is tight?

Who notified the carrier, the DC, and the customer, and how much of it was manually typed?

Reconciliation: The Bill Doesn’t Match the Final Carrier and Rate

If your freight audit still shows the original carrier and rate, the new carrier’s invoice may be flagged for review because it doesn’t match the final tender. Match the bill to the final tender, then compare the bill with the original rate to see what the late change cost you, a handy number the next time that lane comes up in a bid.

Open the audit record and check:

Did the freight audit use the final carrier and rate, or the original?

Did the outcome change anything in the routing guide, the carrier scorecard, or the next procurement round?

Five Causes of Shipment Delays to Investigate When Evaluating Your TMS

You now have a shortlist of places where the load waited, and each wait traces back to one of five causes:

Data and configuration. If rates, contracts, and carrier capacities were out of date when the change happened, the system planned, or maintained a plan, with outdated information.

Adherence. If a planner skipped the routing guide to call a carrier they trust, the system never got the chance to choose.

Handoffs. If the change got stuck in another system or inbox before transportation saw it, the TMS never had a chance to act on it. Solving handoff delays usually means integrating systems, but that’s rarely simple. Even inside transportation, a TMS often has to connect with separate visibility, parcel, and routing tools. “Integration has always been an ugly word,” Brock Johns, a director analyst at Gartner, told Logistics Management’s 2025 technology roundtable. He noted that Gartner expects 75% of large shippers to “struggle to juggle their fragmented transportation application portfolios” through at least 2027.

Unused capability. If your system has re-optimization or automated tendering that nobody enabled, the fix is a configuration project with your current vendor. Each new configuration carries potential cascading implications which must each be considered.

The system itself. If the data, setup, integrations, and process are sound, but your TMS can’t replan around a change, you may have found a capability gap that configuration alone won’t close.

What a Modern TMS Makes Possible

Several delays in our example listed above sit at the boundary between transportation and another team or system, which is why the Gartner Magic Quadrant for Transportation Management Systems names “the convergence of transportation with broader supply chain execution” as one of three trends shaping the market. The report also identifies two other trends: predictive analytics for smarter transportation decisions, and fast adoption of AI agents for supply chain productivity to automate routine work such as appointment scheduling, exception handling, and freight procurement.

On our example load, if the order change had reached the TMS as data, a shipment tracking agent could have monitored the shipment’s progress against the new delivery window and flagged delays before they became emergencies. When the fourth carrier’s invoice arrived, a freight payment agent could have validated it. The planner would still make decisions that call for human judgment, like whether to pay for an expedite or ask the buyer if the original Thursday delivery could still work.

Together, predictive analytics and AI agents can give transportation teams earlier visibility while leaving planners in control of decisions that affect cost and customer commitments.

Look For Causes That Repeat Across Loads

One delayed load might just reflect a bad week, so it’s important to review two or three other recent changes with your planners, carrier managers, and IT. Compare where each load waited and what caused each delay. Then, choose one recurring cause to investigate first. A cause that appears across multiple loads is more likely to point to a repeatable process or system issue.

How Manhattan’s ActiveTransportation™ Connects the Order, the Tender, and the Bill

If handoffs between teams keep delaying loads, Manhattan ActiveTransportation brings planning, execution, and settlement in one system on the Manhattan ActivePlatform foundation. When a customer changes an order, Manhattan ActiveTransportation re-optimizes the affected shipments based on the change, and embedded AI agents help streamline traditionally challenging workflows. For example, the Shipment Tracking Agent monitors shipments in motion and flags delays before they become emergencies, and the Freight Payment Agent processes carrier invoices and supports creating and validating freight invoices, freeing your planners to make decisions that need human judgment. Manhattan’s Agent Foundry empowers your team to build bespoke agents to handle organization-specific requirements. Transportation modeling software gives them a place to rehearse the next holiday week before it comes.

Going into a year with less spare capacity and spot rates up 10%, you can’t afford to let a late change sit idly in an inbox until Monday. ActiveTransportation re-plans the load as soon as the change reaches the TMS, while your primary carrier still has a truck to spare.

Gartner, Magic Quadrant for Transportation Management Systems, Brock Johns, Oscar Sanchez Duran, and Manav Jain, 30 March 2026.