Every storm runs on one clear board.
When the snow starts, every site needs a crew, a route, and proof. This lines them up, flags what is missing, and assembles the service proof for your approval. Your ops lead still owns dispatch.
A working sample you can click through. No signup, nothing to install.
Snowed overnight, need the lot plowed and salted before tenants get in at 8. Sidewalks too. Usual spot for the truck.
Your ops lead approves the dispatch and the crew call.
You know this morning.
- 11:52 PM
The trigger hits every account at once
5 cm and climbing. Every serviced site goes live at the same time, and they all want the same trucks.
- 2:10 AM
A crew stalls at the gate
The gate code is in last winter's email thread. The truck idles at the curb while someone scrolls for it.
- 9:30 AM
The invoice waits on proof
Before and after photos on two phones, the salt log on paper, the signed ticket in a cab somewhere.
Service you cannot prove is service that did not happen. In a slip-and-fall dispute, that is usually how it gets decided.
Why the proof packet exists: time-stamped logs, photos, and the signed ticket, in one place.
The scramble becomes a board.
whats the gate code for glenway??
Maple Ridge property manager
did anyone get before photos at northgate
- STM-2001Maple Ridge Business ParkNew
- STM-2002Glenway CondominiumsMissing details
- STM-2003Northgate Retail PlazaOps lead review
- STM-2006Brookfield Office CampusService-ready
Access, route, crew, and equipment checked per site. Gaps flagged before trucks roll.
STM-2006 in the live demo. Sample data.
From trigger to invoice-ready, one clean path.
- 01Storm start
Trigger
When a storm meets the trigger, every serviced site opens in one board, timed and sorted.
Sample data in this demo. Your accounts stay yours.
- 02Minutes in
Readiness
Site access, route, crew, and equipment are checked against what the service needs. Gaps are surfaced and labeled.
The system flags gaps. It never guesses site access.
- 03Before trucks roll
Clarification
When access or priority is unclear, a short question to the site is drafted for you.
Routine updates run under your rules. Unclear sites wait on your ops lead.
- 04By morning
Service-proof packet
Before and after, salt logs, and the signed ticket come together in one invoice-ready packet.
Your ops lead owns dispatch, safety, and billing.
Watch one site go from trigger to invoice-ready.
This is the real board on sample storm tickets. Open a site, check readiness, approve a clarification, and see the proof packet come together. It runs entirely in your browser.
Your ops lead decides. The rest, answered up front.
You set how far it runs on its own. Out of the box, site updates go out under your rules and every dispatch waits for your ops lead; safety issues and claim language always stop and wait, at any setting. The board handles the tracking around the storm so your team spends its time on the calls that matter.
Who approves a dispatch?
Your call, and it is a setting. Default: your ops lead confirms every dispatch. Some operators let routine routes confirm themselves once they trust it. Safety flags and claims always wait for a person, at every setting.
Do we change how we run storms?
No. Your routes, your crews, your accounts. This organizes readiness and proof around what you already run.
What does it cost?
A flat diagnostic first, then a flat monthly rate through the season if the numbers make sense. If your operation does not need this, we will say so.
When does setup happen?
On our time, before the season, never during a storm. Nothing changes until your ops lead has seen the board run.
Is any of this demo real?
No. Every site, account, and file is made up, and nothing you click is stored.
An operations diagnostic, then a plan.
We map how a storm moves through your operation, show where dispatch and proof stall, and lay out what a managed board would change for your ops lead. One focused session, and you keep everything we produce.
- 01
Walk us through your last storm
How the night actually went, trigger to invoice. Plain talk, no forms.
- 02
See the managed version
Your kind of sites, running on the board you just watched.
- 03
Leave with next steps
What we would fix first and what it costs. Yours either way.
The call is 20 minutes. Bring how your last storm actually went. No prep beyond that.
No sales pressure. If it is not a fit, we will tell you.
You talk to the people who build and run this. No sales team.
Prefer email? contact@teamdct.ca
The calendar loads right here.