Adverse action in employment has two meanings that often get conflated. In hiring, it's a legal term under the Fair Credit Reporting Act (FCRA) that describes the rejection of a candidate based on information in a background check, triggering a specific two-notice process. In broader employment law, it's any employer decision that negatively affects an employee, which is one of the core elements in retaliation and discrimination claims. Both definitions matter, and HR teams need to handle each correctly to avoid compliance exposure.
What Counts as Adverse Action in Employment Outside the FCRA context, adverse action describes employer decisions that materially affect an employee's job: termination, demotion, a pay cut, a schedule change that disadvantages them, exclusion from assignments or training, a transfer to a less desirable role, or a suddenly negative performance review. The standard is objective. Would a reasonable employee view the action as discouraging them from raising concerns?
This definition shows up directly in retaliation and discrimination law. To win a retaliation claim, an employee has to establish that an adverse action happened after they engaged in protected activity. To win a discrimination claim, they have to show the adverse action was tied to a protected characteristic.
The FCRA Adverse Action Process in Hiring When an employer wants to reject a candidate based on a background check (criminal history, credit, employment verification), the FCRA requires a two-step notice process.
Step one is the pre-adverse action notice. The employer sends the candidate a complete copy of the background check report , plus the current CFPB-issued "Summary of Your Rights Under the FCRA." This gives the candidate a chance to review the report and dispute any inaccuracies with the consumer reporting agency before the final decision is made.
Step two is the final adverse action notice. After a reasonable waiting period (industry standard: five business days), if the employer still wants to reject the candidate, they send a formal adverse action notice. It must include the consumer reporting agency's name, address, and phone, a statement that the agency did not make the decision, and information on the candidate's right to dispute the report.
How Long Should You Wait Between the Two Notices? Federal law says a reasonable amount of time. The practical standard across most employers is five business days, which gives the candidate a realistic window to review their report and file a dispute. Some states impose stricter timelines. Washington's Fair Chance Act, for example, imposes a two-business-day minimum for employers with 15 or more employees starting July 2026. When state and federal rules conflict, use the stricter one.
Does Every Background Check Result Trigger Adverse Action? No. Adverse action only applies when the employer decides to reject, restrict, or take other negative employment action based on information in the report. A clean background check does not require any notice. A background check that surfaces information the employer decides to accept also does not require a notice. The process kicks in specifically when the report causes or contributes to a negative decision.
How Adverse Action Shows Up in Retaliation and Discrimination Claims In the post-hire context, every adverse action an employer takes is a potential exhibit in a future complaint. The EEOC's analysis in retaliation and discrimination cases looks at whether the action was tied to protected activity (filing a grievance , participating in an investigation, requesting accommodation) or a protected characteristic.
Timing matters. An adverse action that happens within days or weeks of a protected activity creates a strong inference of causal connection, even without direct evidence. This is why documentation of employment decisions against a complainant's timeline is critical the moment a complaint, harassment claim, or discrimination concern is filed. See the EEOC guidance on background checks for how these frameworks interact in hiring.
Building an Adverse Action Workflow That Holds Up Three operational requirements separate compliant workflows from exposed ones.
First, hiring adverse actions need a standard two-notice template and a tracked waiting period. The CFPB summary version changes periodically; use the current one. Document when each notice was sent.
Second, post-hire adverse actions need contemporaneous documentation. Every demotion, pay change, schedule change, or performance finding should be supported by records that predate the protected activity when possible, or that are clearly tied to a business reason that didn't originate from it.
Third, post-complaint employment decisions need a second set of eyes. When an employee has filed a complaint, investigation, or legal claim, routine employment decisions about that person should be reviewed by someone outside the decision-maker's chain.
This is the operational reality behind modern case management. An HR case management platform like AllVoices gives HR teams a system of record for every complaint, every investigation, and every employment decision tied to a case. Paired with investigations management workflow and a single timeline view, the "no contemporaneous documentation" defense that most retaliation cases die on becomes a non-issue.
.svg)
.svg)
