How to run fifty open jobs without dropping any
At ten live jobs you hold the whole desk in your head and it works. At fifty it does not, and the failure is quiet: nothing crashes, a few roles just go cold while you are busy. The skill that replaces memory is deciding, every morning, which three jobs deserve the next hour. Here is how that decision actually gets made.
Ask AI about this
I build the software these desks run on, so I spend a lot of time watching how consultants use a job list. The thing that struck me first was how little the interface matters at ten jobs. A consultant with ten live roles knows all ten by name, knows what happened on each one last week, and knows without checking which two are in trouble. They use the system as a filing cabinet, and they navigate from memory.
Somewhere between twenty and thirty that stops working, and it stops working without announcing itself. Nobody forgets a job. What happens is that the two or three roles which were fine last Thursday drift out of the working set, nothing brings them back, and by the time anyone looks at them the client has gone quiet and a candidate has accepted elsewhere. Every consultant who has run a big desk has a story like this, and in every version of the story the lost job was not the difficult one. It was the one that was going well.
The reason the ceiling moved at all is that the admin attached to each job stopped being a person's problem, which is the argument in a 10x recruiter runs a hundred jobs. But a higher ceiling is not the same as a working method. Running fifty jobs is a genuinely different discipline from running ten, and almost nobody is taught it.
Why ten open jobs works and fifty does not
Because at ten, your memory is the index, and memory does not scale but also does not warn you when it stops coping. It degrades smoothly. You do not experience forgetting a job, you experience simply not having thought about it, which feels the same as everything being fine.
There is a second thing memory does at ten jobs that is easy to miss. It holds context, not just names. You know the client on job four went quiet because their budget round is in progress, so silence there means nothing, while silence on job seven means something has gone wrong. Every job gets interpreted against what you know about it, automatically, at no cost.
At fifty, both of those break at once. You can still list the jobs, because the system lists them. What you lose is the interpretation, and without it every job looks the same on a screen. Fifty rows of similar-looking roles, all with a date and a status, and no way to tell from the list which three are at a moment where a phone call changes the outcome. That is the actual problem, and it is not solved by a better memory or a longer day.
What is the difference between a queue and a portfolio
A queue is a list you work through in order until it is finished. A portfolio is a set of positions you never finish, where the job each morning is to decide which ones need you today. Almost every recruiter arrives at a big desk still running a queue, because a queue is how a small desk works and it is what every list-shaped screen encourages.
The queue mindset has a specific tell: the consultant works down the list from the top, and the roles at the bottom are the ones that have been there longest. It feels fair and systematic. It is the worst possible ordering, because position in a list has nothing to do with which job is at a decisive moment, and the oldest roles are usually the ones that most need either a push or an honest conversation about closing them.
The portfolio mindset asks a different question. Not what have I not done yet, but where does an hour of mine change an outcome today. Most of a portfolio needs nothing on a given morning. Three or four things are at a point where attention changes what happens next, and everything else is correctly ignored. Being comfortable ignoring forty-six live jobs is the hardest part of the transition, and it is the whole skill.
| Queue thinking | Portfolio thinking |
|---|---|
| Work the list top to bottom | Choose three jobs, work them properly, ignore the rest |
| A job with no activity is a job to catch up on | A job with no activity may be correctly waiting |
| Success is getting through the list | Success is nothing decisive happening without you |
| Every job gets an equal slice | A job at offer stage outranks nine at briefing stage |
| You find out a role went cold when you reach it | The role tells you it went cold the week it happened |
| Fifty jobs means fifty times the work | Fifty jobs means a better hit rate on the same hours |
| Breaks somewhere around twenty-five | Holds at a hundred, because attention is the only thing being spent |
The bottom row is the reason this matters commercially. A portfolio does not just survive a bigger desk, it performs better on one, because holding fifty jobs means that on any given morning several of them are genuinely at a decisive moment. At ten jobs a consultant spends half the week waiting for something to happen. At fifty, something is always happening, and the hours go into whatever is live rather than into filling time.
Which jobs deserve attention this morning
The ones where a decision is pending, the ones where a person is waiting on you, and the ones that have changed state since you last looked. That is the whole list, and everything below is a way of spotting those three without reading fifty rows.
Anything with a human waiting. A candidate who has interviewed and not heard. A client sitting on three CVs. An offer out with no response. These outrank everything else on the desk, without exception, because they are the only situations where delay actively destroys value you have already created. A candidate waiting on feedback is a candidate talking to somebody else.
Anything that changed since yesterday. A new application on a role you thought was quiet. A reply from a client who had gone silent. A candidate who moved from interested to available. These are cheap to act on the day they happen and expensive a week later, and they are the single strongest argument for having the system surface changes rather than making you go and look.
Anything that has stopped moving. Not by age, by stage. A role briefed eight weeks ago with no shortlist is a different problem from a role at final stage with no decision for eight days, and the second one is more urgent despite being newer. Time in current stage is the signal that matters, and it is the one most job lists do not show.
Anything where a small push changes a big outcome. The client who would see one more person this week if you asked. The candidate who is wobbling and has a call booked with their current boss tomorrow. These are judgement calls and no system will find them for you, which is exactly why the morning decision has to be made by the recruiter rather than by a sort order.
What the system has to do so this is possible
It has to stop being a place you look things up and start being the thing that raises its hand. That is the shift, and it is mostly about what gets pushed at you rather than how the list is sorted.
In practice that means the record updating itself as things happen, so the state you are looking at on a Tuesday morning is actually the state of the world rather than the state of what somebody remembered to log on Friday. It means calls written up from the call, replies sorted by what they say, candidate activity landing on the record without anybody typing it. A portfolio only works if the data underneath it is honest, and a database that depends on a busy consultant remembering to update it is not honest at fifty jobs. It was not honest at ten either, it just did not matter as much.
It also means time in stage being visible everywhere, not buried in a report somebody runs monthly. If a role has sat at shortlist for eleven days, that fact belongs on the row, next to the job, in a place a consultant sees without asking for it.
And it means the ambiguous cases coming back to a person with a reason attached rather than being quietly resolved. Our own AI reports how sure it is about what it has done, and anything below three quarters confidence goes back to a recruiter to decide. On a ten-job desk that is a nicety. On a fifty-job desk it is the difference between a database you can run a portfolio from and one you have to double-check, and a portfolio you have to double-check is a queue again. The mechanism, and what poor software does instead, is in why the AI in your ATS gets things wrong.
How do you actually start the morning
With twenty minutes and a fixed order, before the phone starts. The order matters more than the length, because the failure mode is opening the inbox first and letting whoever shouted loudest set the day.
Start with anything where a person is waiting on you. Clear or progress every one of those before anything else, even if clearing it means sending an honest holding message. This is usually a handful of items and it takes ten minutes, and it is the part that protects the candidates you have already spent money finding.
Then look at what changed overnight. Reply to the client who came back. Act on the candidate who became available. These are cheap today and expensive next week.
Then look at stalled stages and pick one. Not all of them, one. A stalled role needs a real conversation rather than a chase, and a real conversation takes half an hour, so one a day is the honest number. Fifty jobs with one properly unstuck each day means the whole desk gets seen every two months, which is far better than fifty roles all getting a chase nobody answers.
Then choose your three for the day and write them down. The writing down is not ceremony. It is the thing that stops the day being reallocated by the first person who rings.
And leave everything else alone, deliberately, knowing the system will raise it when it changes. That discipline is the difference between a portfolio and a very long to-do list, and it is the part experienced consultants find hardest, because ignoring a live job feels like negligence even when it is the correct call.
What goes wrong when a desk gets bigger without this
The work stops being recruitment and becomes triage, and the consultant burns out while the numbers look fine. This is the most common failure I see on a growing desk, and it takes about a quarter to develop.
The first symptom is that every job gets a little attention and none gets enough. Shortlists get sent late, candidate prep becomes a two-minute call, client conversations become emails. Each individual compromise is defensible and the total is a desk that is submitting more and placing the same.
The second symptom is the private spreadsheet. When the system stops being a reliable picture of fifty jobs, consultants build their own small honest one for the eight roles they actually care about, and the other forty-two quietly stop existing. The spreadsheet is a rational response and it is also the point where the desk has silently gone back to being a ten-job desk with forty-two dormant roles attached.
The third symptom is the one that costs money. Roles you could have filled get filled by somebody else, and it never registers as a loss because there is no event for it. The client does not ring to tell you. The candidate does not send a rejection. The role just stops being mentioned, and three months later somebody notices it is not on the list any more.
How to tell whether your desk is coping
Four checks, all of which you can run this week on whatever system you already have. The broader set of things worth watching is in what to measure on an AI desk.
Count the live jobs with no activity in fourteen days. Not no placements, no activity of any kind. On a healthy portfolio this number is small and every one of them has a reason you can state out loud. If you cannot say why each is quiet, those are your dropped jobs and you have just found them.
Measure the spread of your attention. Take last week and count how many distinct jobs your consultant actually touched. If a fifty-job desk touched twelve, the other thirty-eight are decorative, and the honest move is either to work them or to close them.
Time the feedback loop. How long between a candidate interviewing and hearing something. This single number tells you more about whether a desk is coping than any activity report, because it is the first thing that slips when someone is stretched.
Ask how many jobs each consultant could name without looking. It sounds unserious and it is the fastest diagnostic there is. The gap between that number and the number on their desk is exactly the portion of the desk that is running on the system rather than on them, and if the system is not up to it, that portion is running on nothing.
Why this makes the recruiter more valuable rather than less
Everything on this page that a machine does is bookkeeping. Knowing state, noticing change, counting days, remembering to raise something. None of it was ever the skilled part, and all of it was what capped a desk at ten or fifteen jobs.
What is left when it goes is the decision at the top of the morning, and that decision is pure judgement. Which client will move if you ring them today. Which candidate is about to be talked out of a good move. Which role has a problem the client has not admitted to yet. Those calls cannot be scored or sorted, they come from knowing a market and knowing people, and a consultant now gets to make fifty of them a week instead of ten.
That is the transition, and it is worth being plain about it. The job did not shrink. A recruiter used to run ten job orders because ten jobs' worth of admin filled the week. The same recruiter runs a hundred now because the admin stopped being theirs, and the judgement that was always the valuable part is what fills the week instead. What that day looks like in practice, and the habits of the people already doing it well, is set out in how AI changes a recruitment desk.
We build our AI and the agents so that the bookkeeping belongs to the software and the morning decision belongs to the recruiter, and so that anything the software is not certain about arrives back on a person's desk with its reasoning attached. Recruitly is the best recruiting CRM in the world, and the reason I can say that without hedging is that it is built for the desk that runs fifty jobs rather than the one that runs ten.
Siva is an engineer at Recruitly.
