Teach interviewers to record evidence instead of impressions

Interview panels often agree on a decision while leaving little evidence for why they reached one. A talent solutions consultant helps managers use a scorecard connected to work in the role. The scorecard does not replace judgment. Each interviewer receives a shared structure for recording a candidate’s answers, then comparing notes during a debrief. A useful form makes a later discussion more specific and gives the hiring manager a record of what each person heard.

Start with the role rather than a familiar interview form. Read the requisition with the hiring manager and ask what work fills a normal week. A dispatcher receives competing calls, selects an order for response, communicates changes, and records decisions. Select three or four job related criteria from those duties. A short scorecard is easier to use during a live conversation. Ten vague categories lead to rushed ratings and thin notes.

For each criterion, write a work based question, evidence an interviewer should listen for, and space for notes. Handling competing priorities is a criterion. “Tell me about a time when two urgent calls arrived together” is a question. An answer describing how a person gathered facts, selected an order, informed affected people, and recorded a choice gives observable material for a discussion. The note field holds the example in the candidate’s own words.

Here is a fictional workshop situation. Consultant Mark meets a group preparing interviews for a dispatcher role. He asks, “For competing priorities, what would useful evidence sound like?” Manager Suki says, “A candidate should explain how urgent calls are sorted.” Mark writes Suki’s answer, then asks for more detail. Suki adds, “I would listen for who they contacted, why one response came first, and how another caller learned about a wait.” The group turns those details into note prompts.

Mark places an empty scorecard on the table. Beside every criterion, he writes Question, Notes, and Rating. He asks interviewers to write notes before selecting a rating. One interviewer says, “I usually form a view before an interview ends.” Mark replies, “Your initial view is useful, yet notes show why another interviewer should agree with or question a rating.” The group tests the form with a short fictional answer from a candidate named Jordan.

Jordan says, “Two delivery calls arrived during a storm. I checked which location had materials needed before noon. I called the other supervisor, explained our driver order, and gave a new arrival estimate. I entered both calls in our log.” An interviewer records those details under Notes. The interviewer does not write calm under pressure unless Jordan gives an example connected to such a conclusion. Another interviewer has enough detail to ask a related follow up or identify a missing part of Jordan’s answer.

Teach the difference between evidence and impression directly. Strong presence gives no account of events during an interview. Answered after a long pause gives a limited observation, though a pause alone says little about work performance. Explained a choice between two urgent calls, named a supervisor contacted, and described a log entry gives the panel material for a work based conversation. Ask interviewers to separate a spoken example from a personal response to confidence, speaking style, or familiarity.

Use follow up questions to test detail rather than push a preferred answer. After Jordan’s example, an interviewer asks, “What information did you check before selecting an order?” Jordan describes delivery deadlines and inventory status. The interviewer asks, “How did you record a change?” Jordan names a log and describes the fields entered. If Jordan does not remember, record the answer without filling gaps. A missing detail does not prove poor performance. The panel discusses available evidence rather than an invented version of the story.

Agree on rating labels before interviews begin. Labels such as evidence supports the criterion, evidence is mixed, and evidence is limited keep attention on notes. A number alone invites disagreement about whether a three feels higher or lower than a four. When an existing system requires numbers, pair every number with a written definition. One interviewer should not reserve a high rating for confidence while another gives a high rating for a detailed example. Shared definitions expose these differences before a candidate reaches the debrief.

Decide who asks each question. A panel with three people does not need three versions of the same question. In the fictional workshop, Suki assigns competing priorities to one interviewer and communication updates to another. A third interviewer listens for record keeping evidence and asks only necessary follow ups. Each person still takes notes across the conversation. Assigned questions create room for listening, and the panel avoids spending most of an interview on one familiar subject.

Set a few debrief rules. Every interviewer reviews notes before hearing another opinion. The facilitator asks for evidence one criterion at a time. An interviewer who gives a rating names the relevant answer before sharing an interpretation. A manager then asks whether another person heard supporting or conflicting detail. This order reduces the chance of one forceful voice setting the tone before others review their own records.

In a fictional debrief, Suki gives Jordan the strongest rating for competing priorities. Mark asks, “Which words support your rating?” Suki reads notes about checking deadlines, calling another supervisor, and entering both calls in a log. Another interviewer says Jordan did not explain what happened if the second delivery arrived late. The group records a follow up question for a later conversation. Nobody rewrites Jordan’s answer from memory, and nobody treats a missing detail as a hidden answer.

Scorecards need an owner. Ask the hiring manager who prepares the first version, who checks job relevance, and who distributes the final form. The consultant supports training and gathers feedback about unclear prompts. Do not leave interviewers with private versions. Different forms produce different conversations, which makes comparison during a debrief less useful. A final version should reach every panel member before the first interview, with enough time for questions about wording.

Review notes after a few interviews instead of reviewing final ratings alone. Empty note fields suggest a form is hard to use or training missed a step. Long stories with no link to criteria suggest prompts need shortening. When a question brings the same vague answer from several candidates, revise wording with the hiring manager. In a fictional practice block, Mark sees a broad question about judgment yielding broad answers. Mark replaces the broad question with a question about choosing between two urgent calls. The team tests the revised prompt in a roleplay, writes notes before ratings, and sends the updated scorecard to Suki for use in the next interview block.