A raise request email is a door opener, not the entire negotiation. Its job is to put a clear ask on the calendar, show that you did the math, and give your manager something forwardable to HR without trapping either of you in a brittle thread. Pair this guide with live-meeting scripts in how to ask for a raise, size the number with how much should I ask for a raise, and verify arithmetic on the pay raise calculator or how to calculate a raise.

What belongs in the first email

Include four blocks: purpose, evidence, ask, and logistics. Purpose is one sentence—“I would like to discuss adjusting my base pay based on scope and outcomes this cycle.” Evidence is two or three bullets tied to results you own. Ask states a range in percent and annual dollars, plus the paycheck view if you know your frequency. Logistics proposes two meeting times and offers to send a one-page summary in advance.

Leave out tax lectures, peer salary gossip, and threats to resign. Those belong nowhere in a first note, and most belong nowhere at all in writing.

Subject lines that get opened

Keep subjects boring and specific: “Request to discuss base pay adjustment — [Your Name]” or “Compensation discussion before merit submissions.” Clever subjects age poorly in HR archives. If your company uses ticket systems for comp conversations, follow that channel and treat email as a confirmation trail.

Template: annual cycle, before budgets lock

Subject: Request to discuss base pay adjustment — [Name]

Hi [Manager name],

I would like to schedule 25 minutes to discuss a base pay adjustment ahead of this cycle’s recommendations.

Over the past [timeframe], I [outcome 1], [outcome 2], and took on [scope change]. Based on that contribution and the current range for this role, I am requesting an increase of [X–Y]%, about $[annual dollars] per year ([paycheck dollars] per [biweekly/semi-monthly] paycheck).

I can meet [option A] or [option B]. Happy to send a one-page summary beforehand. Thanks for considering the conversation.

[Name]

Before you paste numbers, run them through the pay raise calculator so percent and dollars agree.

Template: after a major scope change mid-year

Subject: Mid-year compensation check-in — expanded scope

Hi [Manager name],

Since [date], my role has included [new ownership]. That work was not reflected in my last base adjustment. I would like to discuss an off-cycle review or a documented plan tied to the next cycle.

I am proposing a base increase of [X]%, roughly $[annual] ($[per paycheck] on our [frequency] schedule), or a written path to that outcome by [date] if timing is constrained.

Could we meet this week? I will bring a short evidence list and the math behind the ask.

[Name]

Template: soft follow-up after silence

Subject: Re: Request to discuss base pay adjustment

Hi [Manager name],

Checking on my note from [date] about a base pay conversation. I know calendars are heavy—open to a shorter 15-minute slot if that helps, or to share the one-pager asynchronously so you can advise on timing.

Thanks, [Name]

One follow-up after five to seven business days is professional. Daily nudges are not.

Template: if the answer was “not this cycle”

Subject: Documenting next steps for compensation discussion

Hi [Manager name],

Thank you for talking through compensation on [date]. As I understand it, a base change is not available until [window], contingent on [criteria].

I will focus on [criteria] and suggest we reconvene by [date]. Please correct anything I misunderstood so we share the same checklist.

[Name]

Written criteria prevent moving goalposts. Revisit math if hours change before the follow-up.

Tone: firm, not theatrical

Replace “I deserve” with “I am requesting based on.” Replace “everyone knows I’m underpaid” with a range ask and outcomes. Gratitude can appear once; groveling undercuts the evidence. If you are angry, draft offline and send after a cool-down. Email is evidence.

Attachments and one-pagers

A one-page PDF or doc with outcomes, ask, and calculator screenshot (or a clean table) helps managers advocate. Do not attach confidential peer comp data you were not authorized to have. Market citations should be high level; detailed survey tables belong in a conversation if your company already licenses them. For climate context without inventing figures, point yourself to average raise percentage while keeping the email about your role.

Common failure modes

  • Asking only in percent with no dollars (finance thinks in cash).
  • Asking only in dollars with no percent (harder to compare with guidelines).
  • Negotiating the final number exclusively over email (context collapses).
  • Mixing bonus and base in one fuzzy “total raise” line—see raise vs bonus.
  • CC’ing skip-levels on the first ask without a relationship or process reason.

Evidence bullets that travel well when forwarded

Write each bullet as outcome + scope + time window: “Reduced average ticket resolution from 18 hours to 11 hours across Q2–Q3 while covering the vacant team lead queue.” Avoid bullets that only restate job duties. Avoid confidential metrics you are not allowed to email. If a metric is sensitive, offer to walk through it live and keep the email at a higher altitude.

Percent ranges vs single-point asks in writing

Email favors a narrow range (“5–6%”) more than a hard single point, because managers often need wiggle room to champion you inside a matrix. Still verify both ends of the range in dollars. If your company culture expects a single number, give one—and know your floor privately. Sizing logic lives in how much should I ask for a raise.

Skip-level and HR copies

Default to your manager only. Copy HR when policy requires a ticket, when your manager asked you to loop them in, or when you are documenting a legally sensitive concern (which is a different email than a routine raise request). Blind-copying mentors outside the chain creates screenshots waiting to happen.

Remote and async-first teams

On distributed teams, the email may carry more weight because live time is scarce. Keep the packet crisp and propose video times in overlapping hours. If your manager prefers docs, link a one-pager in the company workspace instead of attaching mystery files from personal cloud accounts.

When the raise is really a promotion ask

Say so in the first paragraph: you are requesting a level review with an associated base adjustment, not only a merit bump. Point to scope already performed at the higher level. Model with the promotion raise calculator and read average raise for a promotion so your percent expectations match level guidelines rather than merit means.

International tone notes

In some cultures, direct asks feel blunt; in others, indirect asks feel evasive. Match your company’s operating culture while staying clear: a softener sentence is fine (“I welcome your candid view on timing”) after a concrete ask—not instead of one. Translate paycheck examples into local currency and local pay frequency if you work across borders.

Security and privacy

Do not paste peer salaries, scraped offer data of unknown origin, or medical details into a raise email. Market context can be general. Personal hardship can be mentioned at a high level if relevant to timing, but compensation cases still rest on role value. Cost-of-living framing differs from merit framing—see cost of living raise vs merit raise.

After you send

Prepare the live conversation using how to ask for a raise. If an outside offer appears later, switch frames to negotiate a raise after a job offer rather than forcing the annual-cycle email template onto a different situation.

Accessibility and clarity

Use plain language. Avoid idioms that do not travel across cultures on a global team. Spell out paycheck frequency. If your manager is in another time zone, propose times in both zones once.

What not to promise

Do not promise what you will do with the money. Do not claim tax outcomes. Do not assert that HR “always” approves a percent. Your email should survive being forwarded verbatim to compensation. Stub surprises after a yes are a separate literacy topic—why your raise looks smaller on your paycheck.

Bottom line

Write short, specific raise emails that open a meeting, show evidence, and state percent plus dollars you already verified on the pay raise calculator. Keep bargaining for the conversation, document next steps when the answer is delayed, and reuse the sibling scripts and sizing guides so every channel tells the same story.

Sample evidence bullets that travel well

Prefer bullets like shipped the billing migration with zero Sev-1 incidents, reduced vendor spend by a documented amount, or owned on-call for a product line for two quarters. Avoid bullets like worked really hard or stayed late. Hard work without outcomes is hard for a manager to forward. Tie each bullet to the ask in one breath so the email does not read like a performance review dump.

Scheduling politics

If merit recommendations are due on a known date, send the meeting request at least two weeks earlier when you can. Late emails force exception paths. If you missed the window, say so honestly and ask for a documented off-cycle criteria list rather than pretending the calendar is open. Timing notes in how to ask for a raise still apply when the medium is email.

When HR owns the channel

Some companies require compensation requests through HRIS forms. In that case, keep email as a courtesy heads-up to your manager and paste the same percent and dollar pair into the form fields. Inconsistency between channels is how asks die in process.

Closing without painting yourself into a corner

End with openness to discuss structure—base, dated bonus, or a written path—without volunteering a discount on your ask in the first note. Discounts belong in live negotiation after you hear constraints. The email’s job is clarity, not pre-concession.