Report Types

Employment Verification Checks: What Employers Can and Can't Ask Former Employers

By Dale Whitfield · August 28, 2026

A standard employment verification confirms three things: the dates you worked there, your job title, and sometimes whether the company would rehire you. That's it. It almost never includes your salary, and it almost never includes anyone's opinion of how you did the job.

I spent close to 30 years running these checks. The number of calls I got from a hiring manager asking "why did this come back with basically nothing on it" is more than I can count. Here's what's actually going on, and why a thin answer usually isn't hiding anything.

What employment verification actually checks

Employment verification is narrower than people expect. A verifier, whether that's your screening company or someone calling HR directly, is confirming facts, not gathering opinions. The usual list is dates of employment, job title, and sometimes eligibility for rehire. That's the whole menu at most companies.

Reasons for leaving sometimes get confirmed too, but only in the most generic terms, "resigned" or "terminated," never the story behind it. Anything past that, why someone left, how they performed, whether they'd hire that person again in detail, is usually off the table before the call even starts.

Can employers verify salary history?

Less and less, and that's by design. A growing number of states and cities now restrict employers from even asking a candidate about past salary, and some go further and restrict what a former employer can confirm too.

That list changes state by state, so don't take my word as the final answer for where you're hiring. Check your state's current law or ask a lawyer before you build a policy around it.

Even where it's technically allowed, most companies stopped sharing salary years ago. It's one more piece of information that can only get them in trouble and never really helps them, so a lot of them just dropped it entirely.

Why so many verifications come back thin

Here's the part that actually explains most of what you're seeing. A lot of companies, especially bigger ones, run under what's usually called a neutral reference policy. HR, or a third-party verification service they've hired, will confirm name, dates, and title. Nothing else.

Not performance, not why someone left, not any off-the-cuff comment from a manager who remembers that employee fondly or not.

This isn't the verifier being difficult. It's the company protecting itself. If a former manager tells you an employee was unreliable, and that turns out to be wrong, exaggerated, or impossible to prove, the company can end up defending a defamation claim over one offhand comment.

Saying nothing costs nothing. So a lot of companies decided the safest answer is the shortest one.

That's genuinely useful to know as a hiring manager. A thin verification isn't a red flag on the candidate. It's usually just a policy on the other end of the phone.

Not sure which provider fits your team? Answer a few questions and get matched, free.
Find Your Match

What a full verification confirms versus a neutral reference

What each type of employer response typically includes
DetailStandard/full verificationNeutral reference policy
Dates of employmentYesYes
Job titleYesYes
Eligibility for rehireOften yesRarely, sometimes "no comment"
Reason for leavingSometimes, in general termsNo
SalaryRare, and shrinking by stateNo
Performance opinionAlmost neverNo

Most companies these days sit in that right-hand column. If you're seeing it on every single verification you run, you're not doing anything wrong. That's just how it works now.

How to read a thin verification without overreacting

Don't treat "name, dates, title only" as a warning sign by itself. It's the most common outcome there is, not the exception. Look instead at whether the dates line up with what the candidate told you and whether the title matches what they claimed.

If you genuinely need more than dates and titles, you have a few real options, not just hoping the next call goes better.

  • Ask for eligibility for rehire directly. Some companies will still answer this even under a neutral reference policy, and a flat "no" is worth a follow-up conversation with the candidate.
  • Run a separate reference check. Talk to actual people the candidate worked with, not just the HR department that has to follow a script.
  • Watch for patterns, not one thin answer. One company giving you name-and-dates only is normal. A candidate whose whole work history comes back with unexplained gaps is a different question entirely.

When a gap or mismatch actually matters

A short gap between jobs usually means nothing. People take time off, get laid off and search for a while, or just don't list a seperate short-term gig on their resume.

What's worth a real conversation is a dates mismatch, the candidate says three years, the employer confirms one, or a title that's clearly inflated from what the company confirms.

Ask the candidate about it directly before you assume the worst. A lot of the time there's a simple explanation, a title change nobody updated on paper, or a company that got acquired and renamed mid-employment.

I've seen plenty of good hires almost get passed over for a mismatch that turned out to be nothing more than a merger nobody bothered explaining.