Built for the storm, not the office
Every capability below exists because a live dispatch engine is running underneath — grouped by where it earns its keep during a storm.
New
Point each tractor at its own side of town
Some fleets want the same equipment starting the same side of town every storm. Give each vehicle a compass bearing on a simple dial — one per service plan, with your real properties mapped right on it — and it heads that way out of the yard, then the swarm takes over. Predictable start directions, zero hand-built routes.
- Your real properties show up on the dial as dots — aim each tractor at where the work actually is, not at an abstract number.
- Snowmass flags a busy direction with no tractor pointed at it, and “Balance by workload” evens the load in one click.
- Print a one-page Storm plan for the crew — and it stays fully optional; leave it off and the swarm spreads out automatically, as always.
New this season
Prove it, plan it, share it
Every storm now leaves a durable record you can replay, re-run as a what-if, and turn into a shareable reel — plus interactive charts across every report.
Rewind any storm
Replay a finished storm from its own timeline — no GPS needed, kept forever — and re-run it with a different plan.
Share a Storm Reel
Turn a cleared storm into a watermarked, shareable animated reel — with a one-tap anonymize mode.
Reports with live charts
Interactive donut, bar, and line charts on every report, with CSV and PDF export.
The dispatch engine
Dispatch that runs itself
There are no routes to draw and no per-operator lists to assemble. Drop your properties on a map once and the swarm scores and assigns every one of them live, from the first flake to the last pass.
Dynamic swarm dispatch
Every tractor continuously claims its highest-value next property from live scoring — not a route you drew the night before. Each machine re-scores against the fleet's live positions the moment it needs its next stop, so coverage stays coordinated with no dispatcher grouping stops by geography.
More info →Atomic claiming — no double-booking
When a machine takes a property, the claim is settled in the database in a single atomic step. Two tractors can never grab the same property, even when they reach for it in the same instant — the race is decided cleanly, every time.
More info →Start-spread fan-out
On the opening move from the yard, machines prefer properties far from where their peers already headed. The fleet spreads across the perimeter instead of piling onto the same block, so coverage begins wide.
More info →Fixed start directions, per vehicle and service
Prefer the same tractor heading to the same side of town first every storm? Give each vehicle a compass bearing on a simple dial. It heads that way out of the yard on its first stop, then the swarm takes over — predictable starts without hand-built routes. Set a separate heading per service plan (a tractor can plow one direction and salt another), and it's fully optional: set a heading to use it, leave it blank for the automatic spread.
More info →Density cohesion — block sweeping
Once a machine is working a dense block, the swarm keeps it there until the block is swept rather than chasing a marginally better score across town. No ping-ponging, fewer wasted minutes between stops.
More info →Anti-steal protection
A machine won't reach in and grab a property right next to a peer already sweeping that block. Work stays with whoever is best placed to finish it, so crews don't trip over each other.
More info →Direction control
Choose how the sweep flows — outside-in, inside-out, or nearest-first — and the fleet rolls out from your depot to fill it in. You set the shape of the storm; the swarm does the rest.
More info →Real road travel times
Scoring uses real road distances and drive times from a live routing engine, not straight-line guesses. The machine that's genuinely closest by road wins the property — not the one that only looks close on a map.
More info →What-if storm simulation
Build a scenario — drop properties, pick a service plan, set vehicle count, type, and speed — run it through the real dispatch engine, then replay it frame by frame. Add a machine and see the difference before the storm, never touching live operations.
More info →Live operations
A command center for the storm
Dispatchers watch the whole fleet in real time, get warned before small problems become missed SLAs, and can step in with a single tap when human judgment should beat the algorithm.
Self-healing fleet
When a machine goes silent past its window, a background job releases its claimed properties back to the swarm automatically — the exact moment a static route would strand every downstream stop. No dispatcher re-carving routes over the radio.
More info →Plow-ridge recheck
When a crew clears a property but the road plow re-buries the entrance, the operator marks it cleared-with-issues. Snowmass holds the property through a cooldown, then re-queues it so the swarm sends someone back — tracking attempts and plow-lag along the way.
More info →A live "cleared by" time
Every active pass shows a projected all-clear time — "all clear around 5:40" — computed from the fleet's measured pace over the last half hour. A trend arrow flags a pace that's slipping or improving, and a stragglers line calls out the stops far from every vehicle.
More info →Wind-down advisory
When the fleet is ahead of the work, Snowmass says so in one sentence: release one tractor at 11:20 and you still finish on time. It names no machine and pushes no button — it hands dispatch the numbers behind a call only dispatch should make.
More info →Preview a reserve before you commit
Before you reserve a stop for a specific vehicle, hit Preview and the live scoring engine answers read-only: where the stop naturally lands in that vehicle's order, and how much sooner it clears if you force it Next. You see the ripple before you make it — nothing moves until you commit.
More info →Real-time ops dashboard
See every machine's liveness at a glance — online, at-risk, silent, paused, or offline — with per-pass progress bars and org-wide coverage. The state of the whole storm on one screen.
More info →Proactive failure alerts
Snowmass surfaces the problems that matter in seconds: a silent machine still holding work, a stranded stop with no live vehicle to take it, a stuck or wedged claim. You act before a customer ever notices.
More info →Live interactive map
Machine positions and liveness, color-coded stop statuses, geofence and lot boundaries, and a coverage view across your service area — all moving in real time.
More info →Restricted & Warning Zones
Admins draw no-go areas that operators' turn-by-turn navigation automatically routes around, and caution zones highlighted on the map for dispatch and operators — so hazards are spotted before decisions are made.
Reserve override
Reserve a pending property for a specific machine when you know something the algorithm doesn't — optionally as that machine's next stop. The swarm respects your call and re-optimizes everything else around it.
More info →Reopen without losing evidence
Reopen a completed or skipped stop when a property needs another look — the original photos, materials, and timestamps stay intact for the record.
More info →Pause and resume
An operator can pause — releasing their claims back to the swarm for coverage — while keeping their slot reserved. Resume and they rejoin the storm right where they left off.
More info →Seamless device handoff
Open a run on a fresh phone or tablet mid-storm and it silently takes control. Newest device wins, the old one goes read-only — a dead battery never means a lost run.
More info →Turn-by-turn to the next property
Every operator gets a road route to their next claimed stop from the same routing engine that scores dispatch, with a straight-line fallback when connectivity drops.
More info →Customer experience
The people paying you finally know what's happening
Most tools stop at the operator. Snowmass gives your customers a live, credible picture of their service — driven by the real dispatcher — before, during, and after every storm.
Live ETAs from the real dispatcher
Customers see a moving arrival time projected by the same swarm logic that drives real dispatch — not a static "sometime today." It updates as the fleet moves, so it stays credible.
More info →Your vehicle, promoted on the map
When a machine is en route to a customer's property, their live map promotes it — the marker grows and a calm banner counts down the minutes. If the swarm reroutes, the banner simply steps aside — no alarm, no broken promise — and returns when a vehicle is inbound again.
More info →A privacy-safe sense of progress
Customers see a percentage-only fleet pulse — "about 40% cleared" — and an approximate place in line that appears only once they're within ten stops. It's clamped to only ever count down, so a reroute never looks like losing your spot.
Authenticated customer portal
A dashboard with the live event map and ETA, full service-visit history with materials and photos, storm history, and support — scoped so a customer only ever sees their own properties.
More info →Embeddable live tracking
A live tracking view your customer can embed on their own site, showing vehicle-name-only positions with no personal data exposed.
More info →Run-log embed for your website
A white-label, org-wide log of your storm activity — every event and service pass, by season — that you drop straight into your own company website.
More info →Service-visit history
Every visit is recorded with timestamps, materials applied, and photos — a clean, defensible record when a customer asks what happened during a storm.
More info →Satisfaction ratings to public reviews
Collect a satisfaction rating when a support request is resolved; with consent, strong reviews can flow to a public feed — real social proof from real customers.
More info →Email and SMS status alerts
Pass-started, en-route ETA, and service-complete notifications reach customers by email or text in their own language, so no one is left guessing.
More info →Rehearse, rewind, replay
Prove it & plan it
Because dispatch is a real engine, every storm can be rehearsed before it lands, replayed after it clears, and pace-checked while it runs. All of it is advisory and sandboxed on throwaway copies — nothing here ever touches a live storm.
Rehearse a storm on your real book
One button runs the real dispatch engine over your current properties and fleet, on a throwaway copy, and hands you the projected storm to replay frame by frame. Rehearse in October, after winning a new neighbourhood, or any quiet afternoon — live operations are never touched.
Every storm becomes a rewind
When a pass finishes, Snowmass captures a durable replay from the service record — no GPS needed, kept forever. Scrub through the storm, read why each reassigned stop moved, then re-run it as a what-if with a different direction or vehicle count and compare.
More info →Ghost Lap pace check
Opt in, and when a storm goes active a shadow simulation launches from the same starting conditions and runs alongside it. The live-ops board shows one honest line — minutes ahead of or behind the engine's own pace — so "are we okay?" has an answer mid-storm. Advisory only.
More info →Storm Reel — share the win
Turn a cleared storm into a watermarked animated reel with a link you can share anywhere — or revoke instantly — and a short clip you can download. Anonymize is one toggle, on by default, and strips every name, address, and real coordinate — show off the storm without showing your book.
More info →Crew & communication
Mobilize the crew, then keep everyone in sync
The storm starts before the first flake. Snowmass helps you line up who's working, then keeps dispatch and operators talking all the way through.
Availability polls
Ask the crew "can you work today?" by text or email before a storm — with an in-app response surface too — and answers collect on the event's crew roster, so you know your real headcount early.
More info →Attendance confirmation
Confirm who's coming and when — "be at the shop at 7" — with quick late-by responses, so you're not guessing at mobilization.
More info →Mass stand-down
Called it off? Stand the whole crew down in one message so nobody drives in for a storm that fizzled.
More info →Two-way operator chat
Dispatchers and operators message directly, with web push to the operator's device, so a question from the field gets an answer without a phone call.
More info →One-tap fleet broadcast
Push a single message to every on-shift operator at once — a road closure, a priority account, a change in the weather — without repeating yourself.
More info →Unified message board
Every on-shift operator's thread in one place, so dispatch has the whole conversation of the storm on a single screen.
More info →Incident reporting with photos
Operators log an incident with photos from the field, and dispatch is alerted in real time — the paper trail writes itself.
More info →Material application logging
Salt, sand, or liquid applied at a property is logged and timestamped on arrival, feeding both the customer record and your reporting.
More info →Platform
Built to hold up under a storm
The unglamorous foundations that keep a live operation trustworthy — offline resilience, bilingual from day one, compliant messaging, and an append-only log of staff access and impersonation.
Winter-operations KPIs, tracked
The five metrics that tell you whether a storm went well — SLA attainment, coverage over time, idle-and-overlap, plow-lag, and properties-per-machine — on your dashboard, and charted storm-over-storm so you can see whether you're improving.
More info →Offline-ready tablet PWA
The operator app installs like a native app and keeps running when connectivity drops — buffering position locally and syncing on reconnect. (Honest limit: offline you keep logging, but new claims resume once you're back online.)
More info →Bilingual — English and Quebec French
The entire product, and every customer notification, works in English and fr-CA. Each contact hears from you in their own language.
More info →TCPA-safe messaging
Notifications respect verified consent, per-channel opt-out, and quiet hours in your organization's timezone. Overnight updates aren't dropped — they're held and delivered as a morning "while you slept" summary, so customers wake to proof their driveway was cleared without a 3 a.m. buzz.
More info →Append-only audit log
Staff access and impersonation are written to an append-only record — including who was acting on whose behalf — so privileged access always leaves a paper trail.
More info →Reports and exports
Filter your operational history and export it to CSV or PDF for billing, SLA reviews, or a customer who wants the receipts.
More info →Bulk property import
Bring your whole book of business in from a CSV, so onboarding doesn't mean adding properties one at a time.
Strict multi-tenant isolation
Every organization's data is walled off from every other's, enforced at the core of the app — not just hidden in the interface.
More info →Single sign-on across Snowmass
One sign-in carries across the Snowmass apps your team uses, so operators and dispatchers aren't juggling logins mid-storm.
More info →Passwordless sign-in
Six-digit codes and magic links replace passwords — nothing to forget, reset, or leak, and onboarding a new operator takes seconds.
More info →Side by side
Snowmass vs. manual route-building
Eight moments winter throws at every fleet — and what each approach does with them.
Getting started
Legacy static routes
Hand-build every route, property by property, with endless clicking — before the storm even starts
Snowmass swarm
Drop your properties on a map once; the fleet assigns itself from the first flake
A driver doesn't show
Legacy static routes
Their whole route is late; the dispatcher re-carves it by hand over the radio
Snowmass swarm
Their properties flow to the rest of the swarm automatically — no one re-plans
Reworking mid-storm
Legacy static routes
Every change means hand-editing a fixed list while the storm runs
Snowmass swarm
Nothing to edit — the swarm re-optimizes the whole fleet every few seconds
A machine breaks down
Legacy static routes
Downstream stops stall until someone manually re-routes them
Snowmass swarm
Its work is released and re-claimed within minutes, automatically
Add a customer mid-season
Legacy static routes
Rebuild the affected routes to fit the new property in
Snowmass swarm
Just add the property — there's no route to redraw
A plow re-buries an entrance
Legacy static routes
A static list can't even express it; the property is quietly missed
Snowmass swarm
The operator flags it and the swarm sends someone back after a cooldown
Customer experience
Legacy static routes
A live map, at best — the customer still guesses at timing
Snowmass swarm
Live ETAs from the real dispatcher, before/during/after updates, and a portal
Proof and reporting
Legacy static routes
Photos and notes, gathered and exported by hand
Snowmass swarm
Every visit, material, and incident logged automatically and exportable to CSV or PDF
Ready before the next storm
Run a simulation scaled to your fleet, or talk to the team about the season.