How to write an interview feedback summary for a hiring debrief
Write an interview feedback summary by role competency, keep disagreements visible, and ground follow-up questions in the original interview notes.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What an interview feedback summary is
An interview feedback summary turns separate interview records into a single account of the evidence for one candidate and one role. You organize examples by what the role requires, such as diagnosing a problem or communicating a project risk. Each entry tells a hiring panel what the candidate said or did, how the interviewer interpreted it, and where the panel can find the source. A good summary also shows where interviewers disagree or where the interview process leaves a question open.
In structured interviews, the team uses planned questions and agreed role competencies, which are the skills and behaviors the job calls for. The summary uses those definitions to make notes from different sessions comparable. A candidate scorecard summary can refer to the evidence recorded on scorecards while leaving existing ratings and decisions in their original systems. Treat the summary as a draft for the recruiting lead or another qualified HR reviewer to check before the hiring debrief. The panel uses its established decision process after reviewing the evidence.
What it does for the business
- Use debrief time to resolve real differencesSend reviewers to the exact examples behind a disagreement so they can read the same passages before the meeting. The panel can spend the discussion on what each example shows and what evidence would help resolve the issue.
- Direct follow-up to the evidence you needA clear account of what the team already asked helps you avoid repeating a whole interview. If the panel still needs evidence about a specific behavior, book the right interviewer and give them a question that fills that gap.
- Improve the interview planRepeated gaps can reveal an assignment that leaves an important competency without a question. Update the interview guide and assign explicit coverage before the next loop, so panels have a better chance of getting comparable examples.
- Keep the decision record traceableA panel member can return to the original wording when a paraphrase loses context. Recruiting can preserve the links between sources and observations in the approved record, making a later review easier to reconstruct.
How to build an interview feedback summary, step by step
Inventory the notes against the interview plan
A debrief starts with the evidence you expected to collect.
What to do
- Record the candidate ID and the role or requisition version from the authorized records. Check each note against that identity before including it, especially when two candidates share a name or a candidate is interviewing for two roles.
- Copy the approved competency definitions and assigned questions from the interview plan. Keep the original definition when shorthand in the notes refers to something broader, such as leadership.
- List the sessions, interviewers, dates, and question assignments. Mark which notes you have, which are incomplete, and which still need confirmation from the person who conducted the interview.
- Keep only authorized, job-related excerpts and the references needed to find them. Leave sensitive personal details out of the summary and use the approved record as the source.
Why
An inventory tells you whether a thin evidence set reflects what happened in the interviews or what made it into the notes. A blank competency could mean the question was skipped, the note has yet to arrive, or the example sits under a different question. The reason determines whether you should retrieve a record or arrange another assessment.
Separate observed examples from interpretations
A reader should be able to trace every judgment back to a specific example.
What to do
- Read each note in the context of the question. Identify the candidate's reported action or the work the interviewer directly observed, and label the type of evidence in your paraphrase.
- Keep the interviewer, date, and question or exact note reference beside each observation. If you condense a long example, retain who took the action and which parts the notes leave unclear.
- Put interpretation on its own line. For example, record that a candidate described posting a status update after a missed deadline, then attribute any judgment about the timing of escalation to the interviewer.
- Map the example to the behavior in the supplied competency definition. Where evidence challenges an earlier observation, keep both accounts and describe the conditions under which each was collected.
Why
A phrase such as good communicator hides both the task and the evidence. The notes might show that the candidate explained a tradeoff clearly to a technical audience, while a different exercise tested how they would convey uncertainty to a customer. Keeping those details lets a panel compare two observations without exaggerating the agreement or the conflict.
Prepare the evidence for the hiring debrief
A useful follow-up identifies the behavior the panel still needs to see.
What to do
- Give each competency its own section. Add supporting and challenging evidence where available, and mark any competency the team has yet to assess.
- Describe disagreements in terms of the task and the behavior. If one interviewer cites an early escalation and another cites a delayed one, record the sequence each interviewer saw and the context each provided.
- Write focused follow-up questions against the open point. For example, ask the candidate to walk through a missed deadline and explain what triggered escalation, who received the first update, and what the update contained.
- Give missing notes an owner. Ask the interviewer for the original observation or confirmation that the question was skipped, and distinguish that request from a proposed question for the candidate.
Why
Different situations can produce different observations about the same competency. A question that asks for a specific action and the circumstances around it can clarify whether the difference reflects the setting, the prompt, or a remaining gap in the evidence. The debrief can then decide which follow-up is worth the candidate's and the team's time.
Check the draft against the original records
An open evidence gap belongs in the summary even when the panel wants a simple answer.
What to do
- Ask a qualified recruiting or HR reviewer to trace the most consequential examples back to the original notes and verify their attribution. Check both accounts of any disputed observation.
- Read each competency definition next to its mapped examples. If the notes describe participation in a meeting, verify that the summary preserves the difference between attending, contributing, and leading.
- Check the language around missing evidence. Reserve descriptions of a demonstrated difficulty for a specific observed task, and label absent or incomplete records as coverage gaps.
- Remove personal information unrelated to the role and unsupported judgments about personality or fit. Check that the short debrief view and detailed pack show the same evidence status and unresolved questions.
Why
Small wording changes can turn a self-reported example into an observed fact, or a missed interview question into a criticism of the candidate. Source review catches those changes before the panel relies on them. When a material claim still lacks support, hold that claim and keep the usable parts of the draft available for review.
Hand off the open questions and their owners
The handoff is complete when each unresolved item has a clear owner and a way to close it.
What to do
- Lead with the gaps or disagreements most likely to affect the debrief. Name the competency and explain what evidence the panel has and what remains open.
- Assign each follow-up to the person who can resolve it. A missing record belongs with the interviewer or recruiting coordinator, and a disputed interpretation may need both interviewers to revisit the same passage.
- List the source location alongside each action. Give reviewers an exact reference to the supporting note or to the interview plan entry when the task is to confirm unassessed coverage.
- Give the recruiting lead a clear handoff for approval. Record which interviews you reviewed, any records still outstanding, and the next check before the summary goes to the panel.
Why
A debrief pack can gather evidence and still leave the next action unclear. Named ownership saves the recruiting lead from tracing the interview plan again just to find who should respond. A short list of concrete actions also makes it easier to refresh the summary after a late note arrives.
Common mistakes
- Organizing only by interviewerGrouping by session alone scatters evidence about the same skill and makes differences hard to examine during the debrief.
- Treating a blank as a failureIf the prompt or notes are missing, record a gap in coverage and ask the interviewer to confirm what happened.
- Repeating a judgment as factKeep a label such as unclear under pressure attached to the interviewer and the specific interaction that prompted it.
- Smoothing a disagreement into consensusCarry forward each interpretation with its own example and reference so reviewers can assess the difference.
- Using a broad fit labelUse the supplied definition of the job behavior and drop personal impressions that you cannot tie to relevant evidence.
What a good result looks like
- The scope identifies one candidate and role version, with the expected interviews and incomplete records listed.
- Each recorded example has a source, and the summary distinguishes the candidate's report from what the interviewer directly observed.
- Every supplied competency has an evidence status, including unassessed areas and unresolved disagreements.
- Each follow-up states the missing information, identifies an owner, and gives them an evidence reference or question to use.
- A qualified reviewer can check the draft against the notes before the panel uses it.
And then what? Using the result
- Send missing-note requests through your approved recruiting workflow so each interviewer can confirm what was asked and supply the relevant observation.
- Use disputed examples to structure the debrief agenda. Ask each interviewer to identify the observed behavior behind their interpretation.
- Brief the designated interviewer on a focused follow-up if the panel still needs evidence, and record the new observation with its own source reference.
- Review unassessed competencies after the loop and update interview assignments where the plan repeatedly leaves a gap.
- File the reviewed evidence through your approved recruiting process and have the panel record any hiring decision in its designated record.
When to run it
- Before a panel debriefCollect the individual records after interviewers document their observations. Give the panel time to read the relevant passages before discussing them.
- When an interview loop changes midstreamUpdate the evidence inventory after a canceled session or reassigned question. Check whether another session covered the same role competency.
- When interviewers report different observationsBring both notes into the same competency section so reviewers can compare the tasks, prompts, and behavior behind each interpretation.
Questions people ask
How do you write an interview feedback summary?
Organize the authorized notes by role competency, attribute specific examples to their sources, and flag disagreements and missing evidence. Give each needed clarification an owner and have a qualified HR reviewer check the draft before the debrief.
What goes into a candidate scorecard summary?
Include the agreed competency, the observed or reported example, the source reference, any interviewer interpretation, and gaps or conflicting evidence. Keep existing evaluations in their designated record so readers can trace the evidence independently.
How do you handle conflicting interview feedback?
Preserve each account with its evidence and identify the point of disagreement. Check whether both interviewers saw the same task, used the same criterion, and interpreted the behavior in the same context.
What should you do when interview notes are missing?
Mark those sessions or questions as missing and ask their owners to supply the record or confirm that the question was skipped. Keep conclusions limited to the evidence you can verify.
How do you write follow-up questions for a hiring debrief?
Ask for a concrete example of the specific job behavior the existing notes leave open. Include enough context for the interviewer to recognize useful evidence and avoid directing the candidate toward a preferred answer.
Can a feedback summary decide whether a candidate advances?
The hiring panel owns that decision under its established process. 10folds prepares a local draft of evidence, disagreements, and follow-up tasks for a qualified reviewer.
More jobs in Hiring
Summarise interview feedback, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac