Proof of service photos: what actually holds up after a slip and fall
A photo is not a record. What a defensible service record needs, the four ways contractors lose them, and how to set the standard before you need it.
Disclosure: Bloombilt builds Dispatch, which captures timestamped proof photos as a core feature. This post is about the standard rather than our product, and we are not lawyers. If you have an active claim, talk to your attorney and your insurer, not a software company’s blog.
Snow and ice contractors carry a risk that lawn work does not. Someone falls on a property you service, and a year and a half later you are asked to demonstrate what you did and when.
The uncomfortable part: your defense was created, or not created, on a night you do not remember, by a driver who may not work for you anymore, in the dark.
Why “we were there” is not enough
The claim will not be that you never showed up. It will be about timing and adequacy. You cleared it at 4am, the incident was at 7am, and the question becomes what the surface looked like when you left and whether the interval was reasonable.
Testimony from a driver about a night eighteen months ago is weak. Contemporaneous records made at the time, in the ordinary course of business, are strong. That distinction is the whole game, and it means your documentation habit has to be automatic on ordinary nights, not something you switch on when a site feels risky.
What a defensible record looks like
Aim for all five on every service visit, every site, every time.
1. A timestamp from the device, not typed in later. The time has to come from the phone at the moment of capture. A field somebody fills in afterward is worth much less, and a system where anyone can edit the timestamp undermines the whole set.
2. Location tied to the photo. The photo should be associated with the property, ideally with device location. “A cleared parking lot” is not evidence. “This cleared parking lot” is.
3. Before and after, on the sites that matter. For zero-tolerance and high-traffic commercial properties, both. Before establishes the conditions you were dealing with; after establishes what you left.
4. What you applied. Salt, sand, brine, how much, where. A photo of a clear lot plus a record of material applied is a much better answer to “was the treatment adequate” than the photo alone.
5. Consistency across every visit. This is the one people miss and it matters enormously. A contractor who documents everything, always, has records that look like ordinary business practice. A contractor who documented only the three sites that felt risky has records that look like they were anticipating a problem, and that is a worse story.
The four ways contractors lose the record
The photo never left the phone. Taken in a parking garage or a dead zone, upload failed, app discarded it. This is the most common and the most preventable. Photos must save locally first and sync when signal returns. Test it: airplane mode, complete a stop with photos, reconnect, confirm they arrive.
The driver left and took the phone. If proof lives in a personal camera roll or a text thread, it walks out the door with the person. Records have to land in a system the company controls.
It went into a group text. Text threads are not searchable in any useful way eighteen months later, they lack reliable metadata once images are recompressed, and nobody can produce “every service record for 1400 Industrial Boulevard, winter 2025” from a chat history.
Retention ran out. Claims surface long after the season. Know how long your system keeps photos and confirm it covers your statute of limitations, which varies by state. Ask your insurer what they want to see. Then confirm your software actually retains that long, because default retention on a lot of tools is much shorter than you would assume.
Setting the standard before you need it
Write it down, one page, and hand it to every driver:
- Every site, every visit, no exceptions, including the easy ones.
- Photo at arrival and at completion on commercial and zero-tolerance sites.
- Note the material applied.
- Mark the stop complete in the app, at the stop, not at the shop.
- If the app cannot upload, keep going. It will sync. Do not skip the photo because the signal is bad.
That last line is worth saying out loud to crews, because the instinct when an upload fails is to stop bothering. If your software handles offline properly, the crew should never need to think about it.
Two questions for your software vendor
“What happens to a photo taken with no signal?” If the answer is anything other than “it saves on the device and uploads later, automatically,” you have a gap on exactly the sites where coverage is worst.
“Can I export every service record for one property across a date range?” The day you need this, you will need it quickly and in a form you can hand to someone. A tool that can show you photos in an app but cannot produce a clean record for one address is going to be painful at the worst time.
Where we fit
Dispatch captures a status and timestamped proof photos on every visit, and the capture is offline-first by design: the photo and status save on the phone immediately and sync when the truck is back in coverage. The crew never waits on a network and never has to decide whether to bother. Records live in the company’s account rather than a driver’s phone.
Being straight: Dispatch is new, and for something that functions as part of your liability posture, that is a real consideration. Dedicated snow platforms like Yeti have been doing this longer and model commercial snow contracts more deeply. We wrote an honest comparison of the snow options here, and for a pure snow and ice specialist we point at them rather than at us.
What we would say regardless of what you buy: pick a standard, apply it to every site every night, and test the no-signal path in October rather than discovering it in March.
Fifteen minutes if you want to put ours in airplane mode and see what survives.