Every winter contractor who grows eventually hits the same wall: more contracts than machines. The season is short, the peaks are brutal, and buying equipment that sits idle from April to November is a hard way to spend money. So you do what the whole industry does. You bring in subcontractors.
And then, some night in January, you find yourself at 3 AM with a phone in each hand, trying to work out whether the subcontractor in the northern area actually cleared the retail park, while his voicemail insists he did and the customer's photo insists he didn't.
Subcontractors are not the problem. Managing them over phone calls, text messages, and end-of-month paper is the problem. This guide covers how to run a subcontractor network that scales past the size where you personally know every driver.
Table of Contents
- Why winter operations run on subcontractors
- Onboarding: the paperwork that prevents the disputes
- Give them jobs, not phone calls
- Visibility: one map for your fleet and theirs
- Documentation that protects everyone
- Settlement: pay fast, pay fair, pay from data
- Scaling up: from five subcontractors to fifty
- Conclusion and next steps
Why Winter Operations Run on Subcontractors
Snow is the definition of peak-load business. You may need three machines in a normal week and thirty machines twice a season. Subcontractors turn that fixed cost into a variable one, and for many operators they're also the local knowledge in areas you don't drive yourself.
The trade-off is control. An employed driver runs your route, on your machine, with your app. A subcontractor has his own machines, his own habits, and often his own other customers competing for the same storm hours. Your management system has to close that control gap without adding an hour of admin per subcontractor per night.
Onboarding: the Paperwork That Prevents the Disputes
Almost every subcontractor conflict traces back to something that was never written down. Before the season, per subcontractor, get these agreed and stored:
- Area and locations. Exactly which sites are theirs, with the site details attached: where the snow goes, which gates, which surfaces, what the trigger depth is.
- Service standard. What "done" looks like, ideally as photo examples. A cleared lot means different things to different people at 4 AM.
- Rates and units. Per visit, per hour, per season? Salting priced separately from clearing? What does a call-out outside the agreement cost?
- Response expectations. How fast after dispatch, and what happens if they can't respond. Silence is the real killer; a "can't take it" ten minutes after dispatch is manageable, a no-show discovered at 6 AM is not.
- Insurance and liability. Who covers the cracked shop window and the slip-and-fall claim, and what documentation is required for either.
Field note: the best time to have an awkward conversation with a subcontractor is September. The worst is mid-storm. Every clause you settle in autumn is a phone call you don't make in January.
Give Them Jobs, Not Phone Calls
The traditional dispatch method is a call chain: forecast looks bad, you call your subcontractors one by one, they say yes or don't pick up, you keep a mental list of who's covering what. It works up to maybe five subcontractors, badly, and then it stops working at all.
The scalable version is treating subcontractors like a dispatchable resource, the same as your own crews:
- Storm triggers a dispatch for the affected areas and work types.
- Each subcontractor receives their jobs on their phone, with the site details attached, and confirms or declines in the app.
- Declines surface immediately, while there's still time to re-assign, instead of at sunrise.
- Extra requests during the night go out the same way, to whoever is nearest and active.
One dispatch action instead of thirty phone calls, and a written trail of who accepted what, when. In SnowManager's dispatch, your own drivers and your subcontractors sit in the same dispatch flow, which is the point: one storm, one plan, one screen.
Visibility: One Map for Your Fleet and Theirs
"Did the northern area get done?" should never be a question you answer by phone. When subcontractors report through the same system as your own crews, dispatch sees one live picture: which stops are done, which are in progress, which are stuck, regardless of whose logo is on the machine.
That visibility changes the conversations. Instead of accusations ("the customer says you never came"), you have facts ("you checked in at 02:14, the complaint is about the rear entrance, was it blocked?"). Most disputes stop being disputes when both sides can see the same timeline.
Documentation That Protects Everyone
In winter work, documentation isn't bureaucracy, it's the product. The customer is usually asleep while the work happens, so the evidence is the service. For subcontracted work it matters double, because you're vouching for work you didn't watch.
Minimum standard, per visit:
- Time-stamped check-in and check-out at the site.
- Photos of the result, taken in the app, attached to the job.
- Work type performed (salting, clearing, both) and any deviations noted: blocked areas, machine issues, sites skipped and why.
This trail protects three parties at once. The customer gets proof of service. The subcontractor gets proof of work for their invoice. And you get an answer, months later, when an insurance company asks exactly when the car park was last salted before someone fell.
Settlement: Pay Fast, Pay Fair, Pay From Data
Ask subcontractors what they hate about winter work and the answers cluster: unclear expectations, and slow, disputed payment. Both are fixable with the same data you're already collecting.
When every visit is logged with time, place, work type, and photos, subcontractor settlement stops being an end-of-month archaeology project:
- Their reported drives match your dispatch records, because they're the same records.
- Extra call-outs are already documented, so nobody is reconstructing 2 AM decisions from memory.
- You can generate the subcontractor's settlement and the customer's invoice from the same underlying drives, so the two always agree.
Fast, predictable settlement is also a competitive advantage. The good subcontractors have options in a busy winter. They stay with the operator whose paperwork doesn't waste their time and whose payments don't need chasing.
Scaling Up: From Five Subcontractors to Fifty
The pattern in everything above is the same: move information out of heads and phone calls, into structured jobs and records. That's what removes the ceiling. With the call-chain method, every subcontractor you add makes storms harder to run. With dispatch-based management, subcontractor number twenty costs roughly the same effort as number six: onboard them, attach them to their locations, and the system handles the nightly traffic.
That's the shift that lets a winter operation take on the contracts it used to decline, without the owner spending every storm as a human switchboard.
Conclusion and Next Steps
Subcontractors are how winter operations scale, and phone-based management is how they stop scaling. The fixes are unglamorous and effective: written onboarding, dispatch instead of call chains, shared live visibility, per-visit documentation, and settlement generated from the same data the customer invoice comes from.
If storms currently turn you into a call centre, book a demo and we'll show you how dispatch, subcontractor management and settlement work together in SnowManager. Curious about route planning too? Read our practical guide to snow removal route planning next.