Load Radar: Real-Time Load Alerts for Dispatchers
Good loads vanish fast. Load Radar watches your freight sources and alerts you the moment a match posts, so you move first.
Guide
Load Radar: Real-Time Load Alerts for Dispatchers
The best loads on a board do not sit there waiting for you. A clean lane at a strong rate gets posted, gets seen, and gets covered, often before a dispatcher who is mid-call ever scrolls past it. If your process is to refresh boards by hand between other tasks, you are structurally late: you only see a load when you happen to look, and the good ones are gone by the next time you check.
Load Radar is Numeo's answer to that timing problem. It is the real-time alert feature inside Load Hub that watches your freight sources in the background and pushes an alert the instant a load matching your rules appears. Instead of you polling the market, the market notifies you. This post is about that specific capability, real-time alerting, and how to set it up so the alerts are worth acting on instead of noise you learn to ignore.
Why hand-refreshing boards loses you loads
Manual searching has a built-in delay that has nothing to do with how fast you click. A dispatcher juggles check calls, rate confirmations, driver texts, and broker email all day. Load search competes with all of it for attention, so in practice you check the boards in bursts: a flurry of refreshes, then twenty minutes on something else, then back. Every gap is a window where a load you would have taken posts and gets covered without you ever seeing it.
The board itself makes this worse. Posting volume is enormous. DAT's network alone moves more than 500,000 loads a day across a marketplace of over 1.7 million trucks, and there are roughly 27,000 active brokers posting freight. The signal you actually want, a specific lane, your equipment, above your rate floor, is a thin slice of a very loud stream. Refreshing by hand means re-scanning that whole stream every time and hoping the match is still live when you spot it.
Speed matters because the cost of being late is not abstract. With truck operating costs around $2.26 per mile (ATRI's 2025 report, on 2024 data), the difference between a backhaul at your target rate and whatever you can scrape together a few hours later is real margin. The carriers feeling this most are the small ones: about 91.5% run ten trucks or fewer (ATA, 2025), which means one or two dispatchers covering everything with no slack to sit and stare at a board. Real-time alerting is how a small team competes on timing without adding headcount, especially when a dispatcher's time runs near $46,860 a year (BLS, 2023) and every hour spent scrolling is an hour not spent booking.
How Load Radar works
Load Radar inverts the model. Rather than you querying the market on a schedule, you describe the loads you want once, and the system watches continuously on your behalf. It monitors your connected freight sources in the background, and the moment a posting clears your criteria, it pushes an alert to you. The watching never pauses to take a call or answer an email, so there are no gaps in coverage between your bursts of attention.
This is deliberately narrower than unified search. Load Hub's search lets you pull from many sources at once when you sit down to actively look for freight, you ask, it answers. Load Radar is the standing-order version: you are not asking, it is telling. Search is for "what's out there right now"; Radar is for "tell me when the thing I want shows up." They share the same sources and rules, but the workflow is opposite. One is pull, the other is push, and for time-sensitive freight the push is what keeps you from being last to the load.
What you do with the alert stays entirely in your hands. An alert is a heads-up that a qualifying load just posted, not an instruction and not an automatic booking. You still open it, judge it against the rest of your day, your driver's hours, and the relationship with that broker, and then decide whether to act. Numeo negotiates with brokers primarily over email today, so the natural next step from an alert is to reach out on a load while it is still fresh, with the timing advantage of having seen it first.
Writing alert rules that actually work
An alert is only as good as the rule behind it. The failure mode on both ends is predictable: rules that are too broad bury you in pings you stop reading, and rules that are too narrow stay silent and let real loads slip by because they missed a filter by a hair. The goal is a rule specific enough that most alerts are worth a look, but loose enough that you are not filtering out loads you would happily take.
Four dimensions carry most of the weight, and it is worth being explicit about each:
- Lane. Origin and destination, scoped sensibly. A single city pair is often too tight; an origin region with a destination radius usually captures the freight you actually want without going silent.
- Equipment. Dry van, reefer, flatbed, your specific trailer type. This is the cheapest, highest-value filter, since equipment mismatches are pure noise.
- RPM floor. A minimum rate per mile below which you do not want to be interrupted. This is what keeps Radar from alerting you on freight you would never book anyway.
- Deadhead. A cap on empty miles to the pickup. Deadhead routinely runs 15 to 30% of total miles, so a load that looks fine on rate can quietly lose money once you account for the empty drive to it. Setting a deadhead ceiling keeps those out of your alerts entirely.
Here is a concrete starting point for a reefer running out of the Central Valley:
| Field | Rule | Why |
|---|---|---|
| Origin | Fresno, CA + 100 mi | Region, not one city, so you do not go silent |
| Destination | Pacific Northwest | Where your driver needs to end up |
| Equipment | Reefer | Filters out van and flatbed noise |
| RPM floor | $2.50/mi | Below your cost-plus-margin line, do not ping |
| Max deadhead | 75 mi | Empty miles that still pencil out |
Start a little tighter than feels comfortable and loosen from there. If a rule is quiet for a full day on a lane you know has freight, widen the radius or drop the RPM floor a notch. If it is firing constantly and you are dismissing most of the alerts, the floor is too low or the lane is too broad. Tune it like a thermostat over the first week, and run separate rules for genuinely different needs, one per driver, lane, or equipment type, rather than one sprawling catch-all that does none of them well.
Where alerts fit the dispatch day
The point of real-time alerting is to change when you engage with a load, not to add another screen to babysit. Done right, you are no longer scheduling "go scroll the boards" as a recurring task. The boards effectively watch themselves, and your attention only gets pulled when there is a concrete, qualifying load to act on. That frees the long stretches you used to spend scanning for the work that actually moves the needle: covering trucks, negotiating, and keeping drivers rolling.
When an alert does land, you are at the front of the line instead of the back. Because you are seeing the load close to when it posted, you can reach out to the broker while it is still uncovered and while you still have leverage on rate, rather than calling on something that has been sitting and is either gone or stale. That early position is the whole advantage. The same load, surfaced two hours later through a manual refresh, is a different and worse negotiation. This is also where Radar hands off cleanly to the rest of Load Hub: the alert tells you a match exists, and from there you move into searching the surrounding market, comparing options, and working the broker thread.
It is worth being clear about what alerting does not do, because that boundary is what keeps it trustworthy. Load Radar does not book anything, does not commit you to a rate, and does not decide that a load is right for your operation. It surfaces timely matches; you still own every judgment call about price, fit, and which brokers you want to work with. Treating alerts as fast, well-filtered tips rather than decisions is exactly the posture that makes them safe to lean on. The dispatcher who wins with Radar is not the one who reacts to every ping, but the one whose rules are tuned well enough that most pings are worth reacting to.
The takeaway
Good loads disappear because freight is a real-time market and manual searching is a part-time activity, so by the time you look, you are already behind. Load Radar closes that gap by watching your sources continuously and pinging you the moment a load that fits your lane, equipment, rate floor, and deadhead limit posts, so you are first to a fresh load instead of last to a stale one.
The leverage is almost entirely in the rules. Spend the time to make them specific enough to be useful and loose enough to stay alive, run a separate rule per real need, and tune them over the first week until most alerts earn a look. Get that right and real-time alerting stops being one more notification stream and becomes the thing that lets a small team consistently beat bigger ones to the best freight. Load Radar lives inside Load Hub if you want to set up your first rule.
Try Numeo
Ready to find better loads?
Numeo automates load search, rate negotiation, and broker emails — so you spend more time moving freight.
Explore Numeo
Related posts
Which AI Engines Recommend Trucking Software?
ChatGPT, Perplexity, Claude and Google AI Overviews all surface trucking software differently. Here is how each one decides what to recommend.
Mar 24, 2026 · 8 min read
GuidesWhy an AI Dispatcher Should Ask Before Booking a Load
Booking commits money, a driver, and a broker relationship. Here is why a one-click human approval gate is a feature, not a limitation.
Apr 16, 2026 · 8 min read
GuidesWhy a Chrome Extension Is the Right Architecture for AI Dispatch
Dispatchers live on DAT and Truckstop all day. The right place to add AI is inside those boards, not in a separate app that forces re-keying.
Mar 24, 2026 · 8 min read