Automated Hyperproof Overdue Control Chasing
Every morning, WebRun opens Hyperproof, checks every control for overdue evidence or a missed deadline, posts the chase list to the compliance team's Telegram channel, and texts the control owner via Twilio once their deadline has passed.
How do I chase overdue compliance controls in Hyperproof before an audit?
WebRun checks Hyperproof every morning for controls with overdue evidence or a missed deadline, posts the full chase list to Telegram, and texts each overdue control's owner via Twilio. It only reads due dates and status, so gathering and uploading evidence always stays with the assigned owner.
- Overdue controls are chased daily, not discovered at audit time
- Every control owner gets a direct text once they're overdue
- Evidence upload and control completion always stay with the owner
Built for compliance teams · GRC managers · audit readiness teams · security and compliance leads
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
hyperproof.ioin a real browser with your saved login - no setup, no API keys. -
1
Hyperproof - check control deadlines
WebRun opens Hyperproof to check control deadlines. - Open Hyperproof and check every control's evidence status and due date
- Flag controls with no evidence uploaded past their due date
- Note the assigned owner for each overdue control
Done when Every control has a checked status and, if overdue, an identified owner.
-
2
Telegram - post the chase list
WebRun opens Telegram to post the chase list. - Post the full list of overdue controls to the compliance team's Telegram channel
- Include the control name, owner, and days overdue
- Leave gathering and uploading evidence to the owner
Done when Every overdue control is visible in Telegram.
-
3
Twilio - text the overdue owner
WebRun opens Twilio to text the overdue owner. - Text each overdue control's owner via Twilio once their deadline has passed
- Name the control and how many days it has been overdue
- Never upload evidence or mark a control complete on the owner's behalf
Done when Every overdue owner has been texted this run.
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 WebRun upload evidence or complete a control?
No. WebRun only reads due dates and evidence status. Gathering and uploading evidence, or marking a control complete, is always done by the assigned owner.
What counts as overdue?
Any control with no evidence uploaded after its due date in Hyperproof has passed, read directly from the control's own status.
Will the owner be texted more than once for the same control?
Yes, every day it stays overdue, so it keeps surfacing until evidence is uploaded and the control's status changes in Hyperproof.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.