Before you’ve had your first sip

You open the routing guide before your coffee’s done brewing. It’s 6:52 AM, pickup’s at 9, and the spreadsheet’s got three columns for this lane: primary carrier, backup, and whoever you call when both of those fall through.

You call the primary carrier. It rings four times and drops you into a voicemail greeting you could recite from memory at this point. You hang up, open your email, and draft a note to your backup, because at least email doesn’t feel like yelling into a void. You hit send and you wait. You check Slack. You answer something unrelated. You check your inbox again. Nothing.

By the time your backup finally writes back — a flat, apologetic “no capacity this week” — your coffee’s gone cold and you’re manually crossing them off the list, dialing your third option, and hoping this one picks up before the pickup window starts feeling less like a deadline and more like a threat.

You’ve done this same dance a dozen times this month already, and you’ll do it a dozen more before the month’s out. Doesn’t matter what industry you’re in or what’s on the truck. It’s still you. It’s still this.

Here’s the thing nobody says out loud often enough: tendering is the first promise your company makes to the customer waiting on that order. Before the truck rolls, before the tracking updates, before the delivery confirmation — someone has to actually get a carrier to say yes. Right now, you’re keeping that promise by hand, one phone call and one cold cup of coffee at a time.

What load tendering actually is (and what we mean when we say it)

You know this cold: a tender is your formal offer to a carrier for a load, sent in priority order down your routing guide, until someone accepts it. If your primary carrier declines, you waterfall to your backup, then whoever’s next. If you’re running EDI, that’s a 204 out and a 990 back. If you’re not — and if you’re moving a few hundred loads a month, there’s a good chance you’re not, because EDI-to-every-carrier only pencils out once you’re running serious volume — that’s a phone call, an email, and a manual note about who said what.

You don’t need this explained. What breaks isn’t your grasp of the process — it’s executing it once volume outpaces however many people you have watching the clock for a decline.

And the clock matters more than it feels like in the moment. MIT Center for Transportation & Logistics research, sponsored by C.H. Robinson, found that giving carriers more lead time between tender and pickup measurably raises the odds your top carrier accepts, and that even pushing average lead time out by a day or two lowers cost per load. Every minute a load sits between one call and the next isn’t neutral. It’s lead time your best carrier doesn’t get, and it’s the difference between covering a load at your contracted rate or watching it waterfall onto the spot market.

Why manual tendering breaks down at volume

You already waterfall Plan A to Plan B to Plan C by hand. The question was never whether you know the process. It’s what happens to that process once your load count climbs and you still only have so many people watching the clock for a decline.

Here’s the number that puts a hard edge on that: FreightWaves’ SONAR Outbound Tender Rejection Index (OTRI) tracks exactly how often carriers say no to contracted loads shippers tender them, and it’s been running in the mid-teens percentage nationally through mid-2026.

That means somewhere around one in every six or seven tenders you send gets rejected before you even get to the “waterfall” part of your day. Industry analysis of this data shows that once rejection rates sustain above 10%, contracted carriers start rejecting enough freight that shippers get pushed onto the spot market at a real premium, often 20–30% above the contract rate they’d planned on paying. Declines are the baseline you’re building a process around.

EDI doesn’t fix this for you; it’s not built for your carrier base

EDI doesn’t close that gap for most shippers moving a few hundred loads a month, either. EDI 204/990 automates tendering well once you’ve got the integration budget to run it against your whole carrier base. Most mid-size shippers don’t have that.

Your routing guide lives in a spreadsheet, your carriers live in your phone and inbox, and building EDI out to your secondary and tertiary carriers usually costs more than the lanes are worth. So the gap between “we know the process” and “the process runs itself” doesn’t close. It gets covered, manually, load after load, by whoever’s free to make the next call.

That’s where the real cost shows up, and it’s not just hours:

• Decline reasons disappear. A carrier says no over the phone, and unless someone writes down the exact reason — no capacity, rate too low, equipment unavailable — it’s gone. No pattern to learn from, no record if a customer asks why a shipment ran late.

• The waterfall only moves as fast as someone notices. A decline doesn’t trigger the next tender by itself. It waits for whoever’s watching that load, and every minute it waits is lead time your next carrier doesn’t get.

• None of it gets more efficient with more volume. More loads mean more calls, more inboxes, and more people needed just to keep the clock moving. There’s no version of “call and wait” that scales with your growth.

See how Ana reads your routing guide exactly as it is without reformatting.

Load tendering, status by status

Every load moves through the same five stages before it’s covered, whether that takes one call or five. Here’s where the process actually lives, and where it actually breaks.

1. Routing guide setup

• Info needed: Carrier tiers per lane, contracted rates, equipment type, insurance and compliance status, current contacts.

• Method: A spreadsheet, maintained by ops or procurement, updated whenever a contract changes.

• Your job: Keep it current. Add new carriers as they’re vetted, reorder tiers as performance shifts, update rates as they’re renegotiated.

• Common failure: The guide drifts out of date faster than anyone updates it. A carrier who stopped answering calls two months ago is still sitting at the top of the list, and nobody finds out until a load stalls there.

2. Primary tender sent

• Info needed: Pickup and delivery details, equipment, rate, response deadline.

• Method: A phone call or email to your primary carrier for the lane.

• Your job: Reach the right contact, confirm they’ve actually received it, and start the clock on a response.

• Common failure: The tender lands with a contact who’s out of office or doesn’t check that inbox often. There’s no read receipt and no way to know it landed until you’re already following up.

3. Response window

• Info needed: Accept, decline, or silence.

• Method: Waiting on a callback or reply, usually while juggling several other open loads at the same time.

• Your job: Watch the clock, follow up if nothing comes back, and log whatever answer you get.

• Common failure: Nobody’s watching this specific load closely enough among everything else open. Silence gets read as “still deciding” instead of what it usually is: a decline nobody bothered to send.

4. Waterfall

• Info needed: The next carrier in tier order, an updated rate if the lane’s shifted, and whatever the last decline reason tells you about your odds.

• Method: Manually restarting the call-and-wait cycle with your backup carrier, then the next one if it comes to that.

• Your job: Catch the decline the moment it happens and re-tender immediately, before the lead time you have left shrinks any further.

• Common failure: The gap between a decline and the next tender stretches to hours instead of minutes. By the time your backup gets the call, they’ve already committed their capacity somewhere else.

5. Exception: routing guide exhausted

• Info needed: A full record of who declined and why, plus your spot market options.

• Method: Escalation to a manager or transportation lead, sometimes straight to the load board.

• Your job: Decide fast: spot market, a rate bump, or a carrier outside the guide entirely.

• Common failure: Nobody realizes the guide is exhausted until the pickup window is already tight, turning what should be a routine exception into a scramble.

Why manual load tendering is expensive

Every hour your team spends chasing a decline is an hour not spent on the shipments that are already moving, or the rate negotiations that would actually lower your freight spend. That math doesn’t stay small for long; a coordinator who spends even a couple of hours a day on carrier chasing is giving up close to half a workweek to a task that doesn’t move a single load forward on its own.

And that’s before you count what happens when a load actually falls through the cracks: a blown delivery window with a retail partner doesn’t just delay a shipment, it can trigger an OTIF chargeback, and that’s on top of whatever spot market premium you just paid to cover the load instead.

You don’t have to take an outside analyst’s word for what this costs in practice, either. Cody Schmidt, corporate purchasing manager at Plastic Ingenuity, saw his own team’s tendering time drop “from three hours to under 15 minutes” after moving off manual tendering. That’s one team, one real switch, and a number you can hold up against your own tendering time to see where you actually stand.

You’re also not early to this. McKinsey’s most recent survey of logistics shippers and service providers found that more than 85% already say their digital investments have added real value to the business. The leaders in this industry have already moved past asking whether automation is worth it.

The question left on the table is which parts of the operation to automate first, and load tendering — high-volume, repetitive, and directly tied to service performance — is usually the easiest place to start.

Here’s the part worth being honest about, though: automation in supply chain has a real trust problem, and it’s not paranoia. Forrester’s own research puts the failure rate of AI-powered supply chain implementations at 72%. That’s a pattern in how most of these tools get built, as black boxes that make decisions you can’t see and can’t explain when a customer or a carrier asks what happened.

That’s exactly why Ana doesn’t work that way: every change you make happens in plain English, in Slack or email, with a confirmation step before anything ships. Every tender, decline, and waterfall gets logged in a full audit trail you can open on any load. The failure mode Forrester is describing is a transparency problem, and transparency is the whole design, not a feature bolted on after the fact.

$1 per tender, no platform fees, no long-term contracts.

How Ana turns tendering into a force multiplier

You’ve already read what breaks when a person has to run every step of the routing guide by hand. Here’s what changes when Ana runs it instead.

1. Bring your routing guide exactly as it is

What Ana does: Upload your routing guide in whatever format it already lives in — Excel, PDF, or connect it directly by API. Ana reads it as-is, maps your carrier tiers, and follows the standard operating procedures you’ve already built. No reformatting, no cleanup, no migration project.

Impact: You don’t spend the first month of implementation rebuilding a spreadsheet you’ve already spent years refining. Ana adapts to your routing guide. You don’t adapt to hers.

2. Control everything in plain English

What Ana does: Need to swap a carrier, update a lane, or change a policy? Just tell Ana in plain English, in Slack, Teams, or email. She confirms the change, shows you exactly what she’s about to do, and applies it only after you approve it.

Impact: Changing your routing guide stops being a ticket to your TMS team or a spreadsheet edit someone might forget to save. It’s a conversation, and you can see exactly what’s about to change before it does.

3. Auto-tender and auto-waterfall

What Ana does: Ana sends the tender, tracks every response, and the moment a carrier declines, she automatically waterfalls to the next carrier in your routing guide without waiting for someone to notice.

Impact: This is the core bandwidth problem, solved directly. The lead time you lose waiting for someone to catch a decline and make the next call goes away. Ana catches it the instant it happens.

4. Catch every exception the moment it happens

What Ana does: When every carrier in your routing guide has declined, Ana flags it immediately, with full context on who declined and why, sent straight to Slack, Teams, or email.

Impact: You stop finding out your routing guide is exhausted only once the pickup window is already tight. You find out the moment it happens, with enough runway to actually do something about it.

5. A complete, auditable trail of every move

What Ana does: Every tender sent, every decision made, every carrier response — logged and timestamped. Open any load and see exactly what happened and why.

Impact: No more decline reasons that evaporate the second someone hangs up the phone. When a customer asks why a load ran late, or you’re renegotiating with a carrier who’s declining too often, the answer’s already sitting there.

Learn more about how Ana tenders.

The impact: time, trust, margin

Put all of that together, and here’s what actually changes on your side of the routing guide:

• Hours back every week. The time your team spent watching the clock for declines and making the next call goes back to sourcing new capacity, negotiating rates, and handling the shipments that actually need a human’s judgment.

• Faster time-to-cover, every load. The lead time you lose waiting for someone to notice a decline is exactly the lead time your next carrier needs to say yes. Close that gap, and more of your loads get covered at your contracted rate instead of waterfalling onto the spot market at a premium.

• A full audit trail, ready before you need it. Every tender, decline, and waterfall is logged and timestamped automatically. When a customer asks why a load ran late, or you’re deciding whether a carrier’s declining too often to stay in your routing guide, the answer’s already there.

• The math holds up. $1 per tender, no platform fees, no long-term contracts, live in under a week, and a proven 5:1 ROI. This isn’t a multi-quarter transformation project. It’s a change you can make this week and measure by next month.

A quick comparison: manual vs. EDI/TMS vs. Ana

Every tender is a promise

Every tender you send is a small promise: to the carrier making the call on their capacity, and downstream, to the customer waiting on that load. A routing guide is really just a written record of who you trust to keep that promise, and in what order.

Right now, keeping it depends on someone noticing a decline in time, remembering who’s next, and making the call before the window closes. That’s a lot to ask of any one person once volume climbs, and it’s why so much of what looks like a tendering problem is really a bandwidth problem wearing a different name.

Ana makes sure the promise gets kept every time, at every tier, without waiting on whoever happens to be free to notice. Your routing guide runs the way you built it to run. Every decline gets logged. Every waterfall happens the moment it needs to. And when something genuinely needs a person, you’re the first to know about it, not the last.

See it on a real load, not a slide deck.

Frequently asked questions

What is load tendering for a shipper?

A tender is your formal offer to a carrier to haul a specific load. Load tendering is the full process of sending that offer, in priority order down your routing guide, until a carrier accepts it.

What’s the difference between EDI 204 and EDI 990?

EDI 204 is the load tender itself, sent from you to a carrier with pickup and delivery details, equipment type, and rate. EDI 990 is the carrier’s electronic response, accepting, declining, or countering the offer. Every tender-response cycle uses both.

What is a routing guide waterfall?

Waterfalling is what happens when your top carrier for a lane declines a tender: the load automatically drops to the next carrier in your routing guide, then the next, until someone accepts it.

Do you need EDI to automate load tendering?

No. EDI 204/990 works well if you’re a large shipper or enterprise carrier with the integration budget to run it across your whole network. Ana automates tendering directly from the routing guide you already have — Excel, PDF, or API — without requiring EDI setup with every carrier.

How much does load tendering automation cost with Ana?

$1 per tender. No platform fees, no long-term contracts, and no separate implementation project. You only pay for what you actually tender.

What happens when every carrier in the routing guide declines a load?

That’s an exception, not a routine event. Ana flags it immediately, with full context on who declined and why, sent straight to Slack, Teams, or email, so you can decide whether to go to the spot market, adjust the rate, or bring in a carrier outside your guide.