Most agencies screen 200 CVs to make a shortlist of six, then let the other 194 disappear into "rejected" status in the ATS. That's a mistake — a properly screened CV holds skills data, salary expectations, and availability that stays useful for months. The fix isn't screening harder. It's tagging what you already learned and filing it somewhere you'll actually search again.

It's Monday morning. You've got a new brief for a mid-level project manager, a live construction role that's been open two weeks, and a client chasing you for feedback on candidates you sent Thursday. The PM brief lands with 200 applications by lunchtime and the client wants a shortlist by Wednesday. You screen, you shortlist six, you send them off. The other 194 get marked "rejected" and vanish into the ATS. Three weeks later, a near-identical PM role comes in from a different client — and you start from zero again, screening 200 more CVs, several of whom you've already seen.

Where the process actually breaks down

The failure isn't the screening — it's what happens to the screening data afterwards. An experienced recruiter spends roughly five to seven minutes on a genuine first-pass read of a CV: skills match, experience level, red flags, gaps. Across 200 applications, that's 16 to 23 hours of judgment applied to a single role. Then 97% of that judgment gets thrown away, because "rejected" in most ATS setups is a dead end rather than a category.

The gap isn't just wasted hours, it's wasted intelligence. A candidate who scored 78% against a brief wasn't a bad candidate — they were the wrong candidate for that specific role, at that specific time. Maybe they were overqualified, maybe the salary band didn't match, maybe your client wanted five years' experience and they had three. None of that makes them unplaceable. It makes them a fit for something else, and without tagging at the point of screening, that nuance disappears the moment the role closes. Six months later, when a similar brief lands, the recruiter working it has no way of knowing that candidate exists — so the desk pays for the same screening hours twice.

Build the pool at the point of screening, not after

The trick is capturing the categorisation while the AI screening data is still live, not trying to reconstruct it later. Here's a workable framework:

Step 1 — Screen against the brief, but keep the score. When you run CVs through AI screening, don't just take the pass/fail line for this role. Keep the match percentage and the reasoning behind it (which skills matched, which didn't, what the tool flagged as a gap). This is the raw material for every future tag.

Step 2 — Sort into reactivation categories, not just "reject." Instead of one bucket, use three or four: Near-miss (70–85% match, right skills, wrong timing or seniority), Different-role-fit (strong skills that suit a different brief entirely — a screened PM candidate who's actually a stronger fit for change management), Future-fit (junior or transitioning candidates worth revisiting in 6–12 months), and Do-not-contact (screened out for a real reason — won't relocate, salary floor way off, unresponsive).

Step 3 — Tag on searchable fields, not free text. Location, salary band, notice period, core skill cluster, and screening score. Free-text notes don't surface in a search six months later; structured tags do. This is the step most agencies skip, and it's the one that makes the pool actually usable rather than just archived.

Step 4 — Set a review trigger. Every time a new brief comes in, search the reject pool against it before you open the fresh CV pile. This is where CV Matcher earns its keep beyond the initial screen — because it's already scored and tagged the candidates, searching your existing pool against a new brief takes minutes, not hours. If you're not already running screening through a tool that keeps this data structured, that's worth fixing before you build the pool on top of it — you can Start Free Trial and see how the tagging holds up against a real brief.

What the algorithm still can't tell you

None of this replaces the qualification call — it just means fewer calls get wasted on the wrong candidates. A screening score tells you a candidate matches on paper. It doesn't tell you why they left their last role, whether they're actually open to contract work or just said so to keep options open, or whether their salary expectation is a hard floor or an opening position. A 20-minute call surfaces motivation, notice period reality (as opposed to what's on the CV), and whether someone tagged as "near-miss" six months ago has since picked up exactly the skill gap that ruled them out last time. Before reactivating anyone from the pool, that call still happens — the tagging just tells you who's worth calling first.

What to do with the next role

On your next brief, before you archive the CVs that don't make the shortlist, spend ten minutes tagging the near-misses and different-role-fits before you close the req. Don't try to retrofit your whole database at once — start with one role, build the habit of tagging at the point of rejection, and search that pool the next time a similar brief lands. The value compounds fast: after three or four roles in the same skill area, you'll have a pool worth searching before you open a single new CV.