All articles

How to explain a candidate score to a hiring manager

A match score only helps if you can say what is behind it. A simple structure for explaining any shortlist, with a message template you can reuse.

By Kevin Thibaut 6 min read

Most recruiters have had this conversation. You send a shortlist, the hiring manager opens the first profile, and the reply comes back within minutes: “Why is this person on the list?” If the only answer you have is “the system gave them 87%”, the shortlist has already lost some of its credibility.

A score is a summary. Hiring managers do not trust summaries they cannot unpack, and they are right not to. This article covers how to explain a candidate score so that it holds up in that conversation, whether the score comes from an AI matching tool, a scorecard your team fills in by hand, or your own judgement.

Why a single number is not enough

A single percentage hides the trade-offs that matter most to the person hiring. Two candidates can both score 80%. One meets every technical requirement but has never worked in a client-facing role. The other is a strong communicator who is missing one certification the team could fund in three months. These are different hiring decisions, and the number makes them look identical.

Hiring managers think in requirements and risks: “Can this person do the job, what will they need help with, and will they stay?” Your explanation should answer in the same terms.

Score by dimension, not overall

Start by splitting the assessment into a few dimensions that map to how the manager thinks. Four work well for most roles:

  • Hard skills: the technical requirements, tools, certifications and years of relevant experience.
  • Soft skills: communication, stakeholder management, leadership, the way they work with others.
  • Culture fit: the environment the candidate has thrived in compared with the team they would join. Size of company, pace, autonomy, language.
  • Availability: notice period, location, salary expectations, openness to the role.

A candidate who is strong on three and weak on one is easy to discuss. You can say where they fall short and let the manager decide whether that gap matters. This is the reason Digger scores these four dimensions separately rather than producing one blended number.

Requirement, evidence, gap

For each dimension, the explanation should follow the same three steps.

  1. Requirement. What the job asks for, in the manager’s own words where possible. “Five years of B2B sales in software”, not “sales experience”.
  2. Evidence. What in the CV, the interview notes or the candidate’s history shows they meet it. Be specific: the company, the role, the length of time, the result.
  3. Gap. What is missing or uncertain, stated plainly. “No direct experience selling to the public sector” is more useful than leaving it out and letting the manager discover it in the interview.

Naming the gap is the part recruiters most often skip, and it is the part that builds the most trust. When a manager sees that you have already spotted the weakness, they spend less time looking for it and more time deciding whether it matters.

A message template you can reuse

Here is a structure that fits in a short email or a message next to the profile:

Anna Peeters, senior account manager

Strong fit on hard skills. Six years selling SaaS to mid-sized companies, the last three at a payroll software vendor. Ran a portfolio of around 40 accounts.

Soft skills: good. Led onboarding for new sales hires at her current company. Clear and structured in the first call.

Culture fit: likely good, one question. Comes from a team of 200, yours is 25. She says she wants more autonomy; worth testing in the interview.

Availability: two-month notice period. Salary expectation within your range.

Main gap: no public-sector experience. If that is a hard requirement for this role, she is not the right profile.

It takes two minutes to write, and it changes the conversation from “why her?” to “is the public-sector gap a deal-breaker?”. That is the conversation you want to be having.

When the hiring manager disagrees

Sometimes the manager reads your explanation and still says no. That is useful information, not a failure. Ask which part of the reasoning they disagree with:

  • If they weigh a dimension differently than you did, the brief was incomplete. Update the job requirements before you search again.
  • If they spotted something you missed, add it to your notes on the candidate so the next search accounts for it.
  • If they reject on something that was not in the brief at all, say so. It is far better to surface a hidden requirement after the first shortlist than after the fifth.

A score that can be disagreed with, line by line, gets better over time. A number that can only be accepted or rejected does not.

What to look for in an AI matching tool

If you use software to score candidates, hold it to the same standard you would hold a colleague to. Before you rely on it:

  • Can it show its reasoning for each candidate? If you cannot read why a profile scored highly, you cannot explain it to anyone else.
  • Does it name the gaps? A tool that only lists strengths will make every shortlist look better than it is.
  • Can you correct it? Your notes and feedback from hiring managers should change future results.
  • Does a person make the decision? Under GDPR, candidates have the right not to be subject to decisions based solely on automated processing. The score should inform your judgement, not replace it.

Digger was built around this idea: every score comes with a written explanation, including the gaps, so you can forward it to a hiring manager as it is or edit it first. If you want to see what that looks like on your own candidates, the 30-day free trial includes the matching on every plan.

Try it on your next open role

Import your CVs, open a job and see ranked, explained candidates in the first hour.

Start free trial

30-day free trial. Cancel anytime.