What You Can Safely Say When Another Employer Calls for a Reference

Your phone rings on a Tuesday afternoon. It is a hiring manager at another company, and she wants to know about someone who used to work for you — someone you fired. "Just a few quick questions," she says. "Would you rehire him? Why did he leave? Was there anything… we should know about?"

Every sentence you say next is a legal decision. Say too much, and you could hand a disgruntled former employee the raw material for a defamation claim. Say too little, or the wrong kind of nothing, and you can create a different problem entirely. Yet most small-business owners handle these calls with no policy, no notes, and a vague memory of something they once heard about only confirming dates of employment.

Here is what the law actually says: honest, factual references are far better protected than the folklore suggests — if you follow the rules. And your answer carries real weight. In one staffing-industry survey, managers removed about one in three candidates from consideration after checking references, and the vast majority of employers still check them. This guide explains what you can safely disclose, what to never say, the two traps most small businesses miss, and the one-page policy that keeps a routine reference call from becoming a legal headache.

The Three Legal Shields That Protect Honest References​

When owners worry about reference calls, they usually imagine a lawsuit they cannot win. In practice, an employer giving a truthful reference starts with three layers of protection. Understanding them is what lets you speak confidently instead of hiding behind "we only confirm dates."

1. Truth Is an Absolute Defense​

Defamation means a false statement of fact that harms someone's reputation. The key word is false. If what you say is true — and you can prove it from your records — a defamation claim fails at the threshold, no matter how much the former employee dislikes hearing it. "He was late 14 times in his last two months, received two written warnings, and was terminated for attendance" is not defamation if your timecards and warning memos back up every clause. "He was lazy and probably stealing" is an opinion wrapped around an accusation, backed by nothing, and it is exactly the kind of sentence that gets employers sued.

The practical consequence: your protection is only as good as your documentation. A reference should be a readout of the personnel file, not a memoir of your feelings.

2. Qualified Privilege for Good-Faith References​

Beyond truth, the common law in nearly every state recognizes a qualified (sometimes called conditional) privilege for employment references. The idea is straightforward: when you share job-related information in good faith with someone who has a legitimate reason to receive it — like a prospective employer making a hiring decision — the law protects you even if some detail turns out to be wrong.

But qualified means conditional, and employers lose it the same handful of ways every time:

• Knowing falsity or reckless disregard. Saying something you know is untrue, or repeating a rumor you never bothered to verify, destroys the privilege.
• Malice and spite. A reference motivated by a desire to punish the former employee — exaggerated language, volunteered dirt nobody asked about, a tone better suited to a grievance than a hiring decision — looks like malice to a court.
• Telling the wrong audience. The privilege covers the hiring decision-maker with a need to know, not your neighbor, your vendor, or a group chat. Keep the circle tight.
• Volunteering what nobody asked. Answer the questions you are asked with documented facts. Editorial asides and unsolicited warnings are where privilege goes to die.

Notice the pattern: every way of losing the privilege involves departing from calm, documented facts. Stick to the file and you keep the shield.

3. State Job-Reference Immunity Statutes​

On top of the common law, most states have enacted statutes that specifically immunize employers who give truthful references. The details vary, but the shape is consistent: you are immune from civil liability unless the former employee proves you disclosed information you knew was false, acted with reckless disregard for the truth, or acted in bad faith.

A few examples show the range:

• Florida sets one of the highest bars for lawsuits: a former employee must prove by clear and convincing evidence that the employer knowingly disclosed false information.
• South Carolina grants immunity for disclosing evaluations, separation reasons, and job performance, and withdraws it only where the employer knowingly or recklessly discloses false information.
• Kansas goes further for written references, giving employers absolute immunity when they respond in writing to a written request with evaluations the employee already had access to.

Know your state's version — the policy section below routes every reference through one trained person for exactly this reason. But the core bargain is the same everywhere: tell the documented truth in good faith, and the law is on your side.

What You Can Safely Disclose​

Here is the safe list — facts a former employer can routinely share when they are accurate and documented:

• Dates of employment and job title. The universal baseline. Confirm start and end dates, final title, and full-time or part-time status.
• Job duties. A brief description of what the person actually did, drawn from the job description on file.
• Pay level and wage history — with a caveat. Historically routine, but read the salary-history section below before volunteering a single number.
• Reason for separation. Voluntary resignation, layoff, or termination — stated plainly, matching the separation memo in the file. "Position eliminated in a reduction in force" and "terminated for violation of the attendance policy after two written warnings" are both safe when the paperwork agrees.
• Documented performance facts. Attendance records, sales numbers, completed reviews, written warnings, promotions. Numbers and filed documents, not adjectives.
• Eligibility for rehire. Safe when it reflects a genuine, consistently applied standard — make sure "not eligible" designations are themselves documented and consistent, because an unexplained outlier invites questions.

The golden rule covering all six: if it is not in the personnel file, do not say it. The file is your script. Anything you remember but never wrote down is a memory, and memories make terrible witnesses.

What to Never Say​

Keep these out of every reference, every time:

• Opinions dressed as facts. "Difficult to work with," "bad attitude," "not a team player" — subjective judgments with no paper trail. If the underlying behavior was documented (a warning for refusing a schedule change, say), cite the document, not your conclusion.
• Unproven accusations. Never label someone dishonest, impaired, violent, or criminal. An arrest is not a conviction and an allegation is not a finding — repeating either as fact can be defamation if it is wrong.
• Anything about protected characteristics. Race, religion, national origin, sex, pregnancy, age, disability, genetic information — none of it belongs in a reference. Neither do medical details, disability accommodations, or workers' compensation history.
• Speculation and gossip. Why you think someone really left, what you heard from a coworker, what "everybody knows." If you cannot point to a document, it stays unsaid.
• Off-the-record anything. There is no such thing as off the record in a reference call. Anything you say can be repeated, misquoted, and attributed to you. If you would not put it in a letter on company stationery, do not say it on the phone.
• Retaliatory commentary. If the former employee filed a complaint, a charge, or a claim against you, the reference is not the place to settle it. A suddenly negative reference after protected activity looks like retaliation, which is a separate and often larger liability than defamation.

The Salary-History Caveat: Do Not Volunteer Pay Numbers​

Pay disclosure deserves its own warning because the rules changed under many employers' feet. A growing list of states and cities now ban employers from seeking or relying on an applicant's pay history, and some restrict the former employer from disclosing it at all. San Francisco, for example, bars employers from disclosing a current or former employee's salary history without the employee's authorization. Virginia joined the list in 2026, prohibiting employers from seeking or relying on wage history when hiring or setting pay, effective July 1.

The safe practice regardless of your state: do not volunteer pay figures. If a prospective employer asks, confirm compensation only with the former employee's written consent, and check whether your state or city restricts even that. "We don't disclose compensation details as a matter of policy" is a complete answer, and nobody has ever been sued for saying it.

The Two Traps Most Small Businesses Miss​

Most owners worry about saying too much. The traps below run the other direction — and the second one makes silence itself a violation.

Trap 1: The Glowing Reference That Hides Misconduct​

Trying to "be nice" by writing a warm recommendation for someone you fired for serious misconduct feels harmless. Courts in several states have treated it as anything but: an employer that gives a misleadingly positive recommendation while concealing misconduct it knew about — violence, harassment, theft — can face liability when the person repeats the behavior at the new job. The theory is sometimes called negligent referral or negligent misrepresentation: you did not have to say anything, but having chosen to speak, you had a duty not to mislead.

You do not need to become an alarmist. You need to stop sugarcoating. A neutral, factual reference — dates, title, duties, documented separation reason — neither inflames nor misleads. What creates exposure is the letter of praise that contradicts the termination memo sitting in your own file. Honesty protects you in both directions.

Trap 2: States That Require You to Put It in Writing​

A handful of states flip the script with service-letter laws: when a departing employee asks in writing, you must provide a letter describing their service. Missouri's is the best known. Employers with seven or more employees must respond within 45 days of a former employee's written request, stating the nature and character of the service, its duration, and the true reason for the discharge or quit. An employer that simply fails to issue the letter can owe nominal and punitive damages — liability for silence, not for speech.

A few other states have narrower variants. The takeaway: know whether your state has one of these laws before adopting a "we never put anything in writing" stance — in a service-letter state, that stance is the violation.

The Written-Consent Habit That Changes Everything​

The single highest-leverage habit in this whole area is getting the former employee's written authorization before you say anything substantive. Consent is a freestanding defense to defamation in most states: a person who authorized the disclosure has a much harder time suing over it. Many employers pair the authorization with a release of liability for good-faith, truthful statements.

Put it in practice two ways:

1. At separation. Include a short reference authorization in your separation paperwork: the employee authorizes the company to disclose employment information to prospective employers and releases the company from liability for truthful, good-faith statements. File the signed copy with the personnel records.
2. At the reference request. If you have no signed authorization on file, ask the inquiring employer to have the candidate sign one — or send your one-paragraph form directly to the former employee. A two-day delay beats an unprotected disclosure.

Two companion habits multiply the protection. Respond in writing whenever you can: a short letter or email creates an exact record of what you said. And log every reference: who asked, when, what you disclosed, and where the consent is filed. The log lives with the personnel records and turns "what did you tell them?" into a one-minute lookup.

A One-Page Reference Policy for a Small Business​

You do not need an HR department to do this right. You need one page, consistently followed:

• One designated responder. All reference requests go to the same trained person — the owner, an office manager, or whoever holds the personnel files. Nobody else answers, elaborates, or "just chats" with the caller.
• Route, don't freelance. Train every supervisor to say: "All reference requests go through [name] at [contact]." Callers who hit a careful front door try the side window — hiring managers routinely contact former supervisors directly to get around neutral policies, and one ad-libbed "personal opinion" can create the exact liability your policy was built to prevent.
• Use the script. Confirm the safe-list facts from the file, state the documented separation reason, answer the rehire question per company policy, and stop. Same questions, same answers, every caller.
• Written consent first, written response preferred. No substantive reference without a signed authorization on file; written answers over phone calls whenever the inquirer will accept them.
• Log everything. Date, requester, candidate, what was disclosed, where the consent is filed.
• Annual check. Once a year, confirm your state's immunity statute and any service-letter or pay-disclosure rules still say what you think they say. Employment law moves — Virginia's 2026 pay-history ban is a reminder that last year's compliant script may need this year's edit.

Print it, date it, follow it. A written policy you actually follow is itself evidence of good faith.

Keep the Records That Make References Easy​

Notice what every section above depends on: records. Dates of employment, titles, and pay live in your payroll system. Warnings, reviews, and separation memos live in the personnel file. The reference call is just a readout — the real work happened months earlier, when someone documented the warning, filed the review, and recorded the separation reason accurately.

That is a bookkeeping discipline wearing an HR costume. Businesses with clean, contemporaneous records answer reference calls in five minutes from the file; businesses without them answer from memory, and memory is where defamation claims come from. Document performance issues when they happen, record separation reasons before the exit interview fades, and keep payroll records that make dates and titles a lookup instead of a guess. If your personnel paperwork is scattered across email threads and sticky notes, the reference policy above will fail at its first test — not because the policy is wrong, but because there is no file to read from.

Keep Your Employment Records as Organized as Your Books​

Every safe reference starts with records you can trust — and the same is true of every financial decision you make. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data, version-controlled and AI-ready. Get started for free and bring the same discipline to your books that keeps your references safe.