How to prioritize open requisitions when you cannot work them all well

Prioritizing open requisitions means ranking them by a consistent set of factors — fee or business impact, fill difficulty, hiring manager engagement, and urgency — rather than working every open role a little bit each day. A recruiter with fifteen open reqs who splits attention evenly across all of them usually fills none of them fast and several of them poorly. Below is a five-factor scoring rubric, a worked example ranking five requisitions, and how to tell a hiring manager their role dropped in priority without damaging the relationship.

Why "work every req a little" is the wrong default

Splitting attention evenly feels fair, because every hiring manager gets some time. In practice it means every search moves at the slowest possible pace, because none of them ever gets the sustained block of sourcing and screening time that actually moves a search forward. A req that needs eight focused hours to find the right candidate gets forty-five minutes a day for three weeks instead, and forty-five minutes a day rarely compounds into the same result as eight hours at once.

Prioritizing is not about ignoring the lower-ranked reqs. It is about deciding, deliberately, which ones get the focused time this week and which ones get maintenance-level attention — candidates already in process kept moving, but no new sourcing push — until their priority rises.

This is uncomfortable for a lot of recruiters, because it feels like admitting some reqs are being worked less hard than the hiring manager expects. The alternative is worse: every req worked equally badly, with no visible ranking anyone could question or push back on, which tends to produce the same outcome with none of the transparency.

Five factors that should decide priority

• Fee or business impact. What the role is worth financially, or how much the business is blocked by it staying open. A role blocking a product launch outranks one that is simply nice to fill sooner.
• Fill difficulty. A narrow, hard-to-source role needs more concentrated time per week to make progress at all; a role with a deep candidate pool can tolerate lighter, steadier attention.
• Hiring manager engagement. A manager who reviews submittals within a day and gives specific feedback lets a search move as fast as you can source. A manager who takes two weeks to respond caps the pace regardless of how much recruiter effort goes in.
• Urgency and deadline. A real, business-driven deadline (a team launching a project, a backfill for someone leaving on a known date) outweighs a vague "as soon as possible" with no actual date behind it.
• Risk of losing the requisition entirely. Budget that could get pulled, a reorg in progress, or a hiring manager whose own role is uncertain. Time spent on a req that gets cancelled next month is time that produced nothing.

A scoring rubric you can use this week

Score each open requisition from 0 to 3 on every row, for a maximum of 15. Re-score weekly rather than treating the first score as permanent.

Worked example: ranking five open requisitions

Invented scores for five roles on one recruiter's desk this week:

Ranked by total: Senior Backend Engineer (14) gets this week's focused sourcing block, Customer Success Manager (11) next, then Warehouse Supervisor (8) and Data Analyst (7) at maintenance level, and Marketing Coordinator (4) gets candidates-in-process kept moving only, with no new sourcing until either its manager engages more or a deadline appears. Notice that urgency alone did not decide the order: Customer Success Manager scored the highest single urgency point but ranked below Senior Backend Engineer once difficulty and manager engagement were counted.

Re-scoring on a schedule, not just once

A priority list from three weeks ago is not a priority list, it is a historical record. Rescore every open requisition on a fixed day each week — Monday morning works well, before the week's time gets allocated — using that week's actual signals: did the hiring manager respond to last week's submittals, did a deadline move, did a leading candidate mention a competing offer. A requisition that scored low three weeks ago because the manager was unresponsive can jump to the top the moment that changes, and the schedule is what catches it.

Telling hiring managers their req dropped in priority

The conversation goes better when it is specific and forward-looking rather than an apology. Avoid vague language like "we're just really busy right now," which sounds like an excuse and gives the manager nothing to act on.

"I want to be straight with you on where this role sits this week.
Compared to the other open roles I'm working, [reason — e.g. 'the
candidate pool here is deeper, so I can make progress with lighter,
steady time'] means I'm putting concentrated hours into [other role]
first. I'm keeping [candidates already in process] moving on yours,
and here's what would move it up: [specific, actionable trigger —
e.g. a firmer deadline, faster feedback turnaround, more flexibility
on one must-have]."

This does two things: it treats the manager as someone who can act on the information, and it names the specific lever that would change the priority, which is more useful to them than a general promise to "get to it soon." Setting these expectations up front, ideally during the intake meeting, prevents the conversation from feeling like a surprise later.

Signals that a requisition should be paused, not deprioritized

Some reqs are not low priority, they are not ready to be worked at all. Watch for: a hiring manager who cannot articulate must-haves beyond a job title, a budget that has not actually been approved, or requirements that have changed twice already in two weeks. Working a search like this at any priority level burns candidate goodwill on a role that is not stable enough to close. Flag it explicitly as paused, with what needs to happen before it reopens, rather than quietly starving it of attention while it stays listed as active.

Pausing openly also protects candidates already in the pipeline. Someone who interviewed for a role that turns out to be unfunded deserves to hear that directly rather than experience it as the process simply going silent. A short, honest note, along the lines of "this search is on hold while we confirm budget, and I will update you the moment that is resolved," costs little and keeps the candidate relationship intact for whenever the role does reopen, or for a different role entirely.

Keeping the bottom of the list from rotting

A requisition that sits at the bottom of the priority list for months either genuinely does not matter — in which case it should be closed, not left open — or it matters more than its current score suggests and needs a real conversation with the hiring manager about what changed. Review the bottom of the list monthly with exactly that question: is this still open because it is truly lower priority, or because nobody has revisited why it dropped there in the first place.

Mistakes that make a priority list stop working

Most of these mistakes share a root cause: the list existed once, as a good exercise, but stopped being a living document. A scoring rubric only earns its keep if it gets used the same way, on the same schedule, even in a week where nothing seems to have changed. The weeks where nothing seems to have changed are usually the weeks something changed quietly enough that only the rescore would have caught it.