SnowBossPro Blog — Snow Removal Scheduling

Setting Trigger Thresholds That Launch Your Schedule

Ask ten snow contractors when a lot needs plowing and you will get ten different answers, because the honest answer is “it depends on the account.” A hospital entrance needs clearing at an inch; a rural storage yard can wait for four. Those numbers are trigger thresholds, and they are the settings that decide when your schedule fires. Set them well and snow removal scheduling software launches the right work at the right moment without anyone watching the sky. Set them poorly and you either over-service and burn margin or under-service and miss windows. This post covers how to set trigger thresholds that make your schedule run itself.

What a Trigger Threshold Is

A trigger threshold is the accumulation depth at which a specific account becomes due for service. When snow at that site reaches the threshold, the system flags the account and queues it into the active storm for a push. It is the bridge between weather and work — the rule that turns “it is snowing” into “these particular lots need a crew right now.” Without thresholds, someone has to keep deciding by feel when each account is ready, which is exactly the manual judgment that breaks down at 4 a.m. across dozens of sites.

The power of thresholds is that they are per-account. Your whole book does not fire at once at some blanket depth; each site triggers on its own number based on its contract, its traffic, and its risk. That granularity is what lets one schedule serve a hospital and a storage yard correctly in the same storm.

Setting Thresholds by Account Type

Thresholds should map to the obligations and realities of each account. High-traffic, high-liability sites — medical entrances, grocery lots, buildings with elderly tenants — get low thresholds because the cost of snow sitting there is high. Their contracts usually demand it, and the safety exposure justifies more frequent pushes. Lower-traffic sites — back lots, seasonal storage, low-use commercial yards — get higher thresholds because clearing them at every inch would waste crew time and equipment for no real benefit.

You set these once, in the fall, as part of each account's profile alongside its service window, billing method, property notes, and gate codes. When you press ‘Start a Storm’ and draw the circle over the region getting hit, every account inside enters the storm queue already carrying its threshold. The software knows which lots trip at one inch and which wait for four, so the storm intensifies the schedule account by account exactly as designed.

How Thresholds Drive the Push Cycle

Thresholds do not fire once and stop — they govern the whole rhythm of a storm. Each time accumulation at an account crosses its threshold, weather triggers flag it and it re-enters the push queue. In a light event a low-threshold site might trip once or twice while a high-threshold site never triggers at all. In a heavy event the same low-threshold account trips repeatedly, generating push after push, each logged with its snow depth at the time of service. This is how the schedule automatically scales its own intensity to the storm: the thresholds decide, cycle by cycle, which accounts are due.

Because every push logs a depth, you also build a record of exactly when each account crossed its threshold and got serviced. That depth history drives per-inch billing and gives you the evidence trail if a client ever disputes whether their trigger was actually met.

Thresholds Running 24/7

The real value of trigger thresholds shows up overnight. Snow removal is a 24/7 business during an active storm, and the small hours are when accumulation is heaviest and human attention is thinnest. Thresholds do not sleep. A two-inch trigger that trips at 4 a.m. lights the account up on the live dispatch board and queues it for a push without a dispatcher watching a snow gauge. Your on-call crew reacts to a prioritized worklist that the thresholds built automatically, instead of someone guessing when it is “probably time” to send trucks out.

This is what lets a lean office run a large operation through the night. The thresholds are the always-on judgment layer, surfacing exactly which accounts need service the moment they cross their line.

Thresholds and Priority Sequencing Together

Thresholds decide whether an account is due; priority sequencing decides the order in which due accounts get cleared. The two work together. When several accounts trip their thresholds at once, priority sequencing floats the deadline-sensitive sites to the top of the route so the tightest service windows get met first. The dispatch board shows every triggered account and its status, and automated SMS notifies each client off the schedule as their site is pushed — so a triggered account moves from “due” to “serviced” to “client notified” without manual steps in between.

Tuning Thresholds Over the Season

Your first-season thresholds are educated guesses; your logged depth data turns them into calibrated numbers. If an account keeps triggering too aggressively and generating pushes the client questions, raise its threshold. If a site keeps drawing complaints for snow sitting too long, lower it. Because every push and depth is recorded against each account, you have the history to tune thresholds with evidence rather than argument. Over a few storms your thresholds converge on the exact depths that keep each client satisfied at the lowest crew cost.

Trigger thresholds are ultimately the settings that let auto-dispatch run without a human watching the weather — they are what fires the schedule in the first place. Once thresholds are launching your storms cleanly, the natural next step is making sure every push they generate is captured and accounted for, which is exactly what Auto-Dispatch: Scheduling Crews Without Manual Calls leads into on the deployment side.