To give constructive interview feedback safely, anchor every point to a job-related competency and an observed behavior, deliver one clear strength and one clear growth area, and route it through an approved template. This keeps feedback specific, useful, and defensible. It is the human layer of a scalable feedback process.

Before You Start

Have the candidate’s scorecard open and the role’s competency list in front of you. If your interviewers are not using scorecards yet, fix that first — see scorecards vs unstructured notes. Feedback drawn from memory days later is where vague, risky language creeps in, because the specific observations have faded and the brain backfills with impressions. A scorecard freezes the real, job-related observations at the moment they happened, which is exactly what you need to write feedback that is both useful and safe.

You also need your approved templates ready and a clear sense of the one or two points you want to make. Good feedback is not comprehensive — it is selective. Trying to relay everything you noticed produces a muddy, overwhelming message. One genuine strength and one specific growth area is the target.

Step 1: Pull the Lowest-Scoring Competency

Open the scorecard and find the competency where the candidate scored lowest, along with the observation attached to it. This is your growth area, already documented and already job-related. You are not inventing a reason or searching your memory — you are reporting something a trained interviewer wrote down during the interview. That provenance is what makes the feedback defensible: it traces back to a structured, role-based assessment rather than a gut feeling.

If the lowest competency is something genuinely useful for the candidate to hear and act on, use it. If the lowest score is on a competency that the candidate cannot reasonably change or that veers toward the subjective, move to the next-lowest that is concrete and actionable. The aim is feedback the person can do something with.

Step 2: Pull One Genuine Strength

Find a competency where the candidate scored well, with its supporting observation. Real feedback names a strength — not as a cushion to soften the blow, but because it is true and genuinely useful for the person to know. Candidates calibrate their job search partly on what they are told they do well, and an honest strength is a gift. Lead with it, so the message opens on something real and positive before it turns to the growth area.

Resist the urge to invent a strength if the scorecard does not support one. Hollow praise is transparent and undermines the credibility of everything else in the message. If the candidate was genuinely strong across the board and simply lost to someone stronger, say exactly that — it is both true and kind.

Step 3: Anchor Every Statement to the Role

Convert each observation into role-language. “The position requires leading client presentations, and in the panel exercise the pitch structure was hard to follow” is safe and specific — it references a documented job requirement and a behavior the interviewer watched happen. Compare that to “you’re not a strong presenter,” which is a verdict on the person rather than an observation tied to the role. The first is feedback; the second is a judgment that invites dispute.

The pattern to follow every time: name the role requirement, then describe the specific observed behavior in the interview that fell short of it. This two-part structure does double duty — it gives the candidate something concrete to work on, and it keeps the feedback anchored to the job, which is what makes it legally defensible.

Step 4: Strip Out Trait Language

Reread your draft and delete anything about confidence, nerves, age, accent, energy, or personality. “You seemed nervous” is a trait judgment, it is unverifiable, and it invites a candidate to push back. More importantly, it is not useful — “nervous” is not something a candidate can cleanly act on, and it sometimes maps onto protected characteristics in ways that create real risk. Replace any trait observation with the specific behavior underneath it, or cut it entirely.

A simple test: would a stranger reading the feedback be able to tell what the role required and what specifically fell short, without learning anything about the candidate’s personality or background? If yes, the language is clean. If the feedback reveals more about who the person is than about how they performed against the job, rewrite it.

Step 5: Route It Through an Approved Template

Drop your two points into the matching feedback email template. The template handles tone, structure, and the warm opening and closing; you supply the specific strength and growth area. This division of labor is what makes the process fast and consistent — the template ensures every candidate gets the same respectful framing, and the scorecard ensures every message carries real, specific substance. To send these at scale, see how to automate candidate feedback emails, where this same drafting logic runs semi-automatically with a human approving each one.

How to Know It Worked

Good feedback meets three tests. It is specific enough that the candidate can act on it — they know exactly what to build or do differently. It is job-related enough to defend — every statement traces to a documented competency and an observed behavior. And it is warm enough that the candidate would still recommend you to a friend despite the rejection. If a stranger reading it cannot tell which protected class the candidate belongs to and can tell exactly what the role needed, it worked.

One more practical signal: if the feedback would read as fair to the candidate’s own mentor, you are in good shape. Feedback that only makes sense from the company’s side of the table usually means a verdict has slipped in where an observation belongs.

Common Mistakes

• Writing from memory instead of the scorecard, which invites vague and risky language
• Vague platitudes — “wasn’t quite the right fit” — that help no one and frustrate the candidate
• Trait language (“nervous,” “low energy”) instead of observed, job-related behavior
• Burying the decision under so much softening that the message reads as evasive or dishonest
• Trying to relay everything you noticed instead of selecting one strength and one growth area
• Inventing a strength the scorecard does not support, which undermines the whole message

What About Candidates Who Push Back?

Occasionally a candidate replies to feedback wanting to argue the decision or asking for more. The structure you built protects you here too. Because every point traces to a documented competency and an observed behavior, your response is simply to restate it calmly: the role required X, and in the interview Y was observed. You are not defending an opinion — you are reporting an assessment. There is no obligation to relitigate the decision or to provide an exhaustive accounting. A brief, warm reaffirmation of the one specific point is appropriate and sufficient.

The candidates who push back are rare, and they are far rarer when the original feedback was specific. Vague feedback invites argument because it gives the candidate nothing solid and leaves them feeling unfairly dismissed. Specific, job-anchored feedback tends to be accepted even when it is not what the person hoped to hear, because it is visibly fair. The specificity that makes feedback useful is the same specificity that makes it hard to argue with.