A mountain estate can lose access before the owner notices the storm has arrived. A snow removal plan that lives only in a vendor's memory tends to clear the easiest lane first. A written priority plan fixes the route, the trigger depth, and the call sequence before the first snowfall. It also records what was cleared and what was damaged. The plan is the difference between a cleared driveway and a disputed invoice.
Key takeaways
- Map the priority route, turnarounds, and critical access points.
- Set trigger depths and call times for each storm tier.
- Record arrival, completion, scope, and equipment for every visit.
- Protect gates, drains, and landscape edges with written limits.
- Review the plan after each storm cycle and before the season.
Map the priority route and the turnarounds
Draw the driveway, the motor court, the service lane, and every turnout on a site plan. Mark the route that must open first for an ambulance, a fuel truck, or a staff vehicle. Label the gates, the culverts, and the areas where snow can be pushed without blocking a drain. A route that is not mapped will be cleared differently by each operator. The map should be shared with the vendor before the season.
Record the surface of each segment, because gravel, pavers, and heated concrete need different equipment. Note the slope and the drop at the edges, since both affect where snow can be stored. Identify the snow storage areas and the distance from the foundation and the trees. A storage area that is too close to the house can cause meltwater damage. The plan should show where the snow is allowed to go.
Mark every turnaround and the largest vehicle that must use it. Note the gate opening, the overhead clearance, and the turning radius. A plow that cannot turn around will back down the drive or damage a wall. Record the location of the mailbox, the utility pedestal, and the landscape lighting. Each is a candidate for damage if it is not on the map.
Add the access notes for the vendor, including the gate code process, the call-ahead rule, and the contact who can open the house. Note the pet and staff arrangements that affect a night visit. Record the quiet hours and any neighbour agreement about early equipment. A plan that ignores the human context will create friction even when the snow is cleared.
Define trigger depths and call times
Set a trigger depth for each road class and each area, measured at a fixed stake rather than estimated from a window. Record the stake location and who reads it. A two-inch trigger for the main route and a four-inch trigger for the motor court may be appropriate, but the numbers should match the property. The trigger should be written before the storm, not negotiated during it.
Set the call time for each tier, including the latest hour a vendor may start and the time by which the route must be open. Record the escalation contact if the vendor does not answer. A plan that says as soon as possible is not a plan. The times should reflect the owner's schedule and the staff arrival time.
Define the storm tiers by forecast, wind, and duration rather than by a single accumulation number. A long, windy storm can drift a route closed after it has been plowed. Note the wind direction that fills each segment and the drift barriers that help. The tier should tell the vendor what equipment to send and when to return. A second pass is part of the plan, not an extra.
Record the authority to close the driveway or stop work in unsafe conditions. Note the wind chill, visibility, and equipment limits that trigger a pause. A vendor should not be pushed to clear a slope when the road is ice-covered. The plan should say who makes the call and how the owner is told. Safety decisions belong in the document before the pressure arrives.
Record each visit with time and scope
Record the arrival time, the start time, and the completion time for every visit. Note the equipment and the operator, because a different blade or truck can change the result. Capture the areas cleared and the areas intentionally left. A completion time without the scope does not show what was done. The record should match the vendor's ticket and the gate log.
Note the snow depth at the start and the end, measured at the same stake. Record the temperature and the precipitation type, because rain on snow changes the surface. Add a photo of the main route and any problem area. A photo taken from the same point each visit is easier to compare. The evidence should be captured before the next storm covers it.
Record any damage, including a hit gate, a scratched vehicle, a torn edge, or a displaced marker. Note the time, the location, and the person who reported it. Photograph the damage before repair and keep the estimate with the visit record. A damage note without a photo is hard to resolve. The record should show whether the vendor accepted the claim.
Record any task that was deferred, such as a walkway, a roof edge, or a secondary path. Note the reason and the time it was completed. A deferred walkway can become the most important access point after a freeze. The plan should distinguish a priority route from a convenience area. The owner should see both in the same report.
Protect gates, drains, and landscape edges
Mark every drain, swale, and culvert before the season and record the snow storage limit around it. A plow that pushes snow over a drain can create an ice dam and a flood at the thaw. Note the markers and who checks them after each pass. The plan should show the drainage path, not only the driving path. A cleared driveway with a blocked drain is not a completed job.
Record the protection for gates, posts, and walls with physical markers and a written offset. Note the equipment that may not pass a narrow section. A gate that is hit in the dark can leave the property open for days. The plan should identify the person who checks the gate after a visit. The check is part of the service, not a separate favour.
Set limits for snow storage near trees, beds, and foundation plantings. Note the species that are sensitive to salt and the areas where salt should not be used. Record the de-icing product and the application rate. A salt-heavy plan can damage the landscape and the stone. The record should show what was applied and where.
Record the spring inspection that checks the damage from the season. Walk the route and note the ruts, the displaced markers, and the damaged edges. Compare the findings with the visit photos. A repair list should be agreed before the next season. The plan is not finished until the damage is reviewed.
Review the plan after every storm cycle
Hold a short review after each major storm and read the visit records together. Look for a route that was cleared late, a damage that repeated, or a trigger that did not work. Ask the operator what would make the next visit faster. A review held in the quiet season is less useful than one held while the detail is fresh. The output should be one or two changes.
Confirm the next season's contract, insurance, and equipment before the first forecast. Record the vendor's proof of insurance and the equipment list. Check that the named contact and the escalation number are current. A contract that is renewed without a review can carry an old assumption. The plan should be signed before the first storm, not after it.
Keep a season summary that shows the number of visits, the total depth, the damage claims, and the cost per visit. Note any month that was unusual and why. A summary is easier for the owner to read than a stack of tickets. The record should support the next budget conversation. It should also show whether the priority route actually stayed open.
Set a date to revise the map and the triggers with the owner and the vendor. Record the changes and the reason for each. A new gate, a new landscape feature, or a changed staff schedule can make the old plan wrong. The revision should be written into the document rather than left in a message. That keeps the plan usable by the next manager.