# Questions to ask before you switch background check vendors

> Before you switch, settle what happens to checks still in flight, whether providers need to consent again, where your historical reports will live, and how your webhooks and statuses map across. Roster's sandbox lets you build and test the new flow end to end before a single live provider moves.

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

## Finish the checks you've started where they started

Let open checks and open adverse actions finish with your current vendor.

Pick a cutover date and send new checks to the new vendor from that day. Checks already running, and any pre-adverse waiting periods already counting down, finish with the vendor that started them. That keeps every letter tied to the report it was based on.

A switch in order: build in the sandbox with test providers; a short credentialing call for live keys; on the cutover date new checks go to Roster; checks already open finish with the old vendor, letters included.

## Every new check gets its own consent

Ask what your current consent says, and plan for providers to sign again.

A consent signed for your old vendor may name that vendor, or may not cover a new check. Either way, every Roster check sends the provider its own hosted disclosure and consent, followed by the live ID step, so re-checks after the switch collect a fresh signature. Have your counsel look at your consent wording if you plan to rely on the old one.

## Decide where historical reports will live

Old reports stay with the vendor that ran them. Keep your own copies.

Ask your current vendor how long you can reach past reports and how to export them before your contract ends. Roster's record starts with the first check it runs, with a report page and PDF for each one. Keep exported reports under your own retention policy.

Ask your current vendor before your contract ends: how long you can open past reports, whether you can export the PDFs in bulk, who answers disputes on old reports, and when open checks need to finish.

## Map your webhooks and statuses

Three events cover a Roster check. Map each to what your app does now.

Roster sends `check.consent_signed` when the provider signs and confirms their ID, `check.updated` as each search moves, and `check.completed` when the analyst signs the report. Each delivery is signed in the `Roster-Signature` header and carries status only, never record details. Map those to the states your onboarding screens already show.

Three webhook events to map: check.consent_signed when the provider signs and confirms their ID; check.updated when a search moves; check.completed when the analyst signs the report.

## What Roster prepares from day one

Consent, notices, letters and a record of every check, from the first one.

Hosted disclosure and consent with the live ID step, state notices for the provider's state, pre-adverse and adverse letters with the waiting-period dates filled in, and a record of every check. A named analyst confirms any possible record at the court, and `explain_status` tells ops which court a check is waiting on.

## What you still own through the switch

The criteria, the letters on old checks, and every decision.

Your criteria move with you: decide whether anything changes, and write it down. Your team sends the letters on checks that finish with the old vendor, sends the ones Roster prepares on new checks, and makes every final call.

## Test the whole switch in the sandbox

Consent, live ID, webhooks and the MCP server, with test providers.

Sandbox keys come without a sales call. Point a branch of your app at the sandbox, run test providers through consent and live ID, check your webhook handler against all three events, and try the MCP server with a status-only key. [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/questions-to-ask-before-you-switch-background-check-vendors/
