Your employee asks about a raise. They deserve one. You know it, they know it. The problem is that you don't set the budget. The number has to go through your boss, or HR, or a compensation cycle that runs twice a year regardless of what you think. So you're stuck in the middle: you can't say yes, you don't want to say no, and you have no idea how honest to be about the constraints you're working under.
Most managers handle this badly. They get vague — "I'll look into it," "let's revisit this at your review," "I hear you and I think you're doing great work." The employee hears none of that as a real answer, which is correct, because it isn't one. They go back to their desk less certain about their future than when they sat down.
There are actually three separate conversations here, and most managers conflate them into one uncomfortable non-answer.
The first is the conversation with your employee. Be direct about what you can and can't control. Something like: "I want to be transparent with you — I don't set the final budget, but I do advocate for my team in the compensation process. Here's what I need from you and here's what I'll do on my end." You're not promising an outcome. You're promising a process, and you're explaining your role in it honestly. That's enough to give someone confidence that they're not being brushed off.
The second is the internal case you build. When raise season comes, or when you get the chance to put names forward, vague endorsements don't move the needle. What works is specificity: the business impact this person has had, what they'd cost to replace, where their compensation sits relative to market, and what the risk is if they leave. Managers who get raises approved consistently aren't the ones with the highest performers — they're the ones who show up to the conversation prepared. Average salary budgets in the US are sitting around 3.5% for 2026 according to Mercer's compensation survey, which means most companies are distributing modest pools. Getting above that for someone requires a deliberate case, not just a good relationship with HR.
The third conversation is the one where you deliver the outcome — whatever it ends up being. If the answer is yes, be clear about what changed and why. If the answer is no, don't hide behind "the company" or "budget constraints" as a faceless explanation. Tell them what you pushed for, where it landed, and what the path forward looks like. "I advocated for X, the approved number was Y, and here's what I'd need to see from you to make the stronger case in the next cycle" is a real answer. It's not a great answer, but it's one they can work with.
The thing managers most want to avoid in this situation is being the bearer of bad news — so they delay, deflect, or stay vague long enough that the employee figures it out on their own. That's the worst outcome. It doesn't protect the relationship; it damages it, because the employee correctly reads the evasion as either incompetence or cowardice.
You don't control the budget. But you control how clearly you communicate, how hard you advocate, and how honest you are when the answer isn't what your employee wanted. That's actually most of what they're asking for.
