Most hiring managers have run into the same wall: they call a candidate's prior employer and get name, title, and dates. Nothing else. That pattern took hold because employers got sued, or feared getting sued, for giving real information about former employees. Job reference immunity statutes are the legislative fix. More than 30 states have passed some version of the law, each drawing its own line on what is protected, what isn't, and what a former employee has to prove to overcome the immunity.
What a Reference Immunity Statute Actually Covers The core of every statute is the same: if you give a truthful reference in good faith, you're protected from a defamation lawsuit. Beyond that, the details diverge. Some states only protect written references. Others cover any medium. Some limit protected topics to job performance and qualifications. Others extend to reasons for separation, policy violations, and rehire eligibility.
The immunity is almost never absolute. A former employee can still sue if they can show the information was knowingly false, recklessly communicated, or shared with an intent to harm rather than inform. The practical effect is that truthful information, well documented, is generally safe.
What Does Good Faith Mean in This Context? Good faith usually means you believed the information was accurate, you had a reasonable basis for believing it, and you shared it for a legitimate purpose (answering a reference request). Opinions labeled as opinions tend to hold up. Speculation presented as fact does not.
Why Employers Still Default to Name, Rank, and Dates Even with immunity statutes on the books, most companies stick to minimal references. Three reasons: defending a lawsuit costs money even when you win, the legal team is risk-averse by design, and the immunity's burden of proof is not the same as preventing the case from being filed. An immunity statute helps you win. It doesn't always stop the plaintiff from suing.
The other reason is internal consistency. If you share detailed information for some former employees and refuse for others, that disparity itself can become evidence of bias or retaliation. A clean, uniform policy avoids that trap.
How to Build a Reference Policy That Uses the Statute A useful reference policy does three things. It identifies who is authorized to give references (usually HR, not former managers). It lists what information the company will share and under what conditions. And it requires that every reference be documented, so there's a record of what was actually said.
Before giving a detailed reference, confirm you're in a state with an immunity statute and understand what it covers. Stick to factual claims you can back with documentation: performance review ratings, documented policy violations, attendance records, and the reason for separation as recorded in the letter of termination . Avoid speculation, personality assessments, or anything you haven't documented.
Making Reference Immunity Part of a Defensible HR Process Reference immunity statutes work best when they're part of a broader documentation discipline. The information you share in a reference call should match the information in the employee's file: performance review records, coaching notes, disciplinary actions, and the documented reason for any separation . If the file says the employee was terminated for attendance issues and the reference says the same, the immunity statute protects you. If the file is silent and the reference is harsh, the statute may not save you.
For HR teams, the bigger lesson is that reference quality is downstream of documentation quality. Build the documentation habit, and reference immunity statutes will do what they're designed to do. For state-specific details, check the Department of Labor state labor office directory to identify your state's statute.
.svg)
.svg)
