← all playbooks

Score one candidate against every open role in your ATS

One candidate ranked against every live role in your ATS, with the evidence quoted per role and the must-haves they miss stated plainly, so a good applicant to the wrong job is not lost.

use when
a strong applicant comes in for the wrong job, and your team is working dozens of other roles they might fit
starts from
A candidate

The prompt

Paste it into Claude Code or the Claude desktop app with Hyreflow connected. The first line tells your agent to use Hyreflow, so it reads the play, asks before it spends anything, and hands the work back to you.

paste this into Claude
Use hyreflow and score this candidate against every open role in my ATS, not just the one they applied to.

The candidate: <ATTACH THE CV, OR PASTE THE LINKEDIN PROFILE URL>. They
applied to <ROLE_THEY_APPLIED_TO>.

- Read every live job in my ATS. Skip anything closed, on hold or filled.
- Score the candidate against each role on its must-haves, and quote the
  line from the CV or profile that supports each point. If a must-have is
  missing, say so plainly. Do not round a near miss up to a fit.
- If they are already in my database, read my notes and their history
  with us, and use it.
- Show me the top <N> roles with the reasoning, and tell me honestly if
  none of them fit.

Score five roles first and tell me what the full run costs before you do
the rest. Do not add them to any job. Show me the changes before you
write to the ATS, and wait for my go-ahead.

Replace every <PLACEHOLDER> with your own detail. Everything else can stay as written.

What you need first

  • A connected ATS or recruitment CRM with your live jobs in it
  • The candidate, as a CV file or a LinkedIn profile URL
  • Job records that carry a real spec, since a title on its own cannot be scored against

Tools it can reach for

The agent picks per step from what your workspace has. Nothing here is required by name.

What happens when you run it

Free steps are marked free. Anything that spends credits is marked, and the agent asks before the first paid run of any size.

  1. 1

    Read the candidate

    credits

    A CV is parsed into a structured profile: titles, hard skills, location, and what the person did at each employer. A LinkedIn URL is looked up for its dated work history instead, which is a paid lookup.

  2. 2

    Check what you already hold on them

    free

    If the person is already in your database, their notes, past applications and the stages they reached are read and carried into the scoring. It is your own data, so the read is free.

  3. 3

    Pull every live role

    free

    Open jobs are read from your ATS with their full specs, not just their titles. Closed, filled and on-hold jobs are left out where your system records that status.

  4. 4

    Score the candidate against each role

    credits

    One candidate, many jobs. Each role gets a score weighted towards its must-haves and reasoned from the dated work history, not the current title, with location and seniority taken into account.

  5. 5

    Rank the roles, with evidence and gaps

    free

    Every score comes with the strengths it rests on and the gaps it found. A missing core must-have caps the score for that role however good the rest looks, and the gap is named rather than buried.

  6. 6

    Say so when nothing fits

    free

    If no live role is a real fit, the play says that instead of promoting the least bad option. A strong candidate with no role to go to is the starting point for a spec campaign, which is a separate play.

  7. 7

    Link the candidate to the job, once you approve

    free

    Adding someone to a job's pipeline is a write to a live system your colleagues work in. It is proposed and shown to you, and it happens only on your go-ahead.

What a run costs

Credits are spent per role the play actually works, and a lookup that finds nothing usually costs nothing. The two figures are the run where the first provider answers and the run where every lookup walks its full chain.

rolesif the first provider answersif every lookup walks the chain
25under $10.1 creditsunder $10.7 credits
100under $10.1 creditsunder $10.7 credits
500under $10.1 creditsunder $10.7 credits
1,000under $10.1 creditsunder $10.7 credits

Free before anything is charged

  • Check what you already hold on them
  • Pull every live role
  • Rank the roles, with evidence and gaps
  • Say so when nothing fits
  • Link the candidate to the job, once you approve

What moves the number

  • Coverage on work history. The chain stops at the first provider that answers, and only that provider bills.
  • How many roles survive the free filters. Everything dropped before the paid steps costs nothing.
  • The scoring and drafting steps run on the metered agent, charged on what they read and write rather than per role, so they sit outside this table.
  • Providers you connect with your own key. Those calls bill your account, not your credits.

An estimate, not a quote, priced at the volume credit rate. Your agent sizes the run against your own workspace and tells you what it will cost before it spends anything.

The good applicant to the wrong job

Inbound CVs get read against the job they were sent for, by the consultant who owns that job. If the fit is wrong, the CV is rejected or parked, and the three other roles it would have suited never hear about it. That is not carelessness. With dozens of roles open across a team, nobody holds every spec in their head, and nobody has the time to check one applicant against all of them.

This play is the inverse of find the candidates already in your ATS. That one takes a single role to many candidates. This one takes a single candidate to every live role, and most of the work is a free read of your own system.

What you get back

A ranked list of your live roles for this candidate: the role, the client, the score, the lines from the CV or profile that support it, and the must-haves that are missing. Roles that were ruled out are listed with the reason, so you can see that they were considered. If the person is already in your database, their history with you sits alongside. Any change to the ATS is a proposal waiting for your approval.

Variations worth knowing

Nothing fits. A strong candidate with no live role is not a dead end. The next step is to spec the candidate out to companies that should want them.

A day's applicants at once. The same scoring runs across a batch of inbound CVs. The work grows with candidates multiplied by roles, so the pilot and the cost check matter more, not less.

A profile instead of a CV. A LinkedIn URL works as the starting point. The dated work history is looked up first, because a current title and employer on their own cannot evidence a years-of-experience requirement.

Where this goes wrong

Thin job records. A job that is a title and two lines cannot be scored against. The play says which roles it could not assess properly instead of guessing at them.

Open jobs that are not really open. A role nobody closed in the ATS gets scored as live. That is a data hygiene problem, and this play keeps surfacing it until it is fixed.

Scanned and designed CVs. A CV with no text layer, such as a scan or a design-tool export, is read as an image instead. It works, but check the parsed profile on those before you trust the scores.

Rounding up. A near miss presented as a fit costs you credibility with the client. The missing must-have stays visible and holds the score down, which is the behaviour you want even when it is inconvenient.

Protected attributes. Age, gender, marital status and similar details are never scored on, whatever a CV or a custom field happens to contain.

Questions

My ATS already suggests matching jobs. How is this different?

A built-in matcher compares words. This reads the candidate's dated work history against each role's must-haves and tells you why: which line in the CV supports the point, how many years of relevant experience the dates actually show, and which requirement is missing. You can disagree with a reasoned score. You cannot argue with a percentage that came from nowhere.

What does it cost to score one candidate against forty roles?

Reading your jobs and your own records is free, because it is your data. The judgement is the metered part, and it grows with the number of roles. That is why the play scores a handful first and tells you what the rest will cost before it carries on.

Will it tell me when the candidate fits nothing?

Yes, and that is a result rather than a failure. Forcing a good person into a poor fit wastes a client's time and the candidate's goodwill. If they are strong and nothing live suits them, the sensible next step is to take them to market yourself.

Will it move the candidate in my ATS?

Not unless you approve it. The play ranks and explains, then proposes the link. Recruit CRM, JobAdder, Recruiterflow, Atlas and Loxo support adding a candidate to a job this way. Where the connection to your system does not, you get the ranked list and make the move yourself.

Can this run on every inbound CV automatically?

Yes, once you have run it manually and trust the shape of the output. It converts naturally into a scheduled workflow that scores incoming applicants against your live roles and puts the suggested redirects in front of you. Prove it by hand first, because scoring that runs unattended against thin job specs produces confident nonsense at volume.