Three points to carry forward
- Put public streets, private streets, lots, walks, entrances, hydrants and storage zones on one responsibility map.
- Compare response and documentation using the same operating scenarios, not unlike marketing labels.
- Ask who performs each task, what can be subcontracted and how extra work is approved and priced.
Map the boundary before issuing a scope
Park City Municipal Code distinguishes public-road clearing from private streets. The code assigns private-street snow removal to the association or other responsible entity, or to abutting owners where no entity exists. That makes the recorded road status and governing documents an essential starting point for an HOA. A road that looks public on a map can still require a private contract, and a contractor's general Park City coverage statement does not decide the legal responsibility.
Extend the responsibility map beyond roads. Label parking lanes, accessible routes, stairs, entries, loading areas, refuse access, fire hydrants, roof discharge zones and each sidewalk tier. Identify which spaces cannot be occupied by a snow pile and which can tolerate temporary stacking. This turns 'full service' into a set of observable duties and makes competing proposals easier to compare.
Write operations around real storm scenarios
Use scenarios that reflect how the site operates: an overnight storm before opening, continuous daytime snow, a holiday arrival period, a blocked parking row and a storm that consumes the designated storage capacity. For each, ask when monitoring begins, what trigger starts each task, the route priority, when repeat passes occur, and who has authority to request hauling or an additional deicing treatment.
A provider's 24/7 statement needs careful translation. BrightView publishes around-the-clock storm monitoring for commercial Park City work; other providers describe emergency or 24-hour availability. Those statements are useful evidence, but they are not automatically the same as a guaranteed arrival or completion time. Put any required response metric, communication interval and exception process in the proposed agreement.
Borrow useful questions from public procurement
Park City's snow-hauling request for proposals is not a mandatory template for private buyers, but its evaluation topics are a useful public example. It asks about functional trucks and equipment, availability and response, experience, subcontractors and pricing. An HOA or property manager can adapt those headings to the site without pretending the municipal process governs a private contract.
Ask bidders to identify primary and backup equipment, where it is staged, which work is self-performed, who dispatches crews and what happens after a breakdown. Require a price schedule for base service, additional passes, hand labor, materials, relocation and hauling. If one proposal bundles a task and another excludes it, normalize the scope before comparing totals.
Preserve an evidence trail
The provider directory separates published support from information that is not publicly specified. Use the same discipline during procurement. Keep the current proposal, site plan, insurance certificate, relevant license evidence, subcontractor list and escalation contacts together. Define the service record expected after a visit—time, task, material or exception—without claiming that any listed provider already supplies a particular reporting system.
Finally, set a review date before the season and a shorter check after the first material storm. The goal is not to grade a provider on conditions outside its control; it is to find gaps in access, storage, communication and scope while they can still be corrected. Public website evidence builds a shortlist. A property-specific operating plan is what makes the contract usable.
Source register