Automated Recruiter Workload Digest
Every Monday, WebRun opens Ashby, reads the recruiting reports, counts open requisitions and active candidates owned by each recruiter, writes the load per recruiter to a Google Sheet, and posts your team a Slack digest showing who is overloaded and who has capacity.
How do I balance workload across my recruiting team automatically?
Every Monday, WebRun opens Ashby, reads the recruiting reports, and counts open requisitions and active candidates owned by each recruiter. It writes the load to a Google Sheet and posts your team a Slack digest showing who is overloaded and who has room, so the hiring load gets rebalanced before pipelines slip or someone burns out.
- Overloaded recruiters surface every Monday, before pipelines slip
- Spare capacity is obvious, so reqs get reassigned fairly
- Workload trends stay visible across the team
Built for recruiters · talent acquisition · hiring managers · HR 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
app.ashbyhq.comin a real browser with your saved login - no setup, no API keys. -
1
Ashby - read load per recruiter
ashbyhq.com
WebRun reads Ashby reporting for load per recruiter. - Open Ashby reporting and group open requisitions and active candidates by recruiter or owner
- Capture each recruiter's open req count, active candidate count, and upcoming interviews
- Note who is well above the team average and who has spare capacity
Done when Open reqs and active candidates are captured for every recruiter.
-
2
Google Sheets - log workload per recruiter
google.com
WebRun logs each recruiter's workload to a sheet. - Write each recruiter's open reqs, active candidates, and upcoming interviews into the workload sheet
- Compare each against the team average to show who is over and under
- Keep a running history so workload trends are visible week over week
Done when Workload per recruiter is recorded and compared in the sheet.
-
3
Slack - post the balance digest
slack.com
WebRun posts the recruiter workload-balance digest to Slack. - Post a short digest of load per recruiter, flagging who is overloaded and who has room
- Suggest where a req or candidates could be reassigned to even things out
- Leave reassignment to your team lead. Never move reqs or candidates between recruiters automatically
Done when Your team has this week's workload-balance 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 reassign reqs or candidates on its own?
No. WebRun only reads Ashby reporting and reports load per recruiter. Moving a requisition or candidates between recruiters stays with your team lead, who decides based on the digest inside Ashby.
How does it measure recruiter workload?
It counts each recruiter's open requisitions, active candidates, and upcoming interviews from Ashby reporting, then compares each against the team average, so overload and spare capacity are both clear at a glance.
Does it message individual recruiters or candidates?
No. The digest is a single internal Slack post to your recruiting leadership and team channel. No candidate is contacted, and individual recruiters are named for balancing, not messaged automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.