Company: Quantum Analytics (fictitious), a mid-sized data consulting firm with 800 employees across Mumbai, Bengaluru, and Delhi.
Background:
Quantum Analytics has been searching for a Head of Client Solutions for three months. The role is business-critical—it oversees Rs 200 crore in annual client revenue and manages relationships with the firm’s top 20 accounts. After rigorous interviews across five rounds, the leadership team has finally aligned on one candidate.
The candidate
Rohit Mehra has 12 years of experience, stellar credentials, and impressed everyone he met. His strategic thinking is sharp. His client case studies are compelling. The CEO called him “exactly what we need.” An offer of Rs 45 lakhs has been drafted and is awaiting final approval.
Then the reference check happens.
The situation
HR speaks to Rohit’s former employer—a senior HR leader at his previous firm—off the record. The conversation starts routinely. Then comes the pause.
“Look, I’ll be honest with you because I’d want the same courtesy,” the reference says. “Rohit is talented. Very talented. But he left under a cloud. There was an incident—an allegation of inappropriate behaviour with a female colleague. Nothing was proven. No formal complaint was filed. But there was enough discomfort that we asked him to resign quietly. He did. We gave him a neutral reference letter and moved on.”
The reference emphasises: No FIR. No inquiry. No documentary evidence. Just “enough smoke that we didn’t want to risk the fire.”
Rohit’s version, when he explained his exit during interviews, was different: “Cultural misalignment with new leadership. I wanted a role with more autonomy.”
Now HR is stuck. The offer is drafted. Leadership has signed off. But there’s a shadow—unverified, undocumented, but unsettling.
The dilemma
Should HR withdraw the offer based on informal, off-the-record information that may or may not be true? Or proceed with the hire, knowing there’s a potential risk—but also knowing that rejecting him punishes someone who was never formally accused or given a chance to defend himself?
What’s really at stake
If HR pulls the offer, they may be denying someone a livelihood based on rumour and hearsay—potentially ruining a career over something unproven. If they proceed and something goes wrong later, they’ll be accused of ignoring red flags.
This is a test of how organisations handle ambiguity, fairness, and risk in an era where informal allegations can derail careers—but also where genuine concerns sometimes get dismissed as “he said, she said.”
Either way, there’s no clean answer.
What HR leaders said
Anil Mohanty, Group CHRO, Falcon Group
“Ideally, reference checks—especially for senior and critical roles—should be completed before the offer is issued. An offer is not a casual decision. It involves deliberation, multiple stakeholders, and collective accountability. Rolling it out and then reconsidering based on informal inputs is neither fair nor ethical.
In this case, nothing has been proven. There’s no formal complaint. No inquiry. No documented misconduct. What exists is hearsay. Acting on that would mean allowing gossip to override process.
As a large organisation, decisions like these are never taken by one individual. If multiple leaders agreed to extend the offer, it’s morally incorrect to withdraw it later unless there’s concrete, verified evidence of wrongdoing.
That doesn’t mean ignoring risk. It means managing it responsibly. Observation, close engagement, and adherence to probation or review mechanisms are valid. But punishment without proof is not.
If organisations want to protect themselves, they must invest in discreet, pre-offer background verification for senior hires—through professional agencies, social footprint checks, and structured references. These checks must happen before the offer, not after.
Once the offer is out, pulling it back on unproven allegations is unfair. My position is firm: do your diligence upfront. If you haven’t, then stand by your decision.”
Manish Majumdar, Head–HR, Centum Electronics
“If there’s documentation of an allegation, I’ll consider it. If there’s none, I cannot. That’s the process. Anything else introduces subjectivity and inconsistency.
Yes, there’s a moral dilemma. What if the person actually did something wrong? But there’s an equally important moral question: what if he didn’t? Are we prepared to punish someone for life based on suspicion?
If the previous organisation genuinely believed there was misconduct, due process should have been followed. A complaint should have been filed. An investigation conducted. Records maintained. If, instead, the person was given a clean exit on paper, then it’s deeply unfair to quietly damage his future through off-the-record conversations.
People often leave quietly because fighting allegations—even false ones—can permanently stain their name. That doesn’t make them guilty. At the same time, we cannot assume innocence or guilt without facts.
As a hiring organisation, my responsibility is to act on what is verifiable. Even the law says that in the presence of reasonable doubt, action should not be punitive. Here, doubt is all we have.
If the individual repeats inappropriate behaviour in my organisation, I will act decisively. But until then, rejecting him based on undocumented suspicion would be unjust.
I ask myself a simple question: would I accept this standard if it were applied to me? If the answer is no, then I know what the right decision is.
Fairness lies in consistency. Consistency lies in process. And process demands evidence.”
Ramesh Shankar, Senior HR Leader
“The law of the land is very clear—you are innocent unless proven guilty. Even in a court of law, an allegation by itself does not make someone guilty. Guilt is established only after a formal enquiry and proof. If an organisation has conducted an enquiry and proven misconduct, then of course, the candidate should not be hired. But if there was only an informal enquiry and nothing could be proven, then the individual remains innocent.
In a situation like this, where there is discomfort but no documented evidence, the right approach is not to jump to conclusions but to deepen due diligence. One reference is never enough. HR can and should take two or three additional references from the same organisation—not just through the HR channel, but also from the candidate’s manager, peers, and even juniors.
Equally important is transparency with the candidate. If the candidate has stated that the exit was due to cultural misalignment, then HR should have a direct and honest conversation with him. Tell him clearly that this feedback has emerged and that, to be fair to all sides, further reference checks are required. Ask him to share references—one senior, one peer, and one junior—before concluding the offer.
If the candidate is honest and has nothing to hide, he will be comfortable sharing names and allowing those conversations to happen. If he resists or backs out, that itself becomes an indicator.
I would always give the benefit of doubt to the individual when there is no proven record. At the same time, I would independently validate facts. Fairness does not mean ignoring risk; it means being objective and evidence-driven.
We must also acknowledge reality. In POSH cases, while the intent of the law is to protect women—and rightly so—there are instances where allegations are found to be baseless after enquiry. I have personally seen cases where both parties were at fault, and disciplinary action was taken accordingly, without branding one person guilty forever.
That is why HR decisions must be balanced, humane, and rooted in facts.
Allegations alone cannot become lifetime punishments. Until something is proven, the individual cannot be treated as guilty.”
Your turn
What would you do? Share your response in the comment box or share on LinkedIn with #HRKathaCaseInPoint