14 September 2026 EN ES
Employment Bench

Workplace law for the people who have to apply it on Monday

Illustration: Before a Background Check Costs Someone a Job
Hiring & Firing

Before a Background Check Costs Someone a Job

A background check is not a simple pass-fail gate. What federal rules actually require before a finding turns into a rejection, and where employers most often skip a step.

A background check comes back with something on it: a decade-old misdemeanor, a gap in employment, a credit blemish that has nothing to do with the job. The easiest move is to quietly pass on the candidate and reach for the next resume. That instinct skips over two separate legal requirements that exist specifically to slow this decision down.

Hiring decisions are among the most important choices for any employer, but the process can be complex — complex enough that the two federal agencies with jurisdiction over it, one covering discrimination and the other covering consumer reports, felt the need to jointly explain the basics rather than leave employers to piece them together from two separate rulebooks.

Permission comes before the report, not after

The first requirement is procedural and easy to get right: employers need written permission from job applicants before getting background reports about them from companies in the business of compiling background information. That is not a box buried in an offer letter or a clause in a handbook someone signed on their first day. It has to happen before the report is pulled, tied specifically to the background check itself, not folded into a general employment agreement covering unrelated topics.

Skipping this step does not just create a compliance gap. It removes the paper trail showing the applicant knew a check was happening at all, which becomes the first thing scrutinized if the hiring decision is ever challenged. This gets messier when a staffing agency or an outside vendor runs the process on the employer's behalf. The obligation does not transfer just because someone else is holding the form; the employer making the final hiring call still has to be able to show that consent was collected properly, on the right form, before any report was pulled. A vendor's own paperwork habits are not a substitute for the employer confirming its own file is complete.

What the results can and cannot be used for

The second requirement governs what happens once the report exists. It is illegal to discriminate based on a person's race, national origin, sex, religion, disability, or age when requesting or using background information for employment. That protection does not disappear just because the information came from a third-party vendor rather than a manager's own judgment; a background check does not launder a decision that would be illegal if made any other way.

In practice, this means the same finding has to be applied consistently across candidates for the same role. A result that quietly disqualifies one applicant but gets waved through for another, for reasons that track a protected characteristic rather than the job itself, is exactly the pattern that turns a routine hiring file into a discrimination complaint.

The applicant does not lose their voice once the report lands

The part of this process employers most often shortcut is what happens after a report leads toward a rejection. When people are turned down for a job or denied a promotion based on information in their background reports, they have the right to review the reports for accuracy. That right exists because background reports are compiled by third parties working from public records and databases that are not always current, complete, or attached to the right person. Mistaken identity on a criminal record is not a rare event; it is a known failure mode of the entire industry.

A hiring process built around that reality looks different from one that treats the report as the final word. It builds in a real pause between the report raising a concern and the offer being withdrawn, long enough for the applicant to actually see what the report says and flag an obvious error before it costs them a job over someone else's history.

What a defensible process actually looks like

None of this requires a legal department on every requisition. It requires three habits, applied the same way every time: get specific written authorization before pulling a report, apply whatever the report turns up consistently across every candidate for the role rather than case by case, and build in a real opportunity for the applicant to see and respond to anything that might sink an offer. Employers who treat those three habits as fixed steps in the process, not judgment calls a hiring manager makes under time pressure, are the ones who are not explaining themselves to a regulator a year later.

Advertisement