You're not drowning in candidates. You're drowning in reqs.

The average recruiter is carrying 10–15 open roles at once. Backend, Sales, a Designer, a PM you're covering for another team, two that are "urgent, like yesterday."

They all pour into one inbox. One brain. One vague gut-check: is this person good?

Good for which role? You never get to ask.

In 2026, AI made having a pile of CVs cheap. The expensive thing now isn't volume — it's precision, one role at a time. You're not losing because you have too few candidates. You're losing because every role runs on the same criteria.

Why more roles make you screen worse

One role is easy to focus on. Twelve at once, and your brain quietly merges them into one.

And once they merge, you judge Role B's candidate with Role A's ruler.

Every role shares one ruler

Backend needs depth. Sales needs grit. Design needs a portfolio. But when 40 CVs land in an afternoon, you filter all of them with a single reflex: looks fine?

Fine for what? No time to ask.

So the specialist who would be a great Backend hire gets waved through on the same three-second glance as a junior Sales CV. Same bar, wrong role.

No role has a home

CVs live in your inbox, in a chat thread, in a spreadsheet called hiring_final_v3, in a message a hiring manager sent at 11pm.

No role has its own place. So no role gets handled properly.

Good people fall into the gaps between roles

You know this one. You're heads-down on the "urgent" req. Someone perfect for a different role applies. You glance, think "not for the one I'm on," and move on.

Three weeks later you open that exact role — and start sourcing from zero, when the right person already knocked.

Last week you had six roles open. Senior Backend Java was on fire, so it ate your week. 50 CVs in three days, screened while you fielded questions from the other five roles' hiring managers.

Backend shortlist? Decent. The other five? "Tomorrow." Tomorrow never came.

You're not managing twelve roles. You're holding twelve roles in one basket, hoping none drop. The basket's full. They all drop.

The fix: one role, one system — the 3 C's

Good news: you don't need fewer roles. You need to give each role a place to stand before candidates arrive.

Call it the 3 C's. You can run it in a Google Sheet — the principle is what matters.

The work isn't screening harder. It's deciding what each role actually needs before the flood starts.

Criteria

Before the first CV lands, write down for each role:

• 3 real must-haves
• 2 nice-to-haves
• 1 instant dealbreaker

One set per role. Never recycled. "Looks fine" isn't criteria — it's a feeling.

Container

Each role gets its own space. Backend CVs don't sit in the same pile as Sales CVs.

When someone great applies to the wrong role, you don't drop them — you move them to their room. Nobody falls into the gaps.

Cadence

Each role gets its own rhythm to track: which is waiting on feedback, which has a shortlist, which has gone quiet for five days.

You look role by role, not at one undifferentiated heap.

The role that has gone silent isn't dead. It's just the one you forgot to look at.

Precision over scale isn't a slogan. It just means every role gets hired as if it's the only role you're hiring.

The Knoot Angle

Now that AI has made "lots of CVs" ordinary, a recruiter's edge isn't how much they can process — it's how precisely each role gets handled.

Every role is different. Your screening criteria should be too.

If your roles are all running out of one inbox, Knoot's Job Management module is built for exactly this part:

• Every role is its own job: create and manage many roles at once without one burying another.
• Scoring criteria per role: set the must-haves and dealbreakers for that specific role, not a shared list.
• Track candidates by job: see who's where and which role is stuck — by position, not by digging through an inbox.

And those per-role criteria should start with

the JD itself

— where most of the drift begins.

One inbox can't hold twelve roles. Give each one its own room.