How snow.ca decides what to clear
Inputs to the scheduling decision
Three inputs drive the schedule during active weather:
- Environment Canada precipitation radar — storm cells tracked in real time across Canada
- Customer accumulation thresholds — per-contract triggers (typical: 2 cm commercial, 5 cm residential plan)
- Crew availability at the nearest snow.ca depot — GPS, equipment status, last-shift end time
Decision logic
- Forecast crosses your threshold → your route is queued at the nearest depot
- Cold-weather forecast → product switch from rock salt to calcium chloride for sub –10 °C pavement
- Crew shift end approaching → route handed off to next-shift crew with documented status
What happens when a trigger fires
| Event | Time elapsed | What happens |
|---|---|---|
| 2 cm accumulation | T+0 | Property enters tier-priority dispatch queue |
| Crew assigned | T+10 min | Local depot dispatcher assigns nearest crew |
| Crew en route | T+30 min | GPS-confirmed vehicle motion toward property |
| Crew on site | T+1–4 hr | Per SLA — completion photo within 30 min |
| Photo + GPS to customer | T+1–4 hr + 30 min | Per-visit proof emailed before invoice |
Photo proof and timestamping
What every photo-proof report contains
- Five geo-tagged photos per property (entry, mid-clearing, completed driveway, completed walkway, applied salt visible on pavement)
- GPS coordinates of the vehicle at each photo timestamp
- Timestamp in UTC with second-level precision
- Crew member identification (named in dispatch record)
- Product applied (rock salt, treated salt, calcium chloride, magnesium chloride, pet-safe blend)
- Application rate (lb / 1,000 sq ft or kg total)
- Pavement condition at application (dry, wet, snow-covered, hardpack ice)
Why this matters for liability
snow.ca documentation standard has produced 0 lost defended claims on documented operations in 5+ seasons. The standard meets or exceeds documentation requirements specified by major Canadian retail, hospital, and government commercial contracts.
- 01Trigger thresholds — per-property, customizable
- 02Route optimization — minimum drive time
- 03Priority routing — healthcare and accessibility first
- 04GPS + timestamp on every photo
- 05Customer notification on clock-in and clock-out
API access for property managers
What the API exposes
Property managers running multi-property portfolios get programmatic access:
GET /api/properties/{id}/visits— all visits for a property with photo, GPS, product, rate, timing, crewGET /api/properties/{id}/active-storm— live storm-event status (queued, en route, on site, completed)POST /api/properties/{id}/trigger— manually trigger a visit (premium accounts)GET /api/billing/invoices— itemised monthly billing reportGET /api/properties/{id}/insurance-package— full claim-defence documentation package
Integration with property management systems
Pre-built integrations:
Photo proof and service records are delivered by email to property managers within 30 minutes of every completed visit — the same data is downloadable from the snow.ca cabinet for insurance audits.
Questions, answered.
How fast does snow.ca dispatch crews after a storm starts?
Auto-dispatch fires the moment the trigger threshold is crossed (typically 2 cm). Average dispatch-to-arrival time in 2025: 3.2 hours in dense urban routes, 4.8 hours in suburban routes, 6.1 hours in rural routes. Priority-tier customers (healthcare, accessibility) average 1.8 hours.
Can I customize my trigger threshold?
Yes — set anywhere from 1 cm (priority commercial) to 5 cm (lower-cost residential). Lower triggers mean more visits per season; higher triggers mean fewer but riskier service intervals. Most residential customers settle at 2 cm.
What happens if a crew can't reach my property?
The dispatch engine detects route blockages (closed roads, accidents) and reassigns to the next available crew. If no crew can reach within the SLA window, the customer is notified by SMS with an explanation and an updated ETA.
How does dispatch handle priority customers?
Healthcare, accessibility ramps, and emergency-services routes are flagged "priority" and routed first. Their trigger thresholds are often 1 cm and SLA windows under 2 hours. Premium commercial accounts can opt into priority routing.