Most HR teams treat a candidate dispute as a problem the candidate has created. Someone says the report is wrong, the recruiter groans, and the file goes into a pile marked “difficult.”
I want to suggest a different way to look at it. A dispute is the only moment in the whole hiring process when a candidate tells you, for free and in detail, where your verification might have gone wrong. Handled well, it protects a good hire, sharpens your process and keeps you on the right side of the law. Handled badly, it costs you the candidate and sometimes your reputation along with them.
Here is how I think about handling candidate disputes during BGV, with a story first, because it explains the stakes better than a framework can.
The offer that almost didn’t happen
Imagine a candidate I’ll call Farhan. He interviews for an operations role at a fintech company, does well, and accepts a conditional offer. Three days later HR gets his background report. The employment check says he never worked at one of the companies on his resume.
The recruiter’s first instinct is to withdraw the offer. Falsified experience is serious, and the report looks clear enough.
Farhan, meanwhile, is at home reading an email that says his verification “could not be cleared.” He worked at that company for two years. What he doesn’t know is that the firm had been renamed after an acquisition, and the verifier had contacted the old entity’s HR desk, which no longer existed.
If HR had acted on the report alone, a genuine candidate would have been branded a liar over a naming issue. Nobody lied. The system just returned an incomplete answer, and the only thing standing between that answer and a wrong decision was whether anyone would listen to Farhan.
That is the real job of a dispute process. It exists to catch the cases where the data is wrong, and those cases are more common than most teams assume.
Why disputes happen more often than you’d expect
It helps to know the usual sources, because they point to different fixes.
Name and identity mismatches are the most frequent. Spellings vary across documents, initials get expanded or dropped, and common surnames throw up false matches. Company records go stale when businesses merge, rebrand or shut down. Education records may sit with a university that has changed its verification process or is slow to respond. Court and police records can match a candidate to someone else’s case entirely. And sometimes the candidate simply made a mistake on the form, such as a wrong date or the wrong campus name.
Then there are the genuine discrepancies, where the candidate has exaggerated or concealed something. These exist too, and a good process has to handle both kinds without assuming either.
Start before the dispute with a process people can see
Disputes feel hostile mostly because candidates have no idea what to do when something goes wrong. The simplest fix happens at the very beginning.
Tell candidates up front what will be checked, why, and how long it usually takes. Get their consent clearly, in plain language. Under India’s Digital Personal Data Protection Act, 2023 (DPDP), transparency and consent are central to how personal data is handled, so this isn’t only good manners. Your legal team should confirm exactly what applies to your organization, as the rules continue to evolve.
Also tell them at that stage that if something in the report looks wrong, there’s a way to raise it, who to contact and what happens next. A candidate who knows the door exists is far less likely to kick it down.
What to do in the first 48 hours
When a candidate raises a dispute, speed and tone matter more than the technical details.
Acknowledge it quickly. A short message saying “we’ve received your concern and we’re looking into it” lowers the temperature immediately. Silence is where suspicion grows.
Do not make or announce a final decision while the dispute is open. Keep the offer status neutral, and make sure the hiring manager knows not to treat the candidate as rejected. This one rule would have saved Farhan a lot of stress.
Then ask the candidate for what you need. Be specific. “Please share your appointment letter, last three payslips and relieving letter” is far more useful than “please provide proof.” If the candidate has documents, a single clear request gets you moving.
Separate the facts from the finding
Here is a habit I’d encourage every HR team to build. When you read a disputed report, split it into three layers.
The first layer is what the source actually said. The second is how the verification partner interpreted it. The third is what you conclude as an employer. Disputes usually live in the gap between the first and second layers. A source saying “no record found” is very different from a source saying “this person never worked here,” but both can end up summarized as “not verified.”
Ask your verification partner to share the underlying evidence and explain how they reached their finding. A reputable provider will have a re-verification or dispute process and will be willing to walk you through it. If a provider can’t explain how they arrived at a result, that’s a warning sign about the result and about the provider.
Re-verify through a different route
When a finding is contested, repeating the same check the same way usually returns the same answer. Change the path.
If an employment check failed because the company contact was unreachable, try the candidate’s former manager, a colleague, official payroll documents or the current corporate entity that took over. If an education check stalled, ask for the original marksheet and degree and go to the university’s own verification channel. If a court record match is in question, confirm identifiers such as father’s name, date of birth and address history before concluding the case belongs to your candidate.
For criminal and court matches in particular, treat a wrongly attributed case as a serious harm. Linking someone to a crime they didn’t commit can end a career, so this is the area where I’d be most conservative about acting before identity is confirmed.
Judge by role and by materiality
Not every discrepancy deserves the same response. A one-month gap in dates on an old job is not the same as a fabricated degree. A minor difference in a designation is not the same as a concealed criminal case relevant to the position.
Before you need it, define what counts as a material discrepancy for your organization. Think about relevance to the role, severity, how recent it is, and whether the candidate was upfront about it. When a candidate voluntarily discloses an issue during the process, that deserves different weight from something you uncovered that they tried to hide. Write these principles down so decisions don’t depend on who happens to be handling the file.
Give the candidate a real chance to explain
A short conversation can resolve what weeks of emails cannot. Call the candidate, explain what the report shows without accusing, and listen.
Often the explanation is mundane. A name changed after marriage. A company was acquired. A university moved its records. Sometimes the explanation is uncomfortable, and the candidate admits something they’d hoped wouldn’t surface. Either way, you learn more from a fair conversation than from a report alone, and you give the person a chance to respond before an adverse decision is made, which is also the most defensible position if the decision is ever questioned.
Document everything, and keep it proportionate
Keep a clear record of the dispute, including when it was raised, what was requested, what the candidate provided, what the verification partner said and what you decided and why. This protects the candidate as much as it protects you. If a decision is challenged months later, a clean paper trail is worth a great deal.
Keep that information limited to people who need it, stored securely, and retained only as long as there’s a legitimate reason. Candidate disputes often involve sensitive personal details, and they shouldn’t be circulating in a hiring manager’s chat group.
The mistakes I see repeated
Treating the report as the final truth when it’s really evidence. Letting the offer hang in limbo for weeks with no communication. Asking the candidate for “proof” without saying which proof. Handing the decision to the hiring manager, who has a deadline and an interest in closing the role. Applying different standards to different candidates for similar issues. And never feeding disputes back into the process, so the same type of error keeps recurring.
That last one is the biggest missed opportunity. If you keep a simple tally of disputes by cause, you’ll spot patterns quickly. Maybe many of them come from one category of check, one city or one type of employer. Those patterns tell you where to tighten data collection, where to ask better questions on the form and where to push your verification partner for improvement.
When the dispute is a genuine red flag
Sometimes the candidate is wrong. The degree isn’t real, the employment wasn’t what they claimed or a relevant case was concealed. A fair process doesn’t mean ignoring that. It means you reach that conclusion carefully, after the candidate has had a proper opportunity to respond, and you act consistently with how you’d treat anyone else in the same situation.
Withdraw the offer if your policy and the facts support it, communicate it clearly and respectfully, and keep the record. Fairness and firmness aren’t opposites.
What good looks like
The best HR teams I’ve seen treat the dispute process as part of the candidate experience, not a legal afterthought. Candidates remember how they were treated when something went wrong. A person who was heard and cleared will often become a loyal employee and a vocal advocate for your company. A person who was brushed aside will tell their network.
Handling candidate disputes during BGV well comes down to a few habits. Communicate early, stay neutral until the facts are in, look at the evidence behind the finding, re-verify through another route, judge by materiality, let the candidate explain and write it all down.
Farhan, by the way, got his offer. It took four days, one phone call and a copy of an acquisition notice. The company kept a strong hire, and the HR team added a line to their form asking candidates to list former company names. That small change prevented the same dispute from happening again.
Leave a Reply