EEOC-Compliant Hiring Documentation: A Defensible Record

Most hiring teams do not lose discrimination complaints because they made a bad decision. They lose because they cannot prove they made a good one. The Equal Employment Opportunity Commission (EEOC) and the federal courts do not require perfection; they require a contemporaneous, consistent, job-related record — one that shows each candidate was evaluated against the same criteria, by the same process, with documented rationale.

This guide gives you a concrete procedure for building that record. It is not about legal strategy — consult employment counsel for that — it is about the documentation discipline that makes a defensible record possible in the first place.

Why the Documentation Standard Matters

Under Title VII of the Civil Rights Act (1964), the Age Discrimination in Employment Act (1967), and the Americans with Disabilities Act (1990), an employer who cannot explain why it selected one candidate over another creates a gap that an adverse-inference argument can fill. The Supreme Court's framework in McDonnell Douglas Corp. v. Green (1973) places the burden of producing a legitimate, nondiscriminatory reason on the employer — but that reason must be articulable, not reconstructed after the fact.

The EEOC's own enforcement guidance on record-keeping (29 C.F.R. § 1602) requires employers with 15 or more employees to retain personnel and employment records for at least one year from the date of the personnel action. If a charge is filed, records must be preserved until final disposition. Many employment attorneys recommend a three-to-five year retention policy as a practical floor.

Separately, the Uniform Guidelines on Employee Selection Procedures (1978), adopted jointly by the EEOC, the Department of Labor, the Department of Justice, and the Office of Personnel Management, require that selection procedures be job-related and, where adverse impact exists (a selection rate for a protected group less than four-fifths of the highest-selected group), that they be validated. Documentation is the mechanism by which you demonstrate both.

The Seven-Step Documentation Procedure

Step 1 — Anchor Every Requirement to the Job Before Posting

Action: Before the requisition goes live, write a documented justification for each stated requirement — education threshold, years of experience, specific technical skill. If you cannot write a one-sentence job-relatedness statement for a requirement, remove it.

What good looks like: A requirements matrix with three columns: Requirement | Business Justification | Source (e.g., O*NET code, manager interview, prior performance data).

Over-specified job descriptions are a common source of disparate-impact exposure. For more on trimming requirements to what is genuinely predictive, see How to Write a Better Job Description and Cut Over-Specs.

Step 2 — Define Evaluation Criteria Before Seeing Any Candidates

Action: Document your scoring rubric — dimensions, definitions, and rating anchors — before the first resume is opened. Changing criteria after reviewing candidates is one of the clearest signals of pretext.

What good looks like: A written rubric stored in your ATS or a shared drive, timestamped before the review period opens. At Verdict, we organize evaluation across six dimensions: Capability, Track Record, Trajectory, Influence, Domain Edge, and Risk Surface. Whatever framework you use, it must be fixed in advance and applied uniformly.

For a deeper treatment of structuring these dimensions, Candidate Evaluation Criteria: How to Score Candidates covers the mechanics in detail.

Step 3 — Apply Screening Criteria Uniformly and Log Dispositions

Action: For every applicant, record the disposition (advance, hold, decline) and the specific criterion that drove it. "Not enough experience" is not sufficient; "fewer than three years of direct P&L responsibility, which is required per the job posting and Step 1 matrix" is.

What good looks like: A disposition log — spreadsheet or ATS field — that maps each candidate ID to a coded reason tied to your Step 1 criteria. Run a simple adverse-impact check (four-fifths rule) on your screened-out population before moving to interviews.

Step 4 — Use Structured Interviews and Document the Questions Asked

Action: Prepare interview questions in advance, tied to the competencies in your rubric. Ask the same core questions of every candidate for a given role. Document which questions were asked and summarize (or record, with consent) the candidate's response.

What good looks like: An interview guide with questions, the competency each question targets, and a scoring key. Interviewer notes should describe behavior evidence — what the candidate said or did — not impressions or traits. "Candidate described a specific instance of leading a cross-functional team through a regulatory audit" is documentable; "seemed confident" is not.

Meta-analytic evidence supports structured interviewing as a meaningful predictor of job performance (Schmidt & Hunter, 1998, Psychological Bulletin, 124(2), 262–274). The incremental validity comes precisely from the consistency that documentation enforces.

Step 5 — Score Independently Before Calibrating

Action: Each interviewer or evaluator should complete their scoring before any group discussion. Capture those independent scores in writing. Then document the calibration conversation — who was present, what was discussed, what score adjustments were made and why.

What good looks like: Timestamped individual scorecards followed by a brief calibration memo. If scores diverge significantly, the reason for reconciliation should be explicit and tied to evidence, not consensus or seniority.

Step 6 — Write the Selection Rationale Before Extending an Offer

Action: Before the offer call, write a one-to-two paragraph selection rationale that states: (a) the criteria used, (b) how the selected candidate performed against those criteria, and (c) how that compared to the next-closest finalist. This document should be written prospectively, not reconstructed if a charge is later filed.

What good looks like: A selection memo that a neutral third party — say, an EEOC investigator — could read and conclude that the decision was made on the documented criteria, not on protected characteristics. It does not need to be long. It needs to be honest and grounded in the evidence you collected in Steps 2–5.

Step 7 — Retain the Complete Record on a Defined Schedule

Action: Identify every document generated in the process — job posting, requirements matrix, application materials, screening logs, interview guides, scorecards, calibration notes, offer letters — and confirm it is stored in a system with access controls and a retention schedule aligned to at least 29 C.F.R. § 1602 minimums.

What good looks like: A retention policy document that specifies: document type, retention period, storage location, who has access, and who is responsible for deletion after expiration. Legal holds override scheduled deletion automatically when a charge is filed.

Worked Example: A Senior Analyst Role

Suppose you are hiring a Senior Financial Analyst. Here is what a compliant record looks like at the selection stage, organized against Verdict's evaluation dimensions:

Selection rationale excerpt: "Candidate A was selected based on stronger evidence across Capability (work sample quality), Track Record (public company close experience meeting the stated requirement), and Domain Edge (SaaS fluency demonstrated without prompting). Candidate B did not meet the three-year public company requirement documented in the job requirements matrix dated [date]. No protected-class information was considered at any stage."

This memo, stored with the scorecards and the requirements matrix, constitutes a defensible record.

Pitfalls to Avoid

• Reconstructing rationale after a complaint is filed. Courts and investigators can identify post-hoc documentation. Write it contemporaneously or not at all.
• Applying criteria inconsistently across protected-class lines. If you waive a requirement for one candidate, document why — and apply that same waiver logic consistently.
• Storing documentation in personal email or local drives. Access controls and centralized storage are not optional; they are what makes the record producible.
• Conflating "culture fit" with documented criteria. Unless "culture fit" is defined, operationalized, and measured the same way for every candidate, it is a liability, not a criterion.
• Failing to run an adverse-impact check before finalizing a slate. The four-fifths rule is a trigger for scrutiny, not automatic liability — but discovering it after a charge is filed is avoidable.
• Over-retaining records. Keeping materials beyond your policy creates discovery exposure. Apply your retention schedule consistently.

A Note on Automation and AI-Assisted Screening

If your process includes AI-assisted resume screening or scoring tools, the documentation obligation extends to those tools. The EEOC has issued technical assistance guidance (May 2023) noting that employers remain responsible for adverse impact caused by algorithmic tools, even those provided by third parties. Your documentation record should include the tool's selection criteria, any validation evidence the vendor has provided, and your own adverse-impact monitoring logs.

For a broader treatment of where AI screening holds up under scrutiny and where it does not, AI Resume Screening vs Human Screening: The Evidence covers that terrain.

See Verdict in Action

If you want to see what a structured, evidence-cited candidate evaluation looks like when every step above is built into the workflow, Verdict makes that comparison concrete. Try a side-by-side candidate evaluation and see how a defensible record comes together without adding friction to the process.