Automated AuditBoard Control Coverage Checks
Every Monday, WebRun opens AuditBoard, counts how many controls have a completed test this period and how many do not, breaks the untested share out by control owner, posts the coverage picture to Telegram, and drafts a reminder in Gmail for each owner still carrying untested controls.
How do I track control testing coverage during the quarter?
Every Monday WebRun opens AuditBoard and measures how much of your control set has a completed test this period. It groups the untested controls by owner, posts the coverage picture and weeks remaining to Telegram, and drafts a Gmail reminder per owner for the audit manager to review and send.
- The untested share of controls is a number every Monday, not a surprise
- Testing load is visible per owner while there is still time to spread it
- Evidence requests blocking a test are named alongside the control
Built for internal audit teams · compliance managers · SOX programs · risk teams
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.auditboard.comin a real browser with your saved login - no setup, no API keys. -
1
AuditBoard - measure testing coverage
auditboard.com
WebRun opens AuditBoard to measure testing coverage. - Sign in to AuditBoard and list the controls in scope for the current testing period
- Record the test status on each control: completed, in progress, or not started
- Note the control owner and the outstanding evidence requests against each untested control
- Work out the tested share of the control set and how many weeks remain in the period
- Group the untested controls by owner so the load is visible per person
Done when Every in-scope control has a test status and an owner recorded.
-
2
Telegram - post the coverage picture
telegram.org
WebRun opens Telegram to post the coverage picture. - Post the tested and untested counts with the percentage covered so far
- Show the weeks left in the period beside the number still to test
- List the owners with the most untested controls first
- Note any control with an open evidence request blocking its test
Done when The audit manager has this week's coverage picture on Telegram.
-
3
Gmail - draft the owner reminders
gmail.com
WebRun opens Gmail to draft the owner reminders. - Draft one email per control owner listing their untested controls and the weeks remaining
- Include the open evidence requests holding each test up
- Keep the tone factual and short
- Leave every email as a draft. The audit manager reviews and sends, WebRun never emails an owner on its own
Done when A reminder draft is waiting for each owner carrying untested controls.
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 email control owners without me?
No. Every owner reminder is left as a Gmail draft for the audit manager to review and send. WebRun writes the email but a person presses send.
Does it change any test status in AuditBoard?
No. WebRun reads the control set and reports coverage. Marking a test complete, uploading evidence and closing an item all stay with the tester in AuditBoard.
Why run this weekly rather than near the deadline?
Because the untested share only becomes fixable while weeks remain. A Monday reading shows the gap against the time left, so testing spreads across the period instead of piling into the final week.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.