Raise request email after taking on extra responsibilities
Short answer
Lead with the scope expansion, not the request. Name two or three specific responsibilities you've absorbed in the last 6–12 months, link each to a business outcome, then anchor on the market rate for the de-facto role you're now doing. Ask for a specific base bump (typically +5–15%) with a 30-minute call to discuss. Keep the email under 250 words.
You're here because
- Your scope has expanded but your title and pay haven't moved
- You feel taken for granted but don't know how to bring it up
- You're worried framing it as money will land badly
- You don't want to threaten to leave just to be heard
- You want a written record that doesn't sound resentful
The exact email to send
Hi [MANAGER_NAME],
I'd like to schedule 30 minutes to discuss my compensation. Over the past [6–12] months, my scope has expanded into responsibilities that weren't part of the original role:
• [RESPONSIBILITY_1] — previously owned by [ROLE / PERSON]; outcome: [METRIC]
• [RESPONSIBILITY_2] — outcome: [METRIC]
• [RESPONSIBILITY_3] — outcome: [METRIC]
Looking at market data from Levels.fyi / Glassdoor, the typical range for the de-facto scope I'm now covering is $[LOW]–$[HIGH]. Given my current base of $[CURRENT], I'd like to discuss adjusting to $[TARGET].
Would [DATE] work for a 30-minute conversation?
Thanks,
[YOUR_NAME]
- Built for the moment a written offer or deadline lands — not casual browsing.
- Written for the 24–72 hour decision window.
- Designed for people who don't negotiate often.
- Real workplace register — not internet bravado.
What NOT to say
- "I'm doing everyone else's job" — sounds resentful even if true. Stick to specific responsibilities.
- "I'll have to look elsewhere if…" — never lead with the threat.
- Asking for a percentage without naming a dollar amount.
- Sending without market data. The data is what makes the ask defensible.
- Burying the request in a wall of context. Lead clean: scope → data → ask.
An illustrative example
Took on hiring loops, onboarding playbook, and weekly exec readout — none of which were in the JD. Sent the email with three bullets and Glassdoor data showing $92–$108K for a CS Lead. Original base was $84K. Manager replied within 48 hours: $94K base + formal Lead title at next cycle. Net uplift: +$10K base + a title that unlocks the next promotion.
Why this works
Managers can't approve a raise for "hard work." They can approve a raise for documented scope expansion mapped to market data. The bullet format gives them something they can forward to HR or their skip-level as the formal case.
What to do next
Send the email today. The Salary Raise Kit includes the follow-up scripts: when to follow up after silence, how to negotiate if they propose a smaller number, and how to ask for a written timeline if they defer to the next cycle.
Before you send — quick check
- Do you have your raise number tied to a market band?
- Do you have 2–3 specific impact examples ready?
- Do you have a follow-up date if your manager says "let me think"?
If you answered "not sure" to any of these, the Salary Raise Kit walks you through all three.
Related reads
FAQ
How long should this email be?
Under 250 words. The scope bullets do the work — keep the framing tight.
Should I include all responsibilities I've taken on?
Pick the three with the clearest business impact. A long list dilutes the case; three sharp bullets focus it.
What if my manager says "wait for the review cycle"?
Ask for a written commitment with criteria and a target number tied to the next cycle. The Salary Raise Kit has the exact follow-up wording.