Pre-onsite screening

Interview debrief template: a 20-minute agenda that starts where the panel disagrees

German Reyes
German Reyes·Oct 12, 2026·7 min read
On this page

Most interview debrief template pages I've seen hand you a form with a box for each interviewer's thoughts, and the meeting goes the way it always did: someone senior speaks first and everyone else finds reasons to agree. The weak part is the order of the conversation, and no form fixes that. This is for recruiters who run debriefs across several functions and usually aren't the most senior person in the room. You'll get a 20-minute agenda you can paste into an invite, three rules that keep it on evidence, and a decision record short enough that people will fill it in.

My bias, up front. Skillvee is a 60-minute "day at work" simulation that replaces the recruiter phone screen and the first interview round. The candidate solves a real challenge, talks to AI teammates to get the information they need, and defends their decisions on a call, while the screen is recorded. So I spend a lot of time on what a hiring team does with evidence once it has some. The template below works with any interview process, ours or not.

What an interview debrief meeting is for

A debrief has one job: turn several people's separate reads of a candidate into one decision the hiring manager can defend a month later.

Consensus is a bad goal for it. If four interviewers leave agreeing, fine, but agreement produced by the meeting itself is usually just the loudest read winning. I'd rather have people commit to a view alone and let the meeting look at where those views split.

That only works if there's something to compare. If you ran the hiring manager intake meeting the way I laid it out, you already have the signals, each tied to a task. Its advance rule only covers the phone screen, so write the panel's version before the first interview, something like no signal below 2 after discussion and at least two at 3 or better. The debrief scores against the intake page and that rule. If you didn't, write the three or four signals down before the first interview, because a debrief without them is a conversation about vibes.

The spread-first debrief: three rules

I call this the spread-first debrief. It has three rules, and they matter more than the form.

  1. Lock scores before anyone talks. Every interviewer submits a 1-4 score per signal, with a line of evidence, before the meeting and before seeing anyone else's. No submission, no seat. It's the same 1-4 scale as the recruiter phone screen template, so the screen and the panel read the same way.
  2. Start at the spread. Put the scores in a grid and find the rows where the highest and lowest score are two or more points apart. Those rows are the agenda. Rows where everyone's within a point get read out and skipped.
  3. Apply the tape rule. A claim counts only if it names something the candidate said or did, the way you'd describe it if you were pointing at a recording. "She asked who else signs off before she talked price" counts. "She's strategic" doesn't, and neither does "I just didn't see the drive."

Here's the grid for an account executive candidate, with the signals taken from the intake page and three interviewers.

SignalRecruiterHiring managerPeer AESpreadIn the debrief
Runs discovery3341Read out, skip
Sets a real next step2432Discuss
Handles a pricing objection3330Read out, skip
Written follow-up13Not tested2Discuss, and note the gap

Four signals, and only two get discussed. The meeting's time goes to "sets a real next step," where the recruiter saw a 2 and the manager saw a 4. One of them heard something the other didn't, or they're using different definitions of a real next step. Either answer is worth the time. Rereading the two rows everyone agrees on isn't.

The 20-minute interview debrief template

Run one of these per candidate, within a day or two of the last interview. The times add up to 20 minutes.

DEBRIEF: [Candidate], [Role]   Decision owner: [Hiring manager]
Scores locked by: [time, before the meeting]

0:00-2:00   READ THE GRID
Recruiter shares the grid. Nobody explains anything yet.
Mark the rows with a spread of 2 or more.

2:00-12:00  THE SPREADS
For each marked row, lowest score speaks first, then highest:
"What did they say or do that got that score?"
Tape rule: no event, no claim.
Scores can change. Write down what changed them.

12:00-16:00 WHAT NOBODY TESTED
Which signal has a blank, or only one read?
Is that a reason to wait, or can you decide without it?

16:00-19:00 THE DECISION
Hiring manager decides against the panel rule written before
the first interview:
advance / decline / one more look at [named signal].

19:00-20:00 THE RECORD
Recruiter reads the record back. Anyone can correct it now.

The lowest score speaking first is deliberate. The person with the concern is usually the one who'll stay quiet once a senior colleague has praised the candidate, so they go before anyone's had the chance.

Interview debrief questions that pull out evidence

When someone gives you an adjective, these get you back to an event:

  • "What did they say, as close to their words as you remember?"
  • "What would a 4 have looked like on that question?"
  • "Is that from the interview, or from the resume?"
  • "What would you need to see to move one point?"

The third one does a lot of work. In the debriefs I've sat in, plenty of opinions turn out to be about the candidate's background, formed before the interview started. That's a preference in the intake's terms, and it was already kept off the scorecard for a reason.

I'd also ban one question outright: "So, what did everyone think?" It invites a verdict before any evidence and hands the meeting to whoever answers first.

The decision record

The record is five lines. Keep it in your ATS or wherever the req lives.

DECISION: [advance / decline / one more look]   Date: [date]
DECIDED BY: [hiring manager]
EVIDENCE: [one line per discussed row: what the candidate did]
OPEN: [signal nobody tested, who closes it, by when]
TELL THE CANDIDATE: [the reason, in a sentence you'd say out loud]

The last line is the one people skip. If you can't write the reason in a sentence you'd be willing to say to the candidate, you probably have a feeling and no reason yet.

Where this gets hard

Locked scores don't stop a senior person from steering the room. A VP who says "I'd hire her tomorrow" at minute three has moved the meeting regardless of the grid. The only fix I know is to agree the order with them before the debrief, privately, and ask them to speak last on every row.

Small panels strain the spread rule. With two interviewers, a one-point gap may be all the disagreement you'll get, so drop the threshold to one. With a single interviewer there's no spread to read, and the debrief becomes that person's scores against that same panel rule.

Don't average across interviewers, either. A 1 and a 4 on the same signal means two people saw different things, and a 2.5 hides exactly the row you needed to talk about.

And the tape rule is only as good as people's notes. Two days after a panel, most interviewers remember their conclusion much better than what produced it. That's a big part of why we record the whole session in Skillvee: your team can replay the candidate's work, so an argument about what happened can be settled by watching it. If you're running live interviews, the cheap version is asking every interviewer to write one direct quote per score before they leave the call.

What to do after the debrief

Send the record to the hiring manager the same day, and close the open line before the next debrief on that req. After three or four candidates, look at which signals keep landing in "what nobody tested." That's a gap in your interview plan, and it's cheaper to fix there than to keep arguing around it.

If the blank that keeps coming back is how someone works when nobody's asking them questions, that's the part an interview can't reach and a simulation can. The pricing page lists the plans if you want to try one on an open role.

Frequently asked questions

What is an interview debrief?
An interview debrief is the meeting where everyone who interviewed a candidate compares what they saw and the hiring manager makes a decision. A good one compares written scores and the evidence behind them. A bad one is a round of impressions that the most senior person in the room settles.
How long should an interview debrief meeting be?
Twenty minutes per candidate is enough when scores are submitted in writing beforehand. Spend two minutes reading the score grid, ten on the rows where interviewers disagree, four on anything nobody tested, three on the decision and one writing the record.
What questions should you ask in an interview debrief?
Ask questions that pull out evidence: what did the candidate say or do that earned that score, what would have made it one point higher, which signal did nobody test, and what would you need to see to change your mind. Avoid asking whether people liked the candidate.
Who should make the final decision in a debrief?
The hiring manager makes the decision, against the rule that was agreed before interviews started. The recruiter runs the meeting, keeps the discussion on evidence and writes the record. Interviewers supply scores and what they observed, and they don't vote.
Should interviewers see each other's feedback before the debrief?
No. Each interviewer should submit scores and notes before seeing anyone else's. Once people have read a colleague's verdict, their own tends to drift toward it, and the debrief loses the independent reads it exists to compare.