8 min read
You're not greedy for wanting more. You're trying to match dollars to work. The mistake is booking one conversation when the company treats raises and promotions as two different workflows.
Managers can often nudge pay inside a band. They can't always skip the committee that owns level changes. When you don't know which path you're on, you'll hear "not this cycle" and won't know if they meant budget or title.
Before you draft the email, check your resume for free so bullet one matches the level you're arguing for. A raise case with coordinator bullets won't support a promotion ask.
Below you'll compare raise vs promotion on approvers, timing, and proof, pick the ask that fits your scope, and copy scripts that don't mix the two requests in one vague paragraph.
Raise vs promotion: what each ask actually changes
A raise keeps your level name and moves base, bonus, or equity inside the band for that level. A promotion changes the level name, opens a new band, and often triggers job description, comp review, and calibration with peers.
| Ask | Who decides | Typical proof |
|---|---|---|
| Raise | Manager + HR band check | Scope growth at current level, outcomes, retention risk |
| Promotion | Manager + committee or skip-level | Next-level duties sustained, JD match, peer calibration |
Composite example: a senior analyst runs two workstreams but still carries the analyst title. Promotion is the unlock if the career ladder says senior scope needs a senior title. A raise fits if the title already says senior and pay sits low in-band after a big delivery year.
Union and government employers sometimes publish step tables where raises are predictable and promotions are competitive exams. Private employers hide bands, but the split still exists: merit within level vs competitive promotion pools. Know which pool you're entering before you rehearse the script.
Contractors and sales roles may tie raises to quota attainment and promotions to team lead coverage. The comparison still holds: one path flexes variable pay inside role, the other changes role definition and approvers.
Pair this with how to request a raise when the title is settled, and how to ask for more money at work when you're not sure which route fits yet.
How to choose and run the right ask
Step 1: Name your level mismatch
Pull the internal level guide or job family sheet. Highlight duties you perform weekly. If more than half map to the next level, you're promotion track. If they map to your current level but pay doesn't, you're raise track.
Before: "I deserve more because I'm stressed."
After: "My scope includes vendor RFP ownership and two direct reports, which matches Senior Specialist on the ladder."
Step 2: Book one conversation with one headline
Don't blend "raise and promotion" in the subject line unless your company treats them as one packet. Most don't. Pick the primary gap and mention the secondary topic only if they ask.
Before: Slack ping "can we talk about comp and title?"
After: Calendar invite "Band alignment for [Level] scope" or "Promotion readiness for [Next Level]."
Copy-paste block: raise meeting request
Copy-paste raise ask (edit brackets)
{`Subject: Band alignment - [Your name]
Hi [Manager],
I'd like thirty minutes to review how my current outcomes map to band for [Current Level].
Since [date], I've delivered [outcome 1 with metric], [outcome 2], and [outcome 3]. I'd like to align base with that scope within our level guidelines.
Are you free [two options]?
Thanks,
[Your name]`}
Step 3: Build the promotion packet separately
Promotions need sustained next-level work, not one heroic month. List three duties from the next JD, attach metrics, and note how long you've carried each. Ask which committee cycle you're eligible for.
I've watched managers approve in-band raises while promotion packets sat unsigned because the employee never separated the two asks. Clear headlines get routed to the right approver.
Before: One slide deck mixing title wish list and rent math.
After: Promotion doc with JD mapping; raise talk scheduled after title effective date if pay lags.
If you're capped in-band after a raise, promotion is the structural fix. If promotion lands with flat pay, schedule a follow-up raise conversation with the new band midpoint in view, still in writing.
Timing cheat sheet: merit cycles own most raises; promotion committees often meet quarterly or twice a year. Ask HR which calendar you're on before you attach urgency. A raise ask two weeks before merit freeze can still enter the packet if your manager sponsors it early.
New parents and caregivers: shrink the ask to one route per quarter. Running promotion paperwork while negotiating retention bonus language splits your proof and burns manager attention you can't replace.
High performers in flat orgs: if there's no next level on the ladder, a raise plus expanded scope title (lead, principal contributor) may be the only in-band flex. Document that hybrid in writing so recruiters later read the right story on your internal profile.
Mixed asks that stall comp
Leading with peer gossip. Their pay isn't your evidence. Scope and level guides are.
Asking for promotion without next-level proof. You'll get mentorship talk, not a level change.
Accepting title without pay path. New scope with old band is a discount. Get review date on paper.
Before: Waited for annual review for both asks without knowing which cycle owns title.
After: Asked HR which calendar governs level vs merit, then timed the meeting.
Equity and bonus noise: a strong stock refresh can make base feel small. Split the conversation. Promotion often re-bands base; refresh may be separate. Don't accept "your total comp is fine" without seeing each line item for the new level.
Remote pay tiers add another trap. A raise inside your geography may not match HQ bands. Promotion sometimes resets location tier. Ask which geography sets comp before you compare numbers from a coworker in another state.
Make bullet one match the ask
Promotion packets fail when the internal resume still reads one level down. Align the file before you argue band or title.
Paste a target internal JD into job match score to see whether your bullets prove the next level or only support a raise inside the current one.
Generate a cover letter only if you're also testing external options while promotion cycles drag. Keep internal and external stories consistent on scope.
Book the right meeting this week
Asking for a raise vs asking for a promotion comes down to whether your gap is pay inside the level or level itself. Match the ask to the org chart path, bring one page of proof, and don't merge two workflows into one vague request.
- Check the ladder: title mismatch or pay mismatch.
- Pick raise or promotion as the meeting headline.
- Paste the script that fits and attach metrics.
When your file matches the story, run a free ATS check on the PDF you keep for internal mobility, then send the invite.
Read more
Frequently asked questions
A raise moves pay inside the band for the level you already hold. Your manager often owns most of that decision within the annual cycle. A promotion moves you to a new level, needs committee or HR sign-off beyond your manager, and runs on its own calendar with a written case.
Ask for a promotion when your duties already match the next level on the career ladder and the title change unlocks band headroom. Ask for a raise when the title is right but pay lags scope inside the same level. If you're capped in-band, a raise alone may not close the gap.
Sometimes title moves first and pay catches up at the next cycle. Get the effective date and review timing in writing. If they offer title only with no pay path, treat it as incomplete and negotiate total comp before you accept the new scope.
Raises need scope growth and outcomes inside your current level. Promotions need sustained work at the next level's duties, often with peer comparison and a job description match. Bring metrics and dates, not mood.