For seasonal-contract snow removal operators

Snow removal route and fuel records against a flat seasonal fee

You signed each client to a flat seasonal contract: one price covers the whole winter no matter how many times it snows. That fee was a bet. A mild winter is profit; a relentless one with twelve plowing events and a salt price spike can quietly turn a good contract into a loss. The only way to know which it was is to log every storm as it happens — the stops you serviced, the bags or tons of salt you spread, the fuel your truck and equipment burned — and tally those actual events against the fixed fee you already locked in. Cash Workspace gives you a free place to keep that per-storm log and the running fee-versus-actual picture in one folder per contract. This page covers exactly that: the storm event log and the seasonal reconciliation. It is not for per-push or per-visit billing, it is not a generic vehicle fuel log, and it is not for tracking the off-season storage lifecycle of your plows and spreaders — those are different jobs.

The problem

A flat fee hides whether each storm is eating your margin

With seasonal contracts, the money comes in on a schedule that has nothing to do with the weather — usually a deposit in October and installments through March. The costs, though, arrive in bursts: a single overnight storm can mean three trucks out for six hours, forty bags of bulk salt, and a tank of diesel each. If you never write down what each event actually cost, the season blurs into one big number and you cannot tell a profitable contract from a money-loser until the bank balance tells you in April — too late to re-price that client next year. Worse, when a client questions whether they got their money's worth, you have nothing but memory. A per-storm log fixes both problems: it turns the winter into a countable list of events you can total and compare against the fixed fee.

  • The flat seasonal fee is fixed in the contract, but the number of storms, the salt you spread, and the fuel you burn are not — so margin swings wildly with the weather.
  • Costs land in bursts (one bad night) while revenue arrives on a deposit-and-installment schedule, so the two never line up on their own.
  • Without a storm-by-storm log you cannot tell, mid-season, whether a contract is already over budget or still comfortably under the fee.
  • When a client asks 'what did I actually get for my money,' undocumented service visits leave you with nothing to show.
  • Next season's pricing is a guess unless you can look back at how many events each contract really took.

The reconciliation loop

Log each storm, then total it against the fee

The rhythm is simple: one record per storm per contract while it is fresh, then a running tally you glance at after each event and a final reconciliation when the season closes. Everything below is organizing your own records — it is not accounting or pricing advice, and Cash Workspace does not calculate margins or read your fuel slips for you.

  1. 1

    Set up one folder per seasonal contract

    For each client on a flat seasonal agreement, create a folder like Maplewood-HOA-2025-26-Season. Drop the signed contract in first so the agreed flat fee and the trigger depth (e.g., service at 2 inches) sit right beside the storm log. This is the boundary you will reconcile against all winter.

  2. 2

    Create a storm event record the same day you plow

    After each route, add one record named for the date — Storm-2026-01-14. Fill in the stops serviced, snowfall, hours on site, salt spread, and fuel used while it is fresh. Doing it the same day is the difference between real numbers and February guesswork.

  3. 3

    Attach the proof to each event

    Pull out your phone and attach the photos and slips: the fuel receipt, the salt or de-icer purchase receipt, and a cleared-lot photo if the client tends to ask. The receipt lives on the storm record it belongs to, so the cost and its proof never drift apart.

  4. 4

    Update the running event tally after each storm

    Keep one summary record in the folder — Season-Reconciliation — listing every storm with its salt and fuel cost. After each event, add the line and update the running total. This is your live answer to 'how much of the fee have we burned through so far.'

  5. 5

    Reconcile actual events against the flat fee at season end

    When the season closes, compare the total of all storm costs against the fixed seasonal fee for that contract. Note the result — comfortably under, near break-even, or over — and keep it as the evidence for re-pricing or renewing the contract. Export the folder if your accountant or partner wants a copy.

Record structure

What to record on each storm event

These are the fields to capture per storm, per contract. You type them in — Cash Workspace stores and organizes them; it does not extract them automatically from receipts or sync any data from your truck.

Storm date and service window
The date you ran the route and the rough start-to-finish time, e.g. 2026-01-14, 11pm–4am. This is how every event sorts and how you count total events for the season.
Stops serviced on this run
Which properties or lot sections on the contract you actually cleared this storm — useful for multi-property or HOA contracts where not every stop needs the same attention.
Snowfall / trigger met
Inches of snow or ice event type, and whether it crossed the contract's service trigger. Records why you went out (or chose not to), which matters when a client questions a billed season.
Hours and equipment on site
Total labor hours and which trucks, plows, or spreaders ran. The effort side of the event, separate from materials.
Salt / de-icer used
Bags or tons of bulk salt, sand, or liquid de-icer spread, plus the cost. The material line that swings most with a long winter and with mid-season price jumps.
Fuel used and cost
Diesel or gas burned for the run and the dollar amount, taken from the attached fuel receipt. Scoped to this storm's route — not an all-year vehicle fuel log.
Attached proof
The fuel receipt, salt purchase receipt, and any cleared-lot photo, attached to this storm record so the cost and its evidence stay together.
Running season cost to date
The cumulative salt + fuel + any service cost across all storms so far for this contract — the figure you compare against the flat fee.

Example setup

An example folder layout for one season

Here is how one operator's records might look for a single commercial contract across a winter. Each contract gets its own folder; the storm records and the reconciliation summary live inside it, under a fiscal-year or season folder.

Riverside-Plaza-2025-26-Season

The contract folder for one commercial lot. Holds the signed seasonal agreement (flat fee $9,600, 2-inch trigger), all storm event records, and the season reconciliation summary.

Contract-and-Terms

Signed seasonal contract, the agreed flat fee, service trigger depth, and the deposit/installment schedule. The fixed-fee baseline everything is measured against.

Storm-Events

One record per storm: Storm-2025-12-03, Storm-2025-12-19, Storm-2026-01-14, and so on. Each carries stops, salt, fuel, hours, and attached receipts.

Storm-2026-01-14

A single event record: 5am route, 3.5 hrs, 18 bags bulk salt ($162), 22 gal diesel ($79), cleared-lot photo and both receipts attached.

Receipts

Fuel and salt purchase receipts for the season, each also attached to its storm record. A convenient all-in-one place when exporting for the accountant.

Season-Reconciliation

The running summary: every storm listed with its cost, the season total to date, and the final fee-vs-actual note used to decide whether to renew or re-price this contract.

Common mistakes

Mistakes that distort the fee-vs-actual picture

  • Logging storms from memory at season end instead of the day you plowed — salt counts and hours are always understated weeks later.
  • Mixing all contracts into one fuel log, so you cannot tell which client's seasonal fee a given run belongs to.
  • Recording fuel and salt costs but not attaching the receipts, leaving the numbers unverifiable when a client or accountant asks.
  • Tracking events but never updating the running total, so you only discover a contract went over the fee after the season is closed.
  • Filing per-push billing items here — this folder is for reconciling a flat seasonal fee against actual events, not for invoicing each visit.
  • Letting the off-season storage and maintenance of your plows and spreaders creep into the storm log; that asset lifecycle belongs in its own records.

How it helps

How Cash Workspace supports this

One folder per contract

Create a folder for each seasonal client, nested under the season or fiscal-year folder, so the contract terms and every storm record sit together and the right events are always tied to the right flat fee.

A record for every storm

Add a dated record per event with the stops, salt, fuel, and hours you type in. They sort chronologically so counting the season's events and totaling costs is straightforward.

Receipts attached to the event

Attach the fuel receipt, salt receipt, and a cleared-lot photo directly to the storm record they belong to, so the cost and its proof never get separated.

Export for handoff

When you re-price next year or hand the season to an accountant, export the contract folder as accountant-ready records — a clean, organized set, not raw scattered files.

FAQ

Common questions from snow operators

Does this track per-push or per-visit billing?
No. This page is built for flat-rate seasonal contracts, where one fixed fee covers the whole winter. The storm log here measures your actual costs and events against that fee. If you bill per push or per visit instead, that is a different billing model and belongs in a per-job invoicing record set, not this reconciliation folder.
Can Cash Workspace read my fuel and salt receipts automatically?
No. There is no OCR or automatic extraction. You attach the receipt photo to the storm record and type in the fuel gallons, salt quantity, and dollar amounts yourself. Cash Workspace stores and organizes what you enter; it does not pull numbers off the image or sync with any fuel card or bank.
How is this different from a generic fuel log?
A generic fuel log tracks every gallon your vehicles burn all year. This is scoped to storm events on a specific seasonal contract — fuel and salt are logged per storm, per client, so you can total them against that client's flat fee. Off-contract driving and year-round fuel tracking are deliberately out of scope here.
Does reconciling the season tell me if I priced the contract right?
It gives you the evidence, not a verdict. The folder shows your total storm costs beside the fixed fee so you can see whether the contract ran under, near, or over. Deciding how to re-price or renew is a business judgment — this is organizational record-keeping, not pricing, tax, or accounting advice.

What this page does and does not do

Cash Workspace is a free tool for organizing your own records — invoices, expenses, receipts, and documents — into folders and records you fill in yourself. It does not sync with your bank or fuel card, does not read or extract figures from your receipts, and does not calculate whether a contract was profitable. Comparing storm costs against a seasonal fee here is organizational record-keeping to help you see your own numbers; it is not accounting, tax, or pricing advice. Operated by HELPERG LLC; questions to info@helperg.com.

Start a free folder for this season's contracts

Set up one folder per seasonal contract, drop in the agreement, and start logging each storm the day you plow. By spring you will know exactly which contracts earned their flat fee and which need re-pricing — all in a free workspace. Open Cash Workspace and create your first contract folder today.