# Background checks for driving and delivery marketplaces

> Delivery and errand drivers carry your customers' orders on public roads, so driving and delivery marketplaces need the core check and a driving record on every driver. Roster runs both through one API with live ID verification on every check; driving record monitoring is on the way.

By Ben Drellishak, Owner. Last reviewed November 6, 2026.

## Who gets checked

Anyone who drives an order to a customer.

Every driver who takes a delivery or an errand through your marketplace gets the same check before their first trip.

Who gets checked: food and parcel delivery drivers, grocery shoppers who deliver, errand runners, and anyone who drives to a customer.

## Checks for driving and delivery

The core check on every driver, plus the driving record.

Live ID verification comes first, so every search runs on the right person. A named analyst matches every possible record to the provider and confirms it at the court before signing the report. Driving record monitoring is coming.

Checks for driving and delivery: live ID verification, identity and address history, national and county criminal records, the sex offender registry and the global watchlist, all included. The driving record is an add-on. Driving record monitoring is coming.

## Every driver gets a driving record

Ordered with the person check, in the same call.

The driving record comes from the state that issued the license. Your team sets the driving criteria for your marketplace; Roster puts the record on the same report as the rest of the check.

The state’s fee is shown at cost before you order, never inside our price.

What a driving record usually shows: license status and class, violations and accidents on record, and suspensions and revocations. It varies by state.

## An example onboarding flow

One call starts the check and the driving record together.

1. A driver signs up and your app calls `POST /v1/checks` with the driving record added.
2. They sign consent and confirm their identity with their ID and a live selfie, on their phone, in your brand.
3. Webhooks tell your app when each search moves and when the report is signed.
4. If something shows up, the notices and letters are prepared with the dates filled in. Your team sends them and decides.

Example: POST /v1/checks with the delivery package and the driving record add-on returns 201 Created with the check id and status consent_sent.

## When a check waits on a court

Tell the driver why, in one plain sentence.

Some county courts don’t put their records online, so a check can wait while someone searches at the courthouse. Waiting doesn’t mean anything was found.

`explain_status` returns a sentence your app or agent can pass straight to the driver, with the court and a rough time. For the longer answer, link them to [why a check waits on a county court](https://www.rosterchecks.com/help/why-is-my-check-waiting-on-a-county-court/).

Example check status: driving record done; national database done; Hamilton County court waiting, expected next business day.

## Driving record monitoring is coming

An alert when a driver’s record changes, on the way.

Driving record monitoring isn’t live yet. When it is, a webhook will tell you when a driver’s record changes after onboarding, and your team will review it and decide.

---

HTML version: https://www.rosterchecks.com/solutions/driving-and-delivery/
