# Background checks for care marketplaces

> Care providers work with children, older adults and people at home, so care marketplaces need the core check on every provider. Roster runs it through one API with live ID verification on every check, and care registries and monitoring are on the way.

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

## Who gets checked

Everyone who books care through your platform.

Every provider a family books through you gets the same check before their first visit.

Who gets checked: babysitters and nannies, senior caregivers and companions, pet sitters who stay in the home, and anyone else who books care through your platform.

## Checks for care

The core check on every provider, with live ID first.

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. Add the state abuse and neglect registry and the federal exclusion lists where your providers need them; ongoing monitoring is coming.

Checks for care: live ID verification, identity and address history, national and county criminal records, the sex offender registry and the global watchlist, all included. The state abuse and neglect registry and the OIG and SAM exclusion lists are add-ons. Ongoing monitoring is coming.

## State rules

Some states set their own checks for care workers.

Some states set their own checks for care workers. Your team decides which rules apply to your marketplace; Roster prepares the state notice for the provider’s state, and the pre-adverse and adverse letters with the dates filled in. Kids and learning marketplaces share most of these rules: see the [kids and learning playbook](https://www.rosterchecks.com/solutions/kids-and-learning/).

## An example onboarding flow

Sign-up to signed report, with your app and your agents kept up to date.

1. The provider signs up and your app calls `POST /v1/checks`.
2. They sign consent and confirm their identity with their ID and a live selfie, on their phone.
3. Webhooks keep your app and your agents up to date.
4. If something shows up, the notices are prepared for your team to send.

Example onboarding flow: the provider signs up and your app calls POST /v1/checks; they sign consent and confirm their identity on their phone; webhooks keep your app and agents up to date; if something shows up, the notices are prepared for your team to send.

## When a check waits on a court

Tell the caregiver 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 provider: their first name, 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: explain_status for a check returns “Your check is waiting on Hamilton County court. That usually takes one more business day.”

## Monitoring is coming

Ongoing checks after onboarding are on the way.

Ongoing monitoring isn’t live yet. When it is, a webhook will tell you when a new record turns up for a provider who has already passed their check, and your team will review it and decide.

---

HTML version: https://www.rosterchecks.com/solutions/care/
