The records you're tempted to delete are the ones you have to keep

Every search you run leaves a paper trail: applications, resumes, interview notes, assessment scores, the reason each candidate was rejected, and the offer that closed the hire. The instinct — especially at a small company drowning in inbox clutter — is to clear it all out the moment a role is filled. That instinct is a legal risk. Several federal frameworks require employers to retain hiring records for defined periods, and if a discrimination charge or audit lands after you've purged the file, you are the one who can't reconstruct what happened.

This is a practical recordkeeping guide, not legal advice. Retention periods come from multiple overlapping rules, they get updated, and some states and government-contract obligations layer on longer requirements — so treat the periods below as the general federal baseline and confirm specifics for your situation with counsel.

Why the rules exist: you can't defend a decision you didn't document

Anti-discrimination enforcement runs on records. If a rejected applicant files a charge, the agency asks the obvious questions: who else applied, who was interviewed, what the selection criteria were, and why this candidate wasn't chosen. An employer with clean, contemporaneous records can show a legitimate, consistent, job-related basis for every decision. An employer who deleted everything is left arguing from memory against a documented complaint — a losing position even when the original decision was completely sound.

That's the core reason retention matters: the records protect the employer. They turn "trust us, it was fair" into "here's exactly how we decided, applied the same way to everyone." It's the same evenhanded discipline that makes structured interviews and knockout screening questions defensible — except here the protection only works if the evidence still exists when you need it.

The general retention baseline

A few anchors cover most situations. Confirm current periods, but the shape is stable:

  • Applications and hiring records — at least one year. Federal anti-discrimination rules generally require keeping all records related to a hiring decision (applications, resumes, interview notes, test results, reasons for rejection) for a minimum period after the decision or the record's creation. If a charge is filed, you must preserve everything related to that charge until the matter is fully resolved, however long that takes — the clock doesn't reset, it pauses indefinitely.
  • I-9 forms — a special, separate rule. Employment-eligibility forms follow their own retention math: keep each I-9 for three years after the hire date or one year after employment ends, whichever is later. Store them apart from the rest of the personnel file. (The mechanics live in the I-9 and E-Verify guide.)
  • Payroll and pay-related records — multiple years. Wage-and-hour rules require keeping payroll, hours, and related records for a span of years — relevant the moment someone's hired and tied to the same discipline behind FLSA classification.
  • Government contractors keep more, longer. If you hold federal contracts, affirmative-action and EEO-1/OFCCP obligations extend both what you track (applicant flow, disposition data) and how long you hold it. Build for the stricter standard.

When periods overlap, the rule is simple: keep the record for the longest applicable period. The shortest clock never wins.

Retain, but retain responsibly

Holding records longer than required isn't free — every resume you keep is personal data you're now responsible for protecting. The goal is deliberate retention, not hoarding:

  • Set a written retention schedule and apply it uniformly. Decide the period for each record type and delete on that schedule — for everyone. Inconsistent deletion (keeping some candidates' files and not others') is itself a fairness problem and looks terrible in litigation.
  • Don't delete during an active dispute. The moment a charge, claim, or audit is on the horizon, all routine deletion of anything related stops until it's resolved. Purging records under a "litigation hold" is its own serious problem.
  • Secure what you keep. Hiring files are full of names, contact details, work history, and sometimes sensitive screening data. Retained records should sit under real access controls and encryption, not in a shared drive anyone can open — handled with the same care as the rest of your candidate data.
  • Keep it organized enough to actually produce. Records you can't find when an auditor asks are nearly as bad as records you deleted. Structured, searchable storage is what turns a compliance request into a five-minute export instead of a week of archaeology.

Bottom line

Hiring records aren't clutter to clear out the day a req closes — they're the evidence that every decision was consistent and job-related, and federal rules require you to keep them for defined periods (with I-9s and government-contract data following their own longer clocks). Write a retention schedule, apply it to everyone identically, freeze deletion the instant a dispute appears, and protect what you store. When applications, interview notes, dispositions, and offers live in one structured applicant tracking system with real access controls instead of scattered across inboxes and drives, retention stops being a liability and becomes the thing that protects you.