For ops and trust teams
Background checks for ops and trust teams
You answer for every provider on your marketplace. Know where each check stands and what to send next.
- Report page and PDFSigned by the analystClear
- State noticeFor the provider’s stateReady
- Pre-adverse letterDates filled inReady
- Adverse actionWaits for your approvalYou decide
Nothing to chase.
Every check’s status, with the court it’s waiting on and when to expect it.
Status reaches your tools by webhook, so nobody refreshes a vendor portal. When a provider asks why their check is taking a while, explain_status gives one plain sentence: the court and a rough time.
For anything else, link providers to the provider help pages, so your support queue doesn’t carry it.

A report you can open, and a person to ask.
A report page and a PDF, signed by the analyst who ran the check.
An analyst reviews every hit and confirms it belongs to your provider. Then the record is confirmed at the court before it’s reported, on every package. The analyst signs the report. Your team opens it as a page or a PDF, and every check is kept on record.
Questions about a report go to that analyst by name, not to a ticket queue.
- Live ID stepID photo and live selfieDone
- County criminal recordsEvery county lived inClear
- Sex offender registryEvery stateClear
- Signed by the analystReport page and PDFSignedExample
Notices and letters, ready with the dates.
We prepare. You act.
Roster prepares the state notice for the provider’s state, and the pre-adverse and adverse letters with the waiting-period dates filled in. A webhook fires when each step is due.
Your team reviews them, sends them and makes the call. That’s everything you need to stay compliant, with nothing to draft. See who does what.
- State noticeSelected for the provider’s stateReady
- Pre-adverse letterReport copy and summary of rights attachedReadyDates filled in
- Waiting periodWebhook when it endsWaiting
- Adverse letterOnly if your team decidesIf needed
A person approves every adverse action.
No API key or agent can take the step.
Agents can start checks, read status and explain delays. Deciding not to onboard someone, or to remove them, waits for a person on your team to approve it, and Roster enforces that gate.
Your team
What stays with you
- Your screening criteria
- Sending the notices and letters
- Approving adverse action
- The final call on every provider
Your part, step by step.
Reading a report, reviewing a record, disputes, the record and who can do what.
The For ops teams pages walk through each part of an ops team’s work on a Roster check, one page each.
Talk to our team.
Tell us about your marketplace. Sandbox keys right away if your engineers want to try it first.
- 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.