How to Ask for a Salary Increase by Email

12 min read

You did the work. Scope grew. Your paycheck didn't. You drafted an email, deleted it, and told yourself you'd bring it up in a one-on-one that never had room for money talk. That's common, and it isn't because you don't deserve a raise.

Most templates online read like ultimatums or therapy journals. Your manager isn't HR. They need a note they can paste into a comp packet without rewriting your life story. You need a structure that survives Outlook forwards and doesn't poison the relationship if the answer is not yet.

Before you send, check your resume for free and pull the same quantified bullets you'll cite in the email. If those wins aren't on paper yet, fix the file first so your internal story matches what you'd show an external recruiter tomorrow.

Below: the symptom when raise emails go nowhere, three causes, how to tell which one is yours, fixes for each, copy-paste scripts, and what not to do. For annual raise rhythm outside email, see how to ask for a raise in 2026 . For offer-stage counters, use how to counter a job offer instead.

When your raise email goes quiet

The symptom: you sent something about pay weeks ago. You got a thumbs-up emoji, a we'll see at review, or silence. Payroll didn't move. You're still doing the expanded job for the old base.

The email probably wasn't wrong morally. It was wrong structurally. Managers approve raises with packets: scope change, outcomes, target band, timing. A paragraph about inflation and burnout doesn't paste into Workday compensation fields.

Internal raises aren't job offers. You already have trust capital and documented performance cycles. The note has to sound like a business case from someone who plans to stay, not a vendor invoice or a resignation threat.

If you're also interviewing externally, keep those threads separate until you have a real offer. This page is for the employee who wants to fix pay where they are first.

Remote teams often default to email because hallway chats don't exist. That's fine. The same rules apply: short note, forwardable facts, meeting request. Don't substitute a Slack DM for the email your manager needs for HR.

New managers sometimes lack history on your scope growth. Your email is the timeline they didn't live through. Spell the before and after of your role in one bullet if you absorbed work from a vacant seat.

When offers are on the table instead, read negotiate salary without competing offers for a different script set.

Why your salary increase email isn't landing

Three causes show up in almost every stuck thread. Match the signal, run the fix, ignore advice that doesn't fit your manager's culture.

Cause 1: The ask is vague

Can we talk about compensation sometime? feels polite. It also gives your manager nothing to act on. Finance needs a number or range and a reason tied to scope.

How to tell: you never typed a dollar figure. The email is longer on feelings than outcomes. You asked for a chat with no subject line routing hint.

Fix: open with purpose, list two or three wins with metrics or clear scope shifts, state target base, propose twenty minutes with two time options. Under 200 words.

Before: I feel underpaid compared to others on the team and would love to discuss when you have time.
After: Based on owning vendor RFPs and cutting cycle time 18%, I am requesting base adjustment to $92,000. Are you free Tuesday 10:00 or Wednesday 2:00?

Cause 2: Proof is old or missing

Tenure alone rarely clears a band. Managers defend raises with outcomes since the last increase or since scope changed. If your email reads like a loyalty badge, it stalls.

How to tell: your bullets reference years ago. You mention busy weeks without naming deliverables. You didn't tie wins to the job description you actually perform today.

Fix: build a one-page summary: current title, last raise date, three bullets with numbers or absorbed scope, target ask. Attach it; keep the email short.

Before: I've been here four years and always go above and beyond.
After: Since March I absorbed QA for two squads, shipped the billing migration on date, and cut support tickets 14% QoQ.

Cause 3: Timing fights the calendar

Sending a raise note the day after layoffs or mid-freeze sounds tone-deaf even when your case is solid. Alignment with review windows isn't mandatory, but random Tuesday pings during budget lock get deferred by default.

How to tell: leadership just announced hiring pause. You sent on a holiday Friday with urgency language. You never asked when comp decisions get made on your team.

Fix: ask in a one-on-one when calibration runs. Send the email so your manager has narrative before that meeting, or right after a shipped win or strong review.

I've seen managers want to approve a raise but lack a forwardable paragraph for HR. The employee had the case in their head and vented in Slack instead of sending a clean email the manager could paste.

Copy-paste block: salary increase email

Subject: Compensation discussion – [Your Name]

Hi [Manager first name],

I would like to discuss a salary increase reflecting expanded scope since [last review or date].

Recent impact:
• [Outcome 1 with metric or scope]
• [Outcome 2 with metric or scope]
• [Outcome 3 with metric or scope]

Based on this scope and market for [title] in [location/remote], I am targeting $[target] base.

Are you available [day/time option 1] or [day/time option 2] for 20 minutes?

Thank you,
[Your name]
              

Edge case: culture prefers live talks first. Send the email to book the meeting only, attach the one-pager, and bring the number verbally in the room.

Edge case: title change is part of the ask. Say so in one line so pay and leveling don't become two surprise threads.

After the meeting, email a three-sentence summary with agreed next steps. That thread is what payroll chases when systems lag.

If they counter lower, ask what would justify the rest at the next cycle and get that criteria in writing. Vague later maybe without metrics repeats the stall.

Use the cover letter generator only if you need practice tightening prose. Raise emails are shorter and more numeric than cover letters.

Reply scripts matter after send. If they agree in principle, thank them and ask for effective date and new base in writing. If they delay, ask for criteria and a calendar check-in. If they counter, negotiate once on total comp, then decide.

Bonus and stipend asks belong in the same thread once base is discussed. Don't open four separate emails for PTO, title, and pay. One packet, one conversation arc.

Parents and caregivers: send during business hours when your manager is online. Urgent weekend language reads as pressure, not proof.

Night-shift workers can draft in the morning and schedule send for when leadership reads mail. Timing is part of cause three; use the delay feature instead of venting at 2 a.m.

Misreads that freeze comp talks

Comparing yourself to a named peer's pay. Policy risk and bad optics. Compare scope and market bands, not gossip.

CC'ing skip-level on note one. You blindside your manager. Escalate only after a documented stall.

Threatening without a real offer. Empty threats burn trust. Mention external offers only when you'd actually leave.

Pasting personal bills. Rent and childcare are real. They don't belong in the first business case email.

Before: Subject Help!!! Body compares coworker salaries and demands answer by Monday.
After: Subject Compensation discussion – [Name]. Body lists three outcomes and $target with two meeting slots.

Before: Long thread in team chat about pay fairness.
After: Private email to manager with forwardable bullets and optional PDF summary.

This won't create budget that doesn't exist. It stops a good case from dying because the email couldn't survive a forward to HR.

Don't confuse annual COL bumps with a scope-based raise. If your duties doubled, cite duties, not grocery prices alone.

When they say no with a path, document the path. When they say no without criteria, you learned something about retention risk for your own planning.

Screenshot salary sites without role, level, and location context look sloppy in calibration. If you cite market, cite the job family you actually perform, not a generic national average.

Writing a novel about company loyalty while base stayed flat since 2022 doesn't replace three bullets about what changed in your job description since then.

Asking for retro pay in email one without prior verbal alignment often gets an automatic no. Sequence matters: meeting, alignment, then written ask with number.

Sharpen the proof list

Run your accomplishment bullets through the free ATS checker on the resume you'd use if you left tomorrow. Weak bullets in the file become weak bullets in the raise email.

Paste a target external posting into score your job match to sanity-check level language when you cite market for your title. You're not applying; you're calibrating wording.

Keep language aligned with how to answer salary expectations so internal and external conversations don't contradict each other.

Send one draft tonight

How to ask for a salary increase by email comes down to forwardable proof, a named target, and a meeting ask. You're not negotiating with a stranger; you're giving your manager ammunition for a process they already run.

• Write three impact bullets with metrics or scope.
• Pick a researched target base or tight range.
• Paste the script block and fix the subject line.
• Attach a one-pager if your wins need more room.
• Follow up in writing after every live conversation.

Open your drafts folder. Run a free ATS check on your resume bullets, then send the email while the proof still matches this quarter's work.

You won't get every yes. You will get clearer nos, and that's still data for your next move inside or outside the company.

Save sent raise emails in a folder with the one-pager and any written approvals. Payroll typos happen; your thread is the backup.

Share this page with a coworker who's drafting the same vague can we talk about pay note. Make them name a number before they hit send.

If you get a yes, update your resume the same week so external options stay current without scrambling later. Raises belong on the file as scope proof, not just on your W-2.