An interview scorecard is a structured document that allows interviewers to take notes about applicants’ answers to job-related questions and score applicants using rating scales ( Workable). It functions as a list of the skills, traits, and qualifications someone will need to have in order to be successful in the upcoming role ( Workable). For teams using specific software, scorecards allow your hiring team to review all of a job's applicants using a set of predetermined criteria ( Greenhouse). This approach aligns with the definition of a structured interview, which is an assessment method designed to measure job-related competencies of applicants by systematically inquiring about their behavior in past experiences and/or their proposed behavior in hypothetical situations ( OPM).
Define the scorecard and the role-specific decision
Anchor the scorecard to the specific decision required for this single role before drafting any interview questions. The scorecard is a list of the skills, traits, and qualifications someone will need to have in order to be successful in the upcoming role ( Workable). This definition establishes the scope of what the panel must evaluate. To create scorecards, you need to identify desirable traits, choose the best interview questions for each trait and then pick a rating scale that makes sense (like a yes/no choice or a 5-point scale) ( Workable). This sequence ensures that the criteria are defined before the questions are selected.
A structured interview is an assessment method designed to measure job-related competencies of applicants by systematically inquiring about their behavior in past experiences and/or their proposed behavior in hypothetical situations ( OPM). Your scorecard must directly support this measurement. If a criterion is not essential to the role's success, it should not appear on the scorecard. Excluding non-essential criteria keeps the focus on the core competencies being assessed.
To build this foundation, start by listing the non-negotiable skills and traits for the role. Then, for each criterion, define what "success" looks like in the context of this specific position. Keep the criteria limited to those that are directly observable and relevant to the daily tasks of the role.
Product-specific configuration notes
In Greenhouse, scorecards include skills, traits, qualifications, and other attributes you want in an applicant ( Greenhouse). You can then choose one or more of these as focus attributes for interviews ( Greenhouse). A scorecard is automatically assigned to an interviewer once their interview is scheduled ( Greenhouse). Once an interview ends, the interviewer will be able to fill out their scorecard ( Greenhouse). Jobs require a scorecard by default, but you can also make scorecards optional ( Greenhouse). You can reconfigure a scorecard even after a job's status is changed to open ( Greenhouse).
Consistency in evaluation
For a structured interview, all applicants are asked the same predetermined questions in the same order ( OPM). All responses are evaluated using the same rating scale and standards for acceptable answers ( OPM). This consistency ensures that the evaluation process is fair and comparable across all applicants for the role.
Choose job-related criteria before choosing questions
Start by grounding your selection in the actual work, not a generic list. You must "1) conduct a job analysis and/or review the job analysis data to determine the tasks and competencies that are critical to the position" ( OPM). This step ensures the criteria reflect the role’s real demands.
Next, have the interview and selection committee review the job description and requisition to "define the job in behavioral terms" ( UC Berkeley). From there, select competencies to describe the desired applicant, including experience, knowledge, education, and intellectual, interpersonal, and motivational competencies ( UC Berkeley). This creates your job/applicant profile.
Do not assume every published behavior applies to your specific role. "You will not be asked to demonstrate all Civil Service Behaviours for one role" ( GOV.UK). Even a comprehensive list must be narrowed to the behaviors that fit the position.
Finally, keep the list manageable. As a general rule of thumb, "structured interviews typically assess 4 – 6 competencies unless the job is unique or at a high level" ( OPM). This limit helps maintain focus during the interview.
Editorial recommendation: * List all potential competencies from the job analysis. * Cut the list to 4–6 items that are critical to success, aligning with the general rule of thumb that structured interviews typically assess 4 – 6 competencies unless the job is unique or at a high level ( OPM). * Ensure each competency is defined in behavioral terms. * Confirm the committee agrees on the final profile before drafting questions.
Pair questions, evidence notes and rating anchors
Link each specific question to the behavioral evidence you intend to capture. Writing questions using the STAR method helps ensure notes capture the situation, the action, and the result ( OPM). This structure keeps the evidence column focused on what the applicant said rather than shifting to personal impressions. Notes should describe the applicant’s answers to the questions and not their personal traits or the interviewer’s perception of the individual ( OPM). When drafting the scorecard, record specific examples of behavior in the evidence field. Avoid adjectives that describe personality or general fit.
Rating anchors must be defined before interviewers score anyone. To develop customized ratings scales, you will need to determine how many proficiency levels you want, create behavioral and/or situational examples for each level, and determine how each question will be scored ( OPM). These anchors serve as the standard for acceptable answers. All responses are evaluated using the same rating scale and standards for acceptable answers ( OPM). This consistency ensures that different interviewers apply the same criteria when reviewing the same applicant.
If you choose a numeric scale, word labels can clarify the meaning of each number. For example, if a 5-point proficiency scale is being used, each competency will receive a score ranging from 1 (Awareness) to 5 (Expert) from each interviewer ( OPM). This specific example from the source material illustrates how labels function as anchors. However, using these specific labels or a five-point structure is an editorial design choice for your team, not a mandated scale. You may select different levels or labels that better fit your role’s requirements. The critical requirement is that the definitions for each level are written as concrete behavioral examples.
Give interviewers a common preparation sheet
A shared preparation sheet ensures every panel member reviews the same baseline before the interview begins. This step aligns the group on what they are evaluating and how they will contribute to the discussion.
Clarify the committee’s charge Make sure the committee's charge is clear and members know their roles and responsibilities ( UC Berkeley). As an editorial recommendation, assign specific competencies to specific interviewers so that the final scorecard reflects distributed observations rather than a single perspective.
Review the job description Have the interview/selection committee review the job description and requisition to define the job in behavioral terms ( UC Berkeley). Select competencies to describe the desired applicant, including experience, knowledge, education, and intellectual, interpersonal, and motivational competencies, which creates your job/applicant profile ( UC Berkeley).
Ensure technical expertise is present If the position requires technical expertise that the hiring authority doesn't have, it is best to include someone who has such expertise ( UC Berkeley).
Leverage multiple perspectives Panel interviews allow for various perspectives on the competencies required for the position and each applicant's qualifications, providing a more objective measurement of the applicant's ability to do the job ( UC Berkeley).
Schedule time for notes Allow fifteen-minute breaks between the interviews to make notes (UC Berkeley).
Record individual evaluations After the interview each interview panelist should record his or her evaluation and recommendation in the interview evaluation form in eRecruit through employee self-service in eRecruit ( UC Berkeley). While this specific workflow uses eRecruit, the core practice is that each panelist documents their own assessment independently before the group discussion.
Review written evidence and handle missing observations
The debrief process relies on written evidence to support opinions during team discussions. As noted in "The pros & cons of interview score sheets | Workable," it is useful to have notes to backup your opinions, without relying on ‘gut’ feelings ( Workable). This approach ensures that the review compares written evidence with each point in the job description and person specification, as documented in "Interviewing job applicants - Recruitment - Acas" ( Acas). Interviewers should complete their notes and/or rating sheets immediately; don't rely on your memory, a timing rule documented in "Closing the Interview | People & Culture" (UC Berkeley).
A critical part of this review is how the team handles gaps in the data. A missing observation remains missing; it does not automatically become a negative score. For instance, "Success Profiles: Civil Service behaviours - GOV.UK" states there is no expectation that you need to demonstrate every part of each example to be successful ( GOV.UK). This principle applies to your own scorecards: if an interviewer did not observe a specific behavior, that blank space indicates a lack of data, not a failure of the applicant.
In some platforms, this distinction is built into the software. Clicking Submit Scorecard without an overall recommendation selected will mark the recommendation as "No Decision" ( Greenhouse). This product-specific behavior keeps a blank recommendation distinct from a negative rating.
Editorial recommendation: When your team reviews the scorecards, explicitly mark any competency where no evidence was recorded as "Not Observed." Do not allow the debrief to fill these gaps with assumptions or negative inferences. If a hiring manager did not ask a specific question, the corresponding evidence field should remain blank or marked as missing. This keeps the decision-making process grounded in what was actually documented.
Copy the blank scorecard and check its limits
The following worksheet is a blank editorial design intended for your team to complete. It is not an official mandated scale or a product-specific feature. When filling out the table, ensure that a missing observation remains missing; do not turn it into a negative score. If an interviewer did not observe a specific behavior, the cell should remain blank or marked as "not observed." This preserves the integrity of the evidence and prevents the absence of data from being misinterpreted as a lack of competency.
| competency | question | evidence to record | rating anchor | interviewer |
|---|---|---|---|---|
| __ | __ | __ | __ | __ |
| __ | __ | __ | __ | __ |
| _ _ | __ | __ | __ | __ |
| _ _ | __ | __ | __ | __ |
| __ | __ | __ | __ | __ |
When implementing a digital version of this process, distinguish between general interviewing practice and specific product settings.
Once an interview ends, the interviewer will be able to fill out their scorecard ( Greenhouse). Depending on your organization’s settings, Job Admins can edit scorecards for up to 30 days after submission, while Site Admins can edit scorecards at any time ( Greenhouse). You can reconfigure a scorecard even after a job's status is changed to open ( Greenhouse). These product-specific workflows and edit windows are distinct from general interviewing practice and should be configured according to your team's specific needs.
Key Takeaways and practical FAQ
What should interviewers write in the evidence column?
The evidence recorded should directly reflect the applicant's answers to the predetermined questions rather than subjective impressions.
How should the team handle an applicant who does not answer a question?
As an editorial recommendation, if an applicant does not provide an answer, the observation remains missing. Do not convert this absence into a negative score, as this would alter the uniform treatment of applicants regarding the specific evidence requested.
Is a specific rating scale mandated for all teams?
Any rating labels used are an editorial design choice by the hiring team, not an official mandated scale from the cited sources. Teams should define their own anchors to ensure consistent interpretation of the evidence collected. This aligns with the principle that all applicants are measured against the same criteria ( University of California, Berkeley).
When should interviewers complete their notes?
As an editorial recommendation, complete notes immediately after the interview to ensure accuracy and reliability of the recorded evidence, rather than relying on memory over time. This supports the goal of measuring applicants against the same criteria consistently ( University of California, Berkeley).