# State fair-chance and ban-the-box rules for platforms

> Many states and cities limit when a criminal record can be considered, ask for an individualized assessment of it, and require notice before a final decision, and some of these rules reach independent contractors. Roster selects the notices for the provider's state and fills in the waiting-period dates; your team does the assessment and makes the call.

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

## The rules share a shape

When you can look, how you weigh it, and what you tell the provider.

Fair-chance and ban-the-box laws differ in detail, but most follow the same pattern. They delay when a record can be considered, often until after a conditional offer. They ask you to weigh the record against the work, and to give the provider notice and a chance to respond before a final no.

What fair-chance rules tend to ask: timing, looking at records later in the process; an individualized assessment that weighs the record against the work; and notice telling the provider why, with time to respond.

## 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.

Examples of places with fair-chance rules, among others: California, New York City and Illinois.

## 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.

Prepared for an example provider with a record: the state notice for their state, ready; the pre-adverse letter with the report copy and summary of rights, ready; the waiting-period dates filled in with a webhook when it ends; and the adverse action letter if your team decides no.

## 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.

Owned by your team: deciding when in onboarding the check runs, weighing the record against the work, sending the notices and reading the response, and making 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](https://www.rosterchecks.com/sandbox/) or [read the developer page](https://www.rosterchecks.com/developers/).

---

HTML version: https://www.rosterchecks.com/guides/state-fair-chance-rules-for-platforms/
