Compliance for builders
State fair-chance and ban-the-box rules for platforms
Your providers work in dozens of places. Some of them have their own rules about records.
- State noticeSelected for the provider’s stateReady
- Pre-adverse letterReport copy and summary of rightsReady
- Waiting periodDates filled inDated
- Your assessmentA person on your team decidesYou act
California, New York City and Illinois have them, among others
States, counties and cities, and the list keeps growing.
California, New York City and Illinois have fair-chance rules, among many other states, counties and cities. Some of them cover independent contractors as well as employees. Which rules apply depends on where the provider lives and works, so check with your counsel for the places you operate.
Ask for the check after the conditional yes
For a marketplace, that usually means after the rest of onboarding.
Many marketplaces start the check once a provider has passed everything else and been told they’re approved pending the check. That keeps the record out of the earlier decisions. Your team decides where that point sits in your flow; the API starts the check whenever you call it.
Roster prepares the notices and the dates
State notices for the provider's state, letters with the waiting periods filled in.
Roster selects the notices for the provider’s state and prepares the pre-adverse and adverse letters with the waiting-period dates filled in. A webhook tells you when each step is due. The analyst who confirmed the record at the court can walk your team through what it says.
- State noticeSelected for the provider’s stateReady
- Pre-adverse letterReport copy and summary of rightsReady
- Waiting periodDates filled in, webhook when it endsDated
- Adverse action letterIf your team decides noIf needed
The assessment and the decision are yours
A person on your team weighs the record. An agent can't.
Your team sets the criteria, weighs each record against the work the provider will do, and records why. You send the notices, read any response, and make the final call. Roster enforces a person’s approval before adverse action.
What you do
Owned by your team
- Decide when in onboarding the check runs
- Weigh the record against the work
- Send the notices and read the response
- Make the final call, with a person
Build the flow in the sandbox first
Consent, live ID and every webhook, with test providers.
Sandbox keys come without a sales call. Start a check on a test provider with POST /v1/checks, place it where your conditional yes sits, and watch the webhooks arrive before a real provider is involved. 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.