Compliance for builders
Rescreening and monitoring: when to re-check a provider
The check you ran at signup gets older every month. Your providers keep working.
- Signup checkSigned by the analystCleared
- Yearly re-checkNew consent, new reportRunning
- MonitoringAlerts between re-checksComing
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
When marketplaces re-check
- Once a year, on the signup anniversary
- After a safety complaint
- Before more sensitive work
- 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.
- Your codePOST /v1/checksSame provider
- ProviderConsent and live IDSigned again
- check.updatedCourts searchedAs each moves
- check.completedSigned reportBy the analyst
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.
- Signup checkNov 2025, signed by the analystCleared
- Yearly re-checkWaiting on Hamilton County courtWaiting
- MonitoringComingComing
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 apply, and a person makes the call. Tell Roster when a provider leaves.
What you do
Owned by your team
- Set the schedule and the triggers
- Call the API when one is due
- Review what comes back and decide
- Tell 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 or read the developer page.
What Roster handles
Sandbox keys right away, no sales call. Live keys after a short credentialing call.
- One call starts a check. Hosted consent and live ID in your brand; a webhook when it’s done. Sandbox keys without a sales call.
- Status by API, webhook and MCP. explain_status says which court it’s waiting on and when to expect it.
- A named analyst matches every possible record to the provider and confirms it at the court before it’s reported. A signed report page and PDF your team can open.
- Every notice and letter prepared, with the waiting-period dates filled in, and a human approval gate before adverse action.
- You send the notices and make the final call. Contractors covered the same way as employees.
Reviewed November 6, 2026 by Ben Drellishak, Owner. Markdown version.