Automated Process Street Checklist Compliance Alerts
Every morning, WebRun opens Process Street, compares recurring checklists against their expected schedule, finds any that should have started today but haven't been, logs the gap to a Google Sheet, and emails the process owner a reminder naming exactly which checklist and assignee is behind.
How do I catch a Process Street checklist that didn't get started?
WebRun checks Process Street every morning for recurring checklists that should have started today but haven't, logs the gap to a Google Sheet, and emails the process owner naming the checklist and assignee. SOP compliance gets caught the same day instead of surfacing weeks later during an audit or a missed handoff.
- Missed checklists get caught the same day, not at audit time
- Every compliance gap is logged with the responsible assignee
- The process owner gets one email instead of checking every SOP
Built for Operations managers · quality and compliance teams · franchise operators · process owners
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
process.stin a real browser with your saved login - no setup, no API keys. -
1
Process Street - check today's checklists against schedule
WebRun opens Process Street to check today's checklists against schedule. - Open Process Street and check recurring checklists due today
- Find any that have not been started or assigned
- Note the checklist name and the assignee responsible
Done when Every checklist due today has a started or not-started status.
-
2
Google Sheets - log any checklist not started
WebRun opens Google Sheets to log any checklist not started. - Open the SOP compliance tracker sheet
- Add a row for each checklist not started today
- Mark previously logged gaps as resolved once they are started
Done when Every unstarted checklist for today is logged in the tracker.
-
3
Gmail - email the process owner a reminder
WebRun opens Gmail to email the process owner a reminder. - Draft and send the process owner a reminder naming each unstarted checklist
- Include the assignee responsible for each one
- Skip sending if every checklist is on schedule
Done when The process owner has been emailed about every unstarted checklist.
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
Will it start the checklist for the assignee?
No. WebRun only reports which checklist has not been started. Starting and completing it stays with the assigned person.
How does it know a checklist is overdue?
It compares each recurring checklist's expected schedule against whether a run has actually been started for today.
Does it track compliance history over time?
Yes. Every gap is logged with its date in the Google Sheet, so the process owner can review patterns, not just today's snapshot.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.