All templates

Automated Avature Requisition Coverage Report

Every Monday, WebRun opens Avature, goes through the open requisitions, counts how many candidates sit at each pipeline stage on each one, flags the stages that are thin or empty against your targets, saves the coverage table to Google Drive, and opens a Trello card per requisition at risk.

Runs on WebRun · Strict Lockdown policy
Every Monday at 8:00 AM WebRunorchestrates each step
1 Avature count candidates per requisition
2 Google Drive save the coverage table
3 Trello open a card per thin role
In short

How do I find open roles with too few candidates in the pipeline?

WebRun reviews your open Avature requisitions every Monday. It counts candidates at each pipeline stage per role, marks the stages that are thin or empty, saves the coverage table to Google Drive, and opens a Trello card for every requisition at risk, so sourcing moves before a start date slips.

  • Empty pipeline stages surface weeks before a start date is missed
  • Sourcing effort moves to the roles that actually need it
  • Every at risk role has a named recruiter and a card

Built for recruiting leads · talent acquisition teams · HR operations · staffing agencies

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens avature.net in a real browser with your saved login - no setup, no API keys.

  2. 1
    Avature - count candidates per requisition
    avature.net
    WebRun in Avature: count candidates per requisition
    WebRun opens Avature to count candidates per requisition.
    • Open Avature and list the requisitions still open
    • For each role, count candidates at every pipeline stage
    • Note the recruiter, the hiring manager, and the target start date
    • Compare the counts against the coverage you expect at each stage

    Done when Every open requisition has a stage by stage candidate count against target.

  3. 2
    Google Drive - save the coverage table
    drive.google.com
    WebRun in Google Drive: save the coverage table
    WebRun opens Google Drive to save the coverage table.
    • Save the week's coverage table into your private recruiting folder
    • Show one row per requisition with the counts at each stage
    • Keep last week's file so the trend per role is easy to read

    Done when This week's coverage table is filed in Google Drive beside the previous ones.

  4. 3
    Trello - open a card per thin role
    trello.com
    WebRun in Trello: open a card per thin role
    WebRun opens Trello to open a card per thin role.
    • Open a card for each requisition with a thin or empty stage
    • Put the role, the recruiter, and the days to the target start date on the card
    • Rank the roles closest to their start date at the top of the list

    Done when Every at risk requisition has a Trello card with its recruiter named.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
avature.net
ScheduleRuns automatically on this cadence
Every Monday at 8:00 AM
DeliveryHow each run's result reaches you
Coverage table · Google Drive
OutputWhat each run produces - A weekly coverage table of open requisitions with candidate counts per pipeline stage and the thin or empty stages flagged.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does it contact candidates or hiring managers?

No. WebRun writes an internal coverage table and internal Trello cards only. It never emails a candidate, never messages a hiring manager, and never changes a candidate's stage.

How does it decide a stage is thin?

You set the coverage you expect at each stage, for example four candidates at interview per role. WebRun compares the live Avature counts against your numbers every Monday.

Will it move or reject anyone in Avature?

No. It reads the pipeline and counts. Advancing, rejecting, or reassigning a candidate is a recruiter decision and stays inside Avature with a human doing it.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.