Blog

How Often Should a Freight Broker Make Check Calls?

By Connor Miller, Founder and CEO, FreightScout. Last updated 8 October 2026.

Make a check call at every point where the load can go wrong: before dispatch, at pickup, in transit on a cadence set by how long the run is, and before delivery. When the truck is on pace and the tracking ping is live, the ping can stand in for the routine in-transit call, but the last check before an appointment should always be a real call.

That is the rule FreightScout runs on its own platform, word for word: "Check calls run from pickup to delivery on a cadence set by transit time. When the truck is on pace, the ping stands in for the call. The last check before an appointment is always a call. Nothing gets marked arrived or loaded off a geofence." (customer ops). The rest of this post is why that rule works, and how to run it on your own floor whether or not you use software to do it.

What is a check call, and why do brokers still make them?

A check call is the call to the driver, or to the carrier's dispatch, that tells you where your freight is and whether it is going to make the appointment. Your customer does not care how you know. They care that when they ask, you already have the answer, and that you told them about the problem before they found it.

Brokers still make them because tracking data alone does not tell you everything. A ping tells you where the truck is. It does not tell you that the driver is out of hours, that the receiver pushed the appointment, that the trailer was loaded short, or that the seal number does not match the BOL. Those come from a person saying so. That is why a good check call program is not "call everyone every two hours." It is "call when a call is the only way to learn what you need."

How often should you make check calls on a truckload?

Think about the load in stages, not on a clock.

Before dispatch. This is the call that prevents most of the bad ones later. Before the driver gets the pickup address, confirm he has the hours left to run it, that he knows the delivery appointment, that he will send trailer photos if the customer requires them, and that he has accepted tracking. FreightScout does these in that order every time: photos, then tracking, then the address (customer ops). If you do one thing differently after reading this, make it this call.

At pickup. Confirm he is loaded, and confirm the BOL matches the load before the truck rolls: the right freight, the right reference numbers, and the seal and temperature when the load has them. A wrong BOL is found days later at the receiver, which is the most expensive place to find it.

In transit. This is where most brokerages over-call. The right number depends on the run. A short same-day run might need nothing between pickup and delivery if the ping is live and on pace. A multi-day run needs a check that lands each day, timed so you learn about trouble while there is still time to fix it. Set the cadence by transit time, then let the ping replace the routine call when the truck is where it should be.

Before delivery. Always a call. Not a ping, not a text with no answer. You want a person telling you the truck will make the appointment, or telling you it will not, while you still have time to call the receiver and the customer.

After delivery. Get the POD. Delivered is not done; billed is done.

Can a tracking ping replace a check call?

Sometimes, and only for the routine in-transit checks. When the truck is on pace and the ping is fresh, calling the driver to ask where he is wastes his time and yours, and a driver who gets called every two hours stops answering. That is the case for letting the ping stand in.

But a ping is not proof of arrival. A geofence says the truck crossed a line on a map. It does not say the driver checked in, that the dock took him, or that he is loaded. FreightScout's rule here is blunt: "Nothing gets marked arrived or loaded off a geofence. The driver says so, or it didn't happen." (customer ops). That rule protects your detention claims too, because the detention clock should start on a real check-in, not on a dot on a map.

Which check calls should you never skip?

Three:

1. The call before dispatch. Hours, appointment, photos, tracking, then the address.
2. The call before an appointment. Pickup or delivery, the last check before an appointment is a call.
3. The call when the data goes quiet. A stale ping, an unplanned stop, a truck off route or behind pace, a reefer out of range. Any of those is the moment for a person on the phone, and the amount of time left decides how fast: plenty of slack can get a text, a tight clock gets a call right now, and your rep should hear about it at the same time.

What should you ask on a check call?

Keep the questions the same, in the same order, on every load, so the answers can be compared and logged without thinking:

• Where are you right now?
• Are you loaded, and does the BOL match what we sent?
• What time will you be at the receiver?
• Do you have the hours to make it?
• Anything I should know: a delay at the shipper, weather, a mechanical issue?

Ask in the driver's language. A Spanish-speaking driver should get the same call, in the same order, in Spanish, and the texts after it too. That is how FreightScout runs it (customer ops), and it is the simplest way to get a straight answer instead of a "yes, yes, fine."

Write the answer into the load in your TMS the moment you hang up. A check call that lives in someone's head did not happen.

What should happen when a check call finds a problem?

The call is only half the job. The other half is what the customer hears and when.

If the driver is late, get the reason and the new ETA, and tell the customer before they ask. If detention is coming, the customer should get a notice before detention starts, with the times and the name of the person at the dock. If the truck falls off, you need the re-cover started right away, not after the next scheduled check.

FreightScout handles this part by bringing the late driver's reason and new ETA back with the delay email to the customer already drafted, so the rep sends it with one click; the same goes for the pre-detention notice and a re-cover (customer ops). Whatever tool you use, the standard is the same: the problem and the customer email arrive together.

How do you keep check calls from eating the day?

Check calls are the clearest example of work that costs every rep the same time no matter how good they are. Your best rep and your newest rep spend the same afternoon chasing drivers. That is time your best rep is not spending on a shipper.

Three ways to get it back:

1. Cut the calls the ping already answers. On pace and fresh ping means no routine in-transit call.
2. Front-load the work. A clean dispatch call removes most of the surprise calls later.
3. Hand off the routine calls. This is where automation is now good enough to trust. FreightScout places pickup, transit, and delivery check calls, captures the POD, writes the notes back to any TMS your team already logs into, and escalates exceptions, supervised by default (check calls). Your rep handles the exception, not the routine.

If you want the details on how automated check calls work, read how freight brokers automate check calls.

What the call is, before you set a cadence, is in what an AI check call is.

FAQ

How often should a freight broker make check calls?

At every point where the load can go wrong: before dispatch, at pickup, in transit on a cadence set by transit time, and before delivery. When the truck is on pace and the ping is live, the ping can replace the routine in-transit call. The last check before an appointment should always be a call.

Can a tracking ping replace a check call?

For routine in-transit checks, yes, when the truck is on pace and the ping is fresh. It cannot replace the call before an appointment, and it is not proof of arrival or loading. A geofence is not a check-in.

What questions should you ask on a check call?

Where are you, are you loaded and does the BOL match, what time will you be at the receiver, do you have the hours, and is there anything you should know. Same questions, same order, every load, in the driver's language.

Can check calls be automated?

Yes. FreightScout places pickup, transit, and delivery check calls, captures the POD, writes notes back to any TMS your team already logs into, and escalates exceptions, supervised by default.

Book a demo: see how FreightScout runs check calls on your loads. Book a demo