Requisition Aging and Stale Req Alerts
Open requisitions accumulate over time, and without an active process to review them, some sit open for months past any reasonable time-to-fill benchmark — priorities shifted, the hiring manager went quiet, or the role got deprioritized without anyone formally closing the req. Those stale requisitions keep counting against approved headcount and budget as if they're actively being worked, distorting workforce planning numbers and leaving recruiters with a phantom workload of reqs nobody's actually pushing forward, while genuinely time-sensitive open roles don't get the visibility they need against that inflated backlog.
STARTING PRICE
From €99
Starter tier · Single-workflow automation, one core integration, fast turnaround.
Get a quote →Saves roughly 2-3 hrs/month for recruiting ops, plus more accurate headcount and budget reporting for finance and workforce planning.
How the automation works
We track every open requisition's age against a time-to-fill benchmark specific to its role type and seniority, since a senior technical req reasonably stays open longer than an entry-level operations role, and flag anything aging significantly past its expected window. Flagged reqs route to the hiring manager and recruiting lead for an explicit status check — still actively hiring, on hold, or ready to close — rather than sitting indefinitely in ambiguous limbo. Reqs confirmed on hold get tagged distinctly from actively worked reqs in reporting, so headcount and budget numbers reflect what's actually being pursued instead of counting stalled requisitions as live work.
Process flow
- 01
Requisition age tracked against benchmark trigger
Every open req's elapsed open time is compared against a time-to-fill benchmark specific to its role type and seniority, rather than one flat threshold for every requisition.
- 02
Flag reqs aging past benchmark ai
Requisitions significantly past their expected time-to-fill window are surfaced on a stale-req list rather than continuing indefinitely without review.
- 03
Route for explicit status check output
Flagged reqs route to the hiring manager and recruiting lead with a specific prompt to confirm status — still active, on hold, or ready to close — instead of assuming the req is fine because nobody's raised a concern.
- 04
Tag confirmed-hold reqs distinctly ai
Requisitions confirmed on hold are tagged separately from actively worked reqs, so they stop being counted as live recruiting effort in funnel and workload reporting.
- 05
Refresh headcount/budget accuracy report output
Workforce planning and budget reports reflect the distinction between actively worked and on-hold requisitions, rather than counting every open req as active regardless of its real status.
Inputs
- Open requisition data with role type and seniority
- Time-to-fill benchmarks by role type/seniority
- Hiring manager and recruiting lead contact mapping
- Headcount/budget reporting requirements
Outputs
- Stale requisition alert list
- Hiring-manager status-confirmation requests
- On-hold vs. active req tagging
- Accurate headcount/budget-vs-actual reporting
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- A single time-to-fill threshold applied to every requisition either flags perfectly normal senior or niche technical reqs as problems constantly, or misses genuinely stalled entry-level roles that should have filled much faster — benchmarks need to be set per role type and seniority level, not as one company-wide number.
- Flagging a stale req without routing it for an explicit human status confirmation just creates another report nobody acts on; the value is in forcing a decision — still hiring, on hold, or close it — rather than passively noting the req is old and leaving it exactly where it was.
- Requisitions quietly deprioritized by a hiring manager who never formally closes them keep counting against approved headcount and budget indefinitely, which distorts workforce planning numbers and can mask actual available headcount that finance and HR both believe is already spoken for.
- Treating an on-hold requisition the same as an actively worked one in recruiter workload and funnel reporting overstates how much real recruiting effort is in flight, making a team's actual capacity and bandwidth look worse — or better — than it really is.
Frequently asked questions
Does the aging threshold differ by role type?
Yes — benchmarks are set per role type and seniority level, since a senior or niche technical req legitimately takes longer to fill than an entry-level operational role, and one flat threshold would misfire on both.
What happens when a req is flagged as stale?
It routes to the hiring manager and recruiting lead with an explicit prompt to confirm status — still active, on hold, or ready to close — rather than just appearing on a report nobody is required to act on.
Does an on-hold req still count against headcount and budget?
It's tagged distinctly from actively worked reqs in reporting, so workforce planning and budget numbers can reflect what's genuinely being pursued versus what's stalled.
Can this close a requisition automatically?
No — closing or holding a req remains a hiring manager and recruiting decision; the automation surfaces the need for that decision rather than making it unilaterally.