Commercial Snow Removal Contracts: Seasonal vs Per-Event

A commercial snow removal contract is really two documents in one: a pricing agreement and a liability shield, and it is easy to negotiate the first while barely reading the second. The pricing question — seasonal flat rate versus per-event versus per-inch — gets all the attention because it’s the number on the budget line. But when a slip-and-fall claim lands long after the storm, nobody asks what you paid per push. They ask what the contract required, when the crews arrived, and whether you can prove it.

The structure question matters in the DMV because Washington-area winters are wildly inconsistent. A seasonal contract that looks brilliant after a Snowmageddon-class winter looks like money burned after a winter with one plowable event. A per-event contract does the opposite. Picking a structure is really deciding who carries the weather risk — you or the contractor — and what you’ll pay for the privilege.

This guide walks through the four standard contract structures and where each fits, how risk and slip-and-fall liability documentation should work, what a proper site scope map includes, and why we suggest signing by early October, not at the first forecast.

What are the main types of commercial snow removal contracts?

There are four standard structures — seasonal fixed price, per-event, per-inch, and time & materials — and they differ mainly in who absorbs snowfall variability. Seasonal contracts put weather risk on the contractor for a predictable premium; per-event and per-inch put it on you; T&M is a meter running with no cap.

Seasonal (fixed price). One flat fee for the winter, which the contract may spread over equal monthly installments, covering unlimited service within the defined scope. You get a fixed budget line and the contractor is incentivized to work efficiently. The tradeoff: in a light winter you overpay relative to work performed, and the contractor is quietly hoping it never snows. Multi-year seasonal deals smooth the variance for both sides, and some carry snowfall caps — read those carefully, because a “seasonal” contract with, for example, a 20-inch cap is a hybrid, not a flat rate.

Per-event. A set price each time snowfall crosses the trigger depth the contract names (for example, 1 or 2 inches), sometimes tiered by storm size — for example, one price for 1–4“, another for 4–8“, and so on. You pay only when it snows; the contractor gets paid fairly per mobilization. Watch the definition of “event”: a 30-hour storm with two full clearing cycles may legitimately bill as two services, and the contract should say exactly how that’s counted. Ice-only events and de-icing applications may be separate line items; the contract should say which.

Per-inch (per-push). Pricing scales with measured accumulation in depth bands, sometimes structured per plowing pass. It tracks actual work most precisely, but it lives or dies on measurement: the contract must name the measurement source — a specific National Weather Service station or another named, checkable source, not “contractor’s estimate.”

Time & materials. Hourly rates for equipment and labor plus materials at cost-plus. It’s transparent and appropriate for unusual sites or as an overflow mechanism for blizzard conditions beyond a base contract, but as a primary structure it gives you zero budget certainty and rewards slow work. If you use T&M, require equipment-level hourly rates in writing and per-application salt pricing.

Which fits which owner: seasonal suits properties that need budget certainty and low tolerance for negotiation mid-storm. Per-event or per-inch suits owners who can absorb variance and want to pay for actual weather. Some owners blend them: seasonal for sidewalks and de-icing (the liability-critical work), per-inch for lot plowing.

Why does DMV snowfall variability change the math?

Because Washington-area snowfall swings so widely from one season to the next, the “average winter” you’d price against seldom happens. The Reagan National normal is misleading precisely because actual seasons swing from nearly nothing to historic multi-blizzard winters.

Seasonal snowfall in the National Weather Service’s Washington, D.C. (Reagan National) snowfall record (opens in a new tab) has ranged from 0.1 inches (1972–73 and 1997–98) to 56.1 inches (2009–10), against a 1991–2020 normal of 13.7 inches. In the 30 seasons from 1995–96 through 2024–25, eight brought less than 5 inches, five brought more than 20, and only seven landed within 3 inches of the normal. In a market where a season can deliver four times the normal or effectively none of it, the contract structure is the risk decision.

Run the comparison honestly: price a seasonal quote against your per-event alternative across three scenarios taken from that record — a light winter like 2020–21 (5.4 inches), a near-normal one like 2024–25 (14.9 inches), and a heavy one like 2002–03 (40.4 inches) — and see where the crossover sits. Expect the seasonal premium to pay off only in the heavier winters, and treat that as the point: you’re buying insurance against the heavy year, not beating the average. Also remember that DMV winters bring freezing rain and refreeze events, which generate de-icing applications that never register as “snowfall.” That is exactly why per-inch contracts here need robust ice-event language.

The same variability argument applies to the contractor’s side: a firm that loads its routes with seasonal contracts after light winters can be overwhelmed in a heavy one. Ask any bidder how many route-hours of capacity they hold against contracted properties. A great price from an overcommitted contractor is worthless during the region-wide storm when every client needs them simultaneously.

Who carries the liability, and what documentation protects you?

The property owner owes visitors a duty of care, and hiring a contractor delegates the work — not necessarily the duty. In Virginia, the Supreme Court held in Amos v. NationsBank (1998) (opens in a new tab) that a business owes invitees ordinary care to keep its premises reasonably safe, but may wait until a storm ends, and a reasonable time after it, before removing ice and snow; DC and Maryland courts apply their own rules. Sidewalk codes also keep the owner in the frame: DC fines the owner even when clearing was delegated in writing (D.C. Code § 9-606 (opens in a new tab)). So claims turn less on whether it was slippery and more on whether the response was reasonable and provable, which makes the documentation clause the most valuable paragraph in the contract.

What a defensible setup includes:

• Defined service levels in writing. Trigger depth, response time (illustrative targets: mobilize within an hour of trigger; lots passable by 6 a.m.), and continuous-service standards during prolonged storms. Vague contracts (“keep property clear”) create arguable negligence in both directions.
• Timestamped service records. Crew arrival and departure times, areas serviced, materials and quantities applied, surface conditions — ideally with GPS-stamped equipment logs and photos. When a claimant alleges an untreated sidewalk at 7:15 a.m., a log showing de-icer applied at 5:40 with photos is the core of the defense. Keep them at least through the personal-injury filing period: two years in Virginia (Va. Code § 8.01-243 (opens in a new tab)) and three years in DC (D.C. Code § 12-301 (opens in a new tab)) and Maryland (Md. Code, Courts and Judicial Proceedings § 5-101 (opens in a new tab)), or longer if your attorney or insurer advises.
• Insurance verification. General liability that covers snow and ice operations (ask the contractor’s broker to confirm the policy has no snow-removal exclusion), auto, workers’ comp, and an additional-insured endorsement naming ownership. Verify certificates before the season, not after an incident.
• Indemnification that matches the scope. Contractors should reasonably indemnify for their own negligence within contracted areas and times; be skeptical of both directions of overreach — contractors demanding blanket hold-harmless for their own work, and owners demanding the contractor absorb liability for decisions the owner controls (like refusing a recommended service).
• A refreeze and monitoring plan. Meltwater that refreezes overnight can make a “finished” site dangerous again. The contract should address post-storm monitoring visits, not just the storm itself.

None of this is legal advice — your attorney and insurer should review the indemnity and insurance language. But operationally, the rule is simple: if it wasn’t documented, it didn’t happen, and the vendor’s record-keeping system deserves as much scrutiny as their price sheet. This documentation should feed the same system as the rest of your emergency preparedness plan, so storm response isn’t a separate paper trail.

What should a good snow removal scope map include?

A site-specific map marking every surface, priority, and hazard — created during a pre-season walkthrough, attached to the contract as an exhibit, and given to the actual plow operators. It turns the walkthrough into information a night-shift operator can use, even one who has never seen the property in daylight.

The map and accompanying scope should mark:

• Priority zones and sequence. Main entrances, ADA ramps and accessible parking, fire lanes, loading docks — what gets cleared first, second, third.
• Snow stacking locations. Where piles go, and critically where they must not: not blocking hydrants, drains, sightlines at exits, or accessible spaces (the ADA rule at 28 CFR 36.211 (opens in a new tab) requires a public accommodation to keep its accessible features in operable working condition), and not uphill of walkways where melt will sheet across and refreeze.
• Surface-specific treatment. Which walkway materials get which de-icer (new concrete, pavers, garage decks and metal stairs can each need a different product; ask the installer or manufacturer what each tolerates), plus any turf or planting beds to protect from splash and piles.
• Hidden hazards. Curbs, speed bumps, bollards, catch basins, and irrigation heads that vanish under a few inches of snow and cost real money when a plow finds them.
• Drainage paths. Where meltwater travels, so crews treat the refreeze zones rather than just the snow.
• Access and staging. Gate codes, height restrictions for equipment, on-site salt storage location if any.
• Jurisdictional obligations. As of October 2026, D.C. Code § 9-601 (opens in a new tab) requires owners to clear abutting public sidewalks within the first 8 hours of daylight after snow or sleet stops (the commercial fine under § 9-606 is $150). Montgomery County (opens in a new tab) allows 24 hours after the precipitation ends, and the City of Alexandria (opens in a new tab) allows 24 to 72 hours depending on the storm level. Other localities set their own rules. The map should mark which frontages carry municipal clearing duties.

If a bidder is willing to price your property without walking it, that tells you how the site will be serviced at 3 a.m. in a whiteout.

When should you sign a snow removal contract?

We suggest signing by early October. Contractors plan routes, equipment, and salt purchases in the fall, and capacity goes to the contracts already signed. By the time the first flakes are in the forecast, good contractors may be full, and what’s left can be leftover capacity at storm pricing with no site walk and no scope map.

Signing early buys you concrete advantages: the pre-season site walkthrough happens on dry pavement where hazards are visible; your property gets a real slot in a route plan rather than an overflow position; salt supply is reserved ahead of the shortages that can follow a run of major storms; and pre-treatment (brine before the first event) is actually available, because it requires the contractor to already know your site. It also aligns with everything else on the fall list — snow contracts should close alongside the rest of your winter building preparation checklist, not after it.

A sensible calendar: solicit bids in August, walk sites in September, sign by early October, and hold a pre-season kickoff in early November to confirm the scope map, communication protocol, and who calls whom when the trigger depth hits at midnight. At Levaru, commercial snow removal is planned on exactly that cycle for the buildings we operate — because the winters you remember in this region are never the average ones, and the contract you sign in a calm September is always better than the one you sign in a snowy January.

Frequently asked questions

Is a seasonal or per-event snow removal contract cheaper?

Over any single winter, whichever structure matches the weather wins: per-event is cheaper in light winters, seasonal wins in heavy ones. Over many winters, expect the gap to narrow, because a contractor prices a seasonal deal from the same snowfall history you’re betting against, plus a margin for carrying the risk. Choose based on budget certainty and risk tolerance, not on a prediction — if a surprise heavy-winter bill would hurt, buy the seasonal contract and treat the premium as insurance.

What trigger depth should a commercial snow contract use?

It is a business choice, set in the contract. A lower trigger (for example, 1 inch) means earlier service and more billed events, which suits busy, liability-sensitive properties; a higher one (for example, 2 inches) costs less but leaves more snow down for longer. More important than the number is automatic mobilization: crews roll when the trigger hits without waiting for your phone call. Ice events need their own trigger language, since freezing rain can make a property dangerous with zero measurable snowfall.

Does hiring a snow contractor transfer slip-and-fall liability away from the property owner?

Not by itself. In Virginia, an owner owes invitees ordinary care to keep the premises reasonably safe (Amos v. NationsBank, Supreme Court of Virginia, 1998), and DC’s sidewalk law keeps the fine on the owner even when clearing is delegated in writing (D.C. Code § 9-606). Well-drafted indemnification and additional-insured status shift some financial exposure, but claims are defended with service records: what the contract required, when crews performed, and what was applied. Have your attorney and insurer review the specific language, including how DC and Maryland courts treat it.

What does commercial snow removal cost in the DC area?

It varies too much by site to quote a number honestly: lot acreage, sidewalk footage, trigger depth, response times, and de-icing scope all move it, which is why credible pricing requires a site walk. Get the same scope priced both ways — seasonal and per-event tiered by storm depth — and compare across light, average, and heavy winter scenarios from the National Weather Service snowfall record.

What happens if the contractor misses a storm or shows up late?

That’s defined by the contract — which is exactly why response times and service standards must be written, not assumed. Good contracts specify remedies: service credits, the right to hire supplemental service at the contractor’s expense, and termination for repeated failure. Timestamped service logs make enforcement factual instead of a memory contest, and your own incident log during storms is worth keeping for the same reason.