Every Reference Call Is a Deposition Waiting to Happen: A Manager's Protocol for What Gets Said After the Paycheck Stops

A reference call lasts six minutes. The transcript of it can last for years.

Managers tend to treat employment verifications as a courtesy rather than a legal act. The caller sounds reasonable, the questions are routine, and the conversation feels like professional small talk. It is not. It is the creation of a spoken record, made by a representative of the company, about a named individual, delivered to a stranger who may later repeat it, transcribe it, or swear to it in a declaration.

Two kinds of exposure, one phone call

Defamation is the claim most employers recognize. To be actionable, a statement generally must be a false statement of fact rather than opinion, published to a third party, and harmful to the subject's reputation. Employers typically defend these claims with a qualified privilege for communications made in good faith to a party with a common interest in the information. That privilege is narrower than it sounds. It is generally lost when the speaker knows the statement is false, speaks with reckless disregard for whether it is true, or volunteers information beyond what the occasion requires. A manager who says, "I probably shouldn't say this, but you should know," has usually just surrendered the privilege in the first clause of the sentence.

Negligent referral is the mirror-image claim, and it is the reason "we never discuss former employees" is not a complete answer. In settings where an employee's conduct presents a foreseeable risk to others, courts in several jurisdictions have allowed claims that an employer knew of a dangerous or unfit employee and stayed silent when a prospective employer asked. Employers in caregiving, security, transportation, and education have faced such claims. The pressure to disclose and the pressure to stay quiet pull in opposite directions, and neither impulse is a policy.

Retaliation is the quietest risk. A conspicuously negative reference given after an EEOC charge, a wage complaint, an OSHA report, or a stretch of protected medical leave creates an inference that a factfinder will notice. Timing and content together can convert a routine verification into evidence.

And if a third-party screener conducts the check, federal obligations under the Fair Credit Reporting Act attach to the process: a standalone disclosure, written authorization, a pre-adverse action notice with a copy of the report and a summary of rights, and a later adverse action notice. Outsourcing the call does not outsource the exposure.

The state line is not one line

Reference immunity statutes vary considerably. Some states provide a conditional privilege or immunity for truthful, good-faith disclosures by former employers. Others limit the protection to specific categories, such as dates of employment, job title, and whether the employee is eligible for rehire. Some statutes condition protection on the employer responding to a written request. Others require that the information be documented in the employee's personnel file. A few states are notably silent on the subject.

For a multistate employer, this means a reference matrix maintained by counsel and reviewed on a schedule, not a single national rule recited in a training deck. The matrix should identify, for each state where the company has employees, what may be disclosed, what must be documented, whether a written release is required, and where the statutes are unsettled.

Centralize the voice

Only one function should speak: human resources, or a designated records custodian within it. Managers should be instructed to route every reference inquiry to that function and to say nothing substantive in the interim, including a warm endorsement or a sympathetic sigh.

The reasons are practical. A centralized voice produces consistency, which matters if the company is later asked why one departing employee received a glowing verification and another received a halting one. It produces a log, which is the only contemporaneous evidence that a call happened and what was said. It preserves the company's ability to apply a policy rather than a personality. And it keeps managers from volunteering judgments that no one authorized them to give.

What the script should accomplish

A workable script does five things in order:

• Authenticate the caller. Confirm name, organization, role, and the subject of the inquiry. Verify that the candidate has authorized contact if company policy or state law requires it.
• State the policy in neutral terms. Not an apology, not a hedge, not a preamble about how much the company values privacy. A plain statement of what the company verifies.
• Confirm only what is documented. Dates of employment, job title, and, where policy permits, eligibility for rehire. Nothing that cannot be supported by a record.
• Decline narrative commentary. No adjectives. No speculation. No characterizations. No "off the record."
• Log the call. Date, caller, organization, information provided, and any request that was declined.

A usable opening sounds like this:

"Thank you for calling. I can confirm dates of employment, job title, and eligibility for rehire if our records support it. I'm not able to provide narrative commentary on performance. If you'd like, I'll confirm what I can now and follow up in writing."

What to avoid is equally important. "He was difficult." "You don't want her on your team." "I can't say anything, but you can read between the lines." Each is a statement, and the last is a statement with an audience eager to interpret it.

The substantiation standard

Before any manager speaks about a former employee, the question should be: could this sentence be handed to a judge with a document attached? If the answer is no, the sentence should not be spoken.

The supporting file typically includes the personnel file, dated performance documentation, disciplinary records with signed acknowledgments, exit interview notes limited to observable conduct, and the rehire eligibility designation with its stated basis. A conclusion such as "not eligible for rehire" is defensible only if the record explains why.

When the request is 'dates and titles only'

A verification limited to dates and titles is often the safest response, and it is the right default for most employers. Two cautions apply. First, some state statutes condition immunity on the employer providing certain information, so a blanket refusal may forfeit protection the employer assumed it had. Second, tone carries meaning. An abrupt "we don't discuss employees" can convey more than a neutral policy statement.

The better phrasing is procedural rather than personal: "Our policy is to verify dates of employment and title only. I can confirm those now." If pressed for more, repeat the policy without commentary and note the request in the log.

A model policy sentence

The company verifies dates of employment, job title, and eligibility for rehire, and provides no narrative commentary on performance or conduct. All inquiries are directed to Human Resources and documented.

That sentence, applied consistently, is worth more than a page of warnings.

When to involve counsel

Escalate before responding when the subject of the inquiry has a pending charge or complaint, when a litigation hold is in place, when the file contains an allegation of violence or harassment, when the role is executive or public-facing, or when the prospective employer requests a narrative. These are the calls where a script is not enough and silence is not an option.

The reference call is not a courtesy. It is a statement made on the record by the company, and it should be treated with the same discipline as any other document the company signs.