Snow Removal Pricing Guide: Per Event, Seasonal, or Hourly

Short answer: A snow removal pricing guide is really a guide to who carries the weather. Per-event and hourly pricing leave the risk with the customer; a seasonal flat rate moves all of it onto you. Build a seasonal number off a bad winter rather than an average one. The same 1.5-acre lot below takes 44 service hours across a 14-event season and 162 across a 31-event season — under a single price, that spread is the whole business.

Every other trade prices work it can see. Snow prices work that has not happened yet, against a forecast nobody can make in September. The three models are not three ways to write the same number; they are three different bets, and picking one without knowing which side of the bet you are on is how a company that ran fine for four winters loses a season in one February. The write-off side of the same equipment is in snow removal business expenses.

Who is actually buying the weather risk in each model?

Read the table before you read anything else on this page.

Model	Who wins in a light winter	Who wins in a heavy winter	Risk sits with
Per event, per push	Customer pays less	You bill more	Customer
Hourly	Customer pays less	You bill more	Customer
Seasonal flat	You keep the money	You eat the cost	You

That is the entire strategic question. A per-event contract cannot bankrupt you; it can only underperform. A seasonal contract can do both, in either direction, by a wide margin. Commercial property managers push hard for seasonal because they are buying budget certainty, and budget certainty is a product — one that has a price, which is the point most contractors miss when they quote seasonal at the same expected total as per-event.

Most operations run a mix: seasonal on the accounts they know cold, per-event on the ones they do not, and hourly for the loader work and the storms that break the model entirely.

How do I count events instead of inches?

Total seasonal snowfall is the wrong number. Twenty inches in four storms and twenty inches in eleven storms are the same season on paper and a completely different season on your payroll.

What you need is the count of qualifying events — snowfalls that exceed your contract trigger — over a long run of years at a station near the property. Daily snowfall records are public and free: the National Weather Service publishes local climate summaries, and NOAA’s National Centers for Environmental Information hold the daily station archives going back decades. Pull fifteen to twenty years of daily totals for a nearby station and count, for each winter, how many days exceeded your trigger depth.

You now have a distribution rather than an average, and the distribution is what you price from:

• The median year is your expected cost.
• The worst year in the record is your exposure.
• The gap between them is the risk premium a seasonal contract has to carry, or the cap you write into it.

Averaging that record into one number and pricing off it means you will be profitable roughly half the time by design. Nobody builds a business on a coin flip they cannot influence.

What does “one push” mean when 14 inches falls overnight?

It means whatever the contract says, and if the contract is silent it means whatever the customer wants it to mean.

A trigger depth of 2 in and a per-push price implies a 2 in event and a 14 in event are the same visit. They are not — a 14 in event is a plow truck that has to return two or three times during the storm so the lot never gets ahead of the equipment, and the last push moves snow that has already been driven on and refrozen.

Depth tiers fix it. A common structure prices 0 to 3 in as the base push, then 3 to 6, 6 to 9, 9 to 12, and each additional 3 in as its own step. Two rules make the tiers work:

1. Measurement is defined in the contract — a named reporting station, or a stake on the property, photographed, with a time stamp. Not “what it looked like.”
2. Returns during a continuous event are billable, with the interval stated. A twenty-hour storm is not one push and it is not four separate events either; it is one event with a stated number of service passes.

Zero-tolerance accounts — hospitals, grocery, anything open through the storm — are a separate product entirely. They are priced hourly or on a dedicated-equipment retainer, because the work is continuous and the trigger concept does not apply.

What has to be in the contract before a flake falls?

Six clauses, all of which are cheap to write in September and expensive to argue about in January.

• Trigger depth. The accumulation at which you deploy without a phone call.
• Service window. Lot cleared by a stated time, and what happens if the storm is still running at that hour.
• Priority order. Which of your accounts gets serviced first, in writing, so the 6 a.m. call has an answer.
• What is included and what is billed separately. Salt, sidewalks, stacking, hauling, and ice events with no accumulation.
• Standby. Who pays when a forecast has your crew on-site or on-call and nothing falls. On zero-tolerance accounts, someone must.
• Site conditions. Where the piles go, what the customer must move by a stated time, and who is liable for damage to unmarked curbs, sprinkler heads, and wheel stops. Stake the lot in November and photograph it.

Why does salt have to be its own line, forever?

Because consumption is set by pavement temperature and event type, not by lot size, and nobody can forecast it.

Published guidance for parking lots and sidewalks puts application rates somewhere around 2.3 lb per 1,000 sq ft at pavement temperatures near 30°F, rising toward 6.8 lb per 1,000 sq ft as the pavement drops into the upper teens. The Salt Smart application rate tables lay the ranges out by temperature and condition. Real-world practice is frequently far heavier — many property managers expect something closer to 700 lb per acre, which is roughly 16 lb per 1,000 sq ft, or three to seven times the guideline.

Two more facts push the number around before you have spread a grain:

• Rock salt stops working when it gets cold. Sodium chloride loses practical melting capacity as pavement drops toward roughly 15°F, so a cold snap forces you onto treated salt, a blend, or a different chloride at a different price per ton.
• Ice events need no snow at all. Freezing rain on a bare lot is a full salt application and zero plow hours, and a per-push contract that never mentions ice will bill nothing for it.

Sell salt by the application or by the ton applied, with the product named. Bundling it into a seasonal price is betting a commodity you do not control against a temperature you cannot predict.

What do the walks, steps, and entries cost outside the plow rate?

They are hand labor priced in crew hours, and they routinely take longer than the lot.

Nine hundred linear feet of sidewalk at 4 ft wide is 3,600 sq ft — about five percent of a 1.5-acre lot’s pavement, and often a third of the total service time. Steps, landings, handicap ramps, and entry mats are entirely manual. Ice melt on concrete walks is usually a different, less aggressive product than lot salt, because chloride damage to a customer’s entry is a claim.

Price sidewalks per visit as their own line, from your own timed rate, and never as a percentage of the lot price. The two scale on completely different variables.

Where does the snow go when the piles are full?

Into a loader bucket, and then possibly onto a truck.

Early in a season the piles go at the ends of the rows and nobody thinks about it. By the fourth heavy event those piles are hard, tall, taking up parking stalls, and blocking sight lines at the exits. At that point the work changes trade: a loader stacks and reshapes at an hourly rate, and when there is genuinely nowhere left, snow gets loaded and hauled to an approved site and billed per load or per truck hour.

Both of those belong outside every seasonal price you write. Neither is predictable, both need equipment you might have to rent, and hauling has a disposal location, a permit question, and a round-trip time that varies with where the site is.

What does the same lot cost in a light season and a heavy one?

A 1.5-acre lot — 65,340 sq ft of pavement — with 900 lf of walks, four entries with steps, a 2 in trigger, and on-site stacking areas.

	14-event season	31-event season
Qualifying events	14	31
Events over 6 in	2	7
Events over 12 in	0	2
Pushes including storm returns	16	44
Plow hours	20.8	74.8
Walk and entry crew hours	14.4	48.4
Salt applications	22	48
Salt at guideline rates	~2.8 tons	~7.7 tons
Salt at ~700 lb per acre	~8.6 tons	~18.8 tons
Loader stacking hours	0	9
Truck-and-haul loads	0	6
Total service hours	44	162

Same lot, same equipment, same crew. Nearly four times the service hours, more than double the salt applications, and an entire category of work — stacking and hauling — that simply does not exist in the light year. A seasonal price written against the light column is a gift; written against the heavy column it loses the bid to whoever wrote it against the light one.

How do I set a seasonal price that survives the heavy year?

Build from cost per service hour, then bound the downside with structure rather than optimism.

Take your own loaded cost per service hour — operator wages and burden, truck and plow, fuel, insurance, equipment reserve, and overhead. Say that lands at $110 — an illustrative figure, not a rate to import, since operator wages, insurance, and bulk salt delivered price swing widely between snow belts and marginal-snow markets. A median 20-event season on this lot runs about 75 service hours, so your expected cost is $8,250 before salt.

Then run the three outcomes against one price. To hold a 30 percent margin on the median year, divide rather than multiply: $8,250 ÷ 0.70 = $11,786. Marking up 30 percent instead gives $10,725, which is a 23.1 percent margin — the same confusion that costs money in every trade, except here it stacks on top of weather risk.

Season	Service hours	Your cost at $110/hr	Result at a $11,786 price
Light, 14 events	44	$4,840	+$6,946
Median, 20 events	75	$8,250	+$3,536
Heavy, 31 events	162	$17,820	−$6,034

One price, three outcomes, and the bad one is nearly twice the size of the good one. Four structures fix that without losing the bid:

• A cap. The flat rate covers pushes up to a stated count; pushes beyond it bill per event at a named rate. This is the single most useful clause in the trade.
• Salt excluded, billed per application or per ton applied.
• A storm carve-out. Events over a stated depth — 12 in is common — are billed as separate storm events rather than as pushes.
• Stacking and hauling excluded, billed at an hourly or per-load rate.

With those four in place, the seasonal contract sells the budget certainty the customer wants across the normal range and stops being an unlimited liability at the tail.

What has to be logged during the storm?

The record that defends a slip-and-fall claim two years later, and it cannot be reconstructed afterward.

For every service pass: arrival and departure times, accumulation at arrival, what was plowed, what was shoveled, what product was applied and how much, pavement and air temperature, and photographs of the finished lot and the walks with a time stamp. Keep the weather data for the event. Keep the signed service tickets. Claims in this trade are decided by whether contemporaneous records exist, and “we always salt the walks” is not a record.

The financial half moves in the same window and gets forgotten because everyone is asleep. Keel handles that part on the phone alone — no account, no login, no bank connection, and an App Store privacy label reading Data Not Collected. Photograph the bulk salt ticket by weight, the fuel receipts, the cutting edge you replaced in January, and the rental invoice for the loader; they are read on-device with Apple Intelligence. Log the miles between accounts as you drive them. Then invoice per event while the storm is still fresh, with your logo and a payment QR on it, instead of assembling a season’s worth of pushes from memory in April. The free tier is unlimited invoices, receipts, and mileage, and Keel Pro is a one-time $249.99 Lifetime purchase rather than a subscription. Chasing the accounts that pay in June for work done in January is in how to get paid for snow removal work, and keeping the season’s paperwork in one place is in contractor receipt organizer.

Frequently asked questions

Is seasonal or per-event snow removal pricing better for the contractor?

Per-event is safer; seasonal is more profitable when you price it correctly and structure it. Per-event revenue rises with the work, so a heavy winter cannot hurt you. Seasonal moves all the weather risk onto you in exchange for guaranteed revenue, which is worth taking only with a push cap, salt excluded, and a carve-out for storms over a stated depth.

How do I estimate how many plowable events a winter will have?

Pull fifteen to twenty years of daily snowfall records from a National Weather Service or NOAA station near the property and count, for each winter, the days that exceeded your trigger depth. That gives you a median year for pricing and a worst year for exposure. The average of total inches is not useful, because event count drives cost, not accumulation.

Should salt be included in a seasonal snow contract?

No. Application rates swing with pavement temperature — roughly 2.3 pounds per 1,000 square feet near 30°F against as much as 6.8 as the pavement drops into the upper teens — and freezing rain events use salt with no plowing at all. Bill salt per application or per ton applied, with the product named on the invoice.

What is a trigger depth and where does it belong?

It is the accumulation at which you deploy without waiting for a call, and it belongs in the contract in writing, along with how depth will be measured and by whom. Two inches is common for commercial lots; retail and medical properties often want one inch or zero tolerance. Zero-tolerance work is priced hourly or on retainer, not per push.

Why does a 12 inch storm cost more than four 3 inch events?

It usually costs more per inch, not less. A large continuous event requires return passes during the storm so the lot never gets ahead of the equipment, the last passes move snow that has been driven on and refrozen, and the piles fill up, which brings a loader and possibly hauling into a job that had neither. Depth tiers and a storm carve-out are how that gets billed.

What should I record during every snow event?

Arrival and departure times, accumulation on arrival, what was plowed and shoveled, product applied and quantity, pavement temperature, and time-stamped photographs of the cleared lot and walks. Keep the event’s weather data and the signed service ticket. Slip-and-fall claims are decided on contemporaneous records, and those cannot be reconstructed months later.

---

This article is general information, not professional or tax advice.