How to Ask for a Raise With Data When Your Manager Avoids the Conversation
When your manager keeps rescheduling, going quiet, or changing the subject, the problem usually isn't your case. It's that no one's forcing the conversation to happen on a date.
I spent eleven years building compensation cases for other people before I ever built one for myself. Not as an HR generalist sitting in on exit interviews, but as the person companies hired to figure out who was underpaid and why, then sit across from managers who very much did not want to have that conversation.
I have watched the same pattern play out at a six-person startup and a 4,000-person logistics company: an employee builds a tight, well-sourced case for a raise, schedules time to present it, and the manager just… doesn’t show up for the conversation. Not a refusal. An absence.
Trending Now!!:
That absence is the part nobody prepares you for. Most advice on how to ask for a raise assumes your manager will sit down, listen, and respond, even if the answer is no.
The harder, more common problem is a manager who reschedules twice, answers in vague generalities, or says “let’s revisit this next quarter” for the third quarter in a row. If that’s where you are, the data you’ve gathered isn’t the problem. The delivery system is.
Why managers avoid raise conversations in the first place
Before fixing it, it helps to know what you’re actually dealing with, because the fix is different depending on the cause.
Some managers avoid the conversation because they don’t control the budget and don’t want to admit it. Telling a direct report “I have no authority here” feels like an admission of weakness, so instead they stall. Others avoid it because they agree you deserve more but know the answer from above will be no, and they’d rather not be the messenger twice.
And some avoid it for the most ordinary reason of all: it’s an uncomfortable conversation, and uncomfortable conversations get pushed to the bottom of the list. Difficult conversations about money, performance, or disengagement are consistently among the discussions managers postpone, and pay is near the top of that list because it touches both their authority and the company’s finances at once.
None of these explanations makes the stalling acceptable. But they do tell you where to apply pressure. A manager with no budget authority needs you to go around them, not through them. A manager who’s avoiding discomfort needs a structure that makes the conversation harder to dodge than to have.
Start with the number, not the feeling
The biggest mistake I saw, repeatedly, in five years of running compensation reviews: employees walked into raise conversations with a feeling (“I work harder than Dave”) instead of a number anchored to a source.
Build your number from at least two independent sources, because relying on one makes it too easy to dismiss. Levels.fyi works well for tech, product, and data roles, since it breaks pay down by base, bonus, and equity at a granular level by company and seniority.
Glassdoor and LinkedIn Salary are useful for company-specific or industry-filtered figures outside of tech. Robert Half’s annual salary guide is a solid third source for roles where the first two are thin. Cross-referencing three sources isn’t overkill; it’s what separates “I think I’m underpaid” from “the market range for this role at this level is $X to $Y, and I’m sitting at the bottom of it.”
Then attach your number to leverage, not just the market rate. There’s a real gap between what companies budget for internal raises and what the market will pay to poach you: employers have been planning average annual increases in the 3 to 4 percent range for standard merit cycles, while employees who change jobs entirely have negotiated raises closer to 20 percent by leveraging a competing offer.
That gap is exactly why a manager would rather avoid the raise conversation than have it: the honest internal number is often smaller than what you could get by leaving, and nobody wants to say that out loud. Knowing this doesn’t mean threatening to quit.
It means understanding why the budget conversation feels so uncomfortable to the person across from you, and pricing your ask accordingly: a counter in the 10 to 15 percent range against an internal review is realistic and defensible; a counter modelled on an external offer needs an actual external offer behind it, not a hypothetical one.
Document everything before the conversation even happens
This is the part that matters most once a manager starts avoiding you. If the conversation gets delayed, escalated, or contested later, your case lives or dies on what’s in writing.
Build a one-page case before you ever ask for the meeting. List specific outcomes with numbers attached: revenue influenced, costs cut, projects shipped, processes you built that didn’t exist before you arrived. “Improved team efficiency” is not evidence.
“Cut average ticket resolution time from 36 hours to 11 hours after redesigning the triage workflow in March” is evidence. I’ve sat through more raise denials than approvals where the employee’s case was true but unquantified, and the manager used the absence of a number as cover to say no.
Send a short, dated request in writing, even if you also ask in person. “Hi [name], I’d like to set up 30 minutes to discuss my compensation, ideally before [date]. I’ll bring some context on my recent work and market data for the role” does two things: it puts a timestamp on the ask, and it removes “I didn’t know this was coming” as an excuse later.
Casual, hallway-style raise requests are easy for a manager to half-acknowledge and then forget. A written request with a date attached is not.
What to do when the meeting gets pushed, again
One reschedule is normal. Calendars are chaos and nobody’s holding it against you. Two reschedules with no replacement date is a pattern. Here’s what actually moves a stalled raise request forward, in the order I’d try them.
Re-anchor the ask to a date, not a vibe. Instead of “can we talk soon,” send: “I know things have been busy. Can we lock in 20 minutes this Thursday or Friday to go over my comp request? I’d like to close this out before [specific milestone, like the next budget cycle or your performance review date].” Specific dates are harder to wave off than open-ended ones.
Ask the direct question, in writing, if the meeting keeps slipping. “Is there a reason this is hard to schedule? I want to understand if there’s a budget constraint on your end so I know what to plan for.” This does something important: it gives a manager who has no authority over the budget a graceful way to say so, without it feeling like a confrontation. Often, this single message gets you more honesty in one line than three rescheduled meetings combined.
Use the structure that already exists. If your company has a formal review cycle, anchor your ask to it explicitly rather than treating it as a separate, optional conversation. It’s much harder for a manager to indefinitely postpone something that’s nominally part of a process HR is tracking than to postpone an informal ask that only exists between the two of you.
Loop in HR or your manager’s manager, but frame it as logistics, not a complaint. This is where people get it wrong. Going over your manager’s head to vent about being ignored reads as conflict and tends to backfire. Going to HR or a skip-level to ask, “I’ve requested time to discuss my comp three times over six weeks and haven’t been able to get on the calendar, can you help me get this scheduled?” reads as someone trying to follow process, not someone trying to start a fight. Skip-level conversations exist precisely to surface things that aren’t moving through the normal chain, and using one for a stuck, time-sensitive request is a legitimate use of it, not an end-run.
Set a deadline for yourself, not just for them. If a request has been live for two full review cycles with no real conversation, that’s information. It usually means one of three things: there’s genuinely no budget, and nobody wants to tell you, your manager has deprioritized you specifically, or the team itself has bigger problems than your raise. Any of those is worth knowing on its own terms, separate from whether you get the raise.
A pattern worth recognizing: the data isn’t usually the issue
Roughly 4 in 10 salaried workers in the U.S. haven’t gotten a raise in the past year, and the data on who actually asks is more lopsided than people assume: in one widely cited Federal Reserve survey, only about 13 percent of full-time employees requested a raise at all, but 66 percent of the people who did ask received one.
That 66 percent figure is the one worth sitting with. The bottleneck isn’t usually the strength of someone’s case. It’s that most people never put the case in front of anyone, and when they do, the conversation that should take twenty minutes stretches across two quarters because nobody forces it to happen on a date.
Build the number from real sources. Write it down before you ask. Anchor every request to a specific date instead of a vague window. And if the conversation still isn’t happening after a reasonable number of tries, treat the silence itself as the answer, and decide what you’re going to do about it, whether that’s escalating formally, treating it as a signal to start interviewing, or accepting that this particular manager will never be the one who moves this forward for you.
The data makes your case correct. It does not make the conversation happen. Those are two different problems, and they need two different solutions.
