Snow and ice

How to prove snow removal was done

By the LockProof Team · Last updated August 10, 2026

How to prove snow removal was done runs into one awkward fact: by the time anybody asks, the evidence has melted. A lot cleared at four in the morning and a lot nobody touched look much alike by mid-morning, both wet, both grey. So the answer is never the lot. It is whatever you wrote down while the snow was still there, and in particular whether any part of that record came from somewhere other than the crew that ran the route.

Read your route sheet the way a client will

Every guide on this subject tells you to keep a snow log, and every one of them is right. Keep the log. But before adding anything to it, take one completed sheet and ask who made each line on it.

The site is right. The service performed is right. The material and the quantity are close enough. The arrival time was typed by the driver, often at the end of a six-lot run, in a warm cab, working backwards through a night that has started to blur. Every field on that sheet has the same author, and that author is you.

None of which makes the sheet dishonest. It is how field paperwork works in nearly every trade. It only becomes a problem in one situation, and it happens to be the situation the sheet exists for: somebody outside your company is deciding whether to believe it.

What that gap is worth to somebody willing to use it

A federal jury in the Western District of Pennsylvania convicted a Pittsburgh snow-removal business owner on five counts of wire fraud and three of money laundering. Prosecutors said he billed his own customers for services that were not performed, then moved the proceeds through three bank mortgage payments of more than ten thousand dollars each. The customers paid because they had an invoice, and an invoice is a claim about a night nobody could go back and look at.

It is worth being careful about what that case does and does not show. It is one prosecution, not a rate, and nobody publishes a reliable figure for how often snow invoices are disputed. What it does show is the shape of the exposure. Where the only account of the work is the account of the party being paid for it, a dispute has nothing to work with, and neither does a client who has begun to wonder.

The same structural gap is what leaves an honest contractor exposed. A sheet reading 4:10 is the assertion under dispute, which makes it a restatement of your position rather than support for it.

Snow arguments are almost never about whether

This is the part that separates winter work from the rest of the trades. A cleaning crew gets asked whether they came. A snow crew usually gets asked when.

Contracts run on triggers. Two inches of accumulation. Cleared before the seven o’clock opening. Back within two hours of the storm ending. Salt on the walks before the first shift parks. Every one of those turns the dispute into a question about a clock, which means the disputed field is the one field on the route sheet that the driver set by hand, from memory, after the fact.

Self-logged entryTyped by the personAny time after the factNothing anchors it to the siteEditable with no traceRecords a claimLive sealed captureThrough the camera onlyServer-set time; GPS if sharedSHA-256 sealed on submitTampering is detectableRecords a live capture
A typed log entry records what the crew says happened. A live sealed capture records the photo itself, and when it landed.

Change one input, keep everything else

Nothing about the route has to change. Nobody carries new equipment or downloads anything. One line of the record moves out of the truck.

The driver gets a text at the site. The link inside it opens the camera directly and offers nothing else, the gallery included, which is what keeps a shot of the same lot from a storm three weeks back out of tonight’s file. Submitting hands the photo to our server, and the server stamps its own arrival time onto the record. That clock sits outside the truck. Coordinates ride along on any submission where the driver shares location. On a lot that matters enough, you can make that reading mandatory before the photo is accepted.

From there, four things fold into one SHA-256 fingerprint: the image, the server’s time, the coordinates where there are any, and where the file is stored. Alter any of them later and the fingerprint no longer matches what it was computed over. Tamper-evident is the accurate word for that, and it is narrower than it sounds. An edit is still possible. It just leaves a mark.

Live camera captureNo gallery uploadsServer-set time attachedGPS when sharedSHA-256 sealFingerprints the recordSealed recordTampering is detectableHand it to the ownerOne signed link
How a live capture becomes a sealed, shareable record.
“A sheet filled in after the run” describes an ordinary paper or spreadsheet route sheet, not any particular product. “A capture sealed on submission” is how a LockProof capture behaves.
The question in AprilA capture sealed on submissionA sheet filled in after the run
Where the arrival time came fromOur server, as the photo landsWhichever clock the driver read
Whether the lot shown is this stormThe link opens the camera and nothing elseAny picture on the phone would pass
Whether a line was edited in MarchThe fingerprint stops matchingRewriting it leaves no mark

There is a second record you did not write, and it is free

Half of a snow dispute is whether you showed up. The other half is whether you needed to, and that one is not yours to settle either. If the contract triggers at two inches, the argument turns on how much fell at that site, on that night, which is a fact held by somebody with no stake in your invoice.

NOAA’s National Centers for Environmental Information publishes the observations from land-based stations through Climate Data Online, free to search, going back decades. Find the station nearest each property once, write the identifier into the site file, and looking up a past event becomes a two-minute job instead of an afternoon. NCEI also certifies data from its archive on request, ordered online and posted out as paper, which is worth knowing about before you need it rather than during.

Pair the two and the file starts to look different from the inside. The station says weather happened. Your capture says you did. Neither one came out of the truck.

Building the season, in five steps

The first three of these work with a clipboard and a phone. The last two are where a sealed record starts to earn its place.

  1. Write the trigger into the contract in checkable terms.“Prompt service” leaves both sides free to mean different things in April. “Drive lanes open by 6:30 AM after any event exceeding two inches” settles to a yes or a no, and it tells your crew what to photograph.
  2. Take a before shot on the first push of each event. Depth on a measuring stick against a wall, or a plain shot of the untouched lot. Without it, a cleared surface is just a surface.
  3. One completion photo per site per visit, not per route. A single picture standing in for eight properties is the weakest link in most snow files, and it is the first thing a client will notice.
  4. Move the timestamp off the phone. A date written into a photo by the handset that took it can be edited in under a minute. When the time comes from a server on submission instead, the field everybody argues about is no longer yours to set.
  5. File by site and date, not by storm.Disputes arrive as “the eleventh, the north lot,” never as “the second event of the season.” If that lookup takes twenty minutes, you will settle rather than search.

Salt is the hard one

De-icing is the least provable thing your crews do. Plowing leaves a cleared surface for a few hours; salt disappears into meltwater and does its work invisibly. A bag count entered that evening is the purest form of the problem, a number you wrote about a material nobody can go back and count.

So photograph the application rather than the outcome: the spreader running, the material on the surface, taken standing there. It is an imperfect record and worth having anyway, because the alternative is a line of text. And for the three in the morning pre-treat that nobody dispatched, a permanent per-worker link lets a driver file the same kind of capture unprompted, on their own initiative, at the site.

The trade has written down what a professional operation looks like, incidentally. The standard is ANSI/ASCA A1000-2014, System Requirements for Snow and Ice Management Services, voluntary, and written to sit alongside ISO 9001. Whether or not you work to it, it is a useful picture of the documentation habits the industry considers normal.

The manager on the other end needs the same record

A property manager buying snow service has a second problem the contractor does not, and it surfaces long after the invoice clears. Somebody falls on ice in the parking lot and files a claim, and the question becomes what the site’s condition was and when it was last treated. The National Insurance Crime Bureau has described how it investigates questionable slip-and-fall claims, and surveillance video is often the deciding factor in them.

Which is why the useful version of this is not a contractor’s private file. When the vendor’s capture lands in a record the manager can open, one photograph taken at the lot does two jobs a season apart. The manager can pass it along as a URL that opens in any browser with no sign-in, and that URL is short-lived by design: seven days, then it stops opening. Issuing a replacement is a couple of clicks, and the record behind it is unaffected either way. The same reasoning runs through dispute-ready vendor records for every other trade a manager hires.

The honest size of the claim

A contractor who oversells his own file loses the client he had already won over, so keep this narrow. Two things are established, and no more. The image came off a camera in the moment instead of out of a folder, and nothing in the record has shifted since sealing.

It does not certify the scene. Whether the lot was cleared to the contract standard, whether the corner out of frame got the same treatment, whether enough material went down for the temperature: those are judgements about snow work, and they still belong to people who understand snow work. What changes is narrower, and it lands where the arguments actually happen. When a client asks how you know the north lot was open by 6:30, you have something to put in front of them besides the driver’s say-so.

Common questions

How do you prove snow removal was done?

With a record made while the snow was still on the ground, carrying at least one element the crew did not author. A route sheet filled in after the run is your own account of your own night. Photograph the cleared surface live and let a server rather than a handset time it, and a client has something to weigh.

What should a snow removal log include?

Site, arrival and departure, what was plowed or shovelled, what material went down and roughly how much, plus the weather at the time. That is the useful minimum. The part worth adding is a photograph per site per visit, because a written line and a picture fail in very different ways.

Do timestamped photos prove a lot was plowed?

Only as far as the timestamp is trustworthy. A date written into a photo by the phone that took it can be changed in under a minute with free tools, so it settles nothing on its own. A time the server writes on submission, by contrast, is not the driver’s to adjust.

How do you prove salt or de-icer was applied?

Photograph the application, not the result, because the result dissolves. A shot of the spreader running on the surface, taken on site and sealed where it lands, holds up better than a bag count entered that evening. Pair it with the material and quantity on the same record.

Who needs the proof, the contractor or the property manager?

Both, from opposite sides of the same event. The contractor needs it to get paid for a push a client says never happened. The manager needs it months later when someone claims the walk was untreated. One record made at the site answers both questions.

Pick the site that argues with you

Name the one lot where the invoice gets questioned every February. We will show you what its next push looks like when the time on the record is written by our server as the photo lands, not typed by the driver afterwards.