Automated Yeti Slip and Fall Liability Log
Every night, WebRun opens Yeti Software, pulls each site's service timestamps, photos, and logged weather condition, appends them to a liability log in Google Sheets that is never overwritten, and pings Telegram if any site had no completed stop during active snowfall or icing.
How do I keep a liability-ready log for slip-and-fall claims?
Every night, WebRun pulls each site's service timestamps, photos, and logged weather condition from Yeti Software and appends them to a liability log in Google Sheets that is never overwritten. If any site had no completed stop during active snowfall or icing, it pings Telegram the same night, so you have a defensible record and an early warning of any coverage gap.
- Every site has a timestamped, photo-backed service record every day
- Coverage gaps during active snowfall are flagged the same night
- A defensible record exists before a claim is ever filed
Built for snow removal contractors · risk managers · commercial property snow accounts · insurance-conscious operators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.yetisoftware.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Yeti Software - pull service timestamps and photos per site
yetisoftware.com
WebRun opens Yeti Software to pull service timestamps and photos per site. - Open Yeti Software and pull every site's service timestamps and photos for the day
- Note the weather condition logged at time of service
- Flag any site with no completed stop during active snowfall or icing
Done when Every site has its service timestamps, photos, and weather condition captured for the day.
-
2
Google Sheets - write the liability log
google.com
WebRun opens Google Sheets to write the liability log. - Write a dated row per site with its timestamps, photo links, and condition
- Keep the log append-only, so no prior entry is ever overwritten
Done when Today's entries are appended to the liability log for every site.
-
3
Telegram - flag sites unserviced during active snowfall
telegram.org
WebRun opens Telegram to flag sites unserviced during active snowfall. - Ping the channel if any site had no completed stop during active snowfall or icing
- Name the site and the hours it went unserviced
Done when Any coverage gap for the day has been flagged to your team.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does this file anything with an insurer?
No. It only builds and keeps an internal log of service timestamps and photos. You or your insurer can pull from it if a claim ever comes up, but WebRun never files anything.
Can old entries be edited or deleted?
No. The log is append-only, so every night adds new rows and nothing already written is changed. That's what makes it useful as a record.
What counts as active snowfall or icing for the flag?
The weather condition logged against each service stop in Yeti Software at the time it was completed, not a separate weather check.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.