Candidate match and evaluations
An evaluation reads a candidate’s resume, application, scorecards and transcripts against the role’s Match criteria, and gives a 1–4 recommendation, strengths, concerns and a score for each criterion. It’s advice, never a decision: nothing moves, archives or emails anyone because of it.
Match criteria#
A role’s Match criteria are what every candidate for it is scored on. Mark each Must-have or Nice to have; must-haves count double. Suggest from the job description drafts them for you, and if a role has none, its first evaluation drafts them from the job description. Choose Save criteria when they’re right.
A criterion about who someone is, rather than the work, is left out, and only you are told.
Running an evaluation#
On a candidate’s profile, Candidate match has Run evaluation, and Re-run once there is one. On a role, the Review view has Evaluate this role with Scout, which evaluates up to 25 candidates who don’t have one yet each time you choose it. From search results, Evaluate selected scores the people you tick.
Evaluations read everyone’s scorecards, so they stay hidden from you until you’ve submitted yours.
The Match column#
| You see | It means |
|---|---|
| A percentage | How well their recorded evidence meets the criteria. Must-haves count twice. |
| Unscored | Not enough recorded evidence for a percentage. It isn’t a zero or a rejection. |
| Pending | It shows once you’ve submitted your scorecard. |
| — | No evaluation yet. |
Missing evidence counts as unknown, not as a zero. When a role’s criteria change, the people already scored on it are re-evaluated; nobody’s stage changes and nobody is emailed.
Read next
Was this helpful?
Still need help?
Someone on the OpenATS team will reply by email.