Here is how to professionally ask for a raise: request a dedicated meeting, open with a specific number, and back it with documented results from the past year. The documentation is what matters most. It moves the conversation from your assessment of your work to a record of it.

Search this question and a lot of what comes back is about delivery. One of the top-ranking guides tells you to strike the words believe, feel, think, just, only, and might. That advice isn't wrong, but it treats the problem as a delivery problem, which is why it doesn't help the people who need it most.

This isn't really about nerve. You might be nervous either way. It's about what the conversation is made of once you're in it. Without documentation, the ask is your read of your own work sitting across from your manager's read of your work, and there's no way to settle that.

How to professionally ask for a raise: what are the five steps?

Request a dedicated meeting in writing, bring three to five documented results, name a specific number, frame the ask forward, then stop talking. In detail:

Request a dedicated meeting in writing, and name the topic. No ambush, no "got a sec."
Bring three to five documented results, each dated, each with an outcome. Not responsibilities. Results.
Name a specific number, grounded in market data you can cite.
Frame it forward. A case about what the role is worth now, not a grievance about the past.
Ask, then stop talking. Let your manager respond before you soften or hedge.

Why is asking for a raise so uncomfortable?

Because without documentation, the only thing holding the ask up is how strongly you say it.

The not-asking is documented. Pew Research Center found in April 2023 that 60% of US workers who received a new job offer didn't ask for higher pay. That figure is about job offers rather than internal raises, but the reason people gave is worth carrying over: among those who didn't negotiate, 38% said they didn't feel comfortable asking, and for women that figure was 42%.

Pew didn't ask them why they weren't comfortable, so nobody should tell you what that discomfort means. But one version of it is fixable, and it's the version worth naming.

It goes like this. You sit down to prepare, you try to list what you've done this year, and you come up with four things. Two happened in the last six weeks. The rest is a blur of work you know was good and can no longer describe. Now the ask rests on your word for it, so you turn up the conviction, because conviction is the only lever left.

That is what the word-choice advice is trying to fix. It's correcting the volume without asking what turned the volume up.

There's a second thing that keeps people in their seats: the worry that asking will damage how they're seen. The research on negotiation suggests that worry is overstated, though the best evidence comes from a different setting. In a 2024 study in Organizational Behavior and Human Decision Processes, Hart, Bear, and Ren surveyed 1,496 managers about job offers and found roughly 94% of negotiated offers were upheld. That's a hiring finding, not a raise finding, and nobody rescinds your job for asking. What carries over is what the researchers were testing: people consistently overestimate how badly negotiating will land.

None of this makes the nervousness go away. What it does is stop the nervousness from being load-bearing. Once the case is written down, the conversation is about what's on the page instead of how convincingly you deliver it.

What makes a raise request professional instead of just your opinion?

Evidence, a specific number, deliberate timing, and forward framing. What makes those four professional isn't how they sound. It's that they rest on a record instead of on your say-so.

Evidence is the record, and the record is not the same thing as metrics. It's what you did, when you did it, and what changed because of it, in enough detail that someone else can confirm it. Numbers make a case stronger when you have them. Plenty of the work that earns raises doesn't come with any. You absorbed a departing teammate's scope. You're the person the team routes the hard calls to. You unblocked a launch that would otherwise have slipped. That's all evidence. The test isn't whether a figure is attached. It's whether the work exists anywhere other than your memory.

The number is a separate thing: it's what you're asking for. A request without a figure puts the burden of naming one on the person who benefits from it being low. Get it before the meeting rather than from a feeling. Pull comparable postings for your title and your metro, check whatever salary data your industry uses, and if your company publishes pay bands, find where you sit in yours. You'll be asked where the figure came from.

If you give a range instead, assume you'll be offered the bottom of it. So set the bottom at the number you actually want.

Notice that tone isn't on the list. Tone is downstream. When you have those four elements you sound calm, because you have something to be calm about, and because the conversation is about the work rather than about you.

What do you say when you ask for a raise?

Request the meeting in writing, then run the conversation.

The meeting request. Short, specific, no ambush.

"Hi [Manager], I'd like to set up 30 minutes in the next couple of weeks to talk about my compensation. I've pulled together a summary of what I've taken on this year and I'd like to walk you through it and discuss an adjustment. Does [day] or [day] work?"

That names the topic so your manager can prepare, and gives them time to check what's actually possible, which matters because they likely can't approve anything in the room.

The conversation. Open with the ask, then the evidence, then the number. Do not build to it.

"Thanks for making the time. I want to talk about my compensation. Over the past year my scope has grown in a few specific ways, and I'd like to walk you through them and talk about bringing my salary in line with that.

[Three specific items with outcomes. See the next section.]

Based on that, and on what I'm seeing for this scope of role in [where your market data came from], I'm asking for [number]. I'd like to understand how you see it and what the path looks like."

Then stop talking. The silence after a number feels like an eternity and it is doing real work. Filling it undoes what the preparation bought you.

Three things to leave out: your personal financial situation, which isn't an argument about the value of your work; comparisons to specific coworkers' salaries, which put your manager in an impossible position; and the ultimatum, unless you have another offer you're prepared to use.

What evidence should you bring to a raise conversation?

Three to five specific items, each dated, each with an outcome. Not a list of responsibilities. A list of results.

The difference between the two is the difference between an opinion and a record:

Responsibility framing: "I've been handling the client reporting."

Result framing: "I took over client reporting in March. I rebuilt the process, cut the turnaround from five days to two, and it's covered three additional accounts since June without adding headcount."

The second version isn't a better-worded version of the first. It contains information the first doesn't have: dates, scope, a change, and a consequence. That information either exists or it doesn't, and you cannot write your way to it the week of the meeting.

That example has numbers in it. Here's one that doesn't:

Responsibility framing: "I help onboard the new analysts."

Result framing: "When we lost our second analyst in April, I picked up onboarding for both new hires on top of my own book. Both were running client calls on their own by early summer, and the reporting escalations that used to come to me stopped coming at all."

No metrics anywhere in that. It's still evidence, because it's specific, it's dated, and other people were there for it. If you only count the work you can put a percentage on, you will walk into that room with a fraction of your actual case.

Aim for range across your items: one that shows expanded scope, one that shows something measurably changing, one that shows work nobody assigned you. And bring it written down. A one-page summary you can leave behind means your manager can carry your case into conversations you won't be in, which is where compensation decisions usually get made. What they can advocate for is limited by what you hand them.

What do you say when your manager pushes back?

Three responses cover most of it: treat "no budget" as a timing question, pin "let me think about it" to a date, and answer "the impact isn't there yet" with documentation.

"There's no budget right now." Often true. Treat it as timing rather than a no.

"I understand. Can we agree on what the number would be when budget opens, and set a date to revisit? I'd rather plan around a real timeline than check back in every quarter."

"Let me think about it." Fine, as long as it comes with a date attached.

"That makes sense. Can we put 20 minutes on the calendar for two weeks out so it doesn't drift?"

"I'm not sure the impact is there yet." This is the one people fear and the one evidence is built for.

"That's useful, and I'd like to understand it better. Here's what I have documented from the past year. Can you tell me which parts of the role you'd want to see more of? I'd like to be specific about what closes the gap."

That last response only works if you have something to put on the table. Without it, the honest answer is "okay," and the conversation is over.

When is the right time to ask for a raise?

Three windows: within a few weeks of a visible win, six to eight weeks before compensation planning starts, or any time your scope has changed. Raises are usually decided well before they're announced, so ask your manager when planning actually happens and work backward. Avoid the week after a bad quarter, a layoff, or a lost account, not because the ask is wrong but because the answer is predetermined.

What if you don't have any of this documented?

Then this year's ask is going to be harder than it needed to be, and that is worth being honest about.

I spent my first year in corporate America believing the work would speak for itself. It didn't. I sat down in front of a self-evaluation form in December and could not account for eight months of my own effort. I started an Excel sheet after that, and I kept it up for about three weeks, which is roughly how long anyone keeps up a document that requires you to open a laptop and write something professional at the end of a day you're already tired from.

What eventually worked wasn't discipline. It was making the capture small enough that being tired didn't matter.

So do the version you can do right now. Go back through your calendar, your sent mail, and your project tools, and pull whatever you can still reconstruct. It will be less than what actually happened. Use it anyway, because a partial record still beats a feeling in a room where someone has to justify a number.

Then start capturing forward. That's the part that changes the next conversation instead of this one.

That's what impactrackr is built for. You capture a win in about 30 seconds, by voice if you're walking out of a meeting or by text if you're at your desk. The AI turns what you said into professional language across three levels, Original, Polished, and Amplified. It works from what you actually told it and does not invent details, numbers, or outcomes you didn't mention, which matters a great deal when the output is going into a conversation about your salary.

Six months from now, you'll either have a record or you won't. The only variable is whether you start today.

impactrackr is free to use. It takes about 30 seconds to log the first one.

Start free →

How to ask for a raise professionally.