References and what you can legally say in India
Reviewed by Mellow Editorial Team, HR & payroll content team
Giving a reference in India sits in a legal grey area. There is no single statute that tells employers exactly what to say or how to say it — but that does not mean anything goes.
What the law does and does not say
India has no dedicated employment reference law. The closest relevant frameworks are general contract law, defamation law under the Bharatiya Nyaya Sanhita (BNS), and data privacy obligations under the Digital Personal Data Protection Act, 2023 (DPDPA). Labour Code provisions deal mainly with wages, conditions and industrial relations — they do not regulate what a former employer may say about an ex-employee.
The practical result: employers have wide discretion, but they are not immune from liability. A false or malicious statement that damages someone's reputation could ground a defamation claim. Sharing personal data beyond what is necessary could attract scrutiny under the DPDPA.
This article is general information, not legal advice. For specific situations, consult a qualified employment lawyer.
The "confirm only" approach — and why some employers use it
Many large Indian employers have moved to a policy of confirming only dates of employment, job title, and whether the person is eligible for rehire. Nothing more.
This is cautious, not cowardly. It eliminates the risk of a defamation claim, reduces the chance of inconsistent statements across managers, and keeps the company out of personal disputes between an employee and a future employer.
The downside is that it gives hiring managers almost nothing useful. It also means your company receives equally thin references when you are the one hiring.
Whether to go beyond bare confirmation is a policy choice, not a legal requirement. If you do go further, put the policy in writing and train managers on it.
What you can safely say
Truthful, factual statements, made without malice, carry the lowest legal risk. Examples of defensible reference content:
- Verified facts: start date, end date, role held, reporting line, location.
- Objective performance outcomes: "She consistently met her sales targets" or "He managed a team of eight engineers." These are verifiable and specific.
- Reason for leaving, if uncontested: resignation, redundancy, end of contract. Avoid characterising a dismissal unless it is documented and the characterisation is accurate.
- Skills directly observed: concrete examples drawn from the person's actual work are harder to challenge than vague praise or criticism.
The key test is: can you back this up with documentation if challenged? If yes, the statement is defensible. If not, leave it out.
What to avoid saying
Statements that create legal or reputational risk for your company:
- Speculation or inference: "I think she was looking for a way out" or "He probably had performance issues in other areas too."
- Undocumented allegations: do not reference a disciplinary matter, misconduct allegation or performance improvement plan that was never formally completed or that the employee successfully challenged.
- Protected characteristics: caste, religion, gender, disability, pregnancy — mentioning these in any reference context, even neutrally, is inadvisable and could attract claims under anti-discrimination provisions.
- Off-the-record remarks: there is no legal concept of "off the record" in a defamation or DPDPA context. If you say it in a phone call to a recruiter, you said it.
- Retaliation-flavoured language: if an employee raised a grievance, filed a complaint, or was a union representative, any negative reference connected in time to those events could be read as retaliatory.
Handling reference requests in practice
Set a clear internal policy. Decide in advance who is authorised to give references (typically HR, not line managers acting unilaterally), what categories of information you will share, and whether you will provide a written reference at all.
Get consent where possible. Under the DPDPA, sharing personal data about an individual requires a lawful basis. Employee consent is one such basis. When an employee leaves, it is good practice to ask whether they consent to future reference disclosures and what they are comfortable with you sharing.
Respond in writing where you can. A written reference creates a record. A phone call leaves room for misquotation on both sides.
Be consistent. If you provide detailed references for some ex-employees and only bare confirmations for others, the difference in treatment itself can look retaliatory or discriminatory.
Keep a copy. Retain any written reference you issue for a reasonable period. If a dispute arises later, you need to be able to show exactly what you said.
When you receive a reference request about a former employee
If a third party calls asking for details, you are not obliged to respond at all. Confirming that the person worked at your company is generally low-risk. Volunteering unsolicited negative information is where employers most frequently create problems for themselves.
If the former employee has a history of conduct that posed a genuine safety risk — fraud, harassment, data theft — you face a harder judgement call. In such cases, take legal advice before saying anything beyond bare facts.
---
Run HR and payroll in India with Mellow
Mellow brings HR, payroll and 12 AI agents into one platform — built to handle India properly, with payroll included, from £4 per employee per month. The AI agents don't just answer questions; they generate contracts, run cost estimates and draft letters for you.
[Start a free trial →](/register)