Scorecard and considerations

A candidate's evaluation after the interview, how its result is calculated and which label it gets.

In Spanish: Scorecard and Consideraciones. Together they're the evaluation (evaluación).

What it is

A candidate's evaluation has two parts, and both go into the client report:

	What it asks	Does it score?
Scorecard	Are they the professional the client needs?	Yes: from 1 to 5 on each evaluation criterion
Considerations	What does the client need to know before deciding?	No

The scorecard

One row for each of the job post's evaluation criteria, with a score from 1 to 5 and a comment. Each criterion has its weight: High, Medium or Low. The result shows at the top, out of 5.

Considerations

Unscored observations the client sees in the report, each with its type:

Type	What for
Requirement exception	You're presenting someone who fails a must-have requirement, and you say why
Gap	Something they're missing
Risk	Something that could go wrong
Data reliability	Something that couldn't be fully confirmed
Compensation	What they're asking for or what was negotiated

What it's for

Putting in writing, after the interview, how good the candidate is for the role, with a number you can compare across candidates. Considerations say what a number can't.

Where you see it

In the candidate's Evaluation tab, in the ATS. It saves itself.

Action	What it does
Generate scores and comments	The AI proposes the scorecard from an interview
Adopt	Accepts a proposal, or Adopt the proposals, all together
Draft with AI	Proposes the recommendation rationale, which the client reads
Confirm or dismiss a consideration	Before the report, each one has to be reviewed

The recommendation label shows in the report.

What it gets mixed up with

Mixed up with	The difference
The Match score	It measures the profile before talking to the candidate. The scorecard, what you saw in the interview
A note or a comment	They're internal. The client reads a consideration. See Tag, label, note and comment
A must-have criterion	Evaluation criteria never disqualify: they only weigh

There's no "doesn't apply". A criterion without a score is pending, not an opinion. To generate the report, they all need a score: if something couldn't be fully established, you put the number and say so in the comment, or add it as a consideration.

A partial result is marked as partial. The easy criteria usually get scored first, so a partial tends to come out higher than the final one, and a number without a warning misleads too early.

A requirement exception doesn't lower the label. They're two different things: how good they are, and whether they meet the minimums. Mixing them would put a 4.2 with an exception on the same level as a clean 3.2.

How it's calculated

Result = the sum of score × weight, divided by the sum of the weights, over the criteria that have a score.

Weights are worth High, 3. Medium, 2. Low, 1.

Example: 4 on High, 5 on High, 4 on High, 4 on High, 4 on Medium and 4 on Low. (12 + 15 + 12 + 12 + 8 + 4) ÷ 15 = 4.2 out of 5.

The result is also shown as a percentage, which starts at the bottom of the scale, because the worst score is 1 and not 0:

Percentage = (result − 1) ÷ 4. A 4.2 gives 80%.

With unscored criteria, it's calculated over the scored ones and marked: 4.1 / 5 · partial · 4 of 6.

The recommendation label comes from the result and the job post's recommendation threshold, which starts at 3.5:

Result	Label, with the threshold at 3.5
Threshold + 1 or more	Strongly recommended, from 4.5
Threshold or more	Recommended, from 3.5
Threshold − 0.5 or more	Recommended with reservations, from 3.0
Below	Not recommended

The threshold is changed in the job post settings.