How to get loads from customer emails onto DAT and Truckstop fast

A customer emails a list of loads at 7:40. When do those loads show up on DAT and Truckstop? At many broker desks, the honest answer is "when someone gets to it". Trucks get booked all day, so every hour a load waits is an hour of carriers finding other freight.

This is a practical guide to closing that gap: how to measure it, where the minutes actually go, and what's left once the typing is gone.

Measure your time to post

Before changing anything, measure. For one week, write down three times for each load:

The gap from the first column to the last is your time to post. Look at the median, and at the worst five. The worst ones usually share a cause: a PDF that had to be read by hand, a customer who sent the same sheet twice, or a morning when one broker was on the phone.

Where the minutes go

Most of the delay comes from six steps. Each has a fix.

1. Finding the email

Loads arrive in several personal inboxes, mixed with everything else. Fix: give customers one loads address, and forward it to the system that builds your board. Outlook rules and a shared mailbox make this easy, as long as IT allows the forward: Microsoft 365 blocks automatic forwarding to outside addresses by default in newer organizations (setting up Outlook).

2. Retyping the load

Every customer sends a different format: Excel sheets, PDFs, Google Sheets, HTML tables pasted into the email, or plain lines of text. Fix: read each format into the same load record automatically. SmartLoads maps columns by header, expands lines like "3 loads" into three loads, and has a super intelligence (SI) model read scanned PDFs, with checks on what it returns (how emails become board loads).

3. Cleaning the data

A load board needs a real city and state, its own equipment code and a date. Fix: normalize cities as they're imported, with a geocoder for messy ones, map equipment to each board's codes, and fill mileage from a cache before calling a mapping service.

4. Catching duplicates

Customers re-send the same sheet with one change, three times a day. Retyped by hand, that means hunting for what changed. Fix: give each load a fingerprint, so a re-sent sheet updates the loads already on the board and only the new ones are new (how the fingerprints work).

5. Reviewing every load

When nothing is trusted, a person checks everything. Fix: hold only the loads that need a person. In SmartLoads that means a city that can't be resolved, or a rate that leaves less margin than the agency's threshold. Everything else flows straight through.

6. Building the upload

The last delay is the posting itself: copying rows into each board, or building an upload file at the end of the morning. Fix: post from the board.

• Truckstop: SmartLoads posts new loads through the Truckstop API right after they're imported, during the agency's board hours. Loads that arrive overnight post when the board opens.
• DAT: DAT API access for SmartLoads is still pending, so it builds a file in the CSV format DAT accepts for bulk posting. "Not sent yet" includes only loads DAT hasn't received, so a broker exports and uploads it in under a minute, as often as new loads arrive.

What fast looks like

With the steps above automated, time to post shrinks to the time it takes the import to run, plus a DAT upload when a broker clicks it. For scale, SmartLoads sent 17,769 distinct load postings to Truckstop through the API for one agency between July 23 and September 26, 2026. Over June 3 to September 26, 2026, it generated 537 DAT upload files.

Speed also means pulling loads fast. Booked and covered loads come off Truckstop within 10 minutes, and loads a customer drops from a re-sent sheet come down when the new sheet is imported (posting cadence).

What still slows an automated desk

Automation removes the typing. A few delays remain, and it's worth knowing them:

• A customer changes its format. A new column layout can stop an import until it's mapped. SmartLoads checks imports through the morning and flags ones that fail or look wrong.
• Missing information. A load whose city won't resolve, or with no origin or destination, waits for a person. That's the right call. A wrong posting costs more than a late one.
• Rates. A rate appears on a posting only when the customer allows rates on load boards. Otherwise carriers call to ask, which is fine as long as someone answers.
• Phones. Faster posting means more calls sooner. Plan who answers them.

Checklist: email to posting

• Do all customers send loads to one address?
• Is every format read automatically into the same load record?
• Do re-sent sheets update loads instead of duplicating them?
• Are only problem loads held for review?
• Do new loads post to Truckstop without anyone clicking?
• Does the DAT file include only loads DAT hasn't seen?
• Do booked loads come down within minutes?

To see your own customer emails turned into a posted board, book a demo.

Frequently asked questions

How fast can a load go from email to Truckstop?

With SmartLoads, a new load posts to Truckstop through the API as soon as its import finishes, during the agency's board hours. Loads that arrive after hours post when the board opens.

Do we need DAT API access?

No. SmartLoads builds a DAT upload file from the board. "Not sent yet" includes only the loads DAT hasn't received, and exporting and uploading it takes under a minute.

What if a customer sends the same sheet twice?

Each load has a fingerprint, so a re-sent sheet updates the loads already on the board instead of adding copies. Loads the customer removed from the sheet come down from the board and from Truckstop.

Does SI book the loads it posts?

No. SI reads documents and SmartLoads posts loads, but a person books every load. SI never books or covers a load.