Yes, in most cases. You can let someone start work before their background check clears, as long as you make the offer conditional and actually mean it. That's the short answer. The part employers get wrong isn't whether this is allowed. It's what happens if the report comes back with a real problem after the person's already sitting at a desk.
Let's slow down and go through why, because "conditional" is doing a lot of work in that sentence, and a lot of employers treat it like a formality instead of a real legal category.
A conditional offer, sometimes called a provisional or contingent offer, is a real job offer with one honest string attached. You're telling the candidate: the job is yours, but it depends on the background check coming back clean. Not "probably fine." Depends on it.
Two things make that string real instead of decorative. First, you say it in writing, before the person starts, not as a line buried in the handbook they get on day one. Second, you're actually willing to walk it back. If a serious issue shows up on the report and you know deep down you'd keep the person anyway, the offer was never really conditional. It was just an unconditional offer with extra paperwork.
Here's a simple test. Ask yourself: could I actually undo this hire if I had to? If the honest answer is no, don't call it conditional. Call it what it is, and plan around that instead.
Say the report comes back Thursday with something real on it. The person started Monday. Your instinct is probably: it's conditional, I can just end it today, no big deal. That instinct is wrong, and it's the most common mix-up in this whole topic.
Under the Fair Credit Reporting Act, the federal law that governs background checks, you can't turn someone down or let them go because of something on the report without going through adverse action first. That rule doesn't care whether the person has been there three years or three days. It doesn't care whether the offer was conditional. It applies the same way either time.
So to say that again a different way: "conditional" changes whether you can end the job. It doesn't skip the process for how you end it.
The process itself has real steps. You send a pre-adverse action notice, along with a copy of the report and a summary of the person's rights. Then you wait. Most employers hold to something like five business days before finalizing anything, though the law doesn't spell out an exact number, it just requires a reasonable amount of time. Only after that wait, if the person hasn't disputed anything that changes the picture, do you send the final adverse action notice and end things for real.
That part's not optional, and it's not slower just because the person was conditional to begin with.
Picture a five-person office that needed someone to start immediately. They brought someone on, conditional offer signed, background check still running. Four days in, the report lands with an old conviction that's genuinely relevant to the job. The employer wants it handled that afternoon.
Legally, it isn't handled that afternoon. The pre-adverse notice still goes out. The waiting period still runs. The person keeps working, or at least keeps getting paid, while that plays out, unless there's a separate safety reason to remove them sooner. That's awkward. I know it's awkward. It's also the law, and skipping it because the timing is inconvenient is exactly how employers end up on the wrong end of an FCRA lawsuit.
Everything above assumes your role falls under the general rule, where starting early and finishing the check afterward is a choice you're allowed to make. Some jobs don't work that way. A separate licensing or regulatory requirement takes the choice away entirely, and the check has to clear before the person ever starts.
This shows up most often in healthcare, childcare, and some government-adjacent roles, though it depends heavily on the specific position and the state you're in. I'm not going to hand you a fixed list here, because these rules vary by role, by state, and they change. If you're hiring into one of those fields, check the licensing or regulatory requirement for that specific position before you assume the conditional-offer approach even applies to you.
Put the contingency in writing, in plain language, before the person's first day. Not a vague line about "standard onboarding requirements." Say plainly that the offer depends on the background check.
Think hard about what the person touches in those first few days. Client contracts, cash handling, access to sensitive records, anything you couldn't easily undo. If your turnaround is running slow, that's a reason to hold those things back a little longer, not a reason to skip the conditional structure altogether.
And decide your standard ahead of time. What would actually disqualify someone, and how does it relate to the job. Work that out before a report lands on your desk with a real person already three days into the role. Deciding it in the moment, with someone you've already met sitting across from you, is how good employers end up making inconsistent calls. That part's worth getting right before you ever need it.