Franchise Background Check Compliance: What Multi-Unit Hiring Gets Wrong

A franchise brand does not run background checks. Its franchisees do, one per location, using whatever vendor, form, and timeline that unit happened to inherit from a hiring manager who left two years ago. Multiply that across 40 locations, or 400, and the same brand name sits behind dozens of slightly different compliance postures, all governed by the same federal statute. Franchise background check compliance reads like a paperwork detail on a new-franchisee checklist. It is actually one of the fastest-growing sources of employment litigation hitting multi-unit operators right now, and most systems have no idea how uneven their exposure is until a plaintiff's attorney finds the weakest location.

Why one location's habit becomes a franchise-wide exposure

The Fair Credit Reporting Act does not care how many units carry your logo. It applies the same way to a five-location franchisee as it does to a Fortune 500 employer, and it rewards plaintiffs' attorneys for finding repeat violations across related entities. FCRA litigation increased more than 37 percent in 2025 compared to 2024, and the pace kept climbing into 2026: April alone saw 974 new FCRA filings nationally, a 45.3 percent jump over the same month the year before. Franchise systems make an efficient target for that kind of litigation, because a single noncompliant disclosure form, once it gets copied across a dozen locations, becomes a dozen separate violations with a shared paper trail instead of one isolated mistake.

What the FCRA actually requires before you can say no

The law sets a specific sequence, and most violations happen because a location skips a step to move faster. Before running a check, the applicant needs a standalone disclosure (a document that exists only to say a background check will happen, not folded into the general employment application or buried in an offer letter). The applicant then signs a separate written authorization. If the report comes back and changes the hiring decision, the employer owes the applicant a pre-adverse action notice that includes a copy of the report itself and a summary of FCRA rights, followed by a waiting period before any final decision, and then, if the decision holds, a final adverse action notice. Bundling the disclosure into the application form is the single most common violation named in FCRA class actions, because it is also the easiest one to prove in court: the form itself is the evidence.

The state patchwork that turns one policy into fifty

More than 37 states, along with Washington D.C. and over 150 cities and counties, now have some version of a ban-the-box or fair chance hiring law on the books, and more than three-quarters of the U.S. population lives somewhere covered by one. Texas passed its first statewide version in September 2025. The laws are not uniform. Some restrict when a background check can happen relative to a conditional offer, some limit which convictions can be considered and for how long, some require an individualized assessment before rejecting a candidate, and only about a dozen to fifteen states extend the rules to private employers at all, versus public-sector hiring only. Background check laws by state vary enough that no single corporate template survives contact with all of them. A franchise system operating across eight states is not running one hiring sequence. It is running eight, and most systems have never done the location-by-location legal review that would confirm it.

Where the adverse action process actually breaks

The disclosure step gets attention because it happens early and it is easy to standardize. The adverse action step gets skipped because it happens under time pressure, when a location manager has a shift to fill and a candidate whose report came back with something on it. The waiting period between the pre-adverse notice and the final decision (five business days is the commonly recommended floor) exists so the candidate has time to dispute an error in the report before losing the job over it. Skipping that window, or sending a generic rejection instead of the required notice, is where FCRA class actions are won. It is also the step franchise systems audit the least, because it does not live in onboarding paperwork. It lives in whatever a location manager decides to do in the moment.

Choosing a vendor without inheriting more risk than it removes

The consumer reporting agency a location uses matters more than most franchise systems treat it. A CRA's own compliance failures, an outdated disclosure template, a notice process that does not account for state-specific timing, become the franchisee's failures the moment a candidate sues. PeopleFacts settled an FCRA class action for 2.4 million dollars in 2025 over notice timing on negative public record information, and it was the vendor's process, not any individual franchisee's judgment, that created the exposure. Before standardizing on a screening vendor across a network, the questions worth asking are whether the vendor generates state-specific adverse action language automatically, whether its disclosure form has ever been challenged in litigation, and whether it flags individualized-assessment requirements instead of leaving that judgment to whoever is hiring that day.

Fixing franchise background check compliance before the next hire, not after the lawsuit

Employers lose negligent hiring cases roughly 75 to 80 percent of the time they go to trial, and the average settlement runs close to a million dollars, on top of defense costs that climb past 100,000 dollars before a case ever reaches trial. That risk sits on the other side of the ledger from FCRA exposure: skip the screening and risk a negligent hiring claim, run it wrong and risk an FCRA claim. Fixing franchise background check compliance is not a paperwork exercise. It takes one standalone disclosure form built to the strictest state a system operates in, an authorization form kept separate from every other document, an adverse action workflow that cannot skip the waiting period because the step is built into the process instead of left to a manager's judgment, and an annual check that what is written in the policy matches what is actually happening at the location level, since that gap is usually where the exposure lives. Revscale's franchise data layer can already flag which locations are running an outdated hiring template or missing an adverse action step before that gap turns into a claim, which is a cheaper problem to catch than the one that shows up in a demand letter. A few hours of state-by-state legal review costs a franchise system almost nothing. The lawsuit that follows one copied disclosure form costs a great deal more, and it costs it network-wide, not location by location.