Shortlist comparison

What this report is — and the decision it supports

Choosing one finalist over another is rarely a question of who scored highest; it is a question of which strengths matter most for this role and which gaps your team can live with. The shortlist comparison is built for exactly that conversation. It lines up each finalist's role-fit against the same blueprint, breaks the comparison down per competency, and puts the panel's own notes next to the evidence they refer to.

The decision it supports is the final selection — or the final two or three to bring forward. Like every SkillCort report, it supports the decision rather than making it. Nothing is ranked out of sight, nothing is auto-rejected, and every number in the grid traces back to rubric scores from named evaluators on real work samples.

When to reach for it

The natural moment is the panel debrief. Instead of each panelist arriving with a private impression and a favorite, everyone opens the same comparison and the discussion starts from shared evidence. Disagreements become specific — 'you weight written clarity higher than I do' — instead of a contest of overall impressions.

It is equally useful when a shortlist has to be defended: to a hiring manager who was not in the room, to a client reviewing an agency's recommendation, or to leadership asking why an internally favored candidate did not make the cut. The side-by-side format answers 'compared to whom?' — the question a single candidate's report cannot.

• Before and during a panel debrief, as the shared document everyone argues from.
• Presenting a recommended shortlist to a hiring manager or client.
• Breaking a deadlock between two panelists backing different finalists.
• Revisiting a runner-up when a similar role opens within the same process.

What's inside, section by section

The comparison is organized so the panel can move from the headline view to the evidence behind any cell in the grid without leaving the report.

• Role-fit comparison: each finalist's overall fit against the same role blueprint, side by side, with the weighting visible.
• Strengths and gaps per competency: where each candidate stood out and where they fell short, competency by competency, on the shared rubric.
• Risk flags for human review: any integrity signals or evaluator concerns, surfaced as context for the panel to weigh — never as an automatic rejection.
• Panel notes: observations captured by evaluators and panelists during review, attached to the candidate and competency they describe.

How it's produced

The comparison assembles itself from work already done. Because every finalist completed the same blueprint-driven assessment and was scored against the same rubrics, their results are genuinely comparable — the report simply lays the same measurements side by side. Scores follow SkillCort's transparent rollup: evaluators average within a criterion, criteria combine by rubric weights, and tasks roll up by skill weight times section weight.

No one exports spreadsheets, reconciles column orders, or copies notes between documents. When a panelist adds a note or an evaluator finalizes a score, the comparison reflects it. That removes the most common failure mode of manual comparison decks: candidates evaluated on subtly different information because the deck was built by hand.

How to read it well

Resist the urge to read it as a leaderboard. The overall role-fit row is a summary of weighted evidence, not a ranking to be obeyed — two candidates a few points apart are better treated as a judgment call than a settled order. Start instead with the competencies your team has agreed matter most, and see who is strong where it counts.

Treat risk flags as questions, not answers: a flag next to a strong candidate is a prompt to review the underlying evidence or raise it in conversation, not a reason to quietly drop them. And read the panel notes before the debrief, not during it — they are where the texture lives, and they often explain a score that looks surprising in the grid.