A snow removal company does not have a booking problem in the usual sense. Nobody calls on Tuesday to ask for a plow on Thursday at 10. The contract says that when snow reaches a trigger depth, you show up, and every customer with that trigger is now due at the same time.
That flips the normal scheduling question. Instead of "which slot can this crew reach," it becomes "in what order does this truck work its accounts, and how long until it gets back to the first one." The answer is decided in the off-season, when you build routes, and it is tested at 3 a.m. when the forecast is wrong.
What makes snow scheduling different
The trigger fires for everyone
Seasonal contracts usually name a trigger depth: plow at two inches, or salt at any accumulation, or clear by a set hour. When the snow crosses that line, every account sharing the trigger becomes due together. There is no spreading the work across the week. Your capacity is whatever your trucks can cover in the hours the storm gives you.
Priority order is part of the contract
A hospital entrance, a 24-hour distribution center or a retail lot that opens at 7:00 has to be clear first. An office park closed for the weekend can wait. Most snow businesses end up with tiers: accounts that must be open by a fixed time, accounts that must be cleared during the event, and accounts that get done after the snow stops.
The tiers are not just a list. They decide the route. A truck that does its top-priority lot first and then drives 25 minutes to the next top-priority lot, past four lower-tier accounts, is making a deliberate trade. Make it on paper before the season, not in the cab.
Long storms mean loops, not stops
In a storm that lasts all night, a lot cleared at midnight is covered again by 4:00. The route is a loop, and the number that matters is loop time: how long one truck takes to work every account on its route and return to the first. If the loop takes longer than the snow takes to re-accumulate to the trigger, your first accounts are out of contract before the truck comes back around.
A worked example: how long is the loop?
This is an illustrative route. The figures are invented to show the arithmetic, so replace them with your own plow times and drives.
One plow truck has 12 commercial lots. Average plow time on site is 25 minutes. The average drive between lots is 12 minutes, and there are 12 legs to complete the loop back to the first lot.
At one truck, the first lot goes out of contract before the loop closes. Splitting into two clusters does more than halve the work: shorter legs inside a tight cluster cut the drive share as well. Run it on your own routes: (accounts × average plow minutes) + (legs × average drive minutes) = loop time. Compare that with how quickly snow reaches your trigger in a typical storm for your area.
How to schedule snow plow routes
1. Build routes around clusters, then around priority
Start with geography. Group accounts that sit close together, because the drive between them is the part of the loop you can shrink. Then check priority within each cluster. If a cluster has two "open by 6:00" accounts at opposite ends, decide which comes first and confirm the second can still be reached in time. Route planning for snow is mostly this: geography first, then the fixed-time accounts placed so they can actually be met.
2. Time every route before the first flake
Drive each route in the off-season, or at least time it from your past storms. Record plow minutes per lot and drive minutes per leg. A route that "should take about five hours" usually takes longer once you add the legs, which is the same gap between booked time and real time covered in the cost of windshield time.
3. Keep salt and plow loops separate on paper
Salt trucks and plow trucks move at different paces. A salt truck may touch an account in a few minutes; a plow may take most of an hour. If one truck does both, the route order for salting is rarely the right order for plowing. Plan them as separate loops.
4. Plan for the truck that goes down
A breakdown mid-event leaves a route uncovered. Decide in advance which neighboring route absorbs which accounts, and check what that does to the neighbor's loop time and its own top-priority deadlines.
5. Separate event work from booked work
Sidewalk shoveling, roof snow, ice calls and one-off driveways come in as individual requests. They can be booked into the gaps between events, and they are the work most likely to wreck a route if squeezed in during a storm. Treat them the way you would any emergency call: check which truck can reach it without breaking a priority deadline before you say yes.
Off-season and shoulder-season crews
Many snow businesses run landscaping or property maintenance in the warm months with the same trucks and people. The routing habits carry over. The difference is the clock: a mowing route has a week; a plow route has hours.
Where CrewLink fits, and where it doesn't
CrewLink does not watch the weather, measure snowfall or trigger dispatch when a storm crosses your contract depth. It does not track trucks by GPS.
What it does is scheduling and dispatch with the drive visible. CrewLink builds live travel time into availability, so a one-off ice call or sidewalk job is only offered in a slot a truck can physically reach, with travel computed from where the truck will actually be. On the dispatch board, drive time sits next to each job instead of being hidden inside it, so a route's legs are in front of you when you build it. It is built for companies running 5 to 50 trucks, and a walkthrough uses your own territory and service times. For the mechanics, see travel-time scheduling.
What to take away
- A trigger depth makes every matching account due at once. Capacity is what your trucks can cover in the storm, not across a week.
- Loop time = (accounts × plow minutes) + (legs × drive minutes). Compare it with how fast snow reaches your trigger.
- Build routes by cluster first, then place fixed-time accounts where they can actually be met.
- Plan salt and plow loops separately, and decide in advance who absorbs a broken-down truck's route.
- Book one-off ice and shoveling calls only into slots that don't break a priority deadline.
Common questions
How many accounts should one snow plow truck handle?
Work it backwards from loop time. Add up plow minutes for every account on the route and the drive minutes for every leg, including the return to the first account. Then compare that total with how long it takes snow in your area to re-accumulate to your contract trigger in a typical storm. If the loop is longer, the route has too many accounts or they are too spread out.
How do you prioritize snow removal accounts?
Sort accounts into tiers by what the contract promises: open by a fixed time, cleared during the event, or cleared after the snow stops. Build each route so the fixed-time accounts are reached first and in a sensible geographic order, then fill in the other tiers along the way. Check the drive between fixed-time accounts before the season, not during the storm.
Should snow removal and landscaping use the same scheduling software?
If the same crews and trucks do both, keeping one board avoids double-booking people across the seasonal switchover. The scheduling logic differs, though. Landscaping is recurring weekly routes, while snow is event-triggered loops, so make sure whatever you use lets you see the drive on each leg either way.
How do you schedule one-off snow jobs during a storm?
Hold them until you know which truck can absorb them without pushing a top-priority account past its deadline. Check where that truck will be when it finishes its current account, add the drive and the job, and see whether its remaining fixed-time accounts are still on time. If not, offer the customer a time after the event.