Résumé verification vs. background check: what each one covers

What a background check answers

A background check pulls from records that someone else already keeps. The joint FTC and EEOC guidance describes the material employers use as a person's work history, education, criminal record, financial history, medical history or use of social media. In practice a hiring-stage check confirms that the person is who they say they are, that the employers on the résumé employed them, that the dates and job titles on file match, and that the criminal or licensing record contains what the role requires it to contain.

Those answers are binary and they come from a custodian: a court, a registrar, a payroll database, an employer's HR department. That is the source of both their strength and their limit.

What it cannot see

Employment records hold a title and a date range. They do not hold scope. Nothing in a verified record distinguishes the engineer who rebuilt the payments system from the engineer who sat next to them, or the director of a four-person function from the director of a hundred-person one. Outcomes are invisible for the same reason — a former employer confirming dates is not going to attest that checkout latency fell forty percent.

So a candidate can pass every element of a background check and still have a résumé that reads two levels above what they did. The record confirmed the frame; nobody checked the picture inside it.

What verification adds

Résumé verification takes the specific claims — the team of ten, the rebuild, the percentage, the "core contributor" — and looks for public evidence of them: launch posts, org and product pages, conference programs, repositories, archived pages, press coverage. The output is not pass or fail. It is the wording the evidence supports, next to the wording the candidate used, with the difference visible to whoever makes the decision.

It is also weaker evidence, and should be treated that way. Public sources are incomplete and sometimes wrong, and a claim with no public trace is unverified rather than untrue.

Both can be consumer reports

The legal test does not turn on which of the two you call it. Under federal law, if a third party assembles information on a candidate for employment purposes, the result is generally a consumer report, whether it is a criminal record search or a summary of what public sources say about a project. That brings disclosure, authorization, the pre-adverse action notice and the dispute window with it, as set out in what the FCRA requires when a claim fails.

Which one you need

Use a background check when the risk is identity, a disqualifying record, or a job that did not exist. Use verification when the risk is a job that existed at a different size than the one described — which, for senior hires, is the more common way a hiring decision goes wrong. If you need both, the background check normally belongs late in the process, after an offer, where its cost and its consent requirements are proportionate; verification belongs early, while it can still change the shortlist. Run each consistently across candidates for the same role; applying either one selectively is how a defensible process stops being defensible.