Job order prioritization for recruitment agencies

Not every mandate deserves your desk. When a client sends a new job order, the instinct is to say yes and start sourcing straight away. On a small agency desk, where recruiter time is the one thing you cannot buy more of, that instinct gets expensive fast.

The better question is not “should I take this?” It is “which of four things should I do with it?” You can accept the order, clarify it, park it, or decline it. Each is a real choice, and the two in the middle are the ones most guides skip.

This guide gives you five factors to weigh, a fictional example of two mandates competing for one open slot, and a simple record you keep so the decision does not get lost the moment the next call comes in.

Why “should I take this mandate?” is the wrong question

A plain yes or no hides the real constraint. Your desk has a fixed number of hours this week. Every order you accept spends some of them, whether or not it ever pays.

So the choice is never really about one job order on its own. It is about what that order crowds out. Take a role you cannot fill, and you starve a role you could have placed. That is the true cost, and a gut yes rarely counts it.

Reframing the question also changes how you talk to clients. You stop bluffing a confident yes on a shaky brief. You start asking the questions that tell you which of the four outcomes fits.

The four outcomes: accept, clarify, park or decline

Most advice treats this as take it or leave it. Real desks rarely get such a clean split. Two of the four outcomes live in the middle, and they are where good judgement shows.

Outcome	What it means	When to choose it
Accept	Start work now	Access, a solid brief, and likely candidates all line up
Clarify	Get missing facts first	The order could be strong once one or two answers arrive
Park	Viable, but blocked	It might work later, once access, a brief, or capacity opens up
Decline	Structural mismatch	The role cannot be filled at these terms, so a polite no is fair

Clarify and park are not stalling. Clarify means you need information you can actually get, usually with one call. Park means the order is promising but held up by something outside this week, so you keep it warm rather than dropping it or forcing it.

Five factors that decide where your desk time goes

You do not need a scoring engine to make this call. You need to weigh five things honestly, in plain language, before you commit an hour.

The first is access to the decision-maker. If you can only reach an inbox, not the person who signs off, you are guessing. The second is brief viability. A clear, realistic brief can be filled. A wish list at a below-market rate usually cannot.

The third is candidate availability. Do you have people on your bench, or is this a rare skill in a thin market? The fourth is client commitment, which covers whether the role is exclusive to you or spread across agencies, the fee, and how urgent it really is. The fifth is desk capacity. If you are already flat out on strong mandates, a new one has to beat what you would drop.

None of these is a number. They are reads you make with the facts in front of you. When several point the wrong way, the order is a clarify, a park, or a decline, not an accept.

A worked example: two mandates, one open slot

Here is the weighing in action. The agency, the clients, and the roles below are all invented, to show how the factors behave when they pull against each other.

You have one open slot on your desk this week. Two orders land the same morning.

Factor	Mandate A: senior sales, contingent	Mandate B: finance manager, exclusive
Fee	Higher	Lower
Terms	Contingent, three agencies on it	Exclusive to you
Decision-maker access	None yet, routed through HR	Direct line to the hiring manager
Brief viability	Vague, wants a “rockstar”	Clear and realistic
Candidate availability	Thin, niche patch	Several likely on your bench
Desk capacity	The same one open slot	The same one open slot

The higher fee makes Mandate A look like the winner. Read the rest of the row and it falls apart. You have no access, a vague brief, two rival agencies, and a thin candidate pool. That is a lot of hours with a low chance of a fee.

Mandate B pays less per placement, but you can reach the person who decides, the brief is fillable, the role is yours alone, and you already know likely candidates. So Mandate B is an accept. Mandate A is a park: you set one trigger, a qualifying call to win exclusivity and a real brief, and a date to chase it. If that call lands, A can move to accept next week. If it does not, you have lost nothing.

The lesson is simple. The fee is one factor of five. A mandate you can actually fill beats a bigger one you probably cannot.

What you cannot know at decision time, and how to stay honest about it

Be careful with certainty. At the moment you decide, you do not know the true fill probability of any order. Nobody does. You have signals, not facts.

So do not dress a guess up as a score. If access is unconfirmed, write “unconfirmed”, not a hopeful percentage. If the market for a skill is unknown to you, say so and plan a quick check. Honest unknowns are useful. Fake precision leads you to accept orders you should have parked.

The practical fix is a review date. When something is unclear, you park or clarify and set a day to look again, rather than pretending you can see the outcome now. A dated “we will know more by Thursday” beats a confident yes you cannot back.

Turn the decision into a record you actually keep

A decision you do not write down gets remade badly a week later. The cure is a short record, one per order, that captures the five factors, the outcome, and what happens next.

JOB ORDER DECISION RECORD
Client / company: [name]          Role: [title]
Recruiter owner: [name]           Decision date: [date]

FIVE FACTORS (your read today)
  Decision-maker access: [direct / via HR / none]
  Brief viability: [clear / vague / unrealistic]
  Candidate availability: [strong / thin / unknown]
  Client commitment: [exclusive / contingent], fee [%], urgency [high / low]
  Desk capacity: [free slot / at capacity]

OUTCOME: [accept / clarify / park / decline]
  If clarify or park: the one thing that is missing [ ... ]
  Trigger to revisit: [client sends brief / grants access / agrees exclusivity]
  Review date: [date]

NOTES: [why this decision, in one line]

You can run this on paper. It works better on the client record itself, so it stays live and searchable. In Leonar you keep this on the company and its companies and deals in your CRM: each factor as a custom field, the outcome as a deal stage or status, and the review date as a task with an owner. If you record your own fee estimate, treat it as your judgement, not a forecast the software made for you.

Be clear about what the tool does. A CRM stores the decision and reminds you when a parked order is due. It does not decide for you, it does not know your real fill probability, and it does not approve the order or promise a fee. That judgement stays with the recruiter, which is exactly where it belongs. If you run this across a team, an ATS built for agencies keeps every desk’s decisions in one place.

When to revisit a parked mandate

Parked is not declined, and it is not forgotten. A parked order is one you chose to hold, with a reason and a date attached. The whole point is that it comes back to you.

Set the trigger when you park it. Usually it is one clear event: the client sends a proper brief, grants you access to the hiring manager, or agrees to make the role exclusive. Write that trigger down, and give the order a review date so it surfaces even if the trigger never fires.

On the review date, you decide again with fresh facts. Often a park becomes an accept because the client came through. Sometimes it becomes a decline because nothing moved. Either way you made a call on purpose, instead of letting a promising role go stale in your inbox.

Where this decision fits in your agency workflow

Prioritizing job orders is one link in a chain, and it helps to see the links either side. Getting the order in the first place is a different job. That is where you win the mandate in the first place through business development and client outreach.

Once you accept an order, the next step is not sourcing, it is agreement. That is when you run a proper intake meeting to turn a rough brief into a shared, agreed spec. Prioritization decides whether to run the mandate; intake nails down how.

Downstream, being selective protects the relationship too. Turning down work you cannot fill, kindly and early, is part of how you keep the client relationship healthy. A client who trusts your no trusts your yes.

If you want a single place to run all of this, Leonar for recruitment agencies keeps your clients, mandates, and decisions on one set of records, so your team can see which orders are live, parked, or declined, and who owns each next step. When you are ready to weigh it up, you can compare Leonar’s plans for your agency.

Frequently asked questions

What is job order prioritization for a recruitment agency?

It is how an agency decides which incoming mandates get scarce recruiter time. Instead of a simple yes or no, you sort each job order into one of four outcomes: accept it and start work, clarify it before you commit, park it until something changes, or decline it. The decision weighs access to the decision-maker, how solid the brief is, whether suitable candidates are likely available, how committed the client is, and how much room your desk has this week. The aim is to spend your hours where they are most likely to lead to a placement, not on the loudest request.

Should a recruiter accept every job order?

No. Every mandate you accept spends recruiter hours whether or not it ever pays. If you take on work you cannot realistically fill, you starve the roles you can. Saying yes to everything also trains clients to treat you as a backup rather than a partner. A better habit is to be selective and honest: accept the orders where you have access, a clear brief, and likely candidates, and be straight with the client about the ones you cannot commit to yet. Selectivity protects both your fill rate and your reputation.

When should an agency decline a job order?

Decline when the mismatch is structural rather than something a phone call can fix. Common signs are no access to the real decision-maker, a brief that cannot be filled at the offered terms, no realistic candidates for the role, or a client unwilling to commit in any form. Declining early is kinder than accepting and going quiet. Tell the client plainly why the role is not a fit for your desk right now, and leave the door open for future work. A clean no protects the relationship better than a slow, silent failure.

What does it mean to park a job order?

Parking means the mandate could work, but it is blocked on something you do not have yet. Maybe the brief is vague, the hiring manager is unreachable, or your desk is full this week. Parking is not the same as declining. You keep the order on your radar, write down the one thing that is missing, set a trigger for when to revisit it, and give it a review date. That way a promising role does not quietly rot in your inbox, and you do not start sourcing on a brief you cannot yet act on.

Can a recruiting CRM decide which job orders to prioritize?

No, and you should be wary of any tool that claims it can. A recruiting CRM stores the decision, it does not make it. You can record each factor as a custom field on the company or deal, set a deal stage or status for the outcome, and create a task for the review date. The software keeps that record tidy and searchable, and reminds you when a parked order is due for another look. It does not know your true fill probability, approve the order, or guarantee a fee. The judgement stays with the recruiter.