Understand what the two labels actually mean
A seasonal arrangement generally establishes a price for a defined term and defined group of duties. A per-event arrangement generally charges when stated event or visit conditions occur. Neither label tells you which zones are covered, what triggers work, how many passes are included or whether materials and hauling are extra. Some seasonal agreements contain accumulation caps or exceptional-event charges. Some per-event agreements separate plowing, walkways and ice into different visits. Read the definitions and pricing schedule together, because the commercial effect lives in the details rather than in the model name.
Compare risk allocation, not just the first total
Seasonal pricing can make budgeting more predictable, while per-event pricing can track service volume more directly. The trade-off depends on the exact inclusions, property complexity and winter conditions; it is not automatically resolved by choosing the lower headline number. Ask which party bears cost changes from frequent events, long-duration storms, repeat visits, drifting, freezing rain and unusually large accumulations. Then check whether the agreement caps, reclassifies or separately prices those situations. A fair comparison uses the same operating assumptions and shows how each proposal handles variation.
Give every bidder one property and zone schedule
A model comparison fails if one proposal includes entrances and walks while another prices only vehicle areas. Provide the same map, approximate areas, operating windows, priority sequence, storage plan and known constraints to everyone. Ask each bidder to state whether a zone is included, conditional, excluded or separately priced. Include loading, refuse access, fire access and after-hours entrances if they matter to operations. This structure exposes scope gaps without requiring an invented cost estimate and makes later revisions easier to track if the property or tenant pattern changes.
Test trigger and repeat-visit scenarios
Use a few written scenarios to reveal how the model behaves: overnight accumulation before opening, continuing snowfall through business hours, a wind-driven drift after plowing, freezing rain, and refreeze the next evening. Ask when the first visit is triggered, what creates another billable or included pass, how an incomplete area is revisited and who authorizes a change. These are comparison questions, not predictions. The agreement should explain the decision process without promising a particular weather outcome or continuous surface condition.
Separate ice, materials and hauling from plowing
Ice observations, material applications, loader relocation and off-site hauling can drive substantial operational differences between proposals. Identify whether each is included, capped, priced by use or subject to approval. For materials, ask what record is provided and who resolves a site restriction. For hauling, identify the loading unit, disposal or destination assumptions and authorization threshold. For ice work, define inspection points and recheck expectations. Keeping these categories separate prevents a seemingly comparable seasonal or event price from hiding different exposure to optional charges.
Define exceptional conditions before they occur
Contracts may treat a prolonged storm, large accumulation, restricted road access or unusual ice condition differently from a normal event. Ask for the actual definition, notice process, revised duties and pricing mechanism rather than accepting an undefined force-majeure or extreme-weather reference. Do not assume the City of Prince George's municipal snow-event classification governs a private agreement. Public-road conditions may affect access, but the parties must define how that information influences private-property decisions. Qualified review is appropriate where an exception affects liability, insurance or contractual rights.
Review performance with records, not memory
Choose a regular review point and the records needed to evaluate the arrangement: events, visits, zones completed, exceptions, concerns, hauling decisions and scope changes. For a per-event model, reconcile invoices to the agreed event and task definitions. For a seasonal model, confirm whether recurring gaps reflect the written priority sequence or an unclear inclusion. A review should lead to a documented correction, map update or contract amendment where needed. It should not rely on unrecorded conversations after several events have passed.
Use a quote worksheet that preserves assumptions
For each proposal, create columns for model, term, triggers, included zones, repeat visits, walkways, ice, materials, stacking, hauling, records, communications, add-ons and exclusions. Record the source page or proposal clause for each answer. Keep unresolved items visible rather than filling them with assumptions. This worksheet allows a property manager or strata council to compare the same facts, explain a recommendation and return to the decision later. Final selection still requires the organization's procurement, insurance and legal review where applicable.
The City's published snow-event definitions apply to municipal operations. Do not import them into a private seasonal or per-event agreement without an explicit property-specific definition. Compare proposals using the same private map, duties and assumptions.
City of Prince George — Snow Clearing
Sources reviewed September 22, 2026. Confirm current requirements for the exact property and proposed scope.