Employment Verification

A candidate lists three years at a particular company, and the hiring team wants to confirm dates and role before a final decision, so a verification request can ask the prior employer or an authorised data provider for those facts. Decide what needs checking, because confirming an employment period is different from asking why someone left or how their manager rated them, and gather only information relevant to the decision.

Identify the requester too, since a new employer, lender or landlord may seek different facts under different rules, and the person or organisation responding must know who is asking and on what basis. Check the current legal route, because notice, authorisation, lawful basis and disclosure rules vary by jurisdiction and by how the information is obtained, and no single universal consent form fits all checks.

The UK Information Commissioner's Office discusses necessity and proportionality in pre-employment vetting, and its relevant guidance is under review, so check current UK requirements before relying on operational detail. In the United States, the FTC explains additional duties when an employer obtains a consumer report through a background-check company, and those federal rules do not automatically cover every direct call to a previous employer.

Use verified contact channels, since a phone number supplied on a resume may be a helpful lead but should not be the sole proof that the respondent represents the named employer. Confirm identity before disclosing records, because several people can share a name, and use appropriate identifiers without sending unnecessary personal data to a stranger.

Specify the facts requested, as a narrow form for dates and title is easier to answer and less likely to collect irrelevant comments, and do not ask for protected or sensitive information without a lawful reason. A past employer may have a policy of confirming only dates, and that limited answer is not evidence of poor performance, since some employers use specialist verification services instead.

Handle differences carefully, because a title may change internally, an employer may rebrand, and payroll dates can differ from work dates, so ask for clarification before treating a mismatch as dishonesty. If a candidate says a current employer must not be contacted, respect the stated restriction while considering lawful alternative evidence, since a premature call can reveal a job search.

Keep the result in context: a confirmed title does not prove all listed responsibilities, and an unconfirmed record is not necessarily false, so record exactly what source answered. An illustrative verification completion rate is records with a completed response divided by records requested, so if 18 of 20 checks return, completion is 90%, which does not say the remaining two claims are inaccurate.

Protect the response, because employment history and pay data can be sensitive, by storing only what is needed, limiting access and using the applicable retention period. For incoming requests, set a company process in which HR or another authorised team verifies the requester, scope and former worker identity, so that individual managers do not improvise broad disclosures.

Record the method, noting whether the response came from HR, payroll data or an unverified person, and consider disputes and corrections because an automated database can be out of date. Offer a correction route so a person can challenge a report that attributes another person's work history or lists wrong dates, use consistent criteria across similar roles because selective checks can create unfair treatment, and train staff on phishing risk, since a request claiming to be from a bank or future employer can be an attempt to collect private data; for owners, employment verification is a focused fact check whose quality rests on the right source, proportionate scope and fair treatment of discrepancies.