River
Y CombinatorBacked by Y Combinator

People & Exec SupportFree tool

Hiring Debrief From Interview Scorecards

A hiring debrief built from your panel's scorecards: each comment under the skill it shows, the disagreements that are real, and what nobody tested.

Helpful to include

Free to start · Opens in your River workspace, ready to edit and share

How to run a hiring debrief

A hiring debrief is the meeting where everyone who interviewed a candidate pools what they learned and the team makes a decision. A good one starts from scorecards written before anyone talks. It compares evidence one skill at a time, separates what interviewers saw from what they concluded, reduces each real disagreement to one answerable question, and names any skill nobody tested. It ends with a written decision and its reasons, or a short list of what must be checked first.

If you remember one rule, make it this: compare evidence, not verdicts. When two interviewers disagree, first check whether they tested the same skill. Often they didn't, and what looked like a split turns out to be two separate findings.

Three people seated behind a long wooden table face a person in a dark suit, who is seen from behind in the foreground
When three people watch the same interview, each should score it alone first. Photo: Saúl Bucio on Unsplash

Collect every scorecard before anyone talks

Ask each interviewer to write up their notes and ratings alone, soon after the interview, and submit them before the debrief. In its guide to structured interviews, the US Office of Personnel Management (OPM) says each panelist should form an independent evaluation without discussion with other panel members1. Only then does the panel compare notes.

Keep scorecards hidden from other interviewers until all of them are in. Greenhouse, which sells hiring software, studied scorecards from more than 10 million panel interviews. Interviewers who peeked at a colleague's scorecard before submitting were 3.6% more likely to give the exact same rating2. Each rating that drifts toward a colleague's hides a disagreement the debrief should hear.

Set a deadline, such as the end of the next working day, and chase anyone who misses it. Notes written after the meeting record what the room decided, not what the interviewer saw.

Separate what they saw from what they concluded

Before the meeting, mark each comment as an observation or a verdict. An observation records the question and what the candidate said or did: "Asked who set the go-live date, she said the client's IT lead did." A verdict is a conclusion with nothing behind it, such as "not strategic," "lacks presence" or "great culture fit."

Only observations can be checked against someone else's notes. OPM's guide wants every rating "specific, defensible, and supported by behavioral examples," including actual examples of the candidate's answers1. When a verdict matters, ask the interviewer what they saw. If nothing comes back, it stays on the record but carries no weight.

ExampleTurning a verdict into evidenceAn illustrative example written for this guide

Scorecard: "Not strategic. I wouldn't trust her with a big account."

Facilitator: "What did she say or do that made you think so?"

Interviewer: "I asked why the client wanted the new system. She listed its features but never mentioned the problem they were trying to fix."

  • Before. A verdict nobody can check or answer.
  • After. One observation about understanding the client, which others can weigh against their own notes.

Some comments must not count at all. Strike any remark about age, accent, family plans, religion, health or appearance, and build no argument on it. In the US, the EEOC says an employer may not base hiring decisions on stereotypes and assumptions3 about protected traits. These include race, color, religion, sex, national origin, age (40 or older), disability and genetic information.

Sort every comment by the skill it shows

List the four to seven competencies the role needs, taken from the job description rather than invented in the room. Google's re:Work hiring guide recommends defining specific attributes for the role instead of relying on "gut feel" or vague cultural fits4.

Comparing one competency at a time keeps the discipline of a structured interview, and that discipline pays off. In a 2022 reanalysis of earlier hiring studies, Paul Sackett and colleagues found structured interviews were the strongest predictor of job performance5 among the methods they compared. Sorting also blunts the halo effect, where a strong impression on one skill lifts the ratings on the others.

File every comment under the competency it gives evidence for, with the interviewer's name beside it. Comments that fit nowhere go in their own pile, counted rather than deleted. The finished grid shows coverage: how many interviewers produced real evidence on each competency. It's often lopsided, with several people probing the same strength while a skill the job depends on goes untested.

A coverage grid for one candidate, an implementation consultant (illustrative)

CompetencyWho tested itWhat the notes holdWhat to do
Running a go-liveHiring manager, peer, customer leadThree accounts; two disagree on who made the final callSettle the conflict with one question
Data migrationPeerOne detailed example, with volumes and datesEnough, if the example holds up
Client communicationRecruiter, customer leadOne observation and one verdict ("great presence")Ask the recruiter what they saw
Training deliveryNobodyNothingTest it before anyone decides

Count observations, not mentions. A verdict on its own doesn't make a skill covered.

Run the hiring debrief meeting

Give the meeting a facilitator who isn't the hiring manager, and book 30 to 45 minutes. At Amazon, a trained employee from outside the team, called a Bar Raiser, facilitates the debrief to keep it data-driven6. One hiring manager there says it helps eliminate "the habit of looking to the most senior person in the room to make the decision."

  1. Read the recommendations first

    The facilitator reads each submitted recommendation aloud before any discussion, so nobody shifts theirs to match the room.

  2. Walk the grid one skill at a time

    For each competency, only the people who tested it share their evidence. Untested skills go on the gap list.

  3. Test each disagreement

    Ask whether both people tested the same skill. If not, record two findings. If so, compare their observations.

  4. Find the question it turns on

    For each real conflict, write the one question that would settle it, who can answer it and by when.

  5. Decide, or list what's missing

    Decide only if the observations support it. Otherwise, name what's outstanding and when it will be closed.

Don't paper over a split with an average. On a 4-point scale, a 4 and a 1 average 2.5: a score neither interviewer gave, which buries the disagreement worth resolving. Talk it through instead. OPM's guide asks panelists to thoroughly explore the basis for discrepancies in their ratings1, then reach a consensus.

Close the gaps, then write down the decision

A real conflict often turns on a single fact. If two interviewers heard different accounts of who made a go-live call, one reference question can settle it. An untested competency needs a short test of its own before anyone decides. A 20-minute exercise often does it, or a call built on one question from a behavioral interview question bank.

Then write down the decision and what carried it: the deciding observations, how each conflict was settled, and anything still untested. In the US, covered employers must keep records having to do with hiring for a year7 after they are made or after the decision, whichever comes later. If someone files a discrimination charge, keep the relevant records until it is resolved.

When to call an employment lawyer

Get advice if a remark about a protected trait shaped the discussion, if a candidate challenges the decision, or if you're unsure which records to keep. This guide is general information, not legal advice.

Before you close the debrief

  • Every scorecard was submitted before the meeting
  • Verdicts with nothing behind them carried no weight
  • Each comment sits under the competency it shows
  • Each real conflict has one question, an owner and a date
  • Untested skills have a test booked or are named as a risk
  • Remarks about protected traits were struck
  • The decision and its reasons are written down and filed

Short on time before the debrief? The tool at the top of this page sorts your panel's comments into this grid and drafts the write-up. For the next candidate, the interview process and scorecard template gives every competency one interviewer to own.

How it works

Paste the scorecards and interview notes in whatever shape they arrived, or attach them, and say what each interviewer was meant to test if you know. River reads every comment, places it under the competency it shows and marks it as something seen or a verdict. You get a sheet with every comment and a coverage grid, plus a written debrief, in your workspace.

The debrief says what's settled, sets out each real conflict with the question that would resolve it, and lists the skills nobody tested. River uses your competency list if you have one and drafts four to seven from the role if not. It shows every rating as given rather than averaged, sets aside remarks about protected traits, and leaves the decision to you.

  1. Add the scorecards

    Paste or attach the scorecards and notes as they arrived, and pick what's holding up the decision.

  2. River sorts the feedback

    Each comment goes under the competency it shows, marked as something seen or a verdict without evidence.

  3. Get your debrief

    A sheet with the coverage grid and every rating unaveraged, plus a write-up of conflicts, gaps and open items.

  4. Edit and follow up

    Change anything, share it with the panel, or ask River to draft reference questions or fix the interview plan.

What you get

  • Every comment from every scorecard, quoted under the competency it shows, with the interviewer's name beside it
  • Each comment marked as something the interviewer saw or a verdict with nothing behind it
  • A coverage grid counting how many interviewers tested each competency, zeros included, with every rating shown unaveraged
  • Each real disagreement with both sides' evidence, the question that settles it, and who can answer it
  • The quickest way to test each skill nobody covered, so the gap closes before anyone decides
  • A written debrief in your workspace: what's settled, what's outstanding, and how long each open item takes

Common questions

What is a hiring debrief?

A hiring debrief is the meeting, usually held after the final interview, where the panel shares what it learned about a candidate and agrees on the next step. In a well-run one, everyone submits written feedback first and the group compares evidence skill by skill. It closes with a decision, or with the specific gaps to fill before making one.

How do I write a hiring debrief with River?

Paste the scorecards and notes into the box at the top of this page, or attach up to 10 files, and add the job description if you have it. River sorts every comment by competency and builds a coverage grid with each rating shown. It writes the debrief into your free River workspace, where you can edit it and share it with the panel.

Who should attend a hiring debrief?

Everyone who interviewed the candidate, plus the hiring manager and a facilitator, often the recruiter. Leave out people who never met the candidate, since all they can do is react to what others say. If an interviewer can't attend, their written scorecard still counts, and the facilitator reads it out so their evidence gets the same hearing.

How soon after the interviews should the debrief happen?

Within a day or two of the last interview, once every scorecard is in. Wait longer and memories fade, so people fall back on impressions instead of notes. Meet before the scorecards arrive and the first opinion voiced tends to become everyone's. If one interviewer is late, chase the scorecard rather than starting without it.

What should the facilitator ask in a debrief?

Four questions do most of the work: "What did you see or hear that makes you say that?" "Which competency does that show?" "Did anyone else test it?" and "What would change your mind?" Asked of every strong opinion, positive or negative, they turn verdicts into evidence and show quickly where the panel has nothing to go on.

Does River decide whether to hire the candidate?

No. River gives a hire or no-hire view only when the observed evidence supports one, and it cites the rows that view rests on. Otherwise it lists what's still outstanding and how long each item would take to close. It never invents evidence or softens a thin panel, and the decision stays with your hiring team.

Is the hiring debrief tool free?

Yes, it is free to start. Your debrief opens in a River workspace, where you can edit it, share it with your hiring team or ask River to change it. Paid plans add more AI use and access to the most advanced models.

Sources

  1. U.S. Office of Personnel Management. “Structured Interviews: A Practical Guide.” opm.gov (opens in a new tab)

  2. Greenhouse. “How interview scorecard peeking can create bias in hiring.” greenhouse.com (opens in a new tab)

  3. U.S. Equal Employment Opportunity Commission. “Prohibited Employment Policies/Practices.” eeoc.gov (opens in a new tab)

  4. Google re:Work. “A guide to structured interviewing for better hiring practices.” rework.withgoogle.com (opens in a new tab)

  5. Society for Industrial and Organizational Psychology. “Is Cognitive Ability the Best Predictor of Job Performance? New Research Says It’s Time to Think Again.” siop.org (opens in a new tab)

  6. Amazon. “What is an Amazon bar raiser?” aboutamazon.com (opens in a new tab)

  7. eCFR. “29 CFR 1602.14 — Preservation of records made or kept.” ecfr.gov (opens in a new tab)

Built by

Chandler Supple

Co-founder & CEO, River

Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.

Reviewed by

Brian Joseff, Co-founder, River