Documenting Hiring Decisions So They Survive Legal Review

Interview notes exist in an uncomfortable position. They are useful for making a good decision, they are required for demonstrating a defensible process, and they are discoverable in any discrimination lawsuit.

Most hiring teams do not think about notes until there is a problem. That is too late.

What hiring documentation needs to establish

The legal test for a selection decision is job-relatedness. If a candidate challenges a rejection, the employer needs to show that the decision was based on qualifications connected to the job requirements.

Documentation that supports this:

• The questions that were asked (standardized across all candidates)
• What the candidate said, summarized factually
• How the response was scored and why
• What competency or job requirement each scored dimension connects to

Documentation that creates problems:

• Observations about age, family status, national origin, disability, or anything protected
• Personality assessments of the candidate that are not grounded in a work context
• Comparisons to other candidates by name during the scoring of an individual interview
• Subjective impressions without behavioral grounding (“didn’t seem like a culture fit”)

What to write in interview notes

The goal of interview notes is to record what the candidate said, not to record your overall impression. Good notes look like:

“Candidate described a project where the initial scope expanded significantly mid-delivery. They identified the scope change early, documented the impact on timeline in writing, and escalated to the client before the original deadline. Client approved a two-week extension. Outcome: delivered on revised schedule.”

That note is factual. It describes behavior. It connects to an assessable competency. It says nothing about the candidate’s demographics, appearance, or anything else outside the work context.

Bad notes look like:

“Very impressive, great presence, clearly a natural leader. Client-facing team would love her. Some hesitation when asked about managing up.”

The first sentence is an impression with no behavioral grounding. The second introduces a bias flag without behavioral specifics. If this is the documentation for a rejection, it is not defensible.

How long to retain records

UGESP requires that records supporting hiring decisions be retained for two years from the date of the decision, or one year for employers with fewer than 150 employees. State laws may require longer retention. EEOC charges can extend the obligation further.

Records include:

• Applications and résumés for all applicants, not just those hired
• Interview guides and scoring rubrics used during the cycle
• Interview notes and scorecards for all candidates
• Any correspondence about the hiring decision

The key phrase is “all applicants.” You need records for people you rejected, not just people you hired. The 4/5ths rule cannot be run without knowing who applied and who was rejected.

The practical system

Most organizations do not have a good documentation system. Notes are scattered across email, calendar notes, and personal notebooks. Scorecards are inconsistently completed. Interview guides differ by hiring manager.

The minimum viable documentation system:

1. A standardized interview guide with questions recorded before the interview starts
2. A scoring rubric that each interviewer completes independently before calibration
3. A shared record (ATS or structured document) where notes and scores are stored against the candidate record
4. A decision record that states the basis for the hire or rejection in terms of competency scores

This takes more time than a verbal debrief and a thumbs-up. It also takes significantly less time than responding to a discrimination charge.