Tariff Volatility and Freight Ops Capacity

A tariff announcement becomes a freight ops problem within hours: shippers send the same rerouting and requote questions to 2 or 3 forwarders at once, and a forwarder with a broad client base can see 15 to 25 RFQs land in a single day. Each one takes 15 to 25 minutes of reading, field extraction, rate lookup, and response, so 20 requests stack 5 to 8 hours of unscheduled coordination on top of a normal job load. The forwarder who answers first with a clean quote usually wins the booking; a response that slips 6 to 8 hours mostly loses it. The bottleneck is not rate access. It is the front end of the loop, reading each email and pulling the fields out, before quoting can even start.

The pattern plays out the same way every cycle. The tariff announcement drops Tuesday morning.

By noon your inbox looks different. Shippers who haven’t needed you in weeks are sending emails. Some want to know if their active shipments are hit. Some want quotes on alternative lanes. Some are attaching spreadsheets: what does it cost out of Vietnam? Thailand? Mexico?

The more clients you have, the more of this lands. The emails are not the problem. What your team has to do before they can answer any of them is.

What is an RFQ in freight forwarding?

An RFQ, a request for quote, is a shipper asking a forwarder to price a specific movement: lane, mode, commodity, weight, incoterms, and cargo ready date. On a normal week they arrive at a manageable pace and the desk absorbs them between jobs. What makes a tariff window different is concentration. The same 6 fields still have to come out of every request, but the requests arrive in one day instead of three weeks, and they arrive from clients you have not heard from in months, in formats your team has never seen. An RFQ is also a perishable asset: unlike a filing or an arrival notice, it has no fixed deadline, just a decaying probability of winning that drops with every hour it sits unanswered.

What does an RFQ surge look like after a tariff announcement?

A Section 301 adjustment, a de minimis change, a new surcharge: pick one, and quote requests start landing before lunch.

Some of the emails are clean. Lane, commodity, weight, incoterms, cargo ready date right there in the first paragraph. Most are not. Paragraph-form messages, forwarded threads, spreadsheets with questions buried in cells.

Before your team can respond to any of them, someone has to read it, figure out what the shipper actually wants, and pull out the fields that make a quote possible. Then someone looks up rates, builds the response, and sends it.

A clean RFQ cycle takes 15 to 25 minutes. Twenty of them on top of your normal job load is 5 to 8 hours of coordination work nobody scheduled.

Why does response time decide which forwarder wins the booking?

Shippers rerouting because of a tariff change are not waiting around. They ask two or three forwarders the same question. First one back with a clean quote gets the booking.

If your team is working through a backlog, some of those requests sit 6 or 8 hours. Some until morning. By then the shipper has heard back from someone else.

There is a second cost hiding behind the lost bookings: the jobs already on the desk. The 20 surge RFQs did not arrive on an empty day. They arrived on top of the arrival notices, the filings due, and the containers hitting free-time limits that were already scheduled, and every hour spent reading requote emails comes out of that work. A surge day that ends with the RFQs answered and 2 filings pushed to tomorrow morning has quietly traded compliance risk for quote speed, and nobody made that trade on purpose. The desks that handle tariff weeks well are the ones where the surge work and the scheduled work draw from different pools, because the reading layer is no longer competing with the judgment layer for the same hours.

What does the manual RFQ loop actually cost per request?

For one RFQ, here is the sequence:

1. Find the email. Match it to the right contact or open job.
2. Read the thread. Figure out what the shipper actually wants.
3. Extract the fields: lane, mode, commodity, weight, incoterms, cargo ready date.
4. Check rates across carrier contacts, rate sheets, and your TMS quoting tools.
5. Write and send the quote.
6. If they accept: create the job in your TMS. Your ops team reviews every entry before it goes in. Nothing writes to the TMS without a team member signing off.

Steps 1 through 3 are reading and copying. No judgment. On a normal day your team handles this automatically.

On a day with 20 open threads, those steps eat the morning. Actual quoting starts after.

How can I compress the front end of RFQ handling?

If the extraction is already done when your team opens the email, they go straight to rates and response.

Lane, mode, commodity, weight, incoterms, and cargo ready date already pulled from the email. Shipper matched to an existing account or flagged as new. RFQ bound to an open job if one already exists.

Your team still reviews every quote. They still approve every TMS write. Nothing goes into your system without someone on it. The reading and field-copying just stops being their problem.

At 20 RFQs in a day, same-day response versus next-morning response is the margin on those bookings.

Manual loop versus extraction-first desk, side by side

The judgment work stays with your team on both sides of this table. The copying work moves.

Step	Manual desk	Extraction-first desk
Reading and field extraction	5 to 10 minutes per RFQ, by hand	Done when the email is opened
Matching shipper to account	Inbox search and memory	Matched or flagged as new, automatically
Rate lookup and quote build	The team, with judgment	The team, with judgment, starting immediately
Time to first response	6 to 8 hours on a surge day	Same day, often same morning
TMS entry on acceptance	Keyed by hand, then reviewed	Staged for review; a person approves every write

The judgment steps do not move. Rate strategy, margin, which carrier to lean on for the lane: those stay with your team on both sides of the table. What moves is the 5 to 10 minutes of reading and copying in front of each one, which on a 20-RFQ day is the difference between quoting today and quoting tomorrow.

How do you prepare the desk before the next tariff window?

Tariff dates are published in advance. The surge is predictable even when the policy outcome is not, so the preparation can happen on a quiet week:

1. Count your last surge. Pull the inbox for the last tariff announcement and count the requote emails in the following 48 hours. That number, not your average day, is what the desk has to absorb.
2. Time one RFQ honestly. Read, extract, look up, respond, from open to send. If it is 15 to 25 minutes, multiply by the surge count and see whether the hours exist.
3. Decide the triage rule in advance. Which clients get answered first, which lanes you actually want, what gets a holding reply. Deciding this during the surge costs the time it was meant to save.
4. Fix the front end. The reading-and-extraction step is the only part of the loop that needs no judgment, which makes it the only part worth automating before the date hits.

What happened to RFQ volume around the Section 122 expiration date?

The Section 122 surcharge was set to expire July 24, 2026, with the outcome uncertain right up to the date: a drop, an extension, or replacement by Section 301 or Section 232 coverage. Dates like that generate the same inbox pattern as an announcement, a concentrated round of shipper questions and rerouting requests in the surrounding days, because shippers position before the deadline rather than after it.

The next such date is already on someone’s calendar. Tariff actions in 2025 and 2026 have arrived in cycles measured in months, not years, and every one of them lands on the desk the same way: as email volume. If your team is still running the manual loop when the next window opens, it is going to be a long day.

For background on the current tariff environment and what the IEEPA ruling changed for your clients, see The IEEPA Ruling and What It Means for Freight Forwarders Right Now.

TIO reads every inbound RFQ the moment it arrives, extracts the fields, and queues it for your team to quote and approve. See how the inbox-to-TMS coordination layer works in a live workflow.