What Alerts Should a YMS Send? Fewer Than You Think

What alerts should a YMS send? My answer is blunt: start from "what must interrupt a human," not from the system's default rule list. Alerts aren't better in bulk — split them into red, yellow, and gray lines, and one dispatcher can truly watch an entire yard.

Here's my verdict up front: once a YMS goes live, your dispatcher should stop staring at the screen. Screens are for the system; humans should only look at exceptions. Whether a YMS earns its keep comes down to one thing — do its alerts let you watch less and miss nothing? Get alerts right, and one dispatcher can cover a yard with a couple hundred trailers. Get them wrong, and it's 300 push notifications a day, muted by everyone on day three — which is the same as never buying the system at all.

The Verdict: Good Alerts Mean Less Screen Time

This cuts two ways. Alerts exist to save attention: interrupt you only when you must know. But plenty of yards configure them backwards — pushing every status change the system can produce, terrified of missing a single one. The result is the boy who cried wolf: the critical and the trivial arrive mixed together, and in the end nobody reads any of them.

I've seen too many yards where the YMS money was spent, every alert switched on, and dispatchers still run everything by phone and by walking the yard. The system keeps buzzing; people keep doing what they were doing. That money might as well have been set on fire. Remember: alerts exist to save your attention, not to add to your workload. A YMS that makes you busier is a failed YMS.

There's a second trap worth naming. Some teams go the other way and switch almost everything off, because "the dispatchers don't like being buzzed." Then the one alert that mattered — the reefer losing temperature at 2 a.m. — fires into the void. Too many alerts and people mute them; too few and you're flying blind. The answer was never a number. It's a classification.

Dallas, 2020: 300 Alerts a Day, Muted by Day Three

In 2020, a food distribution center in Dallas, Texas went live with a YMS. IT took the easy path and switched on all 40-plus out-of-the-box alert rules: one push when a truck entered, one when it left, one two hours before each appointment, one when a dock door stayed occupied past 30 minutes, one every time a trailer moved spots. The dispatch supervisor's phone buzzed 300-plus times a day. On day three, the whole team muted YMS notifications. Not because they were irresponsible — the human brain can't process that density. Alert number 301 carries the same weight as alert number 1: both are noise.

The irony came two weeks later. A reefer sitting at a dock door suffered a refrigeration unit failure — four-plus hours without temperature control, a full trailer of frozen product written off. The system did fire an alert. It drowned among 300 "vehicle has exited" messages, and nobody saw it. One trailer of lost product would have paid for several YMS licenses. They spent real money on software and got sunk by "too many alerts." Tell me that's not a waste.

In 2022, a 3PL in California's Inland Empire did the opposite: six alerts, total. Trailer dwell past 3 hours, appointment no-show, dock door overstay, trailer location lost, reefer temperature excursion, abnormal gate queue. Every alert carried escalation: no acknowledgment in 10 minutes, and it went to the operations manager; another 10 minutes of silence, and it rang the on-duty phone directly. After six months, daily interruptions per dispatcher were in the single digits — and detention disputes dropped sharply. Every overstay now had a timestamp and a response attached, so when a carrier showed up waving a detention invoice, the timeline in the system ended the argument on the spot. Fewer alerts, but every single one counted.

Three Lines: Red, Yellow, Gray

The fix fits on one table. Classify first, argue about thresholds second — never the reverse:

Now the attention math: 300 alerts a day at 20 seconds a glance is 100 minutes — one person spends the whole morning just reading alerts. Cutting 40 rules down to 8 takes IT an afternoon, at near-zero cost. The payoff side of that trade is "one fewer cargo loss, a few fewer detention fights"; the cost side is "half a day of labor." That trade wins every time.

But let me state the cost first, because there is one: cutting alerts hard means telling your dispatchers to trust the reports. Plenty of veterans with ten years on the yard don't trust reports — they'd rather be buzzed. So don't do it all at once. Lock in the red line with the front line first; yellow and gray can come later. The red line protects the business. That's non-negotiable; the yellow line is about efficiency, and that's something you can negotiate with the team.

How do you set thresholds? Don't copy the vendor defaults. Work backwards from whatever hurts most at your site: if detention disputes are the pain, set the red line one hour before your detention clock starts; if you handle a lot of refrigerated freight, tighten the temperature band to what the cargo owner actually requires. Thresholds are grown, not configured — run two weeks, watch the false-alarm rate, loosen what's noisy, tighten what leaked through.

One more design point people skip: escalation is part of the alert, not an afterthought. An alert nobody acknowledges within its SLA should climb — dispatcher, then supervisor, then a phone call. If your YMS can't escalate, your red line is just a suggestion.

Counter-Intuitive: Fewer Alerts Make a YMS More Valuable

Don't judge YMS alerting by how many rules are switched on. Judge it by "how many times did it interrupt a dispatcher today?" Single digits is excellent, double digits is a warning, triple digits means the system might as well not exist. The best YMS is the one dispatchers forget about — it only taps your shoulder when something's wrong and stays quiet otherwise. A quiet system means few exceptions, and few exceptions mean a healthy yard.

Start with these five, run them two weeks, then tune: reefer temperature excursion; trailer dwell past X hours (set X at your detention clock start); appointment no-show — the truck never arrived; dock door overstay past 150% of planned load time; trailer location lost — on site but the system can't place it. Remember: alert rules are grown, not configured. Version one should aim for accuracy, not coverage.

Go check how many pushes your YMS sends a day. If it's past 20 and people still read every single one — I'd switch half of them off first. The yard won't collapse. But that one alert you're most afraid of missing? Make sure it's actually making noise.

By Lao Mi, Supply Chain Veteran (20 yrs)