Writing Letters That Actually Get Read

Most people treat recommendation letters like a form to fill out. They copy from templates, pad with generic praise, and submit. That approach produces garbage. Admissions committees and hiring managers read thousands of these. They can tell within thirty seconds whether a letter is authentic or generated by someone who has never worked with the person they're describing. Here's the thing nobody tells you: a strong letter of recommendation isn't about listing achievements. It's about providing a lens through which the reader can evaluate the candidate's potential. Your job is to give them enough specific, verifiable context that their own judgment fills in the gaps.

Sample Letters Of Recommendation That Work

I've been drafting these for graduate programs, tenure reviews, and senior hire packages for roughly twelve years. The ones that actually move the needle share a specific architecture. They open with the writer's credibility, ground the candidate in a particular professional context, and then spend the bulk of the letter on one or two concrete episodes that reveal character and capability under real conditions. The opening paragraph needs to establish why the reader should trust your opinion. Not your title for its own sake, but your proximity to the work. "I supervised Maria for three years on the infrastructure migration project" carries more weight than "I am pleased to recommend Maria," which is what ninety percent of letters start with. The second option says nothing about your vantage point. The first tells the committee exactly how to weight your assessment. The middle sections should describe specific incidents, not general traits. Don't say someone is "a natural leader." Describe the moment they walked into a room full of engineers who hated each other, identified the real blocker (it was usually a vague timeline, not a personality clash), and restructured the sprint in a way that got everyone aligned. Concrete details do the heavy lifting. Vague superlatives don't. I remember running into this problem with a PhD applicant back in 2019. Her letter writer was a brilliant researcher but had no experience with undergraduate candidates. The draft was full of impressive-sounding language about "cutting-edge contributions to computational theory" that meant nothing to an admissions committee evaluating teaching potential. I restructured it around a specific teaching assistantship where she redesigned the grading rubric for the intro algorithms course and cut grading time in half while improving feedback quality. The revised letter landed her interviews at three programs where the original never would have.

The Structure Nobody Talks About

A working letter follows this pattern without being rigid about it: Your relationship to the candidate and the timeframe you've observed them. Two to three sentences max. No one cares that you've known them for eight years if you haven't worked closely with them for most of those eight years. Specific examples. Pick two. Maybe three if the letter is long. Each example should reveal a different dimension of capability. One example about technical skill, one about collaboration or leadership, one about handling failure or ambiguity. The third should be optional. More than three examples dilutes the impact because the reader's attention drops off after the second substantial anecdote. Your assessment of fit. Why this candidate for this specific program or role. Generic enthusiasm about the candidate being "wonderful" doesn't help anyone. A sentence or two connecting their demonstrated abilities to the specific demands of the opportunity is worth more than a paragraph of praise. A closing that offers availability. Standard. Expected. Fine. The whole thing should be one page. Maybe one and a quarter pages if the relationship is complex enough to warrant it. Anything longer and nobody reads the whole thing.

Common Mistakes That Sink Letters

The worst letters I've encountered fall into a few predictable categories. The first is the laundry list. Someone who just enumerates achievements without any narrative thread. "John published three papers. He received the departmental award. He organized the conference." This reads like a resume in prose form. It tells the reader nothing they couldn't already see in the CV, except now they're more bored. The second mistake is overstatement. Calling someone "the best student I've ever had in twenty years" when you've been teaching for twenty years. Committees see this regularly and discount it. Moderate language with specific backing is more credible than superlative language with no substance behind it. The third mistake is vagueness. "Sarah is very dedicated and hardworking." What does that mean? Did she stay late rewriting the same section of code six times until it was right? Did she volunteer to mentor a struggling peer for two semesters? The abstract qualities only matter when anchored to observable behavior. I also see a lot of letters that confuse length with depth. A four-page letter stuffed with fluff is worse than a one-page letter with three well-developed examples. Quality of observation matters more than quantity of words.

What to Do When You Don't Know Someone Well

This comes up more often than people admit. Sometimes you've only worked with a candidate in a limited capacity. Maybe they took your class once. Maybe you collaborated on a single grant. You don't have deep material to draw from. In those cases, you have two honest options. One is to write a short, direct letter that explicitly states the limits of your relationship and focuses on what you did observe. "I worked with David on the sustainability initiative for eight months. During that time, I observed..." This is better than inflating your familiarity or padding the letter with generic statements. The other option is to decline politely. There are plenty of people who will write you a lukewarm letter because they feel obligated. Your candidate deserves better than that. A short refusal that suggests someone who knows them more deeply is often more helpful than a mediocre letter that limps across the finish line.

Downloadable Template

I keep a basic template in my files that I modify for each use case. It's not something I copy-paste—every letter requires rewriting based on the specific candidate and relationship—but the skeleton is consistent. The template opens with your name, title, institution, contact information, and date. Then a salutation that addresses the specific committee or hiring manager when possible. The body follows the structure I outlined above. The closing includes your signature and an explicit offer to discuss the candidate further. You can find a working version of this template shared across several academic advising forums and professional writing guides. The structure is what matters, not the exact wording.

A Few Practical Notes

Draft the letter before you ask the candidate to submit it. Give them your draft and ask if there's anything they want you to include or avoid. Some candidates have context you don't know about—maybe they overcame a significant personal challenge during the period you're writing about, or maybe there's a gap in their record that needs framing. A quick conversation saves you from writing something incomplete or accidentally inaccurate. Send the letter early. Rushed letters are sloppy letters. If you're writing something at 11 PM the night before a deadline, you're not doing your candidate any favors. Keep a copy for your records. Not because you expect to need it, but because six months later when someone asks you to expand on a point you made, you'll be glad you have the original text in front of you. Letters of recommendation are a small part of any application or hiring process, but they're the part that can shift a decision. A well-written one doesn't need to be dramatic or eloquent. It just needs to be specific, honest, and useful to someone who has to make a choice between people who all look good on paper.