Automated Security Guard Overtime Risk Digest
Every morning, WebRun opens TrackTik and totals the scheduled hours for each officer in the current pay period. Officers within 4 hours of the overtime threshold are flagged, logged to a Google Sheet, and reported in a Slack digest so your ops team can reassign shifts before overtime costs accrue.
How do I get an automatic daily overtime risk report for my security staff?
Every morning, WebRun totals each officer's scheduled hours in TrackTik for the current pay period, flags anyone within 4 hours of the overtime threshold, logs the at-risk roster to Google Sheets, and posts a digest to Slack so your ops and payroll teams can redistribute shifts before overtime costs accrue.
- Overtime risks spotted daily before shifts are locked in
- Ops team can redistribute hours with enough notice to avoid overages
- A running Google Sheet log tracks overtime patterns across pay periods
Built for security operations managers · payroll administrators · private security companies · contract security firms
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
app.tracktik.comin a real browser with your saved login - no setup, no API keys. -
1
TrackTik - total scheduled hours per officer in current pay period
tracktik.com
WebRun opens TrackTik to total scheduled hours per officer in current pay period. - Open TrackTik and navigate to the Schedule or Timesheets module
- For the current pay period, total scheduled and worked hours for each active officer
- Flag any officer whose total hours are within 4 hours of the overtime threshold (typically 40 hours for a weekly cycle)
- Note each officer's remaining scheduled shifts and projected total for the period
Done when Every officer approaching overtime is listed with their current hours, remaining shifts, and projected period total.
-
2
Google Sheets - log overtime risk roster
google.com
WebRun opens Google Sheets to log overtime risk roster. - Open the overtime risk Google Sheet and update the current-period tab
- Log each at-risk officer with their name, site, current hours, and projected total
- Mark anyone already over 40 hours as critical
Done when The overtime risk sheet is updated with current-period data for all flagged officers.
-
3
Slack - post overtime risk digest to payroll channel
slack.com
WebRun opens Slack to post overtime risk digest to payroll channel. - Post a digest to the payroll Slack channel with a count of officers at overtime risk
- List each at-risk officer by name, current hours, and projected overage
- Include a link to the Google Sheet for full details
Done when Payroll and ops teams have the daily overtime risk digest in Slack.
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 change anyone's schedule automatically?
No. WebRun only flags the risk and reports it. Reassigning shifts is a human decision left to your ops team.
How is the overtime threshold determined?
It uses 40 scheduled hours as the default weekly threshold, but you can update this to match your pay period rules or state-specific requirements.
What if an officer calls in sick and their hours drop below the threshold?
It reads the live schedule data from TrackTik each morning, so hours reflect actual scheduled shifts and any same-day changes are captured.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.