Skip to content
FitRank

Resource managers · Explained matching and shortlists

A ranked shortlist with a reason for every person

Matching runs in the background and turns your whole pool into a short, ranked list. Every person on it can be traced from rules to facts to five probability answers, so a manager can check a suggestion in seconds.

FitRank matching results: a funnel from 720 people considered to 95 who passed the rules, 26 ranked by the model and 17 recommended, with the top shortlisted person at over 99% overall fit
From 720 people to a shortlist of 15

The problem

Most matching tools return a score with no way to check it. Managers either trust it blindly or ignore it, and nobody can say afterwards why a person was suggested or left out.

How it works

  1. 1Hard rules check everyone in code: free in time, no leave clash, location, working-hours overlap, cost band and clearance.
  2. 2Facts are calculated exactly: must-have and nice-to-have coverage, level, experience against the minimum, domain projects, skill recency and capacity.
  3. 3The in-house model answers five questions with a probability for every option: skill match, level fit, domain relevance, delivery risk and overall fit.
  4. 4Safety checks compare the answers with the facts, and your thresholds place each person in Shortlist, Review or Hidden.
FitRank 'How this was decided' panel: rules passed, facts from the data, the model's probability for every answer to five questions, safety checks and the resulting band
Every score, traced back to rules, facts and probabilities

What's included

Where teams use it

Questions about explained matching and shortlists

Can the model put someone on the shortlist who fails a rule?

No. Rules run first in code, and anyone who fails one is excluded with a recorded reason. The model only scores people who passed every rule.

What if the model's answer contradicts the facts?

Code cross-checks every answer. A contradiction, thin data or an unsure model caps the person at Review, so nobody is shortlisted on a doubtful signal.

How long does a matching run take?

Scoring a run took a median of 0.94 seconds on an ordinary laptop CPU in our benchmark. The run happens in the background while you carry on.

More of FitRank

See all 19 capabilities

Be one of the first teams to staff with FitRank

We're taking on a small number of pilot companies. Pre-register for early access, or talk to us about an annual licence.