Do Not Rehire List - Is It Legal and How to Document It

Blog Image

Retaliation was alleged in 47.8% of all EEOC discrimination charges in fiscal year 2024, so a do-not-rehire designation can be lawful without being low-risk. The list itself isn't automatically illegal, but the employer must prove the decision rests on legitimate, consistently applied business reasons and isn't punishment for protected activity.

Business owners often treat a do-not-rehire list as a simple internal hiring preference. That approach misses the underlying exposure. The greatest risk appears where an internal eligibility flag intersects with an external reference, especially when the company operates across multiple states and different managers control different parts of the process.

A defensible decision needs more than a checkbox in an applicant tracking system. It needs a documented reason, consistent treatment, restricted access, a review process, and a clear separation between what the company decides internally and what it tells prospective employers.

Understanding the Legal Landscape

The enforcement data should change how leaders approach this issue. The EEOC received 88,531 discrimination charges in fiscal year 2024. Retaliation accounted for 42,301 charges, or 47.8% of all filings, making it the leading charge category for the seventeenth consecutive year. These figures are reported in the FY2024 EEOC enforcement statistics.

That doesn't mean every refusal to rehire is retaliatory. It does mean that a rehire decision made soon after a complaint, investigation, accommodation request, or other protected conduct deserves careful review. A manager's belief that someone was difficult isn't enough to carry that decision safely.

A graphic titled Do-Not-Rehire Lists, showing four bullet points regarding legal compliance, written policy, consistent criteria, and documentation.

What employers may decide

Employers generally may decline to rehire a former employee for legitimate reasons, including:

  • Documented misconduct: The file supports a substantiated policy violation or serious conduct issue.
  • Performance failures: Records show the person didn't meet documented performance standards.
  • Qualification problems: The former employee lacks a position-specific qualification or can't perform an essential requirement.
  • Consistent business rules: Comparable former employees were evaluated under the same standard.

The legal problem begins when the designation becomes a pretext for discrimination, retaliation, interference with protected activity, or unlawful blacklisting. A label such as “bad attitude” is weak unless the employer can translate it into dated, corroborated conduct tied to a policy or job requirement.

The distinction also matters to employees trying to understand getting your job back after termination. An internal status can affect a future application without automatically becoming an unlawful blacklist. External communication is a separate question, and careless reference practices can undermine an otherwise legitimate internal decision.

Practical rule: Treat the rehire flag as an employment decision that needs evidence, not as a permanent opinion about a person.

Building a Defensible Do Not Rehire Policy

A defensible methodology requires objective triggers, documented investigation, separation between fact-finding and the final decision, specific records, consistent treatment, and periodic review rather than permanent flags. The EEOC retaliation FAQ supports this basic structure.

Start with objective triggers

Write the eligibility rules before a difficult termination occurs. Appropriate triggers may include substantiated serious misconduct, material policy violations, or documented inability to meet essential job requirements. Avoid broad categories that allow managers to convert personal frustration into a hiring restriction.

The policy should also define who may recommend a designation, who approves it, which records must be attached, and when the status must be reviewed. A hiring manager shouldn't be able to create an informal ban through a private note or verbal instruction.

Investigate before deciding

Give the investigation enough structure to show what happened. Preserve notice, relevant evidence, witness information, and the employee's response. If the company skips this step, the later rehire decision may look like a conclusion searching for support.

Separate the investigation from the final eligibility decision. The person gathering facts shouldn't carry an untested conclusion into the hiring file. HR or another designated reviewer should evaluate whether the evidence supports the proposed restriction and whether a lesser response was considered.

Record facts, not character judgments

The file should identify:

  1. The specific rule or essential requirement involved.
  2. The relevant dates and decision-maker.
  3. The evidence relied upon.
  4. The employee's response.
  5. Whether comparable employees received the same treatment.
  6. Whether a narrower or time-limited restriction was considered.
  7. The approval and review date.

“Problem employee” isn't a useful record. “Failed to complete the required safety handoff on a documented date after receiving the applicable procedure” is specific enough to evaluate.

Test consistency and review the status

Before final approval, compare the case with similar decisions. If other employees engaged in comparable conduct but remained eligible for rehire, the company needs to understand and document the difference. A designation should also have review criteria instead of becoming permanent by default.

The same discipline should apply to employment paperwork generally. Leaders who are revising offer letters, agreements, or related hiring documents may find the discussion from Lerner & Weiss APC on hiring paperwork useful as a reminder that written employment practices should match actual operations.

Separating Internal Decisions from External References

The most overlooked problem is the boundary between the internal flag and the external reference. A company may maintain a restricted internal eligibility status while providing an accurate, consistently authorized reference response. Those records shouldn't be merged.

The safest architecture uses three separate records:

RecordPurposeControls
Separation recordDocuments the end of employmentInvestigation materials, performance or conduct records, policy citations
Internal rehire decisionDetermines whether the person may be considered againRationale, comparator analysis, approval history, review date
External reference responseCaptures what the company disclosedRequest details, authorized responder, approved information, date

Each record should preserve a contemporaneous chronology and an immutable audit trail for edits. Access should be limited by role and business need. The internal code shouldn't automatically flow to affiliates, staffing partners, customers, or prospective employers.

A professional woman and a man in suits conducting a formal job interview in an office setting.

Centralize reference responses

Use one authorized function for reference requests. Give that function a written script, normally limited to employment dates and last title unless a fuller and accurate response has been legally approved. Record who asked, who responded, what was disclosed, and which records supported the response.

A neutral process isn't a license to conceal misconduct or create a misleading answer. It is a control against informal manager comments that vary by employee or reveal retaliatory intent. The EEOC's retaliation enforcement guidance recognizes that non-hire and negative references can be materially adverse actions, while a truthful negative reference supported by legitimate reasons isn't automatically unlawful.

Run a consistency check

Before finalizing a designation, ask:

  • Did similarly situated employees receive the same outcome?
  • Did a manager depart from the company's normal reference practice?
  • Is the information factual and supported by contemporaneous records?
  • Does the external response say more than the company normally discloses?
  • Is the internal status being shared beyond those with a legitimate business need?

This check often exposes the documentation gap. The problem isn't always the initial decision. It may be the later disclosure that turns a controlled internal status into evidence of pretext or retaliation.

Navigating State-Specific Blacklisting Laws

Federal principles provide only a baseline. State law may regulate how employers maintain or communicate information about former employees, and multi-state employers shouldn't assume one reference policy works everywhere.

Colorado prohibits maintaining or communicating a blacklist while protecting truthful job-history or performance information provided on request. Colorado also allows a former employee to request a copy of written information supplied to a prospective employer. Washington prohibits willful or malicious public or written statements intended to prevent someone from obtaining employment, while distinguishing unlawful blacklisting from a private, honest negative reference. Connecticut similarly restricts publishing an employee's name with the intent to prevent future employment while preserving the ability to provide truthful facts.

A chart showing state-specific blacklisting laws categorized by permissive, restrictive, and multi-state employer requirements.

Build a state disclosure matrix

Create a matrix showing, for each operating state:

  • Who may provide a reference.
  • What information may be disclosed.
  • Whether the former employee may request a copy.
  • What approvals are required.
  • Which records must be retained.
  • Whether additional privacy or personnel-file rules apply.

This is more useful than a universal “not eligible for rehire” code. The code may be defensible internally, but it becomes riskier when an HR system automatically exposes it to another business unit or an affiliated employer.

A restrictive reference policy isn't automatically safer if it creates inconsistent treatment or ignores a state's disclosure rules.

Record objective facts, not conclusions. A confirmed policy violation, falsified record, or failure to complete a required notice can be evaluated. “Bad employee” cannot. If a former employee claims the company interfered with future work, leaders may also benefit from reviewing practical guidance on suing your employer from Bell Law to understand why communication records matter.

State-by-state handbook obligations deserve the same attention. Use handbook rules by state as part of a broader review, then have counsel confirm the rules that apply to your workforce and reference process.

Identifying and Mitigating High-Risk Scenarios

The highest-risk question isn't “Do we have a list?” It is “What happened before the list was created?” Federal law can make an otherwise legitimate-looking rehire flag evidence of retaliation when it follows an EEO complaint, safety report, union activity, or collective complaint about workplace conditions. Timing and inconsistent treatment may matter more than the label in the HR system.

The National Labor Relations Act can protect employees who engage in concerted activity concerning workplace conditions. Federal anti-discrimination laws also prohibit retaliation for protected complaints, investigations, or charges. A former employee doesn't lose those protections just because the company is making a later hiring decision.

Run a protected-activity check

Before approval, ask whether the former employee recently:

  • Filed or supported a discrimination complaint.
  • Participated in an internal or agency investigation.
  • Requested an accommodation or protected leave.
  • Reported a safety or wage concern.
  • Opposed discriminatory conduct.
  • Engaged in union activity or group workplace discussions.

A “yes” answer doesn't automatically prohibit non-rehire. It requires independent review by HR or employment counsel, a clear chronology, and evidence that the same decision would have been made without the protected activity.

Reject permanent flags by default

Indefinite designations are difficult to defend when job suitability or risk can change. Use a defined review date and objective reconsideration criteria where the underlying concern doesn't require a permanent restriction. A serious, substantiated concern may justify a longer restriction, but the file should explain why.

A recent termination followed by an indefinite flag, without comparable treatment for similar employees, can create an inference that the status was punitive rather than job-related. Require an independent reviewer, written evidence, consistency testing, and scheduled reconsideration before the flag enters the system.

Creating Your Documentation Architecture

For covered private employers, federal EEOC rules generally require personnel and employment records to be retained for one year, including one year from the termination date for involuntarily terminated employees. Longer periods may apply after a charge or litigation begins, so the federal period is a floor, not a reason to delete a rehire file. The applicable EEOC recordkeeping requirements should be reviewed alongside state and sector-specific rules.

The file must show what information existed when the company made the decision. Preserve the final disciplinary record, investigation materials, decision-maker notes, policy citations, approval history, and effective date and scope of the designation.

Record typeRequired elementsRetention period
Separation recordFinal action, policy citations, investigation materials, performance or conduct recordsAt least the applicable federal and state period
Rehire decisionSpecific rationale, dates, decision-maker, comparator analysis, approvals, review dateAt least the applicable federal and state period, longer if a dispute arises
Reference responseRequest, authorized responder, information disclosed, supporting records, dateUnder the applicable retention and litigation-preservation rules

Control access and edits

Restrict the records to HR, approved decision-makers, and counsel where appropriate. Use role-based access, preserve an immutable audit trail, and prohibit managers from adding informal blacklist comments. Every change should show who made it, when it was made, and why.

The same principle applies to specialized employment files. For regulated fleets, a structured driver qualification file template from My Safety Manager illustrates the value of organizing required records instead of relying on scattered manager notes.

Avoid these failure modes:

  • Verbal bans: A manager tells recruiting not to consider someone, but no approved record exists.
  • Retroactive rationales: The company creates a reason only after the former employee challenges the decision.
  • Permanent flags: The status has no review date or reconsideration criteria.
  • Informal disclosures: Managers share subjective opinions with other employers or affiliates.
  • Selective enforcement: The company applies the restriction mainly to people who complained or engaged in protected activity.

Build the workflow into the HR system. Require a structured form, protected-activity review, HR approval, comparator analysis, reference controls, and a review date before the status becomes active. For the termination decision itself, Paradigm International Inc. on termination risk offers a related resource for leaders tightening documentation around separation decisions.


Strategic personnel advisory firms help owners, COOs, HR leaders, and executive teams structure investigations, termination decisions, rehire reviews, and multi-state personnel practices. If your company needs a defensible process for separating internal eligibility decisions from external references, visit Paradigm International Inc. to discuss the right advisory support.

Recommended Blog Posts