How to verify employment history, and how long each route takes

Verifying employment history is simple to describe and tedious to do. You are confirming three facts with a former employer: that the person worked there, between which dates, in what role.

There are four routes to those facts. Most teams only know about two of them, and pick the slow one by default.

Route 1: call the employer directly

Find the company’s main line, ask for HR, and ask them to confirm employment.

When it works: small and mid-sized employers, where HR is a person rather than a department. You can often get dates and title in a single call.

What it costs you: anywhere from ten minutes to a week, depending entirely on whether anyone picks up. The failure mode is not refusal, it is voicemail. You leave a message, they call back while you are on another call, and the thing quietly dies.

Worth knowing: many companies now have a policy of confirming nothing beyond dates and title. That is not obstruction, it is legal caution about defamation exposure, and it has become the norm. Do not read it as a signal about the candidate.

Route 2: the employer’s verification portal

Larger employers route verification requests to a web form or a self-service portal instead of a person.

When it works: enterprise employers, healthcare systems, universities, government. If the company is big, a portal almost certainly exists.

What it costs you: minutes if you know the URL, an afternoon if you do not. The work is in finding the right portal and getting through whatever it asks for, which is often the candidate’s consent, sometimes their employee ID, and occasionally a fee.

Worth knowing: portals are the reason verification feels inconsistent. Every employer’s is different, and there is no directory of them. This is exactly the kind of work that a person has to redo from scratch for every single candidate.

Route 3: a paid verification service

A large share of US employment records are held by commercial verification services that employers pay to handle these requests on their behalf. You query the service rather than the employer.

When it works: large employers who have outsourced it. If you hit a company that uses one, this is the only route they will accept.

What it costs you: a fee per verification, and a subscription or account to query at all. It is fast when the record exists, and useless when it does not, which is common for smaller employers who never enrolled.

Worth knowing: coverage is the whole question. These services are excellent for large-employer histories and thin for exactly the kind of small-business work history that hourly candidates tend to have.

Route 4: ask the candidate for records

Pay stubs, a W-2, an offer letter, a separation letter.

When it works: as a fallback when the employer is gone, will not respond, or never existed in a form anyone can query. Also common for very recent work, where the employer’s systems have not caught up.

What it costs you: almost nothing in your time, and something in candidate goodwill. Asking someone to produce documents reads as distrust unless you explain why.

Worth knowing: documents confirm that a document exists. They are weaker evidence than an employer confirmation, and you should treat them that way rather than as an equivalent.

The part that actually takes the time

None of these four routes is hard. What takes the week is that a person has to work all four, in order, for every candidate, and remember to follow up on each one.

You call, you get voicemail, you make a note to try again. You find a portal, it wants consent you have not collected, you email the candidate and wait. You get a “we use a service” reply and have to start over somewhere else. Each step is five minutes and two days.

That is the real cost, and it is why verification is the step most quietly dropped on candidates a team already feels good about.

What good looks like

If you are doing this by hand, three things help more than anything else.

Collect consent up front, at offer stage, in the same place you collect everything else. Most of the delay in verification is not the employer, it is going back to the candidate for an authorisation you could have had already.

Record the route, not just the result. “Verified” is not useful six months later. “Confirmed by HR on 4 March, dates and title only” is, especially if the hire goes sideways.

Decide in advance what a non-response means. If an employer never answers, is that a stop or a shrug? Teams that have not decided end up deciding case by case, which means deciding based on how much they like the candidate.

Where this is going

Every one of these routes is a machine-shaped task: find the channel this employer uses, work it, follow up until it resolves. It is repetitive, it is different for every employer, and it does not need judgment. It needs persistence.

That is what we are building toward: an agent that works the browser, the text thread and the phone line until the verification is actually complete, rather than until someone ran out of afternoon.

---

Employment verification is in development. The waitlist is how we decide how fast to build it, so tell us how you handle it today.