The short answer
Classify the failure before choosing the fix. “We need more candidates” can mean five completely different things: no leads, wrong leads, no response, hiring-manager rejection, or later-stage fallout. Each needs a different rescue plan.
The five aging-req failure modes
The diagnostic decision tree
- Are there enough leads to review? If no, inspect search design and market constraints.
- Do reviewed leads meet the evidence standard? If no, inspect titles, evidence terms, donor companies, and intake clarity.
- Do relevant leads respond? If no, inspect outreach, channel, employer/role value, compensation, and timing.
- Does the hiring manager advance recruiter-reviewed profiles? If no, inspect calibration and hidden rejection criteria.
- Do candidates survive later stages? If no, inspect interview process, speed, offer competitiveness, onsite expectations, and late-discovered mismatches.
Do not jump from step 4 back to “source more.” A calibration failure will simply create more rejected profiles.
Build a one-page req rescue evidence pack
Bring these facts to the rescue conversation:
- req age and business priority
- must-have evidence standard
- independent search lanes already tested
- evidence-fit lead yield by lane
- duplicate pressure and recent new-lead rate
- top false-positive patterns
- hiring-manager rejection reasons
- response outcomes by channel or message angle
- location and compensation constraints
- process fallout points
- the single next decision needed from the hiring manager
Use evidence, not “the market is tough.”
Match the rescue experiment to the failure
No leads
Open one independent lane: adjacent titles, donor companies, GitHub/artifact evidence, registries, federal contract data, ATS rediscovery, referrals, or another source that changes the search path. Use the Search Lane Expander.
Wrong leads
Add or change the evidence standard. Remove overloaded titles. Split a blended role into separate work patterns. Rebuild the source pack with Source Pack Methodology.
No response
Keep the same evidence-fit cohort and test message angle, channel, timing, or value proposition before concluding the search pool is wrong. If compensation or onsite expectations are the real objection, document them.
HM rejection
Cluster rejection reasons and ask which search parameter each reason should change. If the manager cannot articulate what evidence would have changed the decision, the req is not calibrated enough for more volume.
Late-stage fallout
Stop blaming sourcing for a process leak. Identify the stage, reason, and repeat pattern, then route the issue to interview, scheduling, compensation, offer, or role-design owners.
Use tradeoff language with the hiring manager
Examples:
- “We can preserve exact domain and open titles, or preserve exact title and open domain. Which matters more?”
- “The accepted platform evidence exists, but mostly outside your preferred donor companies. Is company pedigree a true requirement?”
- “The current compensation range is repeatedly losing the target level. Do we lower level, change geography, or revisit range?”
- “The same three profiles would pass if GovCloud were trainable. Is that a day-one requirement or a 90-day ramp item?”
Record approved tradeoffs so the source pack and next search actually change.
When the rescue becomes a search-exhaustion finding
If strict, adjacent, donor, and independent evidence lanes have been tested; duplicate pressure is high; recent new-lead rate is low; and the hiring manager has reviewed the tradeoffs, then the team has evidence for an exhaustion or constraint escalation. Use the Search Exhaustion framework rather than a subjective “we looked everywhere.”
FAQ
Why do recruiting requisitions age?
Different requisitions age for different reasons: the market may be too small, the search may be aimed at the wrong lane, outreach may be underperforming, the hiring-manager standard may have drifted, compensation or location may be misaligned, or candidates may be falling out later in the process. Diagnose the stage before changing the search.
What should a sourcer do when there are no candidates?
First separate “no candidates exist” from “our current search paths are not finding evidence-fit leads.” Test independent title, skill, evidence, donor, adjacent, owned-history, and role-specific source lanes before declaring the market empty.
What if the hiring manager keeps rejecting candidates?
Analyze the rejection pattern. Repeated rejection for the same unstated reason is a calibration defect, not a sourcing-volume problem. Bring the pattern to the hiring manager and force the hidden standard into the source pack.
When should compensation be escalated?
When the search evidence repeatedly shows that the target market, level, location, or competing employers are incompatible with the approved range, document the pattern and escalate it as a market constraint rather than widening the search randomly.
How do I know when to stop searching?
Use observable coverage evidence: independent lanes tested, duplicate pressure, recent new-lead rate, adjacent-title yield, donor-map coverage, and unresolved constraints. The Search Exhaustion framework is designed for that decision.