Free Letter of Recommendation Generator

Writing a recommendation letter is a strange genre: it must be glowing but credible, formal but warm, and specific enough that a committee reading two hundred letters remembers yours. Describe your relationship to the candidate, how long you've known them, the traits that matter, and one concrete story — the generator assembles the rest in proper letter form.

It's built for recommenders juggling real workloads: professors writing five letters in graduation season, managers drafting for departing reports, volunteer coordinators supporting scholarship kids who need every advantage a strong letter can give.

Real Examples

Graduate program — CS professor for former research assistant

Input

I'm Dr. Lena Ortiz, associate professor of computer science, Bellarmine University. Student: Theo Nakamura, my research assistant for 2 years in the distributed-systems lab. Rare debugging intuition; writes clearer code than most professionals I know. Story: he isolated a race condition that defeated two prior students AND a published paper's replication package, reproduced it, wrote a 3-page explanation the original authors thanked him for.

↓ output

To the Graduate Admissions Committee, I have supervised roughly forty research assistants across twelve years at Bellarmine, and Theo Nakamura is one of the two I would hire tomorrow without an interview. Theo joined my distributed-systems lab in his sophomore year and stayed two. What distinguishes him is not his grades (excellent, for the record) but a debugging instinct I cannot teach. Last spring he took an interest in a consensus protocol whose replication package had defeated two previous students. Within a week he had reproduced the intermittent failure, isolated a race condition the original authors had missed, and written a three-page explanation so precise that the authors replied to thank him — and cited his account in the erratum. Sophomores do not typically correspond with paper authors as peers. He writes code the way technical writers write prose; my other students learn from his pull requests alone. I rate him in the top 2% of undergraduates I have taught, without hesitation. Questions welcome at the address below. Sincerely, Dr. Lena Ortiz Associate Professor, Computer Science

Scholarship — food bank volunteer coordinator

Input

I coordinate volunteers at Riverside Food Bank. Candidate: Dani Reyes, 17, volunteered 400 hours over two summers, built our client intake spreadsheet system that cut wait times from 40 minutes to under 20, trained all 30 active volunteers herself in Spanish and English. Family can't contribute to college costs.

↓ output

To the Scholarship Committee: Some volunteers show up. Dani Reyes showed up early — 400 hours over two summers at Riverside Food Bank, most of them logged before her own school day started. Her signature contribution wasn't the hours, though. At sixteen, she rebuilt our paper-based client intake into a spreadsheet system that cut average wait time from 40 minutes to under 20 — and she built it by sitting with intake workers first, asking what slowed them down. When our director worried about the learning curve, Dani trained every one of our thirty active volunteers herself, one-on-one, in both Spanish and English. Families like Dani's are why food banks exist; students like Dani are why scholarships do. Riverside will lose something real when she heads to campus. I recommend her for your award with full conviction. Respectfully, Sam Whitfield Volunteer Coordinator, Riverside Food Bank

0 chars · free · no signup

How It Works

Step 1

State your role and relationship: "I'm an associate professor of CS; Theo was my research assistant for two years."

Step 2

Add duration, context, and the two or three traits most relevant to what they're applying for.

Step 3

Include at least one specific story with verifiable texture — numbers, names of projects, what happened when.

Step 4

Click Draft Letter and receive a complete letter with salutation, structured body, and sign-off block.

Step 5

Edit for truth. Every claim should survive the candidate handing this letter back to you years later.

Who Uses This, and Why

Graduate school season crunch: A professor with eight request emails in her inbox drafts each letter from two lines of notes per student, keeping every one distinct because each is anchored to a different story.
A promotion packet needs third-party voice: A manager writes for a former report now applying elsewhere for a step up, converting two years of quiet competence into language a stranger can evaluate.
Scholarship committees: A volunteer coordinator documents four hundred hours of service plus the intake system a seventeen-year-old rebuilt — evidence that separates an award winner from a finalist list.
First-job references for interns: A team lead writes for an intern whose only prior credential is a degree, translating project work into professional signals hiring managers trust.
Rental and freelance references: A long-term client vouches for a freelancer's reliability for a corporate vendor application, where procurement wants specifics about deadlines, not adjectives.
Award and board nominations: A nominator frames a colleague's community-organizing record for a civic award committee that reads fifty packets in one sitting.

Evidence-first praise that survives skeptical readers

Admissions committees and hiring panels are professional skeptics; they discount unsupported superlatives automatically. The structural instruction behind every draft is claim-then-proof: no trait appears without the story that demonstrates it, and the story includes concrete detail — hours, scale, outcomes — that reads as remembered rather than composed.

The comparative statement is the power move most letters omit. "Top 2% of undergraduates I've taught" tells a committee more than a paragraph of praise, because it converts opinion into a ranking against a base rate only the recommender knows.

Before

Jane is hardworking, intelligent, and passionate about her studies. She would be an excellent addition to your program and I recommend her without reservation...

After

In two years, Jane never missed a lab deadline. When our sequencer failed mid-project, she rebuilt the prep pipeline overnight and still presented complete results at the spring symposium — the only undergraduate on the floor who didn't ask for an extension.

Trait claim → evidenced claim

Pro Tips From Heavy Users

One vivid story outperforms five adjectives — committees remember the sequencer failure, not "diligent."
Use comparative rankings if you honestly can: "top 5% in eight years of teaching" carries weight no string of praise can match.
Match the story to the destination: leadership programs want initiative evidence, grad programs want intellect evidence.
Open by establishing exactly how you know the candidate and for how long — readers weigh praise by the source before the content.
Never include anything you wouldn't say to the candidate's face with the letter on the table between you.

Frequently Asked Questions

Is it acceptable for the candidate to draft their own letter?

It's widespread practice — busy recommenders often ask applicants for a draft. The ethical line is disclosure and final control: the recommender must review, edit, agree with every word, and submit it themselves. Follow your institution's stated policy where one exists.

How long should the letter be?

One page, roughly 350 to 500 words. Committees skim; a second page signals you couldn't prioritize. The exception is comprehensive tenure or fellowship files, where longer formats are expected.

What makes a recommendation sound genuine?

Specificity with friction. Details like "she disagreed with me twice and was right both times" carry credibility precisely because they're unflattering to the writer. Uniform perfection reads as boilerplate and gets discounted by experienced readers.

Can I write one letter and reuse it for multiple students?

Please don't — committees notice recycled scaffolding fast, and it undersells every student involved. Regenerate from each student's own notes; with the relationship and story in hand, distinct letters take minutes.

Academic versus professional letters — same structure?

The skeleton matches (relationship, evidence, ranking, close), but emphasis shifts. Academic letters foreground intellectual ability and research potential; professional ones foreground delivery, collaboration, and impact on metrics. The draft adjusts based on what you describe.

Should the letter state weaknesses?

One honest, minor, growth-framed note can raise credibility — "his early reports over-explained; he learned brevity fast." Avoid anything touching character or protected categories, and skip weaknesses entirely for fellowships where the reader doesn't know you.