What is employment verification?
Employment verification is the process of confirming that a person’s claimed work history is true: that they actually worked where they say they did, during the stated dates, in the stated position. Employers run it before hiring because resumes are self-reported and a meaningful share of them contain embellishments — inflated titles, stretched dates to hide gaps, and occasionally entire invented jobs. Verification protects the employer from a bad hire and protects honest candidates from competing against fiction.
What information is included
A standard employment verification confirms dates of employment, job title or position, and sometimes whether the person is eligible for rehire. Many companies deliberately confirm nothing beyond dates and title, on legal advice. Salary verification is a separate question — in several jurisdictions employers are restricted from asking about salary history at all — and performance information is rarely given in any formal verification, which is why reference conversations exist as a separate, murkier channel.
How the traditional process works — and how long it takes
Traditionally, verification is manual: the hiring company (or a background-check firm it pays) contacts each previous employer by phone or email, waits for HR to find the file, and records the answer. Per employer, this typically takes one to three business days when it goes smoothly; a full multi-employer history commonly takes three to ten business days, and longer when a past employer has closed, merged, outsourced its records, or simply does not answer. Every day of that delay is a day the candidate might accept another offer.
Documents sometimes stand in for the process: pay slips, employment contracts, tax records, or official employment-confirmation letters. These help, but they verify fragments — and they are also the easiest artifacts to forge, which is why serious verification always goes back to the employer as the source.
Why the traditional process fails
- Companies disappear — close, merge, rebrand — and take their memory with them; the employee’s history becomes unconfirmable through no fault of their own.
- HR staff turn over — nobody remembers the person, and the file is a box in an archive.
- Answers are unauditable — a phone note by a recruiter, not a record either side can verify later.
- The employee is excluded — they usually never learn what was said, or that a wrong answer cost them an offer.
The verified-records model
The modern alternative inverts the flow: instead of asking employers to remember years later, verified employers issue factual records at the time events happen — hire date, position, promotions, training, awards — and the employee carries that verified history permanently. Verification then means reading facts issued by confirmed businesses, with the employee’s consent, in minutes. This is the model EmployDB implements: companies are verified before they can issue records, records are factual events rather than opinions, and the employee controls exactly who sees their history. The result answers every failure above — the record survives company closures, does not depend on anyone’s memory, is auditable, and includes the employee in their own verification.