Employer to Employee Recommendation Letter

A large share of US employers operate what HR functions call a neutral-reference policy: in response to a reference request, the company will confirm only dates of employment, position held, and (sometimes) eligibility for rehire. The policy is risk management. After several large defamation settlements in the 1980s and 1990s involving negative employment references that turned out to be partly inaccurate, most Fortune 500 HR departments concluded that the cheapest defensible posture is to say almost nothing. The Society for Human Resource Management has documented the prevalence of this policy in successive surveys.

The neutral-reference policy does not prohibit individual managers from writing personal references. It restricts what HR (acting on behalf of the company) will say in an institutional capacity. Many managers write personal references for direct reports they would recommend; the practice is widespread and generally tolerated by employers, with the proviso that the letter is written in personal capacity and is not represented as the company's institutional position.

The structural consequence is two layers of reference signal for any given employee. The HR call will confirm employment dates and not much else. The personal letter from the direct manager will add the substantive performance evidence. The hiring decision-maker reads both. Candidates who can produce a strong manager letter and pass an HR confirmation call are well-positioned; candidates whose former manager declines to write personally signal something the HR confirmation will not capture.

Defamation under US common law requires a false statement of fact, communicated to a third party, that damages the subject's reputation. Truth is an absolute defence in every US state. The doctrine of qualified privilege further protects reference writers: statements made in good faith, without malice, to a party with a legitimate interest in receiving them (a prospective employer counts) are protected from defamation liability even if they later turn out to be inaccurate, provided the writer did not know they were false and did not make them with reckless disregard for the truth.

Several states have codified reference-giver protection by statute, going further than the common-law privilege. California Civil Code section 47 provides a privilege for communications made without malice to interested parties. Texas Labor Code section 52.031 grants employers immunity for truthful job-reference disclosures. Florida statute 768.095 and Colorado statute 8-2-114 are similar. Together, the doctrinal protection for truthful, good-faith references is robust across US jurisdictions.

The risk that remains: a reference grounded in personal animus, a reference that contains demonstrably false factual claims the writer should have checked, a reference that retaliates for protected activity (filing an EEOC charge, taking FMLA leave, organising a union), or a reference that violates a settlement agreement with a non-disparagement clause. The first three open the door to defamation, retaliation, and (in California specifically) blacklisting claims; the fourth opens the door to breach-of-contract liability. The template below stays well inside the safe zone.

A practical decomposition. Anything in the personnel file (signed performance reviews, formal goals and ratings, documented commendations and disciplinary actions, project deliverables and outcomes) is fair game for the manager to reference, because it is substantiated by company records and the company itself relied on the same evidence when making employment decisions. Anything the manager believes to be true but cannot point to a document for is opinion, and should be labeled as such in the letter.

The distinction matters because the qualified-privilege defence requires the writer to be acting in good faith. A statement grounded in documentary evidence is presumptively in good faith. A statement that is pure opinion, labeled as opinion, is generally protected as opinion (which is not a statement of fact and therefore not defamatory). A statement that asserts an unverifiable fact (\"I believe she was responsible for the security breach\") is the dangerous category: it sounds factual, the writer cannot prove it, and it is the species of statement that has historically generated reference-related litigation.

For the writer, the rule of thumb: if a statement could be checked against the personnel file, check it before writing it. If a statement cannot be checked, label it as opinion or as personal observation. If a statement is negative and material, consider whether to include it at all; declining to write is often the safer course. See the dedicated how to decline a recommendation and defamation risk pages for the longer treatment.

The opening paragraph of the template above contains the personal-capacity disclaimer that in-house counsel typically recommend: a brief statement that the observations reflect the writer's personal experience and do not represent the institutional position of the employer. The disclaimer is short, neutral, and accomplishes two things. First, it separates the writer's individual speech from the company's institutional speech, which is the legal frame that triggers personal qualified privilege rather than corporate liability exposure. Second, it signals to the reader that the company is operating a neutral-reference policy and that the manager has chosen to write personally, which is itself a credible signal because the manager would not have written personally for a candidate they did not strongly endorse.

For employees of larger US companies, the disclaimer also matters because it protects the manager from internal discipline. If the manager wrote on company letterhead and represented the letter as the company's position, the manager might be in breach of the employee handbook's reference policy. The personal-capacity disclaimer makes clear the manager is acting as an individual, which most policies permit and most companies tolerate.

For smaller employers without a formal neutral-reference policy, the disclaimer is less critical but still good hygiene. It costs the writer one sentence and adds a layer of legal cleanliness to the document at no signal cost; admissions committees and hiring managers read it as a sign of legal literacy rather than as a caveat that undermines the endorsement.

The strongest letters draw their evidence from the same documents the company itself relied on for performance management. Signed annual reviews, mid-year check-in notes, peer feedback gathered through the company's 360 tool, project post-mortems, customer satisfaction scores tied to the employee's accounts, internal awards or recognitions: these are the sources a manager can point to in the letter without exposure. The letter does not have to cite them by document name, but the underlying claims should be ones the documents would support.

A useful exercise before drafting: pull the employee's last two performance reviews, write down the three to five outcomes the reviews credit the employee with, and start the letter from those. The outcomes are the load-bearing evidence; the rest of the letter is context and character commentary around them. Letters built outcome-first read as substantive; letters built adjective-first (\"hard-working, team-oriented, a real go-getter\") read as filler and are heavily discounted by experienced reference readers.

For outcomes the writer cannot quantify cleanly (the employee's contribution to team culture, mentorship of junior staff, ability to absorb organisational change), narrative examples replace numbers. One concrete vignette outperforms three adjectives. The general principle, common to every category of recommendation letter on this site, is that specificity is the currency of credibility. The how to write a recommendation guide develops this principle in more detail.

References for currently employed staff carry an additional complication: the employee has not announced their job search to the wider organisation, and the manager may be one of the few people in the company who knows. Confidentiality is part of the manager's obligation. The letter should be sent only through channels the employee has designated, the manager should not discuss the application within the company, and the manager should not penalise the employee in performance management or assignments for having sought outside opportunities.

The Equal Employment Opportunity Commission has been clear that retaliation against an employee for seeking other employment is not in itself a violation of federal employment law, unless the employment search is connected to a protected activity (a discrimination complaint, a request for accommodation, union organising). State law in some jurisdictions provides additional protection. The practical norm in most US workplaces is that managers do not retaliate against employees for confidential job searches, both because it is bad management and because it can be hard to defend if questioned later.

The harder version of the question: the employee asks the current direct manager for the reference, but the manager does not want them to leave. The manager has two options. The first is to decline and to suggest the employee approach a former manager, a skip-level, or a peer; the decline conversation is awkward but ethically clean. The second is to write the letter genuinely while having a separate conversation with the employee about what would make them want to stay. Combining the two (writing a deliberately weak letter to sabotage the search while pretending to support it) is both unethical and a potential source of tortious-interference exposure if the employee later discovers it.