Asking for a raise works best when you treat it as a business case, not a plea. The strongest position combines three things: a clear record of what you delivered, an outside view of what your role pays, and a meeting scheduled for the purpose. Without those, the conversation drifts into gratitude and vague future promises, which rarely move a number.
The decision point comes first. You can wait for a review cycle and accept whatever adjustment arrives, or you can open the conversation yourself, on your own evidence, before the budget is set. The second option costs preparation time and some discomfort. The first option costs more, because pay decisions are usually made before the review meeting, not during it.
This guide walks through the timing, the research, the script and the follow-through. It also covers what to do when the answer is no, because that outcome is common enough to plan for. Pay is a structural question as much as a personal one, and readers weighing collective options can start with our coverage of the union pay gap, in the 2024 data.
When is the right time to ask?
Ask after a documented win, and before the budget for next year is locked. A completed project, a promotion you covered for, a client you kept: those are the moments when your value is fresh in a manager's mind. The worst windows are the week of a layoff rumor, the day after a mistake, and the middle of your manager's own crunch period.
Timing also means asking early in the cycle. If raises are approved once a year, the people who raised their hands in the months before planning tend to be in the spreadsheet. The people who wait for the meeting are often told the number is already fixed.
How do you build the case before the meeting?
Build a one-page record. List what you did this year, what it changed for the team, and what you took on beyond the original job description. Keep the language factual. "Closed the vendor renewal two months early" beats "went above and beyond."
Then get the outside number. Check public salary data for your role, city and level, and talk to recruiters or peers in comparable jobs. The point is not to demand a match. It is to know whether your current pay sits below the market range, at it, or above it, because each of those leads to a different conversation.
Precision matters here, and so does plain language. Even the Cambridge Dictionary, in its entry on "working", distinguishes a working theory from a tested one, and the same discipline applies to pay: a hunch about what colleagues earn is a working theory, while a documented market range is evidence you can put on the table.
What should you actually say?
Open with the ask, not the warm-up. A workable structure:
- State the request plainly: you want to discuss adjusting your salary to reflect your role and results.
- Give two or three evidence points from your one-page record.
- Name the market range you found and where you sit in it.
- Make a specific request, then stop talking.
The silence after the ask is the hardest part, and it is also where unprepared managers concede the most. Have a fallback ready: if the number cannot move now, ask what would have to be true for it to move, and when that can be revisited in writing.
Two scripts, in compressed form. Direct version: "I'd like to discuss my salary. This year I took on X and delivered Y, and market data for this role puts the range at Z. I'm asking for an adjustment to the middle of that range." Softer version, same spine: "Can we set time to talk about my compensation? I've pulled together my results for the year and some market data I'd like to walk you through."
What if the answer is no?
A no has three useful versions. "No, not now, but here is the path" is a real answer; get the criteria and the date in an email. "No, and I won't revisit it" tells you the ceiling here, which is information about the job, not about you. "No, but here is a title change or a bonus instead" is negotiable on its own terms, and worth costing out before you accept.
Whatever the answer, confirm the conversation in writing the same day. A short email summarizing what was said and agreed protects both sides and turns a hallway chat into a record.
What this means for the broader pay gap
Individual negotiation is one lever, and it is not enough on its own. Pay gaps persist across roles and industries for reasons that have little to do with any one conversation, from opaque pay bands to who gets sponsored for promotion. That is why structural coverage matters alongside career advice: our workplace section tracks the pay data, staffing and scheduling rules that shape what any single negotiation can achieve. Readers in covered roles should also know how overtime and the salary threshold interact with a higher salary, since a raise can change exemption status.
And when the problem crosses from pay into conduct, the playbook changes entirely. If the resistance to your advancement takes the form of harassment, the relevant guide is workplace harassment: what crosses the line and what to do next, not a negotiation script.
The takeaways
Prepare a one-page record, get an outside number, ask before the budget closes, make one specific request, and get every answer in writing. If the answer is no with a path, work the path. If it is a ceiling, treat that as data about the job and weigh your options, including the collective ones, with the same discipline you brought to the ask.
