Commercial Snow Response Plan Checklist

A winter that goes smoothly was planned in the fall. The properties that struggle every year aren’t unlucky — they’re improvising at 4 a.m. because nobody defined the triggers, mapped the priorities, or agreed who gets the call. Use this checklist before the season to turn snow removal from a scramble into a system. It’s written for property managers and strata councils, and it works whether you self-perform or hire a contractor.

1. Walk the site before the snow

Do a physical pre-season walk in daylight, ideally with your contractor. You’re looking for the things a plow operator needs to know and the hazards that will bite in January:

• Where snow can — and can’t — be stacked (watch sightlines, drains, and landscaping).
• Catch basins and drains that must stay clear so meltwater doesn’t pond and refreeze.
• Low clearances, speed bumps, curbs, and islands that need marking before they’re buried.
• Overnight-parked vehicles and access constraints that shrink your working window.
• Anything already damaged, photographed now so it isn’t blamed on the plow later.

2. Map your priorities

Not everything gets cleared first, so decide the order before you need it. Rank zones by traffic and risk:

1. Life-safety and access first — main entrances, accessible parking and ramps, fire lanes, the primary pedestrian routes.
2. High-traffic circulation — drive lanes, loading areas, secondary walkways.
3. Everything else — overflow parking, low-use corners.

Flag the ice-prone micro-spots specifically: north-facing walks that freeze first, shaded stalls, ground below downspouts, and every slope or ramp. These get priority de-icing and pre-treatment, because that’s where falls actually happen. On the North Vancouver hillside, freeze-thaw makes these spots a recurring problem, not a one-off.

3. Define your triggers in writing

Vague triggers cause disputes at the worst possible moment. Nail down:

• Snowfall trigger: the accumulation depth that dispatches crews (commonly 2–3 cm).
• Freezing trigger: de-icing at 0°C with moisture present — including clear days with no snow, when afternoon melt refreezes by evening. The when-to-salt guide explains why this one prevents the most incidents.
• Pre-treatment trigger: anti-icing goes down ahead of a forecast storm or freeze.
• Response time: the clock from trigger to crews on-site, tiered to your opening hours.

4. Build the communication tree

When a storm hits, everyone should already know who calls whom. Write down:

• The single point of contact on your side, and their backup.
• The contractor’s dispatch line and after-hours escalation.
• Who authorizes extra work (like snow hauling after an exceptional event) and up to what limit.
• How and when residents, tenants, or staff get notified — and what they’re responsible for on their own limited common property.

One page, shared before the season, prevents the 5 a.m. round of “I thought you called them.”

5. Set your documentation standard

Documentation is both an operations tool and your liability defence. Decide up front that every event will produce:

• Time-stamped arrival and departure logs.
• Before-and-after photos of serviced areas.
• The weather data that triggered the response.
• Product type and application rate for each salting pass.
• GPS tracks showing which zones were actually serviced.

If your contractor provides this automatically — not on request — you have a defensible record without lifting a finger.

6. Questions to ask your contractor about the SLA

Before you sign, get straight answers to these. Vague responses are the warning sign:

• What are the exact trigger depths and response times, in writing?
• Is salting and pre-treatment included, or billed separately?
• What’s your equipment depth — is there a backup if a machine fails mid-storm?
• How many other properties are committed for the same storm window? Where do we sit in priority?
• What insurance limits do you carry, and will you name us as an additional insured?
• How and when do we receive service documentation?
• Is this a seasonal or per-event structure? (If you’re unsure which fits, the comparison guide helps you decide.)

Before the first storm

Run the list top to bottom by early fall: walk the site, map priorities, write the triggers, build the tree, set the documentation standard, and pin down the SLA. Award a seasonal contract (October 1 – April 30) while good contractors still have capacity — by November they’re committed.

If you’d rather hand the whole plan to someone who runs it on automatic weather-triggered dispatch, with photo-verified records, we’ll measure your site by satellite and build the response plan with you. Call (604) 990-7072 or request a quote.