Compliance for builders
Consent and disclosure: what your onboarding flow must show, and in what order
Your signup flow has one screen the law cares about more than any other. Here's what goes on it.
- DisclosureIts own screenShown
- AuthorizationSigned by the providerSigned
- Live IDID and a live selfieDone
- check.consent_signedWebhook to your appSent
Disclosure first, then consent, then the check
The provider reads, then signs, then confirms their identity. Only then does the check run.
The FCRA asks for a clear disclosure, in a document of its own, that a background check may be run. The provider then authorizes it in writing; an e-signature counts. The check starts only after both.
- Screen 1DisclosureStandalone
- Screen 2AuthorizationThe provider signs
- Screen 3Live IDID and a live selfie
- AfterThe check runscheck.consent_signed fires
Keep everything else off the disclosure
A disclosure crowded with other terms is the most common mistake in this flow.
The disclosure should say that a check may be run and little else. Courts have found disclosures that carried waivers or other terms didn’t stand alone. Put the rest of your onboarding on its own screens.
Not on the disclosure
Keep these on other screens
- A liability waiver or release of claims
- Your terms of service or privacy policy
- Onboarding questions or the application
- Marketing or messaging opt-ins
Some states add their own notices
Where the provider lives can add a notice or a box to ask for a copy of the report.
Some states ask for their own notice alongside the federal disclosure, or a way for the provider to ask for a copy of their report. Which ones apply depends on the provider’s state, among other things. Your counsel should look at your flow once, before you go live.
Roster hosts the screens in your brand
Your logo and colours on top, Screened by Roster underneath.
POST /v1/checks returns a consent_url, and Roster sends the provider the link. They read the disclosure, sign, then confirm their identity with their ID and a live selfie from their phone. State notices are selected for the provider’s state, and the signed documents go into the record of the check.
- DisclosureIts own screen, nothing else on itShown
- AuthorizationSigned by Maya on her phoneSigned
- State noticeSelected for Maya’s stateShown
- Live IDID and a live selfieDone
Your code waits for check.consent_signed
One event tells you the provider signed and confirmed their ID.
Listen for check.consent_signed, then show the provider that their check is under way. If they stall, resend_consent sends the link again. Only the provider can sign: no key, agent or teammate can consent for them.
In your code
Three things to wire up
- Open consent_url, or let Roster send it
- Handle check.consent_signed
- Resend with resend_consent if they stall
You own the flow around it
We prepare the screens. You decide where they sit and why you screen.
Your team decides why you screen, when in signup the check starts, and what the provider sees before and after. If you build your own consent screens instead of using Roster’s, the wording and order are yours to get right, and your counsel should review them.
See the hosted screens in the sandbox
Run a test provider through consent and live ID this afternoon.
Sandbox keys come without a sales call. Create a check, open the consent_url, sign as a test provider and watch check.consent_signed arrive at your endpoint. 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 Dennis Drellishak, Owner. Markdown version.