Interview Notes: What to Write Down (and What Never To)

A useful interview note records observable, job-related behavior: a specific example the candidate gave, the answer they actually spoke, and a competency score you wrote during the interview. Leave out subjective impressions like "seemed confident" and anything touching a protected class. Keep notes consistent across candidates, access-controlled, and retained per your own verified policy.

Most interview notes drift toward feelings. You leave the room with a vibe, jot down a word or two, and by the debrief that word has quietly become your evidence. The fix is a simple discipline: write down what happened, not what you concluded. Behavior, answers, and a score anchored to a job criterion are all repeatable and reviewable. Impressions are not.

Here is the two-column split to keep in front of you while you take notes. It is the extractable version of the whole method.

Interview notes are not a private diary. They are part of a hiring decision, and hiring decisions get questioned. A rejected candidate may ask why. A manager may challenge a panel's call. Your own People team may review a pattern across a role. In each case, the notes are the record of how the decision was actually made.

Three things determine whether that record helps or hurts you, and none of them are about legal cleverness. First, consistency: did every candidate face comparable questions scored against the same criteria? Second, access control: who can read a candidate's note, and can you prove it was not open to the whole company? Third, retention: how long you keep notes and records, and whether you follow your own stated rule.

We are deliberately not citing statutes, dates, or jurisdictions here, because obligations differ by where you operate and change over time. Treat this as directional. Verify your own legal and retention obligations with someone qualified in your jurisdiction before you set policy.

The strongest notes are evidence tied to a job criterion. If the role needs someone who can debug under pressure, you are not scoring "smart." You are scoring whether they walked you through a real incident, isolated the cause, and described the tradeoff they chose. That is observable. That is defensible in the directional sense that matters: it supports a fairer, more consistent decision.

STAR-shaped answers make this easy to capture. When a candidate describes a Situation, the Task they owned, the Action they took, and the Result, you have a self-contained piece of evidence. Write the answer down in their framing, then attach it to the competency it demonstrates.

• Situation and task: the context and what the candidate was responsible for
• Action: the specific thing they personally did, in their words
• Result: the outcome, including what they would change
• Competency link: which job criterion this answer speaks to
• Your score, written now, with a one-line reason

The never-write list has two families. The first is subjective impression: "good energy," "not a culture fit," "felt off," "reminded me of a strong hire." These read as reasons but carry no evidence, and they are exactly the phrasing that looks worst when a decision is later questioned. Replace each one with the behavior that triggered it, or delete it.

The second family is anything touching a protected class: age, family or caregiving status, pregnancy, health or disability, national origin, religion, and so on. Do not record it, do not infer it, do not let it color a score. This is directional legal framing, not a statute cite. The safe rule is simpler than the law: if a note is not about the candidate's ability to do the job, it does not belong in the file.

Risky phrasing to catch and rewrite includes "young and hungry," "might struggle with the travel given the kids," "overqualified, probably winding down," "accent was hard to follow," and "culture fit concern" with nothing behind it. Each one either records a protected-class signal or hides a bias behind a vibe. Rewrite it as job-related behavior or remove it entirely.

Memory decays and reshapes itself around whatever you decided at the end. A scorecard filled in during the interview freezes your read while it is still evidence-based. The method is a small fillable table: the competencies for this role, a 1-5 anchored scale, and an evidence field where you paste the actual example the candidate gave.

The N/A row matters as much as the scores. If a dimension did not come up, mark it not assessed rather than guessing. A guessed score is worse than a blank one, because it looks like evidence when it is not. Reline's Candidate Scorecard Lens works the same way: it scores only what was actually discussed in the recorded interview, marks unassessed dimensions N/A, and never replaces a human hiring decision. There is no ATS integration and no auto-send; it produces notes you review, not a verdict it ships.

There is a real ladder of rigor here, and each rung buys you something concrete. This compares the methods themselves, not any particular tool.

The jump from unstructured notes to a scorecard is the biggest single gain in consistency. The jump from a scorecard to a recorded-plus-scorecard workflow is about accuracy: you stop arguing over what a candidate said and go listen to it.

By the debrief, a candidate's best answer has usually shrunk to a paraphrase, and the paraphrase is doing the persuading. Reline records the interview locally, capturing microphone and system audio on-device on macOS, Windows, and Linux (beta). No recorder bot joins the call and nothing shows up in the participant list to unsettle the candidate. The capture is local; transcription, AI summaries, and storage happen in our cloud under a data-processing agreement, and meetings are never used to train models.

Once it is recorded, playback is where impressions turn back into evidence. You get a timeline scrubber and a transcript you can click to seek: tap a line and playback jumps to that moment, so you can quote the exact sentence in your scorecard instead of a fading memory of it. Transcription covers 60+ languages with automatic language detection, handled by our cloud transcription provider.

Candidate notes are some of the most sensitive documents a company holds. They contain PII, subjective judgments, and the raw material of a decision that affects someone's livelihood. The default in most tools is far too open: anyone with a broad role can read anything. Reline inverts that.

Access is private by default across a 5-level model. A workspace role alone grants zero access to a candidate note. Every viewer needs an explicit, revocable grant. There is no silent admin backdoor: an "open" teamspace grants Edit only to Members, not to Owners or Admins by default, and web-publishing is a separate, deliberate action rather than something that happens by accident. This is access control, not encryption, but it is exactly the posture sensitive candidate PII needs: you decide, per person, who can see each note.

Individual discipline is not enough when four interviewers each take notes their own way. The panel needs one shape. The Interview Debrief Lens turns each recorded conversation into the same evidence-anchored, competency-scored structure, so the hiring committee is comparing like with like instead of reconciling four different note styles at the debrief.

1. Agree the competencies and the 1-5 anchors before the loop starts
2. Each interviewer records their session locally and scores live
3. Run the Interview Debrief Lens to normalize every session into the same format
4. Share each note only with the panel members who need it, via explicit grant
5. Debrief from evidence: pull a quote by clicking the transcript, not from memory
6. Retain or delete the notes per your own verified policy

Better interview notes are not about legal armor. They are about making a fairer, more consistent decision and being able to explain how you made it. Record behavior and answers, not feelings. Score live against job criteria and mark what you did not assess. Keep the notes locked to the people who need them, and quote what the candidate actually said. Do those four things and your notes support the decision instead of undermining it. Reline gives you the capture, the Lenses, and the private-by-default access model to make that the default, not the exception.