Candidate Pipeline Stage-Aging Alerts
A candidate can sit in 'awaiting hiring manager feedback' or 'phone screen scheduled' for a week or more with nobody flagging it, because the ATS shows current stage but not how long a candidate has been stuck there. Recruiters juggling a dozen open reqs don't manually audit every pipeline daily, so the stall only surfaces when the candidate withdraws to take another offer or a hiring manager finally asks why a strong candidate went quiet. By the time anyone notices, the delay has already cost the hire.
STARTING PRICE
From €99
Starter tier · Single-workflow automation, one core integration, fast turnaround.
Get a quote →Saves roughly 2-4 hrs/week per recruiter, plus fewer candidates lost to slow internal feedback loops.
How the automation works
We track how long every active candidate has sat in their current pipeline stage and flag anyone who crosses a stage-specific aging threshold — three days for hiring manager feedback, five for reference checks, and so on, since a reasonable wait varies by stage. Alerts route to the recruiter and, for feedback-stage stalls specifically, a nudge goes to the hiring manager directly rather than only the recruiter chasing them. Aging is calculated per stage, not from application date, so a candidate who's moved quickly through four stages and is now waiting on one doesn't get flagged for the whole elapsed time — only for the stall that's actually happening right now.
Process flow
- 01
Stage entry timestamp captured trigger
Every time a candidate moves into a new pipeline stage, the entry time is recorded, resetting the aging clock for that stage rather than counting from original application date.
- 02
Apply stage-specific aging thresholds ai
Each stage has its own reasonable wait time — feedback stages age faster than reference-check stages — so one flat threshold across every stage doesn't over- or under-flag.
- 03
Flag candidates crossing threshold ai
A candidate who's been in a stage longer than its threshold is surfaced on a daily stalled-candidate list rather than waiting for someone to manually audit the pipeline.
- 04
Route nudge to the right owner output
Feedback-stage stalls prompt a direct nudge to the hiring manager, not just the recruiter, since the hiring manager is usually the actual bottleneck.
- 05
Escalate repeat stalls output
A candidate flagged more than once in the same stage escalates to the recruiting lead, since a repeated stall usually means the process, not the individual case, needs attention.
Inputs
- ATS pipeline stage and timestamp data
- Stage-specific aging thresholds
- Hiring manager and recruiter contact mapping
Outputs
- Daily stalled-candidate alert list
- Hiring-manager feedback nudges
- Stage-aging trend report by requisition
- Repeat-stall escalation log
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 aging threshold applied across every stage either fires constantly on stages that legitimately take longer, like background checks, or misses real problems in stages that should move fast, like initial recruiter screens — thresholds need to be set per stage, not globally.
- Aging calculated from original application date instead of current stage-entry date flags a candidate as stalled even when they've been moving briskly through the pipeline and have only just entered the stage they're currently waiting in.
- Nudging only the recruiter about a feedback delay misses the actual bottleneck — the hiring manager is usually who needs the reminder, and routing every alert to the recruiter just adds another manual chase to their list instead of removing one.
- Treating every stall as equally urgent trains recruiters to ignore the alerts entirely; a first-time stall and a candidate flagged repeatedly in the same stage need different responses, and the second case usually points to a process problem worth escalating.
Frequently asked questions
Does the aging clock reset when a candidate moves to a new stage?
Yes — aging is tracked per stage from the moment a candidate enters it, not from their original application date, so someone who moved quickly isn't flagged for total elapsed time.
Who gets notified when a candidate stalls in feedback?
The hiring manager gets a direct nudge for feedback-stage stalls, since they're usually the actual bottleneck, alongside a notice to the recruiter.
What happens if a candidate keeps getting flagged in the same stage?
A repeat stall in the same stage escalates to the recruiting lead rather than generating another routine nudge, since it usually signals a process issue rather than a one-off delay.
Can thresholds differ by role or seniority?
Yes, thresholds can be tuned by stage and by role type, since a senior technical loop legitimately takes longer at the feedback stage than an entry-level phone screen.