Interview Debrief Template (Structured Notes + Evidence-Based Scoring)

An interview debrief template is a standard form your hiring team uses right after interviews to record what the candidate said, what you observed, and how that evidence maps to the role requirements. A good debrief keeps notes consistent, reduces bias, and makes hiring decisions easier to defend because it focuses on specific examples, not impressions.

Below is a structured, evidence-based interview debrief template you can copy, plus guidance for using interview transcripts to capture exact quotes, what not to record, and a simple scoring rubric you can apply across candidates.

Key takeaways

• Use one debrief template for every candidate to keep feedback consistent and fair.
• Write evidence as concrete examples (and short quotes) tied to competencies, not personality judgments.
• Separate “observed evidence” from “concerns/risks” and from your final recommendation.
• If you score candidates, use a clear rubric with defined levels and role-weighted competencies.
• Keep documentation professional: avoid protected-class details, medical information, and subjective labels.

Why a structured interview debrief matters

Unstructured notes often turn into opinions like “great energy” or “not a culture fit,” which are hard to compare and hard to justify. A structured debrief pushes everyone to document the same information: role requirements, competencies, evidence, and concerns.

It also helps your team make decisions faster because you do not need to reconstruct what happened days later. When you combine the template with an interview transcript, you can point to exact examples instead of relying on memory.

The interview debrief template (copy/paste)

Use this template as a doc, form, or ATS note. Keep it the same for every interviewer and every candidate for the role.

1) Candidate + interview details

• Candidate name:
• Role / requisition ID:
• Interview stage: (screen / hiring manager / panel / final)
• Date + time:
• Interviewer(s):
• Interview format: (phone / video / onsite)
• Interview focus: (technical / behavioral / case / portfolio)

2) Role requirements snapshot (what “good” looks like)

Pull these from the job description and interview plan so every debrief ties back to the same bar.

• Must-have skills: (3–6 bullets)
• Nice-to-have skills: (0–4 bullets)
• Key outcomes in the first 6–12 months: (2–4 bullets)
• Leveling expectations: (scope, autonomy, complexity, influence)

3) Competency scoring summary (rubric-based)

If your organization uses scoring, keep it simple and defined. Score only what you assessed in the interview.

• Scoring scale: 1–5 (definitions below)
• Overall score (weighted):
• Hire recommendation: Strong No / No / Lean No / Lean Yes / Yes / Strong Yes
• Confidence: Low / Medium / High

4) Evidence by competency (the most important section)

For each competency, document (a) what question/task you used, (b) the candidate’s specific example, and (c) your rating. Include short quotes when helpful.

Competency A: (e.g., Problem solving)

• Question/task used:
• Observed evidence (facts + examples):
  • Example 1 (Situation/Task → Action → Result):
  • Example 2 (optional):
  • Quote (optional): “…”
• Concerns / risks (if any): (tie to evidence; avoid assumptions)
• Score (1–5):

Competency B: (e.g., Communication)

• Question/task used:
• Observed evidence (facts + examples):
  • Example 1 (S/T → A → R):
  • Quote (optional): “…”
• Concerns / risks (if any):
• Score (1–5):

Competency C: (e.g., Role-specific expertise)

• Question/task used:
• Observed evidence (facts + examples):
  • Example 1 (S/T → A → R):
  • Quote (optional): “…”
• Concerns / risks (if any):
• Score (1–5):

Add or remove competencies to match your role.

5) Strengths (top 2–4, evidence-based)

• Strength 1: (What it is + the example that proves it)
• Strength 2:
• Strength 3 (optional):

6) Concerns, gaps, and open questions

List only job-related concerns and what you would need to confirm in a follow-up interview, reference check, or work sample.

• Concern 1: Evidence observed + why it matters for this role
• Concern 2:
• Open questions: (what you did not assess yet)

7) Team and role fit (use job outcomes, not vibes)

• Most relevant past work: (projects that match the role outcomes)
• Collaboration style (observed): (what they did/said, not labels)
• Work constraints discussed: (schedule, location, travel, start date—if relevant and lawful)

8) Final recommendation (clear and comparable)

• Recommendation: Strong No / No / Lean No / Lean Yes / Yes / Strong Yes
• One-paragraph rationale: 3–5 sentences tied to must-haves and evidence
• Suggested next step: (move forward, hold, reject, or add an interview focused on X)

A simple scoring rubric you can standardize

A rubric keeps scoring consistent across interviewers. Define the score levels in plain language, then map each competency to the level expected for the role.

Recommended 1–5 scale (with definitions)

• 1 – Does not meet: Evidence shows the candidate cannot perform this competency at the required level today.
• 2 – Below: Some relevant knowledge, but gaps would create risk without heavy support.
• 3 – Meets: Clear evidence they can perform at the expected level for this role.
• 4 – Exceeds: Strong evidence of success in more complex situations; could raise the bar.
• 5 – Exceptional: Repeated, high-impact evidence; teaches others; drives strategy or scale (use sparingly).

How to weight competencies (optional)

If you use weighting, keep it stable for the role and publish it to the interview team before interviews start.

• Example: Role-specific expertise 40%, Problem solving 25%, Communication 20%, Collaboration 15%.
• Rule: Do not “adjust weights” after you meet a candidate.

Scoring pitfalls to avoid

• Scoring without evidence: Every number should tie to at least one concrete example.
• Mixing levels: Do not penalize a junior candidate for not showing senior-level scope if you are hiring junior.
• Halo/horns effect: One strong (or weak) moment should not drive all scores.
• Overvaluing style: Fast talkers can sound confident; slow speakers can still be strong.

How to use transcripts for evidence-based debriefs

Transcripts help you capture exact wording and specific examples, which reduces “he said/she said” memory gaps. They also make it easier to write notes that focus on job-related evidence instead of subjective impressions.

Set up your interview for clean, usable documentation

• Use consistent questions: Ask the same core questions for each candidate in the stage.
• Tell candidates what you are doing: If you record or transcribe, get consent and explain the purpose and retention policy.
• Label speakers: “Interviewer” vs “Candidate” improves clarity in the transcript and your debrief.

Turn transcript moments into strong evidence

When you write “evidence,” use a short structure so your notes read like facts, not opinions.

• Use STAR: Situation/Task → Action → Result.
• Pull 1–2 short quotes: Choose lines that show decision-making, ownership, or results (not filler).
• Keep quotes short: One sentence is often enough, then summarize the rest.

Replace subjective phrasing with transcript-based language

Here are common rewrites that make your documentation more professional.

• Instead of: “Great communicator.” Write: “Explained trade-offs between X and Y, then confirmed requirements by asking, ‘What does success look like at 30 days?’”
• Instead of: “Not confident.” Write: “Paused for long periods and could not describe a clear approach when asked to debug issue X.”
• Instead of: “Strong leader.” Write: “Described leading a cross-team launch, setting milestones, and removing a blocker by aligning stakeholders on scope.”
• Instead of: “Culture fit concern.” Write: “Preferred working alone and said, ‘I usually avoid meetings,’ which may conflict with the role’s daily partner check-ins.”

Keep transcripts and debrief notes professional and compliant

Interview documentation can become part of an official hiring record. Keep it job-related, consistent, and respectful, and follow your organization’s retention and access rules.

If you operate in the U.S., the EEOC guidance on prohibited employment practices is a helpful reference for what to avoid in hiring decisions and documentation.

What not to record in an interview debrief (and what to do instead)

The safest rule: document job-related evidence only. Avoid recording personal details that are not needed to evaluate the candidate’s ability to do the job.

Avoid documenting protected or sensitive personal details

• Do not note: age, race, ethnicity, nationality, religion, pregnancy status, disability/medical details, marital/family status, sexual orientation, or other protected traits.
• Do not note: subjective labels like “abrasive,” “too quiet,” “weird,” or “not a fit.”
• Do not note: appearance, accent, or unrelated background details.

What to write instead (job-related, evidence-based)

• Replace “seems inexperienced” with “Could not explain how they measured success on Project X; no metrics shared.”
• Replace “bad attitude” with “Spoke negatively about two prior managers; did not describe what they would do differently.”
• Replace “may not handle pressure” with “When asked about a deadline miss, did not describe a plan to escalate risks or reset scope.”

Be careful with compensation and negotiation notes

Many teams track pay expectations, but keep those notes separate from competency scoring when possible. Document only what is necessary for process and alignment, based on your policy and local laws.

Recording and consent

Laws on recording conversations vary by location. If you record interviews, confirm you have the right consent process for every place you hire and every place the candidate may be located.

In the U.S., you can review an overview of state recording consent rules from the Justia 50-state survey on recording conversations and then validate requirements with your legal counsel.

How to run a consistent debrief process (step by step)

The template works best when the whole team uses it the same way. This lightweight process helps you keep feedback timely and comparable.

1) Align on competencies before interviews begin

• Choose 4–6 competencies that match the role outcomes.
• Define what “meets” looks like for the level.
• Assign interviewers to specific competencies to reduce overlap.

2) Debrief quickly and independently

• Have interviewers complete the debrief within 24 hours.
• Ask for independent scoring before group discussion to reduce groupthink.
• Require at least one evidence bullet per scored competency.

3) Hold a structured debrief meeting

• Start with must-haves: does the evidence meet the bar?
• Review concerns and decide what can be validated with a targeted follow-up.
• End with a clear decision and next step.

4) Store documentation securely

• Limit access to the hiring team on a need-to-know basis.
• Follow your internal retention policy for notes, recordings, and transcripts.
• Keep a single source of truth in your ATS or HR system.

Common questions

• Should every interviewer use the same interview debrief template?
  Yes, for the same role and stage. You can allow role-specific sections, but keep the core structure identical so feedback stays comparable.
• How long should an interview debrief be?
  Aim for one to two pages of tight notes. Prioritize evidence bullets tied to competencies over long narratives.
• Can we score candidates if we do not use a fully structured interview?
  You can, but scoring works best when questions are consistent. If interviews vary a lot, focus on evidence and “confidence” levels, and treat scores cautiously.
• What is the difference between “concerns” and “gaps”?
  A gap is missing evidence because you did not cover it. A concern is evidence that suggests risk for the role.
• How do transcripts help reduce bias?
  They let you quote exact examples and describe behaviors, which makes it easier to avoid subjective labels and to compare candidates on the same criteria.
• Should we include candidate quotes in the debrief?
  Yes, but keep quotes short and job-related. Use them to support a point, not to editorialize.
• Who should see interview debrief notes and transcripts?
  Typically only the people involved in the hiring decision and HR, based on your policy. Limit access and store files in approved systems.

Where transcription fits (and how to keep it practical)

If you want more accurate, evidence-based debriefs, consider creating a transcript for interviews where you need clear documentation (panel interviews, complex technical interviews, or roles with high hiring volume). You can pair transcripts with a short debrief so your team gets both: a clean summary and the exact wording when needed.

If you use AI tools, a helpful workflow is “automated first, then review,” especially when audio quality varies. GoTranscript offers automated transcription and also transcription proofreading services when you want a second pass for clarity and consistency.

When you are ready to standardize interview documentation across roles and teams, GoTranscript can support you with professional transcription services that make it easier to pull exact examples, write evidence-based notes, and keep debriefs consistent.