A candidate match score is a starting point, not a verdict. It tells you how well a candidate lines up with a job description on paper. It can't tell you whether the job description is right, and that gap between the score and your gut is often the most useful thing on the screen.
We built match scoring into Agency+. It reads the JD, pulls from what we know about the candidate, and gives you a number. Then we tell recruiters the same thing every time: the number is not the answer.
What does a candidate match score actually measure?
A match score measures how closely a candidate's background lines up with the requirements written in a job description. That's it. It compares two documents.
It doesn't know the hiring manager. It doesn't know the last three people who got rejected and why. It doesn't know that the client wrote "10 years of experience" when they'd happily take someone with six.
The platform does the matching. You bring the context the platform can't know.
What should a recruiter do when a match score looks too low?
Treat it as a question, not a rejection. If a candidate scores a 73 against an open role but your experience says they should be a 95, don't override the number and move on. Figure out why the two disagree.
Clark Willcox made this point during our launch session and it's worth repeating. That gap is information.
Usually one of two things is going on:
- The JD is off. It's asking for something the role doesn't actually need, or it's written so narrowly that it screens out people who'd do the job well.
- The company is asking for something the market doesn't have. The requirements describe a candidate who barely exists at that price or in that location.
Either way, you just found a reason to pick up the phone.
Why is a score-versus-gut gap a good reason to call the client?
Because it lets you open with insight instead of a pitch. Every hiring manager gets "I have a great candidate for you." Almost none of them get a recruiter who noticed something about their role.
Compare these two first messages.
The vendor version: "I have a great candidate for your open role."
The partner version: "I noticed this role's been open a while. Your JD is asking for X, but most companies in your market are hiring for Y. That might be part of the problem."
The second one gets a reply. It positions you as someone who understands the market, not someone hunting for a fee. If you've ever wondered why hiring managers treat agencies like vendors, this is a big piece of it.
Should recruiters trust AI candidate matching?
Trust it to do the reading. Don't trust it to make the decision. Matching software is good at the part humans hate: scanning a JD, scanning a database, and surfacing people you'd have forgotten about. It's bad at knowing why a role has been open for 90 days.
That's the split we care about at PerfectHire. Software handles the busywork. The recruiter handles the judgment, the relationship and the call.
A lot of ATS vendors sell a score like it's the finish line. A single number that says "hire this one." We think that's backwards. Recruiting is still a relationship business, and a score that pretends otherwise just makes recruiters stop thinking.
How do you use a match score without letting it replace your judgment?
Use the score to sort, and use your experience to decide. Here's the simple version:
- Let the score surface candidates you might have missed, especially people already sitting in your database.
- When the score and your gut agree, move fast.
- When they disagree, stop and ask what the JD is really saying.
- If the JD looks wrong, that's your opening with the client.
The point of matching isn't to remove the recruiter from the decision. It's to give a good recruiter a better starting line and more time for the conversations that create placements. That's the same reason we built Conduit, the AI backbone behind the platform, to support recruiters rather than replace them.
Frequently Asked Questions
What is a candidate match score?
A candidate match score is a number that shows how well a candidate's background fits the requirements in a job description. In Agency+, it reads the JD and what the platform knows about the candidate to produce that score. It's a sorting tool, not a hiring decision.
Why would a good candidate get a low match score?
Most often, the job description is the problem. It may list requirements the role doesn't need, or ask for a mix of skills the market doesn't have. A low score on a candidate you know is strong is worth investigating before you dismiss it.
Can a match score gap help me win more client business?
Yes. If a candidate you'd rate a 95 scores a 73, the difference usually points to a JD issue or an unrealistic requirement. Raising that with the client shows you understand their market and gives you a much stronger first message than a generic candidate pitch.
Should AI make the final call on which candidate to submit?
No. AI is good at matching and surfacing candidates, but it doesn't know client history, hiring manager preferences or market context. At PerfectHire, we build Agency+ so the platform does the matching and the recruiter makes the call.
How does Agency+ use match scoring?
Agency+ scores each candidate against a role by reading the job description and the candidate information already in your system. The score helps you decide who to call first, and the gap between the score and your own read shows you where to dig deeper. See the ATS+ page or book a demo to see it in action.