If you own or run a Delivery Service Partner, the background check program for your drivers is your responsibility, not the marketplace’s. That distinction matters more than most new DSP owners realize, because it determines who signs the disclosure form, who orders the report, who has to give a candidate notice before turning them down, and who answers for it if a driver with a violent record ends up at someone’s front door. This guide covers what a compliant screening stack for last mile drivers actually looks like, why most delivery vans fall outside the federal commercial driver rules that people assume apply, and how to build disqualifier standards and monitoring that hold up under pressure, including during seasonal surge hiring.
What a Delivery Service Partner is, and why the DSP owns the FCRA duties
A Delivery Service Partner is an independently owned and operated business. It has its own EIN, its own insurance, its own payroll, and its own employees. The DSP contracts with a marketplace to run delivery routes using that marketplace’s branding, technology, and volume, but the DSP hires the drivers, manages them, pays them, and disciplines or terminates them. That ownership structure is publicly documented and is the reason DSPs exist as a business model in the first place.
The Fair Credit Reporting Act attaches its obligations to whoever orders a background check and uses it to make an employment decision. That is the DSP, not the marketplace. A marketplace program may set expectations for what kind of screening its contracted delivery companies run and which vendors are approved for the program, but the legal duties under the FCRA, the disclosure, the signed authorization, the pre-adverse action notice, the waiting period, and the final adverse action notice, belong to the DSP as the employer of record. Assuming the marketplace’s program requirements substitute for your own FCRA compliance is a common and expensive mistake. They do not. Build your program as if you are the only party accountable for it, because you are.
The standard screening stack for last mile drivers
A last mile delivery role is customer facing, vehicle based, and often unsupervised inside homes, gated communities, and apartment buildings. The screening stack should reflect that combination of driving risk and access risk. A solid baseline includes:
- Identity and SSN trace. Confirms the applicant is who they say they are and surfaces address history that points investigators to the right counties to search.
- County criminal record search. County courthouse records remain the most complete and current source for criminal history in most jurisdictions.
- National criminal database search. Used as a supplement to widen the net across jurisdictions, then confirmed at the county level before any decision is made.
- Sex offender registry check. Directly relevant given that drivers regularly interact with residential properties and sometimes with children present.
- Motor vehicle record, with ongoing monitoring after hire. The single most job relevant data point for a driving role, and the one most fleets under monitor.
- Drug testing. Set by the fleet’s own written policy, since most delivery vans are not covered by federal DOT drug testing rules, which is covered in detail below.
Why most delivery vans fall outside CDL and DOT drug testing rules
This is the part DSP owners most often get wrong, in both directions. Some assume every driver on the road needs DOT level screening. Others assume none of it applies and skip building any real policy. Neither is correct.
Federal law sets the commercial driver’s license requirement at a gross vehicle weight rating of 26,001 pounds or more, with some exceptions for certain vehicle combinations, under the definitions in 49 CFR 383.5. The step vans and cargo vans used in most last mile delivery fleets are built well under that threshold. Many also fall under the 10,001 pound gross vehicle weight rating used elsewhere in the Federal Motor Carrier Safety Regulations to define a commercial motor vehicle, as set out in 49 CFR 390.5. A driver operating a vehicle below these thresholds generally does not need a CDL to do the job.
The federal DOT drug and alcohol testing program under 49 CFR Part 382 is built on top of the CDL requirement. Under 49 CFR 382.103, the rule applies to drivers who are required to hold a commercial driver’s license to perform their driving duties. If your drivers are not required to hold a CDL, they are not automatically covered by the federal testing panel, the random testing pool, or a query obligation to the FMCSA Clearinghouse.
What that means in practice is simple and important: the absence of a federal mandate does not mean the absence of risk. It means the fleet’s own written policy carries the full weight of the safety program. A DSP that treats this as a reason to skip drug testing altogether is choosing a weaker safety posture than the law requires of larger carriers, not a stronger one. The better approach is to adopt an equivalent non-DOT testing program voluntarily, pre-employment and for reasonable suspicion at minimum, document it in writing, apply it consistently to every applicant and every driver, and treat that written policy as a real safety control rather than a formality.
Setting disqualifier standards that hold up
A disqualifier list only works if it is written down before you start reviewing candidates, applied the same way every time, and tied to the actual duties of the job. For a delivery driver, the duties are operating a vehicle on public roads and entering homes and buildings to hand off or place packages. Standards should map to that.
| Finding | Why it matters for this role | Reasonable approach |
|---|---|---|
| Recent DUI or DWI conviction | Directly tied to safe operation of a company vehicle | Set a fixed lookback period, apply it uniformly, and review multiple offenses more strictly than a single older one |
| Reckless driving or a heavy point load on the MVR | Predicts on the job crash and liability risk | Use a point threshold and violation type list, not a gut call, and document the standard in the policy |
| Theft, burglary, or receiving stolen property conviction | Package handling and doorstep access make this role a direct dishonesty risk | Weigh how long ago it occurred and how closely it relates to property access, rather than an automatic bar with no review |
| Violent or sexual offense conviction | Unsupervised entry to homes and proximity to residents | Treat conservatively given the nature of the access involved in the job |
Whatever standard you set, apply it the same way to every applicant and keep a record of why each decision was made. An individualized review that looks at the nature of the offense, how long ago it happened, and how it relates to the driving and delivery duties of the job holds up far better than a blanket rule with no documented reasoning, and it gives you something concrete to point to if a decision is ever challenged.
Adverse action at hiring speed
Turning down or removing a candidate based on a background check triggers a specific sequence under the FCRA, and rushing to fill routes is not a reason to skip steps. Give the candidate a pre-adverse action notice along with a copy of the report and a summary of their rights. Hold the position open for a reasonable waiting period so the candidate has a real chance to dispute anything inaccurate before a final decision is made. Only after that window closes should you send the final adverse action notice and move on to the next candidate. Building this sequence into your applicant tracking workflow, rather than handling it manually case by case, is what lets a DSP move quickly without cutting the legally required steps.
Continuous MVR monitoring after hire
A background check run once at hire tells you nothing about a driving record six months later. A driver who passes screening in January can pick up a DUI or a reckless driving citation in June, and a one time check will never catch it. Ongoing motor vehicle record monitoring closes that gap by flagging new violations as they post to the state record, rather than waiting for a scheduled rescreen.
Some states run their own employer notification programs. California’s Employer Pull Notice program, described on the California DMV site, is a well known example of a state run system that alerts enrolled employers when a driver’s record changes. Coverage and mechanics vary by state, so a fleet operating across multiple states typically needs a third party continuous monitoring service that can watch driver records nationally rather than relying on a patchwork of state programs. Either way, ongoing monitoring should be treated as a core part of the driver safety program, not an optional add on.
Seasonal surge hiring without cutting corners
Peak season is exactly when the temptation to shortcut screening is strongest, and exactly when the risk of a bad hire is highest, since volume and vehicle count both spike at once. A few practices keep the program intact under pressure:
- Run the same screening stack for seasonal drivers as for year round drivers. A short assignment does not reduce the access or driving risk.
- Build a pre-verified applicant pipeline ahead of the surge so volume does not force a choice between speed and completeness.
- Work with a screening provider that can scale turnaround for volume spikes without dropping steps like county verification or adverse action notices.
- Keep disqualifier standards written down and consistent so seasonal reviewers apply them the same way permanent hiring staff would.
Screening element, risk covered, and refresh cadence
| Screening element | Risk it covers | Refresh cadence |
|---|---|---|
| Identity and SSN trace | Confirms identity, surfaces address history for county searches | At hire |
| County criminal search | Most complete and current criminal record source | At hire, and again at rehire or promotion into a higher access role |
| National criminal database search | Widens jurisdictional coverage, confirmed at the county level | At hire |
| Sex offender registry check | Residential and doorstep access risk | At hire, and on periodic rescreen |
| Motor vehicle record | On the road safety and liability risk | At hire, then continuous monitoring for new violations |
| Drug test (fleet policy based) | Impairment risk behind the wheel | Pre-employment, plus reasonable suspicion and random testing if the policy includes it |
Frequently asked questions
Is the DSP or the marketplace responsible for FCRA compliance on driver background checks?
The DSP is. As the employer of record that orders the report and uses it to make a hiring decision, the DSP holds the disclosure, authorization, and adverse action duties under the FCRA, regardless of any program requirements set by the marketplace it contracts with.
Do Amazon DSP drivers need a CDL?
Most do not, because the vans used for last mile delivery are typically well under the 26,001 pound gross vehicle weight rating that triggers the federal CDL requirement under 49 CFR 383.5.
Are DSP drivers subject to DOT drug testing?
Generally not, since the federal Part 382 drug and alcohol testing program applies to drivers required to hold a CDL. Fleets whose drivers do not need a CDL should adopt their own written drug testing policy rather than assuming no testing is needed.
What criminal history should disqualify a delivery driver applicant?
There is no single federal list. Most fleets weigh recent DUI or reckless driving convictions, theft or property crime convictions given the package handling and doorstep access involved, and violent or sexual offenses conservatively, applying the same written standard to every applicant.
How often should a DSP recheck a driver’s motor vehicle record?
A one time check at hire misses violations that occur afterward. Continuous MVR monitoring, either through a state program like California’s Employer Pull Notice system or a third party monitoring service, flags new violations as they post rather than waiting for a scheduled rescreen.
Should seasonal delivery drivers go through a lighter screening process?
No. Seasonal drivers carry the same vehicle and access risk as year round drivers. The safer approach is to keep the same screening stack in place and build capacity ahead of the surge rather than cutting steps under volume pressure.
For more on the driving record piece of this stack, see our guide to MVR background screening for employers, and for how platform based driving roles are typically screened, see rideshare driver background checks. Reveal Background builds screening programs for last mile and delivery fleets that need a compliant stack without slowing down hiring.
This article is general information, not legal advice. Employers should confirm current federal and state requirements, and consult qualified counsel, before finalizing a background check or drug testing policy.
