“How much should I ask for?” is really three questions: what would fair pay look like for this role now, what can this employer’s process fund, and what paycheck change would you actually notice? Collapsing those into a single percent borrowed from a headline survey is how solid performers either undershoot or walk in with a number that no guideline can absorb. This guide owns the number—salary-band position, a defendable range, and paycheck math. For timing, scripts, and what to say in the room, use how to ask for a raise: scripts and timing. Start climate research on average raise percentage and verify arithmetic on the pay raise calculator.

Separate climate from your case

Employer budget surveys describe planned spend on salary increases across populations. They are useful context: tight year, loose year, inflation pressure. They are not a personal entitlement. Your ask should survive removing the survey sentence entirely. If the remaining case is empty—no outcomes, no scope change, no range evidence—you were leaning on climate as a substitute for a case.

When you do cite climate, cite the pillar page and keep the language humble: “Planning averages this cycle cluster around a modest envelope; my request is about scope and band position, not about matching a press-release mean.” That framing sounds adult in a calibration room.

Build the ask from four inputs

1. Range position (salary-band framing). Where does your current base sit relative to the published or known min/mid/max for the job? Comp teams often talk in bands or grades: below midpoint with strong performance often supports a larger percent than sitting near the top of band, and a rate already at or above range max may need a level change rather than a big merit percent. You do not need a national statistic to use this frame—only your employer’s band book or an honest “below / near / above midpoint” answer from HR. If you do not know the band, ask for the range or that midpoint relative before you lock an ask.

2. Scope delta. List responsibilities that did not exist at your last increase: systems owned, people guided, revenue or cost levers, on-call, customer severity. Scope without a title change still supports a merit or equity adjustment; a true level change belongs in promotion framing—see average raise for a promotion.

3. Outcomes. Prefer measured results over adjectives. Shipped projects, error rates, retention of accounts, cycle-time cuts, audit findings closed. Two or three bullets beat a paragraph of soft praise.

4. Process constraints. Merit pools, promotion calendars, and off-cycle rules limit what a yes can look like. How raise budgets are set explains envelopes; knowing them keeps you from treating a locked pool as personal rejection.

Turn inputs into a range, not a dare

A single take-it-or-leave-it percent invites a binary no. A narrow range—say a primary target and a walk-away floor—gives your manager room to advocate. The top of the range should still be defendable with evidence; the floor should still be worth the conversation. Avoid theatrical spreads like “anything from 3% to 25%” that signal you did not do the work.

Convert the range to annual dollars and to your paycheck frequency before you speak. Managers budget in cash. Employees feel stubs. Showing both reduces translation errors.

Qualitative bands with stated assumptions

Without inventing a national “correct ask,” you can still speak in qualitative bands when assumptions are explicit: you are not already at range max, the request is for the current level (not a double promotion), no major off-cycle bump landed in the last few months, and your evidence is recent. Under those assumptions, asks that sit modestly above a quiet merit mean are common for strong contributors; asks that mimic a full level-up without a level case usually fail. Pull cited survey means only from the pillar when you need numbers—never invent them here.

Promotion asks and job-change counters use different ceilings. Internal promotion guidelines and external offer math are siblings, not twins. If your real goal is a level change, say so and model with the promotion raise calculator. If an outside offer exists, switch to negotiate a raise after a job offer rather than forcing an annual-cycle sizing script onto a retention event.

Anchors that backfire

  • Peer gossip without verified ranges.
  • “I need X because of rent” as the only argument (cost of living can be context; contribution still carries merit cases—see cost of living raise vs merit raise).
  • Threatening resignation in the first meeting.
  • Mixing a bonus wish and a base wish into one fuzzy “total raise.”
  • Quoting a tax-bracket myth as urgency—read raise tax bracket explained so you do not undermine credibility.

Timing the number

Before budgets lock, your number competes inside the envelope. After letters draft, you may be negotiating exceptions. Mid-year after a scope spike, you may be asking for a dated path rather than immediate cash. Size can stay similar while the vehicle changes: immediate base, deferred base, or base-plus-documented bonus bridge. Compare levers with raise vs bonus so you do not accidentally trade lasting rate for one check without noticing.

Write it before you say it

Draft the ask in the structure used by how to write a raise request email: purpose, evidence, percent and dollars, meeting logistics. Even if you never send the email, the draft prevents rambling. Bring a one-pager to the live conversation from the scripts guide.

When the answer is partial

A partial yes—lower percent, delayed effective date, or bonus instead of base—still needs math. Recalculate the paycheck view, ask what would unlock the rest, and calendar the follow-up. A vague “we’ll revisit” without criteria is not a deal; a dated checklist is.

Manager-side realism

If you manage others, translate employee asks into pool math before you promise. A fair individual case can still exceed what your envelope allows; the honest move is to escalate with a packet or to offer a path, not to invent a percent you cannot fund. Employees who understand envelopes negotiate better and burn less trust.

Checklist before you name a number

  1. Confirm current base and pay frequency.
  2. Note range position if known.
  3. Write three evidence bullets.
  4. Choose a narrow percent range; convert to annual and paycheck dollars on the pay raise calculator.
  5. Decide whether this is merit, equity, promotion, or retention.
  6. Read climate on average raise percentage without copying it as your ask.
  7. Prepare the live script and the email variant.

Special cases: hourly and variable pay

Hourly raises need an hours assumption. A fifty-cent increase at twenty hours is not the same annual story as at forty. Variable roles should model base separately from expected commission under conservative scenarios. Do not present a stretch-quota fantasy as if it were a guaranteed raise.

Special cases: long tenure at range max

If you are topped out, a large percent may be impossible without a level change or a market redesign of the band. Your ask may need to become a promotion case, a dual-track expert case, or a conversation about bonus and equity instead. Pretending the band is elastic when policy says otherwise wastes political capital.

Bottom line

Ask for a raise amount you can defend with scope, outcomes, and salary-band position—stated as a narrow percent range plus dollars you already verified. Use survey climate as context from the pillar page, not as a personal floor. Hand the finished number to how to ask for a raise: scripts for timing and wording, keep the email draft clean, and switch to promotion or offer-negotiation frames when the vehicle is not plain merit.