The panel interview is tomorrow, and yesterday’s interview summary still hasn’t reached the hiring manager. Or it has, and it ends on “lean yes,” so the hiring manager books fifteen minutes with the interviewer to find out what that means. Either way, the decision waits on a conversation the summary was meant to save.

I’d write every interview summary for the person deciding what happens next, and put your recommendation in the first line. The evidence for each rating and the open questions come after it. An interview summary template helps only when it forces that order, so the two templates below are built around it.

Write it in any other order and the debrief ends up doing the summary’s job, days later and from memory, while the candidate waits for an answer.

Why interview summaries get reread instead of used.

Summaries go unused in three recognizable shapes. Each one records the interview, when its reader needed help with a decision.

The first is the recap. It walks through the interview in the order the questions came, so the hiring manager reads the whole thing to find out what the interviewer concluded, and usually finds it in the last line.

The second is the hedge: the “lean yes,” the “could go either way.” Hedges hand over the decision to the hiring manager, who has less to go on than the interviewer did.

The third is the summary that arrives after the next interviewer has already met the candidate. It can be accurate and thorough and still change nothing about what got asked in that room.

Write the summary in the order the reader decides.

A hiring manager reading your summary wants the call first and the reasons second, with what’s still unknown after both. Write it in that order, and keep the practical facts about the candidate for the end. The five steps below follow that order, and the last one is about timing.

Lead with your recommendation and how sure you are.

The first line is the call, and “advance, with one question for the panel” counts as a call. The second line says how confident you are, and why.

Keep the call to what you were asked to assess. If your interview covered discovery and forecasting, recommend on those two. Leave the overall hiring decision to the debrief, where every interviewer’s part of the candidate is on the table at once.

An unsure call is still worth writing. “Advance, low confidence on forecasting” tells the hiring manager what to check next. A “lean yes” asks them to work out what you meant.

Back each rating with the moment that set it.

Under the call, give each competency you assessed its rating and the one moment from the interview that set it: the answer or the action that showed it, and roughly when it came. One moment per competency is enough. The hiring manager needs to see that the rating rests on something they could check, and a rough time lets them find it without watching the whole call.

“Account growth: 4. Walked through the renewal she rescued, including the discount she refused to give (about 18 minutes in)” gives a hiring manager more to weigh than a paragraph about commercial instinct.

Use the scorecard’s competency names word for word, so the summary and the scorecard line up in the debrief. If your team hasn’t settled those competencies yet, start with building interview scorecards.

Hand the next interviewer your open questions.

Close the evidence with open questions for the panel: a competency the interview never reached, or an answer you wanted to push on, plus what the next interviewer should probe. “Didn’t get to how she handles an escalation from an executive sponsor. Worth asking in the panel.”

I’d argue this is the most useful line in the summary, because it’s the only one that changes what happens in the next interview. Label an untested suspicion as a suspicion, so no one in the debrief reads it as a finding.

Add the facts that change the plan.

The notice period and the salary expectation have nothing to do with competencies, and the hiring manager still needs them. Put these in a short block at the end, as the candidate gave them to you, so the hiring manager sees them while they can still change the plan.

Keep these facts out of the ratings, so a salary expectation above the band never reads as a mark against the candidate’s skills.

Send it before the next interview in the loop.

A summary that lands after the next interviewer has met the candidate can’t hand them your open questions. Send it the same day, and before the next round whenever the next round is close.

If the debrief is already booked, the summary is due there with every other interviewer’s, before anyone has heard the others talk.

The meeting that reads every summary has its own walkthrough, how to run an interview debrief.

Two interview summary templates you can copy.

The first template is for an interview where you were asked to assess a set of competencies. The second is shorter, for a recruiter screen, where the question is whether the hiring manager should spend an hour with this person. I’d hold both to one screen of text.

The competency interview template.

The example lines below are for a sales hire, so swap in the competencies from your own scorecard and keep the order of the rows.

The recruiter screen template.

A recruiter screen summary answers one question for the hiring manager, whether to book the next interview, so it can run shorter:

• Next step: book the hiring manager interview, or close the process and say why.
• Why they’re looking, in the candidate’s own words.
• Each must-have for the role, marked met, not met, or not yet known.
• Notice period and salary expectation, as the candidate stated them.
• The first question the hiring manager should ask.

I’d defend the “not yet known” mark hardest, because marked gaps get asked about in the next interview, while a summary written to sound confident hides them.

Where Metaview fits in interview summaries.

Finding the moment behind each rating takes longer than any other step, because notes typed while listening often miss the candidate’s exact words. Metaview helps with that step, and you still own every rating and the call.

Metaview’s Notetaker, one of the agents on its recruiting platform, turns each interview it records into a transcript and structured notes. It captures every spoken word, which puts the candidate’s answer in the record with the minute it came. The evidence line in your summary can then quote it.

Each kind of call can have its own notes template, so set the headings of your recruiter screen template to match the summary you plan to send.

1

2

3

1. 1The screening call’s notes, sorted under two headings from its template, “Overview” and “Salary expectations.”
2. 2The template list, where “Recruiter Screen (Sales)” applies to “Recruiter Screens” for the “Account Exec” role.
3. 3The label “04:25: Motivations for role” ties a topic to its minute in the recording, which is what an evidence line cites.

Metaview also generates one-paragraph candidate summaries, written from the conversation.

1

2

3

1. 1An “AI Notes” card introducing the summary of one conversation.
2. 2One of the interviewer’s questions, about why the candidate took the call, set as a heading.
3. 3Short notes on the candidate’s answer to the next question, about the size of the team they manage.

This 76-second Metaview 101 clip shows the summary step in the product: a product specialist at Metaview picks the topics her hiring team will care about from her interview notes and generates a one-paragraph summary to add to them.

The judgment stays with the interviewer here too. Metaview’s browser extensions for Ashby and Greenhouse autofill the objective parts of a scorecard and leave every subjective field, the hiring recommendation among them, for the interviewer. Write the ratings and the call yourself even when Metaview has generated a summary of what was said, because each one is a judgment about the candidate.

When the hiring manager needs the whole loop, multi-source notes pull the interviews you add, and files like the job description, into a single notes document. Metaview’s chief technology officer, Shahriar Tajbakhsh, explained years ago why no single write-up can carry the hire.

That’s the reason I’d keep each summary to the competencies its interviewer covered and let the loop add up in the debrief, where every summary sits side by side.

Check whether your summaries are doing their job.

Take one open role and read every summary its interviewers sent last month.

• Replies: count the summaries that drew a question from the hiring manager instead of a decision. If that’s most of them, move the recommendation to the first line.
• Evidence: look for the moment behind every rating. A rating with nothing beside it sends you back to the second step.
• Open questions: check whether the next interviewer asked about what the previous summary left open. If they didn’t, the line was missing or the summary arrived too late.
• Timing: compare when each summary arrived with when the next interview started, and fix the sending habit for any that came after.
• Length: open any summary that runs past one screen and check whether it follows the order of the questions. If it does, rewrite it in the template’s order.

I’d start with the replies. A hiring manager who answers “move her to the panel” instead of asking what you meant has made an evidence-led hiring decision from your summary, without the recording.