Pre Adverse Action Letter: The Complete Nonprofit Guide
Learn how to write a pre adverse action letter that keeps your nonprofit fully FCRA compliant. Covers timing, templates, state rules, and common mistakes.
On this page
Maya, a volunteer coordinator at a youth-mentoring nonprofit, has just learned that a background check for a long-trusted mentor returned a five-year-old conviction. She needs to tell him that his placement is paused, give him a fair chance to respond, and protect the relationship her organization spent months building.
That moment is where the pre adverse action letter matters. A clear letter can tell a volunteer, “This isn't final. Here's what we found, here are your rights, and here's how to correct an error.” A rushed or vague letter can make the person feel rejected before the nonprofit has legally made a decision.
Table of Contents
- What a Pre Adverse Action Letter Is
- The Three Documents You Must Send Together
- Preparing and Sending the Letter Step by Step
- A Sample Letter Nonprofit Teams Can Adapt
- State-Specific Rules That Change the Process
- Common Mistakes That Trigger Lawsuits
- Your Pre Adverse Action Checklist
What a Pre Adverse Action Letter Is
A pre adverse action letter tells a volunteer that the nonprofit is considering a negative screening-related decision, while the final decision has not been made. The proposed action might deny placement, remove the person from a role, limit access, or take another step based in whole or in part on information in a background report.
The letter serves as the first half of the two-step process required by the Fair Credit Reporting Act, or FCRA. Before issuing a final adverse action notice, the organization sends the pre-adverse notice with the report and the FCRA rights summary, then allows a reasonable opportunity to dispute inaccurate information. The FTC's employer guidance on consumer reports describes this sequence for decisions such as rejecting an application, reassigning someone, terminating employment, or taking another adverse action based on a consumer report.
Why the second look exists
Background reports can contain identity-matching errors, incomplete court information, outdated entries, or records belonging to someone else. The FCRA pause gives the recipient time to examine the actual report and raise a dispute before the nonprofit makes the decision final.
The framework began as a consumer-reporting safeguard, and its employment applications also reach nonprofit volunteer screening when a consumer report influences the organization's decision. A volunteer may not receive wages, but the screening still needs to follow a regulated decision workflow rather than an informal program decision. Guidance on FCRA compliance for volunteer organizations belongs alongside the procedures used for paid-staff screening.
The letter is also a communication moment. A person may be frightened, embarrassed, or confused when reading it, especially if the report contains information they do not recognize. Clear instructions can preserve trust while giving the recipient a practical way to respond.
Practical rule: Never write “you're denied” in a pre-adverse letter. State that the organization is considering an adverse action, identify the information under review, and explain that no final decision has been made.
Maya should describe the report information under review, explain what the recipient can do next, and use a respectful tone that does not imply guilt. Plain English makes the legally meaningful pause usable. A vague notice can leave a volunteer feeling rejected before the nonprofit has completed its review.
The Three Documents You Must Send Together
A compliant packet contains three documents. Each answers a different question for the volunteer: what the nonprofit is considering, which information it reviewed, and how the person can challenge an error. Sending only the letter creates confusion and makes a fair response harder.
The pre-adverse action letter explains that the nonprofit is considering an adverse decision based in whole or in part on the consumer report. It identifies the consumer reporting agency that supplied the report and gives clear instructions for raising concerns. The wording should leave room for review. A volunteer reading the notice may already feel embarrassed or afraid, so the letter should describe a pending decision without implying guilt or rejection.
The consumer report provides the underlying record. The report, rather than a coordinator summary like “criminal record found,” lets the person examine names, dates, court information, dispositions, and other details directly. Send the same version the nonprofit reviewed, including pages that may seem routine. Omitting a page or substituting an internal summary can prevent the recipient from identifying a mismatch.
The Summary of Your Rights Under the Fair Credit Reporting Act provides the federal rights notice. The Consumer Financial Protection Bureau reinforced the standardized notice framework in 2018, and federal compliance guidance treats the rights summary as part of the pre-adverse packet. It gives the recipient a practical reference for understanding the report and disputing information that is inaccurate or incomplete. Keep the document readable and include it with the other two items, rather than sending it later as an afterthought.
Timing is a control, not a formality
Federal law does not set a fixed number of days for the response period. Compliance guidance commonly uses at least five business days as an operational benchmark, as described in this FCRA compliance plan from Fisher Phillips. Use a longer window when the record is complicated, a county court retrieval needs clarification, or the volunteer reopens a dispute near the end of the review period.
More time helps only when staff use it well. A longer period can give the person a meaningful opportunity to respond and allow the organization to handle a pending dispute responsibly. It becomes poor operations when staff stop monitoring the inbox or leave the volunteer unsure whether the relationship remains open.
Before building the packet, coordinators can review how to get a background report to align intake and delivery practices. The practical standard is straightforward: send the notice, exact report, and rights summary together in a format the recipient can open and understand.
Preparing and Sending the Letter Step by Step
The workflow should feel like one connected chain. A break at the beginning, such as relying on a partial report, can make every later document unreliable.
Start with a final report
Pull the completed report from the screening vendor and confirm that it's final rather than pending, incomplete, or waiting on a county-level search. Check the volunteer's identifying information, report date, report identifier, and the consumer reporting agency's contact details. If those details don't match the file the nonprofit reviewed, stop and correct the record before drafting anything.
Next, identify every item that could reasonably influence the decision. Don't let a coordinator's personal reaction become the screening standard. Match the report information to the nonprofit's written criteria for the specific volunteer role, including the role's responsibilities and access. The letter should reflect an established policy, not an improvised opinion about a person's character.
Assemble the packet before delivery
Use the approved template and write the notice around the actual report. State that the nonprofit is considering adverse action, make clear that no final decision has been made, identify the reporting agency, and explain how the volunteer can dispute inaccurate or incomplete information. Attach the report and the federal rights summary in the same delivery.
Choose a delivery method that gives the nonprofit a usable record. Certified mail can document paper delivery. For digital delivery, a portal message or email with a read receipt can create a stronger audit trail than an ordinary message, provided the recipient can access the documents. Record the delivery channel, recipient address, attachments, and send time.
Protect the pause
Log the send date and mark the earliest permissible date for a final adverse action decision. During the waiting period, managers shouldn't tell the volunteer that they're out, remove them from communications in a way that communicates finality, or send a message that contradicts the letter's statement that the decision remains pending.
Monitor responses. If the volunteer identifies a possible background check error, preserve the message, route it to the appropriate screening or compliance contact, and review the information before proceeding. A clean workflow makes the organization's conduct easy to explain later: complete report, complete packet, documented delivery, response review, then final decision if the original concern remains valid.
A Sample Letter Nonprofit Teams Can Adapt
A volunteer opens this letter without knowing whether the opportunity they have worked toward is about to disappear. The wording must explain the pending decision, identify the records involved, and give the person a practical way to respond. A useful nonprofit letter names the process, the report, the agency, and the next action in plain language a volunteer can follow.
Annotated sample
Subject: Notice of Possible Adverse Action Regarding Your Volunteer Application
Dear [Volunteer Name],
[Preamble: This identifies the recipient and makes the communication personal rather than anonymous.]
[Program Name] is considering taking adverse action regarding your volunteer application for [Program or Role] based in whole or in part on information contained in a consumer report prepared by [Consumer Reporting Agency Name]. The report was obtained for [volunteer screening purpose] and is identified as report ID [Report ID], dated [Report Date]. No final decision has been made.
[Paragraph one: This establishes the pending nature of the decision, names the report, and prevents the letter from reading like a final denial.]
Enclosed are a copy of the consumer report and the Summary of Your Rights Under the Fair Credit Reporting Act. Please review the report carefully. If you believe any information is inaccurate or incomplete, you may contact [Consumer Reporting Agency Name] at [CRA Address], [CRA Phone], or [CRA Website] to dispute it. You may also send relevant information or an explanation to [Nonprofit Contact Name] at [Contact Email] or [Contact Phone].
[Paragraph two: This tells the volunteer what arrived, where to dispute the report, and how to communicate with the nonprofit.]
The organization will consider any information you provide before making a final decision. Please respond by [Review Date], or contact us if you need accessible delivery or clarification about the materials. We'll send a separate notice if the organization makes a final adverse action decision.
Sincerely,
[Name and Title]
[Program Name]
[Organization Address]
[Signature or Approved Electronic Signature]
[Closing: This gives the volunteer a clear response path and keeps the final decision separate.]
Send the letter with the report and rights summary. A polished paragraph cannot cure a missing attachment. Use the exact documents approved for the organization's process, and check each packet before delivery.
| Paragraph / Element | Compliant Version | Shortcut That Fails |
|---|---|---|
| Pending decision | “No final decision has been made.” | “We're rejecting your application.” |
| Report identification | Names the report type, agency, date, and ID | “Your background check had an issue.” |
| Rights materials | States that the report and rights summary are enclosed | Omits the federal rights summary |
| CRA contact | Provides the reporting agency's contact details | Tells the volunteer to “contact the background-check company” |
| Dispute process | Explains how to dispute and contact the nonprofit | Gives no instructions |
| Response period | Provides a review date or clear response route | Sends the final decision immediately |
A stripped-down message such as “Your background check raised concerns. We won't be moving forward” turns the preliminary notice into a final decision. Leaving out the report, rights summary, agency contact block, or dispute instructions also prevents the volunteer from using the review period effectively. Those omissions damage trust as well as the organization's record of compliance.
Build the template with editable fields for the program name, volunteer name, report ID, report date, agency details, contact email, review date, and signature line. Lock the approved wording in the organization's HRIS or applicant tracking system. Before release, confirm that the fields match the report and that every listed attachment is present.
State-Specific Rules That Change the Process
Federal FCRA compliance is the floor, not always the complete workflow. A nonprofit operating across jurisdictions should identify where the volunteer performs services, where the organization makes the decision, and whether a local fair-chance rule controls the sequence.
California's Investigative Consumer Reporting Agencies Act can add disclosure and authorization requirements beyond the federal packet. Its interaction with volunteer screening can also affect when the organization communicates and how it documents the process. New York's General Business Law Article 25 adds requirements for employment-related criminal-record decisions, while New York City's Fair Chance Act can restrict when and how an employer asks about or acts on criminal history for paid staff.
Massachusetts employers must account for Massachusetts General Laws chapter 93L and related certification expectations when obtaining and using criminal-record information. Washington's Fair Chance Act affects ban-the-box sequencing, so a nonprofit may need to delay criminal-history questions or review until the permitted stage. These rules can change the form, order, and timing of communications, even when the federal packet remains necessary.
Local rules belong in the same decision map
Cities can layer requirements onto state and federal law. Los Angeles, San Francisco, Chicago, and Philadelphia are examples of jurisdictions where fair-chance rules may add notice language, individualized-review steps, or restrictions on when criminal history can influence a decision. The exact rule depends on whether the person is a paid employee, applicant, contractor, or volunteer, so staff shouldn't assume that a paid-employment template transfers unchanged to an unpaid program.
| State / City | Key Rule | Effect on Pre-Adverse Action Letter |
|---|---|---|
| California | Investigative consumer-reporting requirements may apply in addition to FCRA | Review disclosures, authorization language, and delivery sequence |
| New York | General Business Law Article 25 governs criminal-record decision practices | Coordinate the letter with the required individualized review |
| New York City | Fair Chance Act can restrict criminal-history timing for paid staff | Don't use the federal notice as the first criminal-history communication when local sequencing applies |
| Massachusetts | Chapter 93L and certification requirements affect criminal-record handling | Confirm certification and process controls before sending |
| Washington | Fair Chance Act includes ban-the-box sequencing rules | Delay criminal-history inquiries or action until the permitted stage |
| Los Angeles, San Francisco, Chicago, Philadelphia | Local fair-chance rules can add requirements | Add jurisdiction-specific language and review steps to the federal workflow |
The operational rule is straightforward: stack the strictest applicable standard on top of FCRA. Maintain a jurisdiction matrix, assign ownership for updates, and route unusual volunteer roles to qualified counsel instead of copying a letter from another city.
Common Mistakes That Trigger Lawsuits
Most failures aren't complex. They happen when a coordinator treats a required packet like an ordinary rejection email.
Five breakdowns to eliminate
Skipping the rights summary: Sending the letter and report without the federal rights notice removes a required part of the packet. The fix is to store the approved rights-summary document in the same workflow as the template and retain the attachment record.
Using no meaningful review period: Sending the notice and final decision on the same day defeats the purpose of the pause. Use the practical five-business-day benchmark described in federal compliance guidance, and document the date from which the organization calculates the review window. The Littler discussion of FCRA notice requirements also reflects how standardized guidance has developed around the required packet.
Sending before the report is complete: A notice based on a partial pull can contain the wrong report ID, missing court information, or facts that later change. The fix is a completed-report status check and a saved copy of the exact report sent to the volunteer.
Keeping weak records: “We mailed it” isn't a reliable audit trail without the address, channel, send date, attachments, delivery evidence, and staff member responsible. Save the final letter, report, rights summary, transmission record, and any response in the volunteer's restricted compliance file.
Ignoring local add-ons: A federally complete packet can still miss a California, New York, Massachusetts, Washington, or municipal requirement. Add a jurisdiction review before release and record which rule set the team applied.
The cost of a mistake isn't limited to rewriting a notice. A nonprofit may face private litigation, regulatory scrutiny, staff time spent reconstructing records, and a damaged relationship with a volunteer community. Don't assign a precise financial outcome to any one error. The exposure depends on the facts, the number of affected people, the jurisdiction, and whether the organization corrected the problem promptly.
Your Pre Adverse Action Checklist
Three decisions control the workflow: which report triggered the proposed action, whether state or local law extends or changes the process, and how the volunteer will receive the packet. Resolve those questions before anyone communicates a final outcome.
Keep this desk-side sequence:
- Confirm the report: Verify that the screening report is complete, matches the volunteer, and is the exact report reviewed.
- Apply written criteria: Identify the report items that may influence the decision and connect them to the nonprofit's approved screening policy.
- Prepare the letter: Use the approved pre adverse action template, name the reporting agency, include its contact details, and state that no final decision has been made.
- Attach both documents: Include the complete consumer report and the federal Summary of Your Rights Under the FCRA.
- Choose a trackable channel: Send by a method that records the destination, delivery attempt or receipt, date, and attachments.
- Calendar the review window: Allow at least five business days as the practical federal benchmark, or use the longer state or local window when applicable.
- Monitor responses: Preserve disputes, explanations, and requests for clarification. Review them before deciding.
- Send the final notice only afterward: If the decision remains unchanged, issue the final adverse action notice through the approved process.
The volunteer may read the letter after a long day, worried that a role they care about is already gone. Clarity, respectful wording, and a usable response path determine whether the relationship survives. Compliance and trust are the same deliverable, not competing priorities.
VolunteerBadge provides nonprofit screening workflows that include the report, the FCRA rights summary, and automated pre-adverse and final adverse action notices when needed. Visit VolunteerBadge to review how its volunteer background-screening tools can support a documented, respectful process.
