Extended definition
Req management is the management discipline that keeps the recruiting engine running. At any given time, a TA function is carrying a portfolio of active reqs at different stages — newly approved, in early sourcing, in active interviewing, at offer stage, on hold.
Req management is the practice of running that portfolio: which reqs need attention, which are at risk, which need recruiter reassignment, which need escalation to the business about scope or timing. Strong req management catches problems early and keeps the portfolio moving; weak req management produces aging reqs that accumulate quietly until the team realises half the portfolio has been open for 90+ days.
How req management works
A working req management practice covers four areas:
- Active req tracking — A live view of every active req with its current stage, recruiter ownership, days open, and next action. Usually surfaced through ATS dashboards or TA operations reporting. Updated weekly or in real-time.
- Aging req review — Reqs aging past defined thresholds — 30 days, 60 days, 90 days — get surfaced for review. The conversation isn’t “why is this still open” but “what’s the diagnosis and what changes.” Sometimes scope adjustment, sometimes recruiter reassignment, sometimes business-side reprioritisation.
- Recruiter portfolio review — Each recruiter’s active req load reviewed against their capacity. Imbalances get rebalanced — overloaded recruiters get reqs reassigned, underloaded ones get reqs added. Done weekly in mature operations.
- Escalation paths — Defined process for what happens when reqs hit specific risk thresholds — slipping past target start date, repeated hiring manager unresponsiveness, scope changes that materially affect feasibility. Escalation surfaces problems before they become crises.
Req management is sometimes a dedicated TA operations function and sometimes a responsibility distributed across recruiter team leads. The structure matters less than the cadence and the data — without weekly review and accurate dashboards, reqs drift.
Why req management matters
Req management determines whether TA capacity actually gets used productively. A team with 50 active reqs and 5 recruiters can produce 50 hires in a quarter or 20, depending on whether the portfolio is managed actively or passively.
The same headcount, the same tooling, the same market — different discipline, different outcomes. Beyond the productivity case, strong req management also produces the reporting that earns TA executive credibility: clean dashboards, aging-req visibility, and proactive escalation are what executives expect from any operations function.
Without them, TA looks reactive in executive forums.
Common mistakes and misconceptions about req management
- Treating req management as administrative — It’s an operational discipline that directly affects throughput. Functions that treat it as paperwork end up with portfolios that move at the pace of individual recruiter motivation rather than at the pace business needs.
- Reviewing only at quarter-end — Quarterly review is far too slow to catch aging reqs while they’re still fixable. Weekly cadence is the operating standard for active req management.
- Letting reqs sit on hold indefinitely — Reqs paused for legitimate business reasons should still get reviewed — every month, the question “do we still want this open?” should be asked. Without review, on-hold reqs accumulate as portfolio noise.
- Failing to escalate — Reqs that have stalled for 90+ days because of business-side issues (hiring manager unresponsive, scope unresolved, comp band insufficient) need escalation to the business, not more recruiting effort. Escalation discipline is what surfaces business-side problems clearly.
- Confusing req management with req prioritisation — Both matter; they’re different. Prioritisation decides which reqs get most attention. Management is the day-to-day operational running of the portfolio after prioritisation. Strong functions do both.
Frequently asked questions
What is req management?
Req management is the operational discipline of tracking, prioritising, and progressing the active requisition portfolio — keeping reqs moving, surfacing aging searches, and aligning recruiter capacity with business demand. At any given time, a TA function is carrying a portfolio of active reqs at different stages — newly approved, in early sourcing, in active interviewing, at offer stage, on hold.
What's the difference between req management and req prioritisation?
Req prioritisation decides which reqs get the most recruiter attention based on strategic importance, urgency, and constraints. Req management is the ongoing operational practice of running the active req portfolio — tracking aging, rebalancing recruiter loads, escalating risks. Prioritisation is strategy; management is operations.
How often should the req portfolio be reviewed?
Weekly at the operational level for individual req tracking and recruiter rebalancing, monthly at the team level for trend analysis and aging-req escalation, and quarterly at the leadership level for portfolio health and capacity planning. Quarterly-only review is too slow to catch problems while they're fixable.
What metrics matter most for req management?
Active req count, aging-req distribution (how many reqs are 30/60/90+ days open), req-to-recruiter ratio, fill rate within target time windows, and req status mix (early sourcing vs active interviewing vs offer-stage vs on-hold). The combination tells the story of whether the portfolio is healthy or at risk.
Who owns req management?
TA operations or recruiter team leads typically own portfolio-level req management. Individual recruiters own their own active reqs. Without explicit ownership at both levels, the portfolio drifts and individual reqs go quiet without anyone noticing until time-to-fill data surfaces the problem weeks later.