The storm is over. Now prove it.
Every finished storm is captured as a durable replay — no GPS trail to dig through, kept forever. How a rewind becomes litigation-grade proof, a planning tool, and the best marketing you didn’t have to make.
The storm ends around nine in the morning. By noon the crew is asleep, the machines are back in the yard, and the only record of the night is scattered — text threads, radio memory, timestamps spread across a dozen screens. Three months later an adjuster asks what happened at one address at 4:12 a.m., and you are reconstructing a storm from fragments.
That reconstruction problem is why every finished storm in Snowmass captures itself. When a run wraps, the whole night is kept as a durable replay — the storm's own timeline of stops, statuses, claims, and reassignments. No GPS trail to store or dig through, kept forever. One artifact answers three very different questions: what happened, what should we change, and what do we show the world.
Rewind: a storm you can play back
Rewind rebuilds the night from its operational timeline, not from raw breadcrumbs. That distinction matters. GPS pings are transient by design — they are pruned within days, as they should be. The replay does not need them, because every stop's lifecycle is the record: when it was claimed, by which machine, when the crew arrived, when it cleared, when it was re-queued. Scrub the timeline and you watch the fleet drain the map exactly as it happened — three weeks or three years later.
For a liability claim, that is the difference between an argument and an exhibit. Not one photo, not one operator's recollection — the entire storm, replayable, with the disputed property in context: what was happening around it, which machine was inbound, and when it actually cleared.
Why did that stop move?
A swarm reassigns work mid-storm — that is the point. It is also the part that used to be invisible. Rewind keeps a record of every reassignment the engine made and shows the reason next to it: a machine went down and its stops flowed back to the pool, a claim expired after silence, a dispatcher reserved the property for someone else. "Why did stop 41 move from vehicle 3 to vehicle 5" stops being a mystery and becomes a line item.
A replay that shows what happened is a record. A replay that shows why is an audit.
The stops that fought back
Every storm has them. Rewind surfaces the squeaky stops — the ones that needed a second pass, got reassigned mid-storm, or took far longer than their peers to clear. That short list is operationally dense: it is your renegotiation candidates, your training conversations, and your "maybe that entrance needs a marker" list, extracted from the night automatically instead of surviving only in an operator's memory.
What if we had run it differently?
Because the replay holds the storm's real stops, you can re-run them against a different plan: a different starting direction, one more vehicle, one fewer. The what-if runs through the actual dispatch engine, not a spreadsheet model, and you watch the alternative night play out on the same properties you actually serviced.
The honest framing: a what-if is advisory. It runs at a synthetic pace — it cannot know that one driveway had a stuck car in it or that the snow turned to concrete at 2 a.m. It will not tell you what would have happened; it tells you what the engine would have done, which is exactly the signal you want when deciding whether next season needs a fifth machine.
The Storm Reel
The same capture has one more life: a Storm Reel — a stylized, watermarked replay of the night, published as a public link anyone can watch. It is the rare piece of marketing that costs nothing to produce, because it is operational exhaust: a real fleet clearing a real storm, start to finish.
One toggle anonymizes it for public sharing — company name, customer details, addresses, and even the map's streets are stripped, leaving just the shape of a storm being cleared. The squeaky stops appear only as counts, never addresses. And the link is yours: turn it off and it is gone.
Key takeaways
- Every finished storm is captured automatically as a durable replay — built from the operational timeline, not GPS, and kept forever.
- The replay is litigation-grade context: the disputed property, the fleet around it, and the reason behind every mid-storm reassignment.
- What-if re-runs put the storm's real stops through the real engine with a different direction or vehicle count — advisory by design, and exactly the right input for staffing decisions.
- The Storm Reel turns the same record into shareable, watermarked marketing — with a one-toggle anonymize mode that strips names, addresses, and streets for public posting.
Frequently asked questions
- What exactly is captured when a storm ends?
- The storm's own operational timeline: every stop's lifecycle — claimed, arrived, cleared, re-queued — plus every mid-storm reassignment and the reason behind it. The replay is rebuilt from that record, so it needs no raw GPS trail and is kept forever.
- Are the what-if re-runs a prediction of what would have happened?
- No — they are advisory by design. A what-if puts the storm's real stops through the real dispatch engine with a different starting direction or vehicle count, at a synthetic pace. It shows what the engine would have done, which is the right input for staffing and planning decisions, not a promise about outcomes.
- Is a Storm Reel safe to share publicly?
- Yes, with the anonymize toggle on: the reel strips your company name, customer details, addresses, and even the map's streets, and squeaky stops appear only as counts. The link is watermarked and revocable — turn it off and access ends immediately.