Employment verification requests: a workable process for HR teams
Answering these badly creates legal exposure. Answering them all by hand creates a queue. Here is the middle path.
Employment verification requests arrive constantly and belong to nobody. They land in a shared HR inbox, get answered inconsistently, and occasionally get answered in ways that create real exposure. A written process fixes most of that in an afternoon.
Decide what you confirm
The first decision is what your organisation will state, and it should be the same every time regardless of who asks or how they ask.
A defensible default confirms employment dates, the designation held at exit, and the employment status: permanent, contract, intern. That answers the legitimate question behind almost every request.
Things to keep out of a standard reply: salary and compensation, reason for leaving, performance or disciplinary history, and any opinion about the person. If a requester needs those, they need explicit written consent from the former employee, and the answer should come from someone senior rather than the inbox.
Verify who is asking
The step most often skipped. A request from a free email account naming a former employee is not self-evidently legitimate, and confirming employment details to an unverified stranger is a data-protection problem regardless of how routine it feels.
A light check is usually enough: reply to the requester's corporate domain rather than the address that contacted you, or confirm the request against a candidate-signed consent form. Under India's data protection framework, and under GDPR for anyone with European operations, personal data disclosed to a third party needs a lawful basis, and "they asked politely" is not one.
Answer consistently
Use a fixed template so the reply does not vary with whoever happens to be on duty:
- Confirmation of employment, with dates
- Designation at exit
- Employment type
- A statement that no further details are disclosed as policy
The last line matters. It makes a refusal to disclose salary look like policy rather than a judgement about that individual, which is both fairer and safer.
Handle the awkward cases in advance
The person was dismissed. Confirm dates and designation as normal. Do not volunteer the circumstances.
Records predate your systems. Say what you can confirm and what you cannot, plainly. An honest "our records begin in 2019" is better than silence.
The letter presented does not match your records. Do not accuse anyone. State what your records show and let the requester draw conclusions.
The former employee objects. Have a position ready. Confirming basic employment facts is generally defensible; it is still worth having decided beforehand.
Reduce the volume
Process improvements make the queue faster. Removing the queue requires the documents to answer for themselves.
If the experience letters you issue carry a unique reference and a verification URL, requesters check them without contacting you, and the routine majority of this work disappears. What remains, disputes, unusual cases, requests about very old records, is the part that genuinely needs a human, and your team gets their week back to handle it properly.
