Coming soon. We aren’t taking orders yet.

For ops teams

When a record shows up

A record on a report isn’t a decision. It’s a question about one provider and one job, and you have time to answer it properly.

Read the record, then the note.

The analyst has already confirmed the record belongs to your provider.

The report shows the record the way the court holds it: the charge, the date, the outcome and the court. The analyst’s note says what it is in plain words, and that it was matched to your provider by more than a name.

Every record on the report has been confirmed at the court, on every package, so you’re reading the court’s record, not a database copy. Anything unclear goes to the analyst who signed the report.

Before you decide

What to check on the report

  • What the record is, and its outcome
  • How long ago it happened
  • The court it was confirmed at
  • The analyst’s note

Does it matter for this job?

That’s your call, against your own criteria. Roster doesn’t make it.

Write your criteria down before you need them: which records matter for which kind of work, and how far back. A driving offense means something different for a delivery driver than for a tutor.

Some states and cities require an individualized assessment before you turn someone away: the nature of the offense, the time since, and what it has to do with the job. Your team prepares and keeps it. State fair chance rules.

Your team owns

The decision

  • Your written screening criteria
  • Whether this record matters for this job
  • An individualized assessment, where required
  • The final call

Only a person can start adverse action.

The step sits on the report page, behind an admin or reviewer seat.

If you decide the record may lead you to turn the provider away, a person on an admin or reviewer seat approves the next step on the report page. Read-only seats can see the report but can’t take the step, and no API key or agent can take it either.

Who has which seat is set by your admin. Roles and permissions.

Adverse action

Who can take the step

  • Admin seats
  • Reviewer seats

The letters, prepared with the dates.

Roster prepares each letter. You review it, send it and decide.

  1. Pre-adverse letter. Prepared with a copy of the report and the summary of rights, so the provider can see what you saw and respond.
  2. The waiting period. The FCRA calls for a reasonable wait before a final decision, and some states set their own. The dates are on the letter, and a webhook fires when it ends.
  3. Adverse letter. If your decision stands, the adverse letter is ready with the details the law asks for. If the provider disputes, hold it. Disputes.

Roster prepares

Ready to send

  • Pre-adverse letter, with the report copy
  • Summary of rights, attached
  • Waiting-period dates, filled in
  • Adverse letter, if you decide no
  • Every step, kept in the record

What fires in the API at each step.

Your tools hear about every step. People still take each one.

Each step moves the check’s status and sends check.updated, so your ops tools and your agents can see where a review stands. Webhooks carry status, never record details. The sandbox serves the same events with test providers.

  1. check.completedReport readyStatus review. A record is on the report.
  2. Nothing firesYour reviewA person reads it and decides.
  3. check.updatedPre-adverse letter sentStatus pre_adverse, with the dates.
  4. check.updatedWaiting period endsThe date on the letter.
  5. check.updatedFinal decisionAdverse letter sent, or cleared.
An example review. Names and dates are made up.

Request

POST https://yourmarketplace.com/webhooks/roster
Roster-Signature: t=1760620800,v1=9c1e…

Response200 OK

{
  "type": "check.updated",
  "check": {
    "id": "chk_4Lm7",
    "status": "pre_adverse",
    "waiting_period_ends": "2026-10-21",
    "report_url": "https://reports.rosterchecks.com/chk_4Lm7"
  }
}

Example: the pre-adverse letter was sent.

What an agent can and can’t do here.

Agents can tell you a review is waiting. They can’t decide it.

An agent on a status-only key can see that a check needs review and when the waiting period ends, and remind the right person. It can’t read the report, approve adverse action or send a letter. Agents and key scopes.

An agent can

Watch and remind

  • See that a check needs review
  • Tell you when the waiting period ends
  • List checks waiting on a person

An agent can’t

Decide

  • Read the report on a status-only key
  • Approve adverse action
  • Send a letter to the provider

Run a record through the sandbox.

Tell us how your ops team works today. Sandbox keys right away if your engineers want to try it first.

  • A report page and PDF for every check, signed by the analyst who reviewed it, with a way to message them from the report page.
  • Status in the dashboard and by webhook. explain_status says which court a check is waiting on.
  • Every possible record is confirmed at the court before it’s reported, on every package.
  • Notices and letters prepared with the dates filled in, behind an approval gate only admin and reviewer seats can pass.
  • Your team reviews, sends the letters and makes every decision.