Snow Removal Trigger Depths: What They Cover, What They Miss, and Why the Industry Is Rethinking Them

Most property managers who sign a snow removal contract can quote their trigger depth from memory: two inches, maybe three. It feels like the one number in the whole agreement that actually protects them. If less than the trigger has fallen, the thinking goes, the contractor isn't obligated to show up — and neither is the liability. That assumption is exactly what a growing number of voices inside the snow and ice management industry are now pushing back on, and it's worth understanding before you renew or sign your next contract.

What a Trigger Depth Clause Actually Says

A trigger depth is the specific snow accumulation — typically measured in inches — that has to be reached before a contractor is obligated to dispatch crews. It's the mechanism that turns a snow removal agreement into something both sides can plan around: the contractor knows when they're on the clock, and the property owner knows roughly what to expect for cost and response.

Most commercial contracts set that threshold at one to three inches, with two inches being the most common starting point for parking lots and drive aisles. The trigger depth also determines how you're billed. Under a per-push contract, you pay each time the trigger is hit and crews are dispatched — a big winter costs more, a mild one costs less. Under a seasonal contract, you pay a fixed price regardless of how many times the trigger fires. Neither structure is universally better; it depends on how much budget volatility your organization can absorb in a heavy winter.

The number itself is only half the clause. A trigger depth is meaningless without also specifying how it's measured — on-site with a physical gauge, or against a nearby official weather station — and how quickly service must begin once it's confirmed. Property managers reviewing a contract for the first time often skip past this detail, then discover during a dispute that "two inches" meant something different to each side of the agreement, depending on whose measurement they were using.

What the trigger depth does not do, on its own, is describe every condition that makes a surface dangerous. That's the gap that matters.

The Gap the Trigger Depth Doesn't Cover

The Snow and Ice Management Association (SIMA) has published guidance directly challenging the idea that a fixed accumulation number should govern when service happens — particularly for ice and salt application. As SIMA contributor David Gallagher puts it, a contract that specifies "salt after one inch of snow" can leave a surface dangerously slick well before that threshold is reached, if the snow arrives mixed with freezing rain or as a light, persistent dusting. The trigger hasn't fired. The hazard already has.

SIMA's broader point is that a single accumulation number was never designed to account for the full range of winter weather — flash freezes, black ice, freezing drizzle — that create unsafe walking and driving surfaces without necessarily producing measurable snowfall. A contract built entirely around "how many inches fell" is, by SIMA's own assessment, an incomplete safety mechanism, not just an outdated pricing convention.

Why "The Contract Was Followed" Isn't a Liability Shield

This gap matters most at the exact moment nobody wants it to: after someone has already fallen. Commercial property operators have made the same observation from the operations side: liability often hinges on response time and conditions, not on whether the trigger technically fired. If a contract's response window is two hours and someone is hurt at hour three, or if the surface was hazardous before the stated trigger was reached, pointing to the letter of the contract does not resolve the underlying question of whether the property was kept reasonably safe. Claims frequently surface hours after service was completed, once conditions have changed again — which is exactly the scenario a rigid, snowfall-only trigger isn't built to anticipate.

The Industry Is Already Moving Past Rigid Triggers

This isn't a fringe opinion. SIMA's own recommendation is to move away from accumulation thresholds as the sole decision point and toward a conditions-based model — one where the contractor is authorized to act on real-time weather data, surface temperature, and forecast information, not just a ruler. The advantages SIMA lists are worth taking seriously: faster response to hazards that don't show up as "inches of snow," fewer disputes between client expectations and contract language, and — counterintuitively — lower cost, since targeted treatment based on actual conditions avoids both under-treating hazardous surfaces and over-treating ones that don't need it.

None of this means trigger depths disappear entirely. They're still useful for setting expectations and controlling cost on routine snowfall. The shift SIMA is describing is toward contracts that pair a trigger depth for plowing with separate, conditions-based authorization for ice and salt response — so the two are no longer forced through the same single threshold.

Making that shift work in practice depends on the contractor actually having the tools to justify acting before a trigger fires: real-time weather feeds, surface temperature readings, and a dispatch team watching conditions between storms rather than only during them. Without that infrastructure, "conditions-based" authorization is just a phrase in a contract with nothing behind it. It's worth asking any prospective provider how they monitor conditions between storms, not just how they respond once snow starts falling — the answer tells you whether the conditions-based language in their proposal is operational or just marketing copy.

What to Ask For Instead of a Single Trigger Number

If you're reviewing a snow removal contract this fall, a few specific additions close most of the gap described above:

• Separate salt/ice authorization language from the plowing trigger, so your contractor can treat black ice or freezing rain without waiting for a snowfall threshold that may never be reached.
• A defined monitoring cadence — how often the contractor is watching weather and surface conditions between storms, not just during them.
• A stated response-time commitment , measured from when conditions warrant action, not only from when the trigger depth is confirmed.
• Documentation requirements that capture what conditions looked like and when service occurred, so there's a record beyond "the trigger was met."
• A clear measurement standard — whether accumulation is confirmed on-site or against a named weather station, and whose measurement governs in a dispute.

How Invictus's First Responder Model Closes the Gap

That's part of why we operate the only boots-on-the-ground snow and ice management coverage spanning the I-5 corridor from Vancouver, BC through Seattle to Portland — geography that lets us stage equipment and monitor conditions across a portfolio rather than reacting one property at a time. It's also why every visit is geo-fenced and documented: not just to confirm a trigger was met, but to create a real record of what conditions looked like and when we responded to them. For property managers overseeing commercial properties in Vancouver, Seattle, or Portland, that combination of proactive, conditions-based response and documented follow-through is what a trigger depth number alone can't provide.

If your current contract only protects you when the snow happens to cooperate with the fine print, it's worth a conversation before winter arrives. You can see the full range of what we cover on our services page.

Frequently Asked Questions

What's a typical trigger depth for a commercial snow removal contract?

Most commercial contracts set the plowing trigger between one and three inches, with two inches being the most common starting point for parking lots and drive aisles. The right number for your property depends on foot traffic, liability tolerance, and how quickly conditions typically escalate at your location.

If my trigger depth hasn't been met and someone slips, am I automatically covered?

No. A trigger depth is a service and billing mechanism, not a liability shield. Ice, freezing rain, and light-but-persistent snowfall can all create hazardous conditions before a stated accumulation threshold is reached, and a property owner's duty to maintain a reasonably safe surface doesn't pause because the trigger hasn't fired.

Can a contract include both a trigger depth and conditions-based salt authorization?

Yes, and that combination is what the industry's own guidance now recommends. Keep a trigger depth for routine plowing and cost predictability, and add separate language authorizing salt or ice treatment based on real-time conditions rather than snow accumulation alone.

Should I choose per-push or seasonal billing if I set a low trigger depth?

A low trigger depth combined with per-push billing can expose you to a high number of billable visits in an active winter, since crews are dispatched more often. If you're setting a low trigger for safety reasons, a seasonal contract can offer more predictable budgeting than paying per visit.