Running verification without wrecking the candidate experience

Why this is worth attention

Verification lands at the worst possible moment in a candidate's experience of you. They have accepted an offer, they may have resigned, and the last interaction before they join is a series of requests for documents from a company they have not started working for, about a process nobody has explained.

Two things follow. A candidate who is anxious and uninformed is slow, because they respond cautiously, ask their own questions first, and hold things back. And a candidate who has a bad experience here has it as their last impression of your hiring process and their first impression of your organisation.

The useful part is that the fixes are cheap. Almost everything below is a matter of telling people something you already know, at a moment you were already contacting them.

Eight changes

1. Say what is happening before it happens

One short message at offer stage: which checks will run, why, roughly how long, what you will need from them, and who to contact with a question. That single message removes most of the anxiety in the whole process, and it costs one template.

2. Ask once, and ask for the right things

The most common complaint is being asked for a document, then another, then a clarification of the first. That is a form problem. Capture what the checks will actually need at the start: the employer's legal entity and location rather than a brand name, an employee code if they have one, the awarding university rather than the affiliated college, an address with a landmark and pin code. This is the same fix as the biggest single cause of delay in turnaround, which is not a coincidence.

3. Say how long, honestly

"Two to three weeks, and longer if a former employer is slow to respond" is a better message than a date that will slip. Candidates deal with honest uncertainty far better than with a promise that breaks.

4. Explain the address visit before somebody knocks

An unannounced visit to somebody's home, where a stranger asks their neighbours about them, is the check people find most intrusive. Telling them it will happen and roughly when removes almost all of that. Where the role allows a digital capture instead, offering the choice is worth doing: a good number of people would much rather do it themselves.

5. Never contact a current employer without saying so

This is the one that does real damage. A candidate whose current employer learns they are leaving, because a verification agency called, may lose the job they still have. Be explicit in the consent record about which employers may be contacted and when, and default to verifying current employment after resignation or through EPFO records.

6. Do not charge the candidate. Ever.

Not for the check, not for a copy of the result, not for a correction. The employer who asked for the check pays for it. This is worth stating to candidates directly, because it is a known route for fraud: people are contacted by someone claiming to be a verification agency and asked to pay a fee. Telling candidates in advance that this will never happen protects them and protects your process.

7. Give people a way to ask

A named contact, or a route in the candidate portal, that a candidate can use to ask what is being checked or query something that was found. A candidate who can correct an error in a day is a case that closes; a candidate who cannot reach anybody is a case that stalls and an argument later. The GVS route is on the candidates page.

8. Tell them when it is done

The end of the process is usually silence. One line confirming that verification is complete closes the loop and stops the candidate wondering, on their first morning, whether something is still open.

The hard case: when something is flagged

This is where candidate experience stops being a matter of tone and starts being a matter of fairness.

A flagged finding means two records disagree. As how to read a discrepancy sets out, most of the time the cause is administrative. So the process should assume that first, not last.

• Tell the candidate what was found, specifically. Not "there is a discrepancy in your employment history" but which employer, which field, and what the source said.
• Give a real opportunity to respond, before a decision rather than after it. And give enough time to obtain a document from a former employer, which is not a same-day task.
• Re-check against whatever they provide. A correction should go on the case with the original finding still visible, so the record shows what changed and why.
• If the decision goes against them, say so clearly and promptly. Leaving somebody who has resigned from another job to work out from silence that the offer has gone is the worst outcome in this whole process, and it is entirely avoidable.

At volume, the same rules with fewer assumptions

Everything above assumes a candidate with an email address, a smartphone and a quiet moment to read a message. For blue-collar and volume hiring that assumption fails, and a process built on it produces what looks like uncooperative candidates and is actually an unusable process.

Three adjustments carry most of it. Instructions in the language the candidate actually reads. A submission route that works on a basic phone, over a poor connection, without a printer or a scanner. And a human phone number, because a person who cannot complete a form will call, and if nobody answers, the case stops.

The legal floor, briefly

Most of this piece is about practice rather than law, but the two overlap. Under India's DPDP Act, a candidate has to be given notice of what personal data is being collected and for what purpose, consent has to be informed and specific, data should be kept only as long as the purpose requires, and a candidate can ask what is held about them and ask for a correction.

An employer doing the eight things above is comfortably past that floor, which is a reasonable sign that the floor is set in the right place. The detail is in the DPDP Act and verification.