Rate-Cons Live in PDF. So Does Carrier Onboarding. Both Belong in the TMS by Lunch.

At a 50-truck carrier operation based in central Nebraska, the dispatcher’s morning starts with the inbox. Rate confirmations from last night’s loads are sitting in email — ten, fifteen, sometimes twenty PDFs from different brokers, each formatted differently, each requiring someone to open it, read the stop sequence, the rate, the accessorials, and any special instructions, and re-enter all of that into the TMS. That entry work takes eight to twelve minutes per rate-con when done carefully. When done fast, things get missed: an accessorial that doesn’t make it in, a special instruction about a lumper charge, a stop sequence entered in the wrong order. Mistakes surface when the driver is already at the first stop.

Meanwhile, somewhere in a folder or a spreadsheet, there’s a carrier packet for a new owner-operator that came in three weeks ago. The W-9 is on file. The certificate of insurance expired last month. The MC authority letter was never received. Nobody followed up because the dispatcher who handled the intake is on a different assignment and the operations manager assumed someone else had it.

Both of these problems — rate-con entry and carrier onboarding documentation — are solvable with the same approach: structured extraction and automated follow-up. Neither requires a new TMS. Neither requires adding headcount. They require building the right intake and tracking layer on top of what the operation already has.

The TMS gap most carriers tolerate

Almost every TMS in the mid-market has an import function. The problem is that it expects a structured file — an EDI 204, a CSV, an XML — and most broker rate-cons come in as PDFs formatted to each broker’s internal template. The TMS import function sits unused because the input isn’t in the right format.

The gap that results isn’t dramatic. It’s a manual entry queue that the ops team treats as a cost of doing business. Eight minutes per rate-con at fifteen rate-cons a day is two hours of manual data entry — every day, by a dispatcher who could be doing something that actually requires dispatch judgment. The errors are infrequent enough that nobody has calculated what they cost, but frequent enough that experienced dispatchers have a mental checklist they run on every entry because they’ve been burned before.

The onboarding gap is quieter but more expensive when it surfaces. A carrier whose COI has lapsed is a compliance exposure on every load she runs in that window. The broker that discovers an expired COI mid-load doesn’t always call politely. The carrier that adds an owner-operator to a load before her MC authority is confirmed is accepting a liability that may never be documented until something goes wrong.

Tolerating these gaps is a choice, usually made by operations that don’t have the bandwidth to fix them and haven’t calculated what they cost.

The rate-con parser

The rate-con parser does one thing: it reads the PDF and produces a TMS-ready record.

The input is whatever arrives in the inbox — PDF attachments, scanned faxes, email bodies that contain the rate-con inline. The parser reads the document, identifies the fields the TMS needs (stop sequence, shipper and consignee addresses, pickup and delivery windows, rate, accessorials, special instructions, reference numbers), and produces a structured record for dispatcher review before it posts to the TMS.

The dispatcher reviews the structured record, not the PDF. She sees the stops in order, the rate broken into line items, any accessorials flagged as unusual relative to the agreed load (a detention charge on a load that wasn’t supposed to have detention, for example), and a confidence indicator where the parser was less certain about a field. She approves, adjusts if needed, and the record posts.

The time goes from eight to twelve minutes of manual entry to two to three minutes of review. The error rate drops because the parser is reading the source document directly — it doesn’t misread a stop sequence because it was moving fast or misplace a decimal in a rate. The dispatcher’s cognitive load drops because she’s reviewing a structured record rather than translating a formatted PDF into TMS fields.

At fifteen rate-cons per day, the time savings run roughly 90 minutes per dispatcher per day in a well-built installation. That range reflects consistent parser performance on high-volume standard broker formats; formats that change frequently or are highly non-standard take longer to calibrate.

The onboarding nag bot (W-9, COIs, MC authority)

Carrier onboarding documentation follows a known checklist: W-9, certificate of insurance with the correct additional insured, MC authority letter, and depending on the operation, a carrier agreement and a drug and alcohol compliance certification. The problem isn’t that anyone is confused about what’s needed. The problem is that collecting it requires follow-up, and follow-up is manual, and manual follow-up competes with everything else on the dispatcher’s or ops coordinator’s plate.

The nag bot is an automated follow-up sequence triggered by a new carrier setup event. When a new carrier is added to the system, the sequence starts: an initial request for the onboarding checklist, a follow-up in 48 hours if the W-9 isn’t received, a follow-up in 72 hours if the COI isn’t received, a daily reminder if anything is still outstanding after five business days.

The messages are specific: not “please complete your onboarding” but “we’re still missing your certificate of insurance — please send the current COI with [carrier name] listed as additional insured.” The specificity is what makes carriers respond. A generic reminder goes in the same pile as every other generic reminder.

The operations coordinator sees a dashboard, not an inbox. She can see, at a glance, which carriers are fully onboarded, which are pending one item, and which have been sitting for more than a week. She can click into any carrier’s record and see which documents are on file and which are outstanding. She doesn’t have to remember who she followed up with yesterday — the system tracks it.

New carriers don’t run loads until their packet is complete. That’s a policy decision, not a technology one, but the technology makes the policy enforceable. If the packet isn’t complete, the carrier doesn’t appear on the available-carrier list for load assignment. The rule is automatic.

Compliance touchpoints that have to stay

Two things in this workflow require a human decision, and the system should be designed to surface them clearly rather than paper over them.

The first is COI review. The parser can confirm that a COI was received and that it’s dated within the coverage period. It cannot confirm that the coverage limits meet the broker’s or shipper’s requirements for a specific load type, or that the additional insured language is exactly what it needs to be. That review belongs to the operations manager or a compliance coordinator. What the system does is flag the COI as received and route it to the reviewer — it doesn’t approve the carrier for load assignment until a human has confirmed the coverage.

The second is exceptions. A carrier with an expired COI who calls to explain that her insurer sent the wrong form and the corrected version is in the mail — that’s a situation that requires a human to make a judgment call about whether to extend the deadline, hold the carrier off loads, or escalate. The nag bot doesn’t handle exceptions. It surfaces them to the operations coordinator with the current document status and the carrier’s contact information.

Compliance isn’t automated. The follow-up is.

What it looks like on a busy Monday at a 50-truck operation

The weekend brought eleven new rate-cons into the inbox. At 7:30 a.m. Monday, the dispatcher opens her review queue, not her email. The eleven rate-cons have been parsed. Nine are clean — she approves them in six minutes. One has a discrepancy: the parsed rate shows $2.20 per mile but the agreed rate on the load board was $2.35. She opens the original PDF, confirms the discrepancy, calls the broker, and gets the corrected rate-con before 8 a.m. One has a stop-sequence question — the parser flagged two stops with similar addresses and asked for confirmation of the order. She confirms the order and approves.

By 8:15 a.m., all eleven loads are in the TMS. Under the previous workflow, that would have taken until 9:30, and two of the entries would have had errors.

Meanwhile, the onboarding dashboard shows four carriers with open items. One has been pending for nine days. The coordinator calls that one directly — the automated follow-ups have gone unanswered, which usually means the carrier isn’t serious. Two are pending COIs that arrived this morning. One is pending a W-9 that came in over the weekend. The coordinator reviews the two COIs, confirms the coverage, marks both carriers as load-ready.

Monday runs the same as any other day. The difference is that the ops team is making decisions rather than entering data.

For more on how Blue Sage approaches logistics operations automation for Nebraska carriers and 3PLs, see the logistics practice.