Adverse Action Notice Requirements a Nonprofit's Guide
Understand FCRA adverse action notice requirements for volunteer screening. Our guide explains pre-adverse/final notices, timing, and compliance for nonprofits.
On this page
You've run a background check on a volunteer applicant who seemed like a perfect fit. Then the report comes back with something concerning. Maybe it's a record you didn't expect. Maybe it's incomplete. Maybe it looks serious, but you're not even sure it belongs to the right person.
Many nonprofits often make an avoidable mistake. They treat volunteer screening like an informal judgment call. In reality, once you use a consumer report to make an unfavorable decision about a volunteer, you've stepped into a regulated process. The good news is that the process is manageable when you understand the rules and build them into your workflow.
For nonprofits, churches, youth programs, and community groups, adverse action notice requirements aren't just a hiring issue borrowed from the corporate world. They're part of fair, defensible volunteer screening.
Table of Contents
- Why Adverse Action Rules Apply to Your Nonprofit
- Defining Adverse Action in Volunteer Screening
- Pre-Adverse vs Final Adverse Action The Two Notices You Must Send
- Critical Timelines for Sending Adverse Action Notices
- What to Include in Your Adverse Action Notices
- How Nonprofits Can Avoid Common Compliance Mistakes
- A Step-by-Step FCRA Compliance Checklist for Volunteers
Why Adverse Action Rules Apply to Your Nonprofit
A nonprofit can trigger adverse action notice requirements even when no money changes hands. If you use a background check to decide that someone can't volunteer, can't serve in a certain role, or can't continue serving, the law may treat that decision as adverse action.
That surprises many nonprofit leaders because they associate the Fair Credit Reporting Act with lenders and employers. But regulators have made clear that adverse action based on any consumer report, not just credit, requires a Section 615(a) notice, including in non-credit contexts like volunteer screening, according to Consumer Compliance Outlook coverage of FTC and CFPB guidance.
That's the blind spot. A church screens nursery volunteers. A food pantry screens drivers. A youth league screens coaches. The organization thinks, “We're not an employer, so this probably doesn't apply.” It can apply.
Practical rule: If your nonprofit uses a background report from a consumer reporting agency and that report contributes to an unfavorable decision, assume an adverse action workflow is required.
This isn't just about avoiding legal trouble. It's also the fair way to handle hard decisions. Background reports can contain errors, outdated information, or records that need context. The notice process gives the volunteer a chance to review what you saw before the decision becomes final.
Many organizations already understand the consent side of screening, but they haven't connected that to the downstream notice obligations. If your team needs a primer on the broader framework, this overview of FCRA compliance for nonprofits is a useful starting point.
A strong adverse action process protects both sides. The volunteer gets a meaningful opportunity to respond. Your nonprofit gets a documented, consistent procedure that board members, insurers, and counsel can understand.
Defining Adverse Action in Volunteer Screening
In volunteer screening, adverse action means an unfavorable decision based in whole or in part on information from a background check report. It isn't limited to a flat rejection.
Nonprofits often recognize the obvious example. You decide not to onboard a volunteer after reviewing the report. That's adverse action.
The less obvious examples are where people get tripped up. If you decide a volunteer can no longer work with children, can't transport clients, can't enter a residential program site, or can't continue in their current role because of the report, that's still an unfavorable decision. It may trigger the same notice obligations.
Common nonprofit examples
Here are the situations I tell volunteer coordinators to watch closely:
- Declining the applicant: You choose not to move forward with a new volunteer because of the background report.
- Restricting responsibilities: You allow the person to volunteer, but not in the role they applied for, such as mentoring minors or handling donations.
- Removing an existing volunteer: You suspend or end current volunteer service after a new report or rescreening.
- Changing placement terms: You shift someone to a lower-trust assignment because of information in the report.
The key question isn't whether the outcome feels severe. The key question is whether the result is unfavorable to the person and tied to the consumer report.
An adverse action process should start whenever the report pushes your organization toward a negative outcome, even if you're calling it a “role adjustment” instead of a denial.
What doesn't work
What doesn't work is informal language meant to soften the decision while avoiding the process. Saying “we've decided to go in another direction” doesn't erase the legal trigger if the background report influenced the outcome. Neither does framing the decision as a temporary hold if, in practice, the person is being excluded.
Another weak practice is relying on internal labels instead of actual impact. I've seen teams mark a decision as “not adverse” because the person could theoretically volunteer somewhere else in the organization. If the report caused you to deny the role they sought or remove duties they had, you should treat it seriously.
Clarity here matters because every later step depends on recognizing the trigger at the right moment.
Pre-Adverse vs Final Adverse Action The Two Notices You Must Send
Most nonprofit mistakes happen because teams collapse the process into one email. That's not how this works. Under the FCRA framework used in background screening, there are two separate notices, and they serve different purposes.
The first notice warns the individual that you may take adverse action. The second notice confirms that you did.
The two-step process exists for a reason. The law gives the volunteer a real opportunity to review the report, challenge mistakes, and provide context before you finalize the decision.
What goes in the pre-adverse notice
The pre-adverse notice is the pause button. It tells the volunteer that your organization is considering an unfavorable decision based on information in the report, but hasn't made the final call yet.
The packet needs to be complete. The pre-adverse action process requires giving the individual a complete, unexcerpted copy of the background check report and the standardized Summary of Your Rights Under the Fair Credit Reporting Act, followed by a mandatory waiting period of at least five business days, during which no final adverse decision can be made, as explained in DISA's guide to the FCRA adverse action process.
That means you should not send a short summary, a screenshot, or a recruiter-style note saying “something came back on your report.” Send the actual report and the required rights document.
A compliant pre-adverse packet usually includes:
- A cover notice: This tells the volunteer that adverse action is being considered.
- The full report: Not excerpts. Not your notes.
- The Summary of Rights: The standardized FCRA document.
- Clear response instructions: Tell the volunteer how to contact you and, if needed, the screening provider.
If your process starts earlier with authorization and disclosure collection, it helps to standardize that piece too. Many nonprofits clean up later compliance issues by fixing the front end first. This guide to a background check consent form is a good companion resource for that step.
What goes in the final adverse notice
The final adverse notice comes later, after the waiting period ends and after you've considered any response from the volunteer. This is the formal decision notice.
It should never be sent at the same time as the pre-adverse packet. Combining them defeats the purpose of the volunteer's right to review and respond.
The final notice is also where many nonprofits leave out required details. At a minimum, it should make clear that the adverse action was based on a consumer report and include the identity of the consumer reporting agency, along with the required consumer rights information discussed later in this guide.
Don't treat the final notice as a courtesy message. It's a regulated communication tied to the report and your decision.
What doesn't work in practice
Three shortcuts routinely create problems:
Sending one notice instead of two.
This is the most common failure. If the volunteer never had a chance to respond before the final decision, your process is exposed.Leaving out the attachments.
A pre-adverse email without the report and Summary of Rights is incomplete.Using verbal conversations as a substitute.
A phone call may be useful for relationship management, but it doesn't replace the notice sequence.
A good system treats pre-adverse and final adverse notices as separate events with separate content, separate timestamps, and separate records.
Critical Timelines for Sending Adverse Action Notices
Timing is where nonprofit workflows tend to break down. The problem usually isn't bad intent. It's speed. A coordinator sees a concerning record and wants to protect the organization immediately, so they move too fast.
For background check decisions under the FCRA process, the most important timing rule is the waiting period between the pre-adverse notice and the final adverse decision. Best practice and HR standards require employers to wait at least five business days after issuing a pre-adverse action notice before making a final adverse decision, giving the individual time to review the report and dispute inaccuracies, as described in Certn's explanation of adverse action notice timing.
Why the waiting period matters
That five-business-day window is the volunteer's opportunity to act. They may tell you the record belongs to someone else. They may show that a charge was dismissed. They may contact the consumer reporting agency to dispute a mismatch or outdated item.
If you send the final notice too soon, you cut off that opportunity. From a compliance perspective, that's exactly what the waiting period is meant to prevent.
For nonprofits, this is also a governance issue. If your board expects screening to be both protective and fair, a documented waiting period shows that your process isn't arbitrary.
The safest approach is simple. Send the pre-adverse packet, log the send date, count business days carefully, and don't finalize anything early.
How to document timing without creating extra work
You don't need a complicated legal operations stack. You do need proof.
Use a workflow that records:
- When the pre-adverse packet was sent
- What attachments were included
- When the waiting period ends
- Whether the volunteer responded
- When the final notice was sent
If you send notices by email, keep delivery records and copies of attachments. If you send by mail, keep mailing records. What matters is that you can show a clean timeline later.
One more practical point. “Business days” should be counted consistently within your process. Don't let one coordinator count weekends and another skip holidays without a written method. A standard operating procedure, even a short one, prevents avoidable confusion.
What to Include in Your Adverse Action Notices
The easiest way to stay compliant is to stop improvising. Adverse action notices should come from a controlled template, not from whatever email a coordinator writes on a stressful afternoon.
The exact content differs between the pre-adverse notice and the final adverse notice. The first is about review and response. The second is about the completed decision and required disclosures.
Pre-Adverse vs. Final Adverse Notice Contents
| Required Element | Pre-Adverse Notice | Final Adverse Notice |
|---|---|---|
| Notice that an unfavorable decision is being considered | Yes | No |
| Statement that the decision is not yet final | Yes | No |
| Complete copy of the background check report | Yes | No |
| Summary of Your Rights Under the Fair Credit Reporting Act | Yes | No |
| Final statement that adverse action has been taken | No | Yes |
| Name of the Consumer Reporting Agency | No | Yes |
| CRA address | No | Yes |
| CRA phone number | No | Yes |
| Statement that the CRA did not make the decision | No | Yes |
| Notice of right to request a free copy of the report within 60 days | No | Yes |
| Notice of right to dispute accuracy or completeness with the CRA | No | Yes |
The final adverse action notice must include the name, address, and phone number of the Consumer Reporting Agency, a statement that the CRA did not make the decision, and notice that the individual has the right to request a free copy of the report within 60 days and dispute its accuracy, according to Consumer Compliance Outlook's summary of ECOA and FCRA adverse action notice requirements.
Sample language nonprofits can adapt
This isn't legal advice, and counsel should review your forms. Still, most nonprofits benefit from having plain-language starting points.
Pre-adverse notice example
We are considering an unfavorable decision regarding your volunteer application or volunteer role based in whole or in part on information contained in the enclosed consumer report.
No final decision has been made at this time. Please review the enclosed report and the enclosed Summary of Your Rights Under the Fair Credit Reporting Act. If you believe any information is inaccurate or incomplete, you may contact the consumer reporting agency and also provide additional information to our organization for review.
Final adverse notice example
After review, we have decided to take adverse action based in whole or in part on information contained in a consumer report.
The report was provided by [CRA Name], [CRA Address], [CRA Phone Number]. The consumer reporting agency did not make this decision and cannot explain why the decision was made. You have the right to obtain a free copy of your report from the consumer reporting agency if you request it within 60 days. You also have the right to dispute the accuracy or completeness of any information in the report directly with the consumer reporting agency.
One more practical note. If a volunteer tells you the report is wrong, take that seriously. Many disputes start with simple matching problems or incomplete disposition data. This short overview of common background check errors is worth sharing internally so staff know what issues can appear.
How Nonprofits Can Avoid Common Compliance Mistakes
Most adverse action failures come from process gaps, not bad policy. The nonprofit has the right screening standards. The problem is that staff members are using email, spreadsheets, and memory to manage a regulated sequence.
Where nonprofits usually slip
I see the same patterns again and again:
- One-message shortcuts: A coordinator sends a single rejection email instead of a pre-adverse notice followed later by a final adverse notice.
- Missing attachments: The message goes out, but the actual report or the Summary of Rights doesn't.
- Premature final decisions: Someone marks the applicant closed before the waiting period runs.
- Poor recordkeeping: Months later, nobody can prove what was sent or when.
- Loose internal handoffs: One person reviews the report, another person sends the email, and neither owns the audit trail.
These aren't small details. They're the mechanics that determine whether your process holds up when questioned by counsel, leadership, or the individual involved.
For nonprofit leaders building broader governance systems, it helps to think of adverse action as one component of larger compliance risk management strategies rather than an isolated HR task.
How automation reduces process risk
A well-designed screening platform can remove a lot of manual error from this process. The goal isn't to replace judgment. Your organization still decides whether a volunteer is appropriate for the role. The system handles the sequence, the attachments, and the records.
For example, VolunteerBadge is built for nonprofit background screening and includes step-by-step FCRA guidance plus auto-generated pre-adverse and final adverse action notices when needed. That kind of workflow helps teams send the right packet, preserve timestamps, and keep the decision trail organized without relying on individual staff memory.
What works in practice is straightforward:
- Template control: Approved notice language lives in the system, not in personal inbox drafts.
- Attachment enforcement: The workflow won't forget the report or rights document.
- Timeline tracking: Staff can see whether the waiting period has run.
- Audit history: You can reconstruct the file later.
What doesn't work is leaving compliance steps to “whoever handles volunteers this week.”
Good automation doesn't make legal decisions for you. It makes sure your team follows the decision process the same way every time.
A Step-by-Step FCRA Compliance Checklist for Volunteers
A short checklist is often more useful than a long policy. Volunteer coordinators need something they can follow when a report raises concern.
A repeatable checklist for volunteer coordinators
Confirm you had proper authorization before the check.
Your file should include the volunteer's written disclosure and authorization.Review the report carefully before acting.
Don't assume every flagged record supports exclusion from the role.If an unfavorable decision is possible, send the pre-adverse packet.
Include the full report and the Summary of Rights.Wait at least five business days before making the final decision.
Use a trackable calendar method and freeze the file during the waiting period.Review any response from the volunteer.
If they raise a dispute, pause the process and verify what changed before moving forward.
A lot of nonprofits send these notices by email, which creates its own operational questions around formatting, delivery, and recordkeeping. If your team is tightening that part of the workflow, this guide to background check email compliance is a practical companion.
Here's a quick video overview you can share with staff during training:
- If the decision remains unfavorable, send the final adverse notice and retain the record.
Keep copies of the notices, attachments, and timeline notes in one place.
That's the entire workflow. It doesn't need to be dramatic. It needs to be consistent.
If your nonprofit wants a simpler way to handle volunteer screening and adverse action notice requirements, VolunteerBadge offers nonprofit-focused background checks with built-in FCRA workflow support, including authorization tools and automated notice generation when a report leads to possible adverse action.
