Edited by us
Asking for a recommendation letter — the email that makes it easy to say yes
A recommender has to reconstruct a memory to write one. Hand over the material and the yes gets easier.
By Mephify (operator)3 min read
Why the ask stalls
What stalls a recommendation request is rarely the wording. Send one line asking whether they could write you a letter, and the reply has to start with questions. When is it due? Where does it go, and in what form? What should the letter emphasize? While that exchange goes back and forth the deadline gets closer, and a busy recommender often steps back rather than commit.
A recommendation letter is a document someone writes by reconstructing a memory. They taught dozens of students, or managed a dozen reports, and the term or the project ended a while ago. If you don't supply the material, they do that work for you.
Six things that make it easy to say yes
What earns a yes is not a politer sentence. It is the material already in the email. With these six, all your recommender has to do is decide.
- Deadline and submission method — an online portal link, a signed PDF, or a sealed envelope. Each one costs them a different amount of time
- Where your paths actually crossed — which course, which term, which project, and what your role was. Add the grade or the outcome so nothing needs looking up
- Where you are applying and why — the program or role by name, and two or three sentences on why that one
- One or two things to emphasize — emphasizing everything is emphasizing nothing
- Copies of what you are submitting — send your statement of purpose or resume so the letter points the same direction
- Room to decline — one sentence saying they should feel free to say no. That sentence is what makes a reply easy to write
What to put in the request when you use AI
Move that material into the request and the only work left for the model is arrangement and tone. Leave it out and the model fills the gap with something plausible. When a project you never did or a grade you never earned lands in the email, the person reading it is someone who knows you.
The line that changes the output
Use only the facts below. Anything missing, mark as [FILL IN: what goes here] instead of inventing it. Due November 15, submitted through an online portal, took your Data Structures course in spring 2025 (A), led the team project, applying to an MS program. Emphasize one thing: following through to the end. Include a sentence making it easy to decline.
Tone is your call. A first ask reads differently from a second one, and differently again depending on how you normally speak to this person. The model cannot know that. Leave it unstated and the model decides for you, and then you spend your time editing against its choice.
The two emails people forget
The ask is not the whole exchange. Two more emails follow, and both shape whether the next ask works.
- 1A check-in one week out — not a nudge but information. Restate the time left and the submission method in one line
- 2Thanks after submission, then the outcome — when you hear back, tell them. The next letter you need is likely from the same person
Checklist before you send
- 1Are the deadline and the submission method in the first paragraph?
- 2Did you write down where your paths crossed, or are you asking them to remember?
- 3Is the emphasis limited to one or two things?
- 4Did you leave room to decline?
- 5Does every fact in the draft trace to something you supplied?
Reading helps; trying is faster.