Aging Requisition Rescue System
Diagnose why a req is stuck before spending another week repeating the same search.
Last reviewed: 2026-09-06
Ask SourcingOS about this page
Inputs
- Original role brief and later changes
- Reviewed/rejected candidate history
- Source-lane yield
- Hiring-manager feedback
- Time-to-stage and outreach/engagement data where available
1. Reconstruct the real brief
Compare the original intake with the reasons candidates were actually rejected. Identify hidden requirements, moving goalposts, and criteria that became de facto hard filters.
2. Audit source coverage
List which source lanes, donor-company pools, geographies, adjacent titles, and owned-talent channels were truly tested.
3. Measure rejection concentration
If most candidates fail for the same reason, test whether the requirement is accurate, searchable, verifiable, and realistically available in the target market.
4. Separate market scarcity from workflow friction
A requisition can age because of compensation, interview latency, approval delays, poor outreach, contact quality, or changing requirements—not just candidate scarcity.
5. Produce a rescue decision
Recommend one of four outcomes: continue with uncovered lanes, recalibrate requirements, widen market/geography, or escalate a genuine scarcity/process constraint with evidence.
What to measure
- Days open by stage
- Repeated rejection reasons
- Unexplored lane count
- Hiring-manager feedback latency
- Qualified-candidate conversion
Failure modes to avoid
- Adding more Boolean strings without diagnosis
- Blaming the market before mapping it
- Ignoring process latency
- Treating every rejection reason as independent