Most background checks come back in one to three business days. If yours is dragging past a week, something specific is holding it up, and it's almost never the vendor sitting on it doing nothing. Here are the seven real reasons a check gets stuck, and what's actually happening at each one.
I dealt with this for almost 30 years. Every single time a hiring manager stormed into my office asking why a check was "still not done," it traced back to one of these seven things. Not once was it just the vendor being lazy, even though that's always the first guess.
A lot of people assume a background check company just types a name into a database and gets an instant answer. For a criminal record check tied to an actual county court, that's not how it works. Someone, or some system, has to go ask that specific courthouse for that specific record.
Some counties answer requests same-day. Others take two weeks because they're short-staffed, still processing paper files, or running an older records system that only updates once a day. Your vendor can't rush a courthouse. Nobody can. If your candidate lived in a county with a slow clerk's office, that's the wait, not the company you hired.
Employment and education verification both depend on a human being at another company picking up the phone or answering an email. Most HR departments are not set up to prioritize a verification request from a stranger. It sits in someone's inbox behind actual work.
Small companies are often the worst here, oddly enough, because there's no dedicated HR person handling requests like this at all. A school over summer break, or during finals, is just as bad. If your candidate worked somewhere five years ago and that manager has since left, the request can bounce around for days before it lands with someone who can actually confirm the dates.
If a candidate's legal name changed, goes by a nickname, or was entered slightly differently on the application than on their ID, the system can't confidently say "this record belongs to this person." That kicks the file out for manual review instead of an automatic match.
This happens constantly with maiden names after marriage, hyphenated last names, and names that get typed one way on a job application and a totally different way on a government record. It's not a red flag. It's just a mismatch that needs a person to look at it and confirm, and that person has a stack of other files too.
International checks are slower almost every time, and there's a real reason for it. Every country has its own court system, its own privacy laws, and its own process for releasing records to an outside party. Some countries make this fast. Others require notarized requests, translated documents, or a local partner to physically request the file in person.
If a candidate lived or worked abroad in the last several years, build extra time into your hiring timeline before you even post the job. This one almost never comes back in a week, and no vendor can promise otherwise honestly.
Courthouses don't run on your hiring timeline. They run on their own calendar, and that calendar has fewer open days than most people realize once you add up state holidays, local closures, and the occasional weather day or system outage. A request that lands the day before a three-day weekend just sits there until the office reopens.
December is the worst month for this, no contest. Between the holidays and end-of-year staffing, courthouse response times slow down almost everywhere. If you're hiring in late December, plan on it taking longer than it would in March.
This is the one most within your control, and its also the one I saw most often as the actual cause. A missing middle initial, a wrong former address, an old employer's phone number that's disconnected, any of these can stall a check before it even really starts.
Verification staff can't guess. If they can't confirm who they're looking for or how to reach a past employer, the file waits until someone tracks down the missing piece, sometimes by going back to the candidate directly. A clean, complete form at the start saves more time than picking the fastest-sounding vendor.
Background check companies get hit with real seasonal surges, same as any other business with a line out the door. Retail and hospitality hiring spikes before the holidays. Seasonal warehouse work does too. Colleges hiring for a new semester create their own wave. When volume jumps everywhere at once, even a good vendor's average turnaround creeps up, because the same staff is now processing alot more files.
This isn't an excuse for a bad vendor. But it does mean the exact same check that took two days in February might take four in November. That's demand, not decline in quality.
Fill out the form completely and accurately before you submit it. That single habit fixes more delays than switching vendors ever will. Ask your provider up front which counties or countries tend to run slow, and build a little buffer into your timeline for anyone with an international or out-of-county history.
And if a check has been stuck for more than a few days with no update, ask your vendor exactly which of these seven things is the holdup. A provider that can't tell you why it's delayed is a bigger problem than the delay itself.
One thing worth saying plainly: a slow check by itself usually isn't a compliance issue, it's a logistics one. But if you're ever tempted to make a hiring decision before a check comes back, or to treat a delay as a reason to reject someone, talk to a lawyer first. That's a different kind of risk than a slow courthouse.
If you're comparing providers and turnaround time matters to you, that's a fair thing to ask about before you sign anything, not after your first check gets stuck.