Good interview notes record observable evidence tied to your scorecard, not personal impressions. The single biggest upgrade you can make is to capture what the candidate actually said rather than how you felt about them. If your notes let a colleague who was not in the room reach the same conclusion from the same facts, they are doing their job. If they read like a mood summary ("sharp, likable, good fit"), they are not.
This guide is written for the interviewer taking the notes: what to write down, what to leave out, how to stay present instead of transcribing, a copy-usable template, and how to turn your notes into a fast, comparable debrief.
What should an interviewer write down during an interview?
Write down evidence. Evidence is anything specific and checkable: the example a candidate gave, the action they personally took, the result they described, and their exact words when the phrasing matters.
Anchor every note to a competency on your scorecard. If the role calls for stakeholder management, you are listening for a moment where the candidate navigated a real disagreement, and your note captures that moment, not a rating of their charm.
Concretely, capture:
- Specific examples. "Led migration of billing system off a legacy vendor; owned the rollback plan." That is a fact you can probe and compare.
- Direct quotes. When a candidate says something revealing, capture it verbatim. "I shipped it without telling the on-call team" tells you more than "seemed a bit reckless."
- Competency signals. Note both the signal and which criterion it maps to. Positive and negative both count.
- What they owned versus what the team did. Listen for "I" versus "we." Note which one they used, because it changes what the example proves.
The test for a good note is simple. Could you hand it to another interviewer and have them independently agree it supports a specific rating on a specific competency? If yes, keep it. If it only makes sense inside your head, rewrite it as evidence.
What should you never write in interview notes?
Some things do not belong in interview notes, and a few actively create risk.
Do not write subjective impressions as if they were findings. "Great energy," "not a culture fit," "felt off" are conclusions without evidence. They are impossible to compare across candidates and easy to challenge later. If you have an impression, trace it back to what caused it and write that down instead. "Felt off" might really be "gave three answers where the result was unclear and could not say what he would do differently." That is a usable note.
Do not reference protected characteristics or anything derived from them. Age, gender, ethnicity, religion, disability, pregnancy, family or marital status, and similar attributes have no place in interview notes. This is not only about fairness in the room. Notes are records, and if a rejected candidate ever challenges a decision, subjective or personal-impression notes are exactly what create exposure. That risk is real in essentially any jurisdiction, which is a good reason to keep every note tied to the requirements of the job rather than to the person.
Do not record "gut feel" as a substitute for assessment. Instinct can flag something worth probing, but the note should capture what you then observed, not the instinct itself.
The through-line: notes describe the candidate's demonstrated ability against the role, and nothing else.
How do I take notes without losing eye contact?
The practical tension is that thorough notes compete with being present. When you are typing, you are not listening, and candidates notice. Miss the follow-up and you lose the best evidence of the whole interview.
Here is how to take notes live without disappearing behind your laptop:
- Pre-load your competencies. Before the interview, write each scorecard criterion as a heading. You are now filling buckets, not writing prose.
- Capture keywords, not sentences. During the answer, jot the trigger: "billing migration, owned rollback, I not we." Two or three words is enough to reconstruct the moment.
- Quote only the line that matters. You cannot transcribe by hand. Catch the one sentence that shifts your read and let the rest go.
- Mark, do not judge, in the moment. Use a quick "+" or "-" beside a note. Decide the rating after the interview, not while the next question is forming.
- Leave a gap after each answer. A three-second pause to finish a note also gives the candidate room to add the detail that becomes your best evidence.
- Fill in detail immediately after. Spend five minutes right after the call expanding keywords into evidence while it is fresh. Notes reconstructed a day later are mostly impression.
There is a cleaner option for the presence problem. If the conversation is recorded and transcribed, you can stop hand-transcribing entirely and actually listen. A verbatim transcript means you leave the room with a complete record and can go back to exact wording when you map evidence to criteria. This is where an AI meeting assistant like Numi helps: it records, transcribes, and summarizes the conversation so you stay present and still have every quote, then you do the judgment of mapping evidence to your scorecard. To be clear about what the tool does and does not do: it produces the transcript and summary; it does not score or rank candidates, and that assessment stays with you and the panel.
A note on records. Because a transcript is a record, handle it like one: tell candidates when you are recording, keep it access-controlled, and use a tool whose data handling you are comfortable with. Numi is EU-hosted and does not train on your data, but the broader point holds with any tool you choose.
How do I map interview notes to scorecard criteria?
Notes and scorecards should share one structure. If your scorecard rates four competencies, your notes should have four evidence buckets, so the mapping is a lookup rather than a reinterpretation.
For each competency, your notes should hold three things: the evidence (what happened), the quote or example (the specific proof), and a flag (a green flag that raises confidence or a red flag that lowers it). Then, and only then, a rating.
Keeping evidence and rating in separate fields matters. It forces you to justify the rating with something concrete, and it lets a colleague check your reasoning by reading the evidence and deciding whether they would land in the same place. When evidence and judgment blur together, you get a number nobody can interrogate.
An interview notes template you can copy
Use the template below as-is or adapt the competency labels to your scorecard. It is deliberately neutral and criteria-based: every field points back to the role and the evidence, never to the person. Fill it during and right after the interview.
INTERVIEW NOTES
Candidate: [ID or reference, not personal details]
Role: [Title]
Interviewer: [Name]
Date: [YYYY-MM-DD]
Interview stage: [e.g. first round / technical / panel]
--- SCORECARD COMPETENCIES ---
(One block per competency on your scorecard.)
Competency: [e.g. Stakeholder management]
Evidence (what happened): [Specific example, situation + action + result]
Quote / example: ["Exact words, when phrasing matters"]
Ownership (I vs we): [What the candidate personally did]
Flag: [ + green / - red, with reason ]
Rating: [Against your scorecard scale]
Competency: [e.g. Problem solving]
Evidence (what happened): [ ... ]
Quote / example: [ ... ]
Ownership (I vs we): [ ... ]
Flag: [ + / - with reason ]
Rating: [ ... ]
Competency: [e.g. Role-specific / technical skill]
Evidence (what happened): [ ... ]
Quote / example: [ ... ]
Ownership (I vs we): [ ... ]
Flag: [ + / - with reason ]
Rating: [ ... ]
--- OPEN QUESTIONS FOR NEXT ROUND ---
[What is still unproven and who should probe it]
--- OVERALL RECOMMENDATION ---
Recommendation: [ Advance / Hold / Do not advance ]
Primary reason: [One sentence, tied to evidence above]
Do NOT record: personal impressions unsupported by evidence,
"gut feel," or any reference to protected characteristics.
The footer is not decoration. Leaving the "do not record" reminder in the template keeps every interviewer honest under time pressure, which is exactly when impressions tend to leak into notes.
How do interview notes turn into a fast debrief?
Structured notes make the debrief a comparison instead of a debate. When every interviewer arrives with evidence organized by the same competencies, the panel talks about specific examples rather than trading impressions, and the loudest voice loses its unfair advantage.
Run the debrief off the evidence. For each competency, each interviewer reads their example and quote, states their flag, and gives a rating with a reason. Where ratings diverge, you compare the underlying evidence, and usually one person heard something the others missed. That is a productive disagreement, and it is only possible because the notes are concrete.
Then collapse to a decision. Each interviewer gives one recommendation and one primary reason. Because the reasons are grounded in what the candidate actually said, the panel is deciding on the same facts.
The payoff compounds across a hiring round. Evidence-based notes are comparable between candidates, defensible if a decision is ever questioned, and far faster to review than pages of prose. And the habit that makes all of it work is the one from the top of this guide: write what the candidate said, not how they made you feel.