What Is an MVR Check? a Guide for Nonprofits
What is an MVR check and why do nonprofits need one? Learn what's on a Motor Vehicle Record, how to stay FCRA compliant, and how to screen volunteer drivers.
On this page
An MVR check is a report from a state's DMV that shows a person's driving history, including violations, license status, and accidents. Nonprofits use it to screen volunteers who will be driving for the organization so they can confirm the person is both safe and legally qualified to drive.
If you manage volunteers, you've probably had this moment. A reliable volunteer says they can drive the van to an event, transport meals, or take clients to appointments. Operationally, that feels like a win. From a risk standpoint, it should trigger one immediate question: have you checked their driving record?
That's where MVR screening stops being paperwork and starts being mission protection. A volunteer can be generous, punctual, and trusted by staff, and still have a suspended license, a recent DUI, or a pattern of unsafe driving. For nonprofits, that gap matters because one bad driving decision can hurt people, create insurance problems, and put the organization's judgment under a microscope.
Most general guides explain what an MVR is for employers. Fewer deal with the issue nonprofit managers encounter: how to screen unpaid volunteers legally and consistently, especially when the Fair Credit Reporting Act applies. That's the part many organizations miss, and it's where preventable compliance problems begin.
Table of Contents
- Your Best Volunteer Might Be a Risky Driver
- Anatomy of an MVR Report
- Why Nonprofits Must Screen Volunteer Drivers
- The Legal Rules of MVR Checks for Volunteers
- How to Read an MVR Report and Spot Red Flags
- Building Your Volunteer Driver Screening Policy
Your Best Volunteer Might Be a Risky Driver
A food pantry is short on drivers for a delivery route. A church has a retreat this weekend and needs someone to take the van. A youth program has one staff member out sick, and a longtime volunteer offers to handle pickup.
These are normal nonprofit moments. They're also exactly when bad decisions happen.
The trouble is that volunteer coordinators usually know the person in a community sense, not in a driver-risk sense. You may know they're dependable, kind, and willing to help at the last minute. You probably don't know whether their license is valid, whether they've had recent crashes, or whether they've picked up serious moving violations.
Practical rule: If someone will drive people, property, or the organization's vehicle, treat driving eligibility as a separate screening question.
An MVR check is the cleanest way to answer that question. It's a Motor Vehicle Record pulled from a state DMV system. In practice, it gives you the driving-specific facts that matter when a volunteer will be behind the wheel for your organization.
That matters because the risk isn't abstract. If a volunteer driver causes harm and the organization never checked whether they were legally allowed or reasonably safe to drive, that looks careless. Boards notice. Insurers notice. Plaintiffs' attorneys notice.
The real decision nonprofits are making
When a nonprofit skips an MVR check, it isn't staying flexible. It's making a risk decision without enough information.
That's especially dangerous with volunteers because many organizations assume informal trust is enough. It isn't. Driving is one of the few volunteer tasks where a person can create immediate physical risk to passengers, pedestrians, clients, and the public.
A strong volunteer program doesn't treat MVR checks as a signal of distrust. It treats them as a routine safety control, the same way you'd verify identity, training, or role fit. The best programs normalize that early, before the urgent ride request or weekend event forces a rushed call.
Anatomy of an MVR Report
An MVR report is a driver's specialized report card. It doesn't tell you everything about a person. It tells you what the state has on file about how they've been licensed and how they've behaved on the road.
What the report actually pulls
The core point is simple: an MVR check pulls data from a state DMV, not from a national MVR database, because no national database exists. That's why lookback periods vary by state, and why most states provide between three to seven years of driving history, while some jurisdictions allow longer or deeper reporting. For occasional driving roles, a 3-to-5-year review is generally sufficient, while CDL and other commercial driving roles often require a 7-plus-year review (Mitratech on MVR checks).
What you'll usually see includes:
- License status such as valid, suspended, revoked, expired, or restricted
- License class showing whether the person holds a standard license or a commercial license
- Issue and expiration dates so you can catch basic eligibility problems
- Traffic violations such as speeding, reckless driving, or red-light offenses
- DUI or DWI offenses
- Accident history
- Points in states that use a point system
- Driver identifiers such as legal name, address, and past licenses held
If you want a plain-language comparison of those elements, My Safety Manager on MVR importance lays out why these records matter in day-to-day screening decisions.
Why it's different from a criminal check
New nonprofit managers often find this confusing: a criminal background check and an MVR report overlap only a little.
An MVR is built for driving risk. It shows the status of the license itself and road-related history. A standard criminal check is built for court-based criminal records. Those are not the same thing.
Serious driving offenses such as DUIs often don't appear in standard criminal background checks, which is why a separate MVR screening is necessary for driving roles.
That distinction changes the screening process. If a volunteer will tutor children, handle donations, or work an event table, an MVR may be irrelevant. If that same volunteer will drive clients, meals, equipment, or youth participants, an MVR becomes one of the most important checks in the file.
Why Nonprofits Must Screen Volunteer Drivers
Nonprofits sometimes hesitate here because they're trying to stay lean. They don't want to add friction to volunteer onboarding. That instinct is understandable, but this is one place where trying to stay simple creates more exposure, not less.
Driving risk has three layers. People can get hurt. Insurance can get complicated. Public trust can erode fast.
The risk isn't only the accident
The immediate concern is safety. If a volunteer has a suspended license, a revoked license, or a pattern of risky driving, that's not a technical issue. That's a foreseeable problem.
The harder part comes after an incident. Once there's a crash, people start asking basic questions. Did the nonprofit know who it allowed to drive? Did it check whether the person was licensed? Did it ignore warning signs that were easy to find?
A lot of organizations spend heavily on child safety, facility security, and staff screening, then leave driving as an informal judgment call. That creates a weak point in an otherwise careful program.
When an organization screens every volunteer driver the same way, it protects people and creates a record that leadership acted responsibly.
What insurers care about
Insurance carriers care about driver risk because claims involving vehicles can become expensive and difficult. MVR checks reveal license suspensions, revocations, and accident history that standard criminal checks miss, and insurers rely heavily on that data to assess risk profiles and premiums for organizations using drivers (Westfield Insurance on protecting your fleet with MVR checks).
That has practical implications for nonprofits:
- Coverage questions: If your process for volunteer drivers is loose, you may have trouble proving the organization used reasonable screening practices.
- Vehicle exposure: This applies whether volunteers drive organization-owned vehicles or their own vehicles for organizational purposes.
- Renewal pressure: Underwriters often care less about good intentions than about documented controls.
Reputation belongs in the same conversation. Donors, parents, congregants, and partner agencies expect nonprofits to act carefully with transportation. If the organization looks casual about who gets the keys, that can damage trust even before any legal issue is resolved.
The Legal Rules of MVR Checks for Volunteers
The most common mistake I see is the assumption that unpaid volunteers sit outside the normal screening rules. For MVR checks, that assumption is risky.
MVR reports are consumer reports when they're used in screening, and the Fair Credit Reporting Act doesn't become optional because the role is unpaid. If your nonprofit orders an MVR on a volunteer through a screening process, you need to handle consent and decision-making carefully.
Volunteers still need FCRA consent
The clearest rule is this: get explicit written consent before you run the MVR.
The FCRA requires explicit consent for consumer reports, including MVRs, even for non-employment purposes like volunteer screening. One analysis cited by the National Council of Nonprofits found that fewer than 15% of nonprofit volunteer screening policies include standardized MVR consent forms, which leaves a real compliance gap (Embark Safety on MVR checks).
That gap exists because many MVR guides are written for HR teams hiring employees. Nonprofits read those guides, borrow the operational parts, and miss the volunteer-specific legal question. But if you're screening a volunteer for driving eligibility, the safer approach is the same one you'd use for other regulated background screening steps:
- Use a standalone disclosure that clearly says you may obtain an MVR for volunteer screening.
- Collect signed authorization before the report is ordered.
- Apply the process consistently for everyone in the same driving role.
- Store the paperwork securely because MVRs contain personal information.
For a broader plain-English explanation of these requirements, VolunteerBadge's guide to FCRA compliance is a useful reference for nonprofit teams.
If you decline a driver based on the report
The second mistake is mishandling what happens after a report comes back with a problem.
If the MVR leads you to decide a volunteer shouldn't drive for the organization, don't jump straight to a rejection email or a quick phone call. The safer path is to follow the adverse action process. In plain terms, that means giving the person notice, a copy of the report, and a chance to dispute inaccurate information before the decision is finalized.
That matters because DMV data can be misunderstood, and records can contain errors or context you don't yet have. A volunteer may have resolved an issue, or the report may belong to the wrong person if identifying information wasn't handled carefully.
Don't let urgency collapse your compliance process. The volunteer who's needed for Saturday's event can't become the reason your organization skipped consent or mishandled an adverse decision on Friday.
One more practical point. Keep the role-specific decision narrow. If the MVR disqualifies someone from driving, that doesn't automatically mean they should be excluded from every volunteer role. Many nonprofits make cleaner, fairer decisions when they separate driving eligibility from general volunteer eligibility.
How to Read an MVR Report and Spot Red Flags
Reading an MVR well is mostly about pattern recognition. One line item rarely tells the whole story. You're looking for severity, recency, and repetition.
A practical review process is easier when you stop asking, “Is this person good or bad?” and start asking, “Is this record acceptable for this driving role under our policy?”
A practical review framework
I use three buckets.
Major red flags are the items that usually take someone out of a driving role immediately. Think suspended license, revoked license, DUI or DWI, reckless driving, or anything else that shows the person may be unsafe or not legally eligible to drive.
Yellow flags don't always mean automatic disqualification, but they do require judgment. Multiple recent speeding violations, a recent at-fault accident pattern, or a growing points problem belongs here. These records often call for management review instead of automatic approval.
Minor issues are isolated, older, and less serious. A single older moving violation may not tell you much by itself, especially if the rest of the record is clean.
A consistent policy matters more than a harsh policy. The goal is defensible decisions, not maximum exclusion.
If a volunteer asks how points work or how they may be able to improve their record over time, this explanation of ways to lower license points can help them understand the issue from the driver's side.
Common MVR Red Flags and What They Mean
You don't need a complicated scoring model to make sound calls. You need a table like this in your policy and the discipline to use it.
| Red Flag | What It Means | Recommended Action |
|---|---|---|
| Suspended or revoked license | The volunteer may not be legally eligible to drive | Do not allow driving. Confirm status and document the decision |
| Expired license | Basic eligibility problem that may be fixable | Hold driving approval until a current valid license is verified |
| DUI or DWI offense | Serious safety concern tied directly to driving risk | Escalate for policy-based disqualification or formal review |
| Reckless driving | Indicates high-risk behavior behind the wheel | Treat as a major concern and review against written standards |
| Multiple recent moving violations | Suggests a pattern, not an isolated mistake | Require manager review and compare against your threshold |
| Recent accident pattern | May indicate unsafe driving habits | Review context, recency, and role risk before approval |
| High or accumulating points | Signals repeated violations in point-based states | Use caution, review trends, and consider restricting driving duties |
If you're building formal review criteria, VolunteerBadge's article on background check red flags is a good companion piece for documenting what needs escalation versus what can be handled routinely.
Building Your Volunteer Driver Screening Policy
A one-off MVR check is better than nothing. A written policy is what protects the organization.
Without a policy, every decision becomes personal. Staff make exceptions for loyal volunteers, hurry through urgent requests, and interpret the same record differently from one month to the next. That inconsistency creates risk and makes adverse decisions harder to defend.
What a workable policy includes
A nonprofit driver screening policy should be simple enough to use and specific enough to enforce.
Include these elements:
- Eligibility rules: State the minimum requirements to drive, such as holding a valid license and meeting your organization's MVR standards.
- Role coverage: Define which volunteer roles require MVR screening. Don't leave “occasional driving” vague.
- Consent procedure: Require written disclosure and authorization before any MVR is ordered.
- Review standards: Spell out what counts as disqualifying, what requires escalation, and who makes the final call.
- Recheck timing: Decide when records are reviewed again after the initial approval.
- Adverse action steps: Document how you handle unfavorable reports before removing someone from a driving role.
- Record retention: Keep reports and related forms secure and limited to people who need access.
For teams building a broader screening workflow around volunteer onboarding, VolunteerBadge's volunteer background check guide can help place MVR screening inside the larger process.
Why one-time checks stop being enough
A pre-service MVR tells you whether the driver looked acceptable on the day you checked. It tells you nothing about what changed after that.
That's why continuous monitoring is getting more attention. MVR monitoring is a real-time evolution of the standard check. It shifts organizations from one-time pulls to automated surveillance that can alert them to new suspensions, violations, or convictions so unsafe drivers can be reassigned quickly (Vetty on MVR monitoring).
For nonprofits, that creates a practical choice:
- Low-frequency driving programs may be able to work with pre-service checks and scheduled rechecks.
- Higher-risk or frequent driving programs should consider an ongoing monitoring approach if volunteers regularly transport people or use organizational vehicles.
The best policy is the one your staff will follow under pressure. Keep it written, role-based, and consistent. If a volunteer shouldn't drive, the policy should make that decision easy. If a volunteer can be approved with confidence, the policy should make that clear too.
Volunteer programs need screening that's affordable, fast, and compliant without creating extra admin work. VolunteerBadge is built for nonprofits that need FCRA-compliant volunteer screening, plain-English results, digital disclosure and authorization, and guided adverse action steps when needed.
