Automated Namely Time Off Coverage Checks
Every Monday, WebRun opens Namely, reads every approved and pending time off request for the week ahead, builds a day by day coverage grid per team in Google Sheets, and sends you a WhatsApp note naming the teams and days where too many people are away at once.
How do I spot understaffed days before the week starts?
WebRun checks next week's Namely time off every Monday. It reads approved and pending requests, matches each person to their team, builds a day by day coverage grid in Google Sheets, and sends you a WhatsApp note naming the teams and days that go under strength.
- Understaffed days are found before the week begins, not on the day
- Pending requests are counted separately so nothing is approved blind
- Every team gets its own away limit in one shared grid
Built for HR managers · team leads · operations managers · people ops 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
namely.comin a real browser with your saved login - no setup, no API keys. -
1
Namely - read next week's time off
WebRun opens Namely to read next week's time off. - Sign in to Namely and open the time off calendar for the coming week
- Capture each request with the employee, their team, the dates, and whether it is approved or still pending
- Match every requester to their team from their employee profile
Done when Every time off day next week is attached to a person and a team.
-
2
Google Sheets - build the coverage grid
WebRun opens Google Sheets to build the coverage grid. - Open the coverage sheet in Google Sheets
- Fill a grid of teams down the side and next week's days across the top, counting who is away each day
- Mark any cell where the count passes the limit you set for that team, counting pending requests separately
Done when Next week's coverage grid is filled in with every over limit day marked.
-
3
WhatsApp - flag the thin days
WebRun opens WhatsApp to flag the thin days. - Send yourself the teams and days that go under strength next week
- Name who is away on each of those days and which requests are still pending
- Leave every approval and reschedule to you. WebRun never approves, denies, or moves a request
Done when You know which days need cover before the week starts.
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 approve or deny time off requests?
No. WebRun reads the calendar and reports the clashes. Approving, denying, or asking someone to move a request stays a manager decision made in Namely by a person.
Does it count pending requests?
Yes, and it counts them separately from approved ones, so you can see a day that is fine today but would go under strength if the pending requests are all approved.
How does it know a team is short?
You set a maximum number away per team, and any day that passes the limit is flagged. Teams with different sizes can carry different limits in the same run.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.