# Rescreening and monitoring: when to re-check a provider

> Most marketplaces re-check providers on a schedule, often once a year, and after events like a complaint, a move to a new kind of work, or a long break. On Roster a re-check is a new check for the same provider: one call, a fresh consent link, and the same court confirmation; ongoing monitoring is coming.

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

## Re-check on a schedule, or when something changes

A yearly re-check is common. Events can call for one sooner.

Many marketplaces re-check every provider once a year. Others add a re-check when something changes: a safety complaint, a move into work with children or older people, or a provider coming back after months away. Pick the rule and apply it the same way to everyone.

Common triggers for a re-check: once a year on the signup anniversary, after a safety complaint, before more sensitive work, and when a provider returns after a long break.

## A re-check is a new check, with a new consent

The provider signs again and confirms their identity again.

Every Roster check sends the provider a consent link, and a re-check is no different. They read the disclosure, sign, and confirm their identity with their ID and a live selfie from their phone. Nobody can sign for them, including your agents.

## One call runs it

POST /v1/checks with the same provider and package.

Send the same provider and package you used the first time. The response is a new check id with its own `consent_url`, and the same webhooks follow: `check.consent_signed`, `check.updated` and `check.completed`. A named analyst confirms any possible record at the court and signs the new report.

A re-check: your code calls POST /v1/checks with the same provider; the provider signs consent and does live ID again; check.updated fires as each court search moves; check.completed fires when the analyst signs the report.

## Ops sees both checks, side by side

Status by API, webhook and MCP, and a report page for each check.

Each check has its own report page and PDF, so your team can open last year's and this year's together. `list_checks` shows what's open, and `explain_status` says which court a re-check is waiting on and when to expect it. Roster keeps a record of every check.

An example provider's checks: the signup check from November 2025, cleared; the yearly re-check, waiting on Hamilton County court; monitoring, coming.

## Ongoing monitoring is coming

Alerts between re-checks are on the way. Until then, schedule re-checks.

Monitoring will tell you when a new record turns up between re-checks. It isn't available yet. Until it is, a scheduled re-check is the way to keep a provider's check current.

## You set the schedule and act on what comes back

We prepare, you act.

Your team decides how often to re-check and what triggers one. If a re-check turns up something that might lead you to remove a provider, the [adverse action steps](https://www.rosterchecks.com/guides/adverse-action-for-marketplaces/) apply, and a person makes the call. Tell Roster when a provider leaves.

Owned by your team: setting the schedule and triggers, calling the API when a re-check is due, reviewing what comes back and deciding, and telling Roster when a provider leaves.

## Script a yearly re-check in the sandbox

Run the same test provider twice and compare the two checks.

Sandbox keys come without a sales call. Create a check for a test provider, then create another for the same provider and watch the second consent link and webhooks arrive. [Get sandbox keys](https://www.rosterchecks.com/sandbox/) or [read the developer page](https://www.rosterchecks.com/developers/).

---

HTML version: https://www.rosterchecks.com/guides/rescreening-and-monitoring/
