Evidence-based scorecards: what to cite and what to ignore

A score without evidence is an opinion. It might be a good one, since experienced interviewers have real instincts, but you cannot audit it, defend it to a candidate, or compare it fairly to anyone else’s. The remedy is easy to state and harder to practice: anchor every rating to something the candidate actually said.

Anchor every rating to a transcript moment

The discipline comes down to one rule: for each competency you score, point to the specific moment in the conversation that justifies the number. The evidence is a quote you can cite; a summary of your impression does not qualify.

When a “4 out of 5 on systems thinking” carries the line “I cut scope to the two tables that actually blocked the migration, then backfilled the rest after launch,” the score has a visible reason behind it. Anyone reviewing the scorecard can see the reasoning, agree or disagree with the evidence in front of them, and move on. The discussion moves from “do you trust this interviewer?” to “is this evidence strong enough?”, and the second question is the one worth asking.

What to cite

Cite content and behavior:

• A concrete decision and the constraint that drove it.
• A tradeoff the candidate named on their own, including what they gave up.
• The failure case: what went wrong, or what would have, and how they handled it.
• Ownership: what they did, distinct from what the team did around them.

These are observable in an answer. Two evaluators reading the same transcript will tend to find the same evidence, which is why it makes scores comparable.

What to ignore

Some signals feel informative and turn out to be noise, or worse, bias. Leave these out on purpose:

• Accent and fluency. How someone speaks is separate from what they said, and interviewer judgments measurably shift with accent alone. A score that moves with accent is measuring bias.
• Confidence and polish. Smooth delivery correlates with practice and privilege, and neither is the trait you are hiring for.
• Biometrics: tone of voice, facial expression, “energy.” These should never touch a score. Hure does not use them, by design: it judges the content of what a candidate says and ignores how they look or sound. We wrote about where that line sits in a voice interview.
• Résumé halo. A familiar logo is not evidence of the competency in front of you.

If you cannot tie a signal to a citable moment about the actual competency, it does not belong in the score.

Map evidence to observable levels

Evidence works best against a rubric with observable levels. Instead of asking “how good was this answer?”, ask “which level does this answer demonstrate?”, where each level describes a concrete behavior. The evidence you cited should map cleanly onto a level. When it doesn’t, the rubric needs sharper language, and the candidate’s number should stay where the evidence puts it.

Make scorecards auditable and comparable

The payoff of evidence-based scoring shows up later: when a hiring manager questions a result, when a candidate asks why, or when you look back across a whole funnel to check whether your bar held steady. Because every rating cites a transcript moment, every decision is auditable, and because everyone was measured against the same versioned rubric, the scores are comparable.

This is the model Hure runs end to end: a versioned rubric authored from the role, a natural voice interview that covers it consistently, and a scorecard where each rating is anchored to the transcript, with a human always making the final call. The scorecard’s job is to make sure that when you decide, you are deciding on evidence.