Build an interview scorecard from the work someone will do

An interview scorecard should explain why a piece of evidence meets a job requirement. A grid with “communication,” “ownership,” and a score from one to five can still hide a general impression if nobody has defined what the numbers mean.

Build the scorecard backward from an actual task. Identify the capability that task requires, the question that could reveal it, and the behavior that would justify each rating. Keep the example below as a starting point to review with people who know your job; it is not a validated selection instrument.

Connect the task to the question

OPM’s job-analysis guidance describes the connection between work tasks and competencies. Its structured-interview guide develops that connection into questions and rating scales. Read the job-analysis overview and the interview guide.

Here is a fictional example for a customer implementation role:

Link	Worked example
Task	Pass a customer issue to the right internal owner with enough information to act
Capability	Clarifies missing information and makes ownership explicit
Question	Tell me about a handoff you managed when the next step or owner was unclear. What did you do, and what happened?
Neutral probes	What did you know then? What was your own contribution? How did you determine whether the handoff had worked?
Evidence recorded	Candidate actions, constraints, follow-through, result, and unresolved questions

The question does not ask whether the candidate is “good at ownership.” It invites an example that can be examined. A different role may require different evidence even if its scorecard uses the same competency name.

Write behavioral anchors before interviews

For this one task, a three-level scale could look like the table below. This small example is intentionally coarse. Adding numbers without meaningful distinctions makes the scorecard look more precise than it is.

Rating	Evidence demonstrated in the answer
1 — Below this role’s requirement	Describes forwarding the issue but, after standard probes, provides no clear method for resolving missing ownership or needed information
2 — Meets this task requirement	Explains how they identified the next owner, assembled the needed context, and checked whether the handoff progressed
3 — Strong evidence for this task	Meets level 2 and explains a relevant failure or constraint they detected, how they adapted, and what evidence showed whether the adaptation worked
N/A — Not assessed	The question was not covered, the record is inadequate, or the permitted assessment did not provide enough evidence to rate it

A rating evaluates the evidence elicited in this assessment. It is not a permanent statement about the person’s ability. An unsuccessful project can still demonstrate strong judgment; an impressive outcome may have depended largely on other people or favorable conditions.

The OPM guide recommends behavior examples to help distinguish proficiency levels and treats those examples as guides rather than exact scripts every candidate must reproduce. That matters when someone demonstrates the same capability through an unfamiliar but relevant approach.

Record the evidence beside the rating

A fictional assessor note might read:

Paraphrase: The candidate described a customer issue that initially had no internal owner. They separated the missing technical details from the approval question, confirmed a responsible person for each, and checked the next day that the technical investigation had begun. The customer deadline was still missed because approval took longer than expected. The candidate did not describe a change to the future handoff process.

Under the example anchors, that supports level 2. The missed deadline alone does not make it level 1. The answer contains a clear ownership and follow-through method, but does not establish all the evidence described at level 3.

Another assessor may disagree. Resolve that by identifying which anchor or fact is in dispute. “I liked the answer more” is not an alternative evidence standard.

Use missing-data rules honestly

Do not enter zero when a question was skipped. Do not average N/A into a total or quietly ignore a required capability because another score is high. Decide in advance what happens when required evidence is missing: an equivalent follow-up assessment, a process correction, or a decision that remains unresolved.

Likewise, avoid a total that conceals a non-negotiable job requirement. If a task has to meet a threshold, state that rule before interviewing. Any weighting should have a job-related rationale; decimal places do not validate it.

Pilot the scorecard with the assessors

Write two or three fictional answers with different strengths. Have interviewers rate them independently, then compare their notes. If they assign different ratings because “checked progress” means different things to each person, refine the anchor before using it with candidates.

Also test whether the question fits the allotted time and whether the probes clarify without supplying an answer. The OPM guide includes piloting as part of interview development. A short practice session can expose ambiguity that a polished blank template hides.

Version the scorecard and retain the rationale for substantive changes. If a revision changes what counts as sufficient evidence, consider the effect on candidates already assessed. The goal is a consistent record of work-related evidence, not a numerical justification added after the team has chosen a favorite.