Gig worker background check requirements start with the Fair Credit Reporting Act, not with how a platform classifies the worker. Whenever a delivery, rideshare adjacent, home services, or care marketplace app orders a consumer report on someone applying to join the platform, the FCRA’s permissible purpose framework applies to that report itself, along with the disclosure, written authorization, and adverse action steps that go with it. On top of that one time check, platforms that want ongoing trust and safety typically add continuous monitoring and a rescreening cadence for people who stay active on the platform for months or years.
This guide covers what the law actually requires, where platforms tend to get the process wrong, and how screening gets embedded into an onboarding flow through an API or white label program. It does not address whether gig workers are or should be classified as employees or independent contractors under labor law. That is a legal classification question for the platform’s own counsel, and it is separate from whether a background check on that worker is subject to the FCRA.
Why the FCRA Applies to Non-Employee Platforms
The FCRA regulates consumer reports based on what the report is and why it was pulled, not the employment status of the person it describes. A “consumer report” is any communication from a consumer reporting agency bearing on a person’s “character, general reputation, personal characteristics, or mode of living” that is used or expected to be used as a factor in establishing eligibility for, among other things, employment purposes or “any other purpose authorized under section 1681b” (15 U.S.C. 1681a(d)(1)).
Section 1681b lists the permissible purposes for which a consumer reporting agency may furnish a report. One is when the requester “intends to use the information for employment purposes,” defined as evaluating a consumer “for employment, promotion, reassignment or retention as an employee” (15 U.S.C. 1681a(h)). A separate, broader permissible purpose covers anyone who “otherwise has a legitimate business need for the information… in connection with a business transaction that is initiated by the consumer,” or to review an existing account to confirm the person still meets its terms (15 U.S.C. 1681b(a)(3)(F)). A platform onboarding an applicant who initiated that relationship, or periodically reviewing an active account against platform standards, can fall within this legitimate business need purpose regardless of how the relationship is later classified.
The Consumer Financial Protection Bureau has also weighed in on how broadly this framework reaches. Its 2024 circular on background dossiers and algorithmic scores states that reports “obtained from third parties and used by employers to make hiring, promotion, reassignment, or retention decisions are often governed by the FCRA,” and that the statute “applies both to information used for the purpose of evaluating a consumer for employment initially, and to information used for ongoing employment purposes” (CFPB Circular 2024-06). The practical takeaway for a platform: order the report only for a purpose that fits within section 1681b, document that purpose, and treat the report the same way regardless of whether the person filling out the application is ultimately an employee or a contractor.
The Disclosure, Authorization, and Adverse Action Steps
Once a platform has a permissible purpose for the report, section 1681b(b) sets conditions specific to reports procured for employment purposes. A platform may not procure the report unless it has made “a clear and conspicuous disclosure… in writing to the consumer” before the report is pulled, stating that a consumer report may be obtained, and unless “the consumer has authorized in writing” the procurement (15 U.S.C. 1681b(b)(2)). That disclosure needs to stand on its own, not be buried inside a longer terms of service or app onboarding screen.
Before the platform acts on the report to deny, deactivate, or decline to onboard someone, the same section requires a pre-adverse action step: providing the individual a copy of the report and a description of their rights under the FCRA before the adverse action is finalized (15 U.S.C. 1681b(b)(3)). A reasonable waiting period between the pre-adverse notice and the final decision, along with a follow-up adverse action notice, is part of that process. None of this is optional based on how quickly a platform wants to activate new users, and none of it is satisfied by a check box buried in a sign-up flow.
Criminal history should also never be treated as an automatic disqualifier. EEOC guidance calls for an individualized assessment before excluding someone based on a criminal record, considering factors like the nature of the offense, how much time has passed, and the nature of the role, rather than a blanket policy that excludes everyone with any record (EEOC enforcement guidance). A platform’s screening reports, including any criminal background check results, should feed into that kind of human review rather than an automated pass or fail.
Continuous Monitoring and Rescreening Cadence
A one time check at onboarding tells a platform who someone was on the day they applied. It says nothing about a new conviction, a suspended license, or a status change that happens six months into an active account, which is why many gig and marketplace platforms pair the initial background check with ongoing monitoring. Continuous monitoring flags new criminal record activity between full rescreens, so a platform is not relying solely on a snapshot from months or years earlier.
Rescreening cadence is a policy decision, not a fixed legal number, and it should be set with counsel based on the platform’s risk profile, the categories of work involved, and applicable state and local law. Whatever cadence a platform chooses, the same disclosure, authorization, and pre-adverse action steps described above apply to a rescreen just as they applied to the original report, since a rescreen is itself a new consumer report pulled for the same permissible purpose.
Embedding Screening Into the Onboarding Flow
Marketplace and gig platforms rarely want a screening step that sends applicants to a separate site to fill out another form. Most build the disclosure, authorization, and status tracking directly into their own signup flow, then call a screening provider’s API in the background so the applicant experiences one continuous process. That is typically done either by integrating directly against a provider’s API or by adopting a white label screening setup, where the platform’s own brand stays in front of the applicant while the screening infrastructure runs underneath it.
The right approach depends on engineering resources and how much control the platform wants over the applicant experience. A comparison of the two paths, including what each requires to build and maintain, is covered in custom screening software versus a white label platform. Either way, the compliance steps above do not change. Embedding screening into the product experience does not remove the disclosure, authorization, or adverse action requirements, it just changes where the applicant sees them.
| Approach | What it covers | When it runs | Best fit |
|---|---|---|---|
| Pre-onboarding check | Point-in-time criminal, driving, or identity records at the moment of application | Once, before the account activates | Every applicant, regardless of platform size |
| Continuous monitoring | New criminal record activity that occurs after onboarding | Ongoing, between full rescreens | Platforms with long-tenure or high-trust roles |
| Periodic rescreening | A fresh full report, comparable in scope to the original check | On a cadence the platform sets with counsel | Platforms that want a documented refresh cycle |
Frequently Asked Questions
Do gig platforms have to run background checks under the FCRA?
The FCRA does not force any company to run a background check. It regulates what happens when a company chooses to order a consumer report from a consumer reporting agency, requiring a permissible purpose, disclosure, written authorization, and an adverse action process before that report is used against the applicant.
Does the FCRA’s “employment purposes” permissible purpose apply to independent contractors?
Whether a specific working relationship counts as employment for FCRA purposes is a legal question that depends on the facts and current case law, and Reveal does not advise on that classification. Separately, the statute also recognizes a “legitimate business need” permissible purpose for reports connected to a transaction the consumer initiated, which platforms and their counsel should evaluate alongside the employment purposes category.
What disclosure and authorization does a platform need before ordering a report?
A clear, standalone written disclosure that a consumer report may be obtained, provided before the report is pulled, along with the individual’s written authorization to procure it, as set out in 15 U.S.C. 1681b(b)(2).
How often should a platform rescreen active workers?
There is no single federal number. Cadence is a policy choice platforms make with counsel based on risk and the type of work involved, and continuous monitoring is often used to catch new activity between full rescreens rather than waiting for the next scheduled check.
Can screening be embedded directly into a platform’s onboarding flow?
Yes, typically through a direct API integration or a white label arrangement that keeps the platform’s own brand in front of the applicant while the screening runs in the background.
What happens if a platform wants to deactivate a worker based on a report?
Before finalizing that decision, the platform needs to complete the pre-adverse action step, which includes giving the individual a copy of the report and a summary of their rights, followed by a reasonable waiting period and a final adverse action notice if the decision stands.
Featured Image Concept
White background, small-caps kicker “GIG & MARKETPLACE SCREENING” above the title, three simple flat icons in Reveal royal blue (#3c52ff) and deep blue (#0018d7) with pale tint (#eff1ff) accent shapes: a smartphone with a small checkmark badge, a shield outline, and three connected dots representing an API. No photographic people, no stock imagery, no AI-generated faces or hands. All text and icons kept inside the center 870px safe area of a 1200×630 canvas.
Related Reading
This article is general information, not legal advice. Background screening requirements vary by jurisdiction and change over time. Platforms should confirm current obligations, including worker classification questions, with their own counsel before finalizing a screening program.
