Everything below is the live system running real records from a full season of work. Nothing here is a mockup.
About 10 minutesPlowtrak runs a commercial snow and ice operation end to end: what has to be cleared, who is out clearing it, proof that it was done, and the invoice that follows.
There are two pieces. The dispatcher console is the office side — the part you can open right now. The crew app is what the operators carry in the truck; there is a note on it at the bottom.
Your username and password came separately, in the message this link arrived with — they are deliberately not printed on this page. Sign in first: every link further down opens a screen inside the console and will drop you at the login page until you have.
Each stop says what to do and what it is meant to demonstrate. Skipping ahead is fine, but the order builds — a route becomes a trip, a trip becomes proof, proof becomes an invoice.
This is the screen a dispatcher leaves open all night. Trucks appear on the map as they report position, and the numbers across the top — trips running, sites done, sites skipped, texts sent, material spread — move on their own as the night goes.
When a storm is open, a blue band across the top names it and counts how many routes have been dispatched. Tap a truck to follow it. The map has a satellite view if you want to see what a lot actually looks like.
Open any route from the list. A route is one truck's run: an ordered list of stops, the map of the drive, the operator and vehicle it normally goes to, and what the season is worth in revenue.
Stops can be dragged into a different order, and Optimize re-sequences them. When a storm hits, Start trip as… sends that route to an operator.
Open a completed trip. You get the full record of that run: every stop in order, when the truck arrived and left, how long it sat there, what was done, and photos the operator took on site. Anything skipped carries the operator's reason.
The Trail panel draws the GPS track of the whole run on a map.
Open a customer, then one of their sites. The site is where the operational detail lives: the geofence that decides automatically when a truck has arrived, the priority (a medical clinic is zero-tolerance, a warehouse is not), and the instructions the operator sees on their screen when they pull in.
Open an invoice. Each line traces back to visits that actually happened, priced off that customer's contract — seasonal flat rate, per push, per inch banded by snowfall, per event, or time and materials. HST is applied, and the customer gets a link to pay online.
The operator scorecard compares crews across a period. Materials by site shows where the salt went. The SMS log is every message sent to a customer, and whether it landed.
From here you can also pull a proof of service sheet for a single site — every visit in the period with times and photos, formatted to print and send.
Every storm of the season, what it cost to service, and one button to invoice all of it.
The five pricing models side by side, with the renewal dates they run on.
Trucks and tractors, and the staff accounts attached to them.
Company profile, tax numbers, storm automation, the customer text templates, and an audit log of who changed what. Read-only on your account.
Operators don't touch the console. They run a separate app on a phone or tablet mounted in the cab, built for cold hands and a moving truck: large buttons, one stop at a time.
It works with no signal. Everything the operator does is queued on the device and syncs the moment the truck is back in coverage — which matters, because the worst roads are usually the ones without bars.
Worth knowing: this is the one piece you can't open from this link. The app is complete and its Android build is configured; producing the first installable build is the remaining step.