How to Ask for a Raise by Email: Templates, and When Not to Send One

You wrote the email. Four paragraphs, the numbers, a link to the market data, a line about how much you like the team. You read it twice and sent it at 8:40 in the morning.

The reply landed at 11. "Thanks for putting this together. Let me look into it and come back to you."

That is not a bad manager stalling. It is the only reply your email made easy. The line people write, usually near the top, is some version of "I wanted to put my thoughts in writing so you have time to consider them." It sounds considerate. What it actually does is grant permission to consider it indefinitely.

Email has two jobs in a compensation conversation and it is very good at both: getting the meeting on the calendar, and writing down what was agreed once the meeting is over. It is bad at the third job, which is making the ask.

What email takes away

The silence. Say a number out loud and there is a pause, and your manager has to fill it. That pause is where the thinking happens. In an inbox there is no pause. There is a draft they will finish later, or not.

The adjustment. Live, you hear the hesitation land on the word budget, and you can move: ask what would change it, ask what number they could put forward instead. In writing you get one shot at the phrasing, then you wait, and anything you failed to anticipate goes unanswered for a week.

Control of the document. Your email gets forwarded. It reaches HR, your manager's manager, and eventually a spreadsheet, in the exact words you chose at 8:40 in the morning and without your tone attached. Every hedge in it is now the official record of what you wanted. "I was hoping we could maybe look at" becomes a quotation.

None of that makes email useless. It makes it a scheduling tool and a record-keeping tool. What to say once you are in the room is a different job, with different rules.

The email that books the meeting

Three sentences. One topic, one duration, one request. No evidence, no number, no apology, no explanation of why you were nervous about sending it.

Name the topic. "Quick chat" gets you a manager who thought this meeting was about the sprint and now has to improvise an answer about money, and improvised answers about money are no. Three days of notice gets you a manager who has checked the band before they sit down. Their preparation is what buys you a yes.

Thirty minutes, not fifteen. Fifteen says this is small.

If they ask you to just send it over

Common, and usually not hostility. It is a manager batching their week. Do not refuse and do not comply.

If they push a second time, they have told you something real about how this company makes decisions, and the four cases further down apply to you.

The email that goes out after

Almost nobody sends this one. It is the one that moves money.

Send it the same day, within a few hours, while you both still remember the words. Its purpose is not pressure. It is a record. Managers move teams, budgets get reallocated, and nine weeks from now the only version of this conversation that still exists is the written one.

Four things go in it and nothing else.

• What you asked for, in the same number you said out loud.
• What they said, in their words, without upgrading it. If they said they would look into it, write that they will look into it. Turning it into a promise gets you corrected, and then you are arguing about the email instead of the raise.
• The date you agreed on.
• What you owe them before that date, if anything.

The last line does the work. "Let me know if I have any of that wrong" makes your version the default, and silence confirms it. It is also fair: you offered them the correction, in writing, and they declined to make it.

When the date passes and nothing happens

Wait two working days. Then send three lines, with no new arguments and no apology for asking.

Not yet is an acceptable answer, and saying so out loud is exactly what makes no answer unacceptable.

The four cases where a written ask is right

Your company genuinely runs on writing. Some fully remote, async companies decide things in documents. Proposals get comments, comments get resolved, and a request that only ever happened on a call did not happen. If that is where decisions live where you work, put the ask there.

Your manager is six or more time zones away. When the only slot you share sits at the ragged edge of somebody's day, the live conversation you fought for will be short and tired. A written ask that gets read properly at nine in the morning beats a call at nine at night. Book the call for the follow-up instead.

HR requires a written submission. Comp review forms, job architecture requests, promotion packets. Fill it in properly rather than treating it as paperwork. That document is what gets read in a calibration meeting by people who have never met you, and it does the arguing while you are not in the room.

You are inside a formal review cycle with a self-assessment. If the company already asks you to write, put the compensation argument in that document, near the top, in plain language. It is going to be read at least two levels above you. Do not spend it on a list of tasks you completed.

The rule underneath all four: ask in writing when writing is where decisions actually get made, or when live attention is genuinely unavailable. Comfort is not on the list. Writing is more comfortable, and that is the real reason most raise emails get sent.

The full written ask

Four blocks, around 200 words. Longer than that and you have stopped making a case and started building a defense. The structure matches the spoken version: topic, evidence, one number. What writing has to add is a deadline.

Two things in there are load-bearing, and both sit in the last block.

A date. A written ask with no requested date has no clock. It can sit for six weeks without anybody being wrong.

A second question. "If it is not, what would need to be true" gives your manager something to answer even when the answer to the first question is no. A message containing exactly one question can be closed with one word.

Notice what is missing. No apology. No line about this maybe not being the best time. No range, because a range gets read as your floor. No paragraph about how much you enjoy the team, because warmth in a compensation email reads as a hedge: it is the only part of the message the reader can agree with for free.

When to use a letter instead of an email

Same content, different envelope. A formal letter, printed and signed or attached as a PDF, earns its formality in three places: public sector and unionized workplaces where the process expects paper, HR portals that want a document uploaded, and any company where somebody has told you to put it in writing after a verbal conversation. Date at the top, your manager and HR named, one page.

The words do not change. The permanence does. Anything you would not want read aloud in a meeting two years from now does not belong in a letter.

This does not work if your manager cannot approve it alone. An email gives them something to forward, which is the point, but it also means the decision gets made in a room you are not in and months before you write. Ask when the budget is set, and send this eight weeks earlier next time.

The part the email cannot do

Every version of this ends in a conversation. Email books the meeting, and then you have to sit in it. HR requires the form, and then somebody calls you about the form. The written ask gets read, and then your manager wants twenty minutes.

The email is the part you can edit forty times. The conversation is the part you get once.

And the sentence that fails is always the same one. On a screen, $110,000 is a figure in a paragraph and it costs nothing to type. Said out loud to the person who signs off on it, while they look at you and say nothing, it tends to come out tilted up at the end with a discount already attached.

You have the words now. What you have not done is say them to somebody who pushes back.