FCRA Pre-Adverse and Adverse Action Notice Workflow

This workflow covers the two-step FCRA adverse action process: the pre-adverse action notice with the consumer report and Summary of Rights, followed by the final adverse action notice after the waiting period. It is meant for hiring decisions where a background check or consumer report may affect eligibility. The template focuses on notice timing, document delivery, and the handoff between the two steps. It does not replace your legal review of state or local requirements.

Use it any time a consumer report may lead to a negative hiring decision, such as before rescinding an offer or moving a candidate out of consideration. It is especially useful when you need a repeatable playbook instead of tracking deadlines manually. If your process never uses consumer reports, this template is not the right fit. If your workflow includes individualized assessment or additional state notices, those can be added as extra steps.

Typically HR, recruiting operations, or a background-check coordinator runs the workflow, with legal or compliance reviewing the notice language. The person or system running it should have access to the candidate record, the consumer report, and the notice templates. If approvals are required before sending the final notice, add a confirm gate before that step. The workflow should be owned by someone who can verify timing and document delivery.

The workflow should wait the period your policy and applicable law require before the final adverse action notice is sent. Many employers use a minimum review window to give the candidate time to dispute or respond, but the exact timing should be set by counsel and local rules. This template makes the delay explicit so it is not skipped. If your process uses business days rather than calendar days, configure the wait step accordingly.

The most common mistakes are sending the final notice too early, forgetting to include the consumer report or Summary of Rights, and using the wrong candidate record. Another frequent issue is failing to log that the pre-adverse notice was delivered, which makes timing hard to prove later. Some teams also forget to pause for disputes or manager review. This workflow helps by separating the steps and making each handoff visible.

Yes. You can add branches for state-specific notices, different waiting periods, or role-based approval steps before the final notice. You can also vary the message text for candidates, contractors, or internal transfers if your policy allows it. Keep the core FCRA sequence intact even when you customize the surrounding steps. Any jurisdiction-specific language should be reviewed before rollout.

Yes, this template is a good fit for ATS, HRIS, background-check, email, and document storage integrations. A typical setup pulls the candidate status from the ATS, fetches the report from the screening provider, sends the notices, and stores delivery logs in HR records. You can also trigger the workflow from a form submission or a status change. The key is to keep the notice steps tied to a single candidate record.

Manual handling often breaks down at the waiting period, where a task gets forgotten or a notice goes out too soon. A workflow makes the sequence explicit, records each step, and reduces the chance of inconsistent treatment across candidates. It also gives you a repeatable audit trail for compliance review. For teams processing multiple background checks, that consistency is the main advantage.