All Things Workplace

Promotion / Raise Case Outline How-to

Sep 10, 2026 | Career Growth, How-tos

Venting about fairness is not a case. Managers can coach evidence. They can’t coach a rant. Before you book the live conversation, draft a clean outline that separates the ask from the evidence spine.

Time box: 45-60 minutes to draft the outline. The conversation is a separate meeting. This is practice prep, not legal advice, not market-salary guarantees, and not a promise that any script gets you a yes.

Stage homes: Individual Contributor hub and New Manager hub. Literacy on process: How HR works (education only). Deeper guides: how to make a case for a raise and how promotions actually happen.

When to use (and when not to)

Build the case when:
– You’re approaching a known compensation or promotion cycle
– Your scope changed sustainably (not one busy week)
– You’ve delivered next-level impact for a meaningful stretch and have receipts
– Your manager already knows the story in pieces from 1:1s and feedback loops

Do not run this when:
– You’re reacting to one good week or one compliment
– You’re leading with an ultimatum or a quit threat
– You have no evidence, only feelings
– You’re planning a hallway ambush
– Your primary “proof” is gossip about a peer’s pay

Company cycles and leveling rules differ. Follow yours. This outline adapts; it doesn’t invent your policy.

Who is involved

  • You draft the outline.
  • Your manager is usually the first conversation.
  • Skip-level or HR/comp may enter later depending on your company (orientation only here, not a playbook to circumvent your manager).

Raise ask vs. promotion / level ask

They overlap but aren’t identical.

  • Raise (same level): emphasize market/internal equity only if your company invites that conversation, plus expanded scope and outcomes in the current role. Many companies separate “merit” from “promotion.”
  • Promotion / level: emphasize sustained work at the next level’s scope: complexity, influence, ownership, and business value matched to the leveled expectations where you work.

If you’re unsure which you’re seeking, write both in draft, then pick one primary ask before the meeting. Split asks confuse the room.

Outline template (1-2 pages)

Role scope today
- What I own now (people, systems, customers, budget slices)
- How that differs from 6-12 months ago

Proof of next-level / expanded impact
- Outcomes (not activities): what changed because of my work
- Examples with dates and evidence links (docs, metrics you own, customer results)
- Peer / partner feedback themes (from your feedback log, not fabricated quotes)

Business value
- How this helped the team or company (revenue protected, cost avoided, risk reduced, speed, quality)
- Use only real numbers you can stand behind; no invented benchmarks

Clear ask
- Promotion to [level/title] and/or compensation adjustment as appropriate in our process
- Why now (scope + sustained proof + timing relative to cycle)

Proposed timeline / next check-in
- What I’ll do next if “not now”
- Date to revisit with updated evidence

Sample spine (fictional, labeled sample, not a benchmark): Taylor drafts: owned onboarding revamp across two teams; cut time-to-first-PR for new hires on their team (internal measure they track); partner feedback from Eng and Support on clearer handoffs; ask is promotion discussion aligned to H2 cycle; revisit date if deferred. No salary percentages presented as “the market.”

Steps inside the 45-60 minutes

  1. Minutes 0-10: Scope. Write role-today vs. role-then in bullets.
  2. Minutes 10-30: Evidence. Pull from your feedback log, 1:1 notes, shipped work, and outcomes. Prefer three strong proofs over twelve weak ones.
  3. Minutes 30-40: Business value + ask. One clear ask. One timeline.
  4. Minutes 40-50: Edit tone. Remove comparisons to named peers’ pay, threats, and sarcasm.
  5. Minutes 50-60: Book or confirm the meeting. Send a short purpose note. Do not paste the whole packet into Slack without context.

Feed this outline over time with the Ask for feedback play and steady 1:1s. Surprise packets land worse than stories managers already recognize.

Scripts

Open the conversation (no instant-yes demand):

I’d like to walk through a short case outline for [promotion / compensation discussion] and get your read on gaps. I’m not asking for an answer in this meeting – I want us aligned on evidence and timing relative to our process.

If they ask for the headline:

My ask is [promotion to X / a compensation review for expanded scope], based on [one-line impact]. Happy to go section by section.

“Not now” follow-up:

Thanks for the clarity. To make the next check-in useful, what evidence or scope change would you need to see by [date]? I’ll send a one-page update two weeks before we revisit.

Handle “not now” without burning the relationship: curiosity, concrete gaps, calendar the revisit. See also career conversations with your manager and how promotions and leveling work.

Output

A 1-2 page case doc plus a calendar note for the conversation and a proposed revisit date. Bring the doc to the meeting; don’t read it like a speech.

Watch-outs

  • Peer pay gossip as your primary case. Risky, often against policy, and weak evidence of your impact.
  • Threats in the first ask. “Match this or I quit” turns coaching into combat.
  • Ignoring cycle rules. Ambushing outside process can stall you even with strong work.
  • Invented market numbers. If you use external data, label sources carefully and expect your company to use its own bands.
  • Ambush timing. No hallway case pitches.

HR/comp literacy belongs as education: how cycles, bands, and leveling tend to work varies. Your handbook and HR partner beat any generic article. Start at How HR works and your internal policy.

You’re done drafting when a manager could coach the evidence without decoding your frustration, and your ask fits one sentence.