How do you say no to a raise request without the employee quitting?

Be direct about the no, specific about the reason (a closed budget cycle, a frozen comp window), and concrete about the path forward. Give a date, name the criteria, and follow up in writing. Employees leave when they feel managed around, not when they hear a real constraint with a real plan attached.

What do you say when you can't give someone a raise they deserve?

Say something like: 'You are right that your output this year justifies this conversation. I cannot approve 15% right now because our comp window closed in March. Here is what I can do: I will formally document this for the January cycle and I want us to agree on the criteria that make the case airtight.' Name what they did specifically, name the constraint specifically, and give them a next step with a date.

How do you respond to an employee asking for a raise you cannot approve?

Do not stall, do not over-promise, and do not make it abstract. Acknowledge the request, state the constraint clearly, and offer a specific path. If the next review cycle opens in January, say January. If there is something you can offer now, like a title change or a one-time bonus, name it. Then ask if there is anything beyond the number you should know about. Sometimes a raise request is really about something else.

How to Say No to a Raise Request When You Can't Afford to Lose the Person

Say no clearly, explain the real constraint, and give Devon a specific path to yes. That sequence is the whole job.

Devon walks into your 1:1 on a Tuesday, and somewhere between the project update and the Q3 numbers, he says it. He wants 15%. He has earned it. You know it, he knows it, and the market knows it. Your hands are tied. Maybe the budget cycle closed in March. Maybe headcount is frozen. Maybe your own boss said no new comp adjustments until January. The reason almost doesn't matter, because what Devon hears in the next 4 minutes will determine whether he starts taking recruiter calls.

This is where most managers fail. Not because they say no, but because of how they say it. They get vague. 'I'll see what I can do.' They deflect. 'It's really a budget thing, out of my hands.' They over-promise. 'I'm fighting for you, I promise.' Devon leaves the room with nothing concrete, no timeline, no criteria, no reason to stay. He updates his resume that night not because you said no, but because you gave him nothing to hold onto.

The hard truth is that a clean, honest no, paired with a real path forward, lands better than a soft maybe. Devon is a strong performer. He can handle directness. What he cannot handle is feeling managed.

Practice this conversation before you have it. The sim below puts you in the room with Devon right now.

Free practice. No signup.

Try it: Declining a raise request

Devon, one of your strongest performers, just asked for a 15 percent raise you cannot approve right now. You do not want to lose him. Respond.

Devon just asked you for 15% and is sitting across from you right now. You have about 30 seconds before silence becomes awkward. Do not stall, do not soften, do not over-promise.

Type your answer here. Say it out loud first if you can, then type what you said.

0/2000

How to Open Without Stalling

Priya, a team lead at a logistics firm in Atlanta, once told her report Marcus, 'I really appreciate you bringing this to me.' Marcus heard that as a prelude to a no and mentally checked out before she finished the sentence. Appreciation openers signal bad news. Devon already knows that.

Open with acknowledgment, not gratitude. There is a difference. 'Devon, you're right that your output this year justifies this conversation' is acknowledgment. It names what he did. It does not perform warmth to soften a blow. Then get to the constraint fast. Within 30 seconds. Do not build up to it.

Say something like: 'I can't approve 15% right now, and I want to tell you exactly why and what comes next.' That single sentence does 3 things. It gives him the answer. It signals you have a real reason, not a runaround. And it signals there is a next. Devon needs a next.

What to Actually Say

Here is the structure, in plain language, with the kind of phrasing that works.

First, name the constraint specifically. Not 'budget issues.' Something like: 'Our comp adjustment window closed in March and the next one opens in January. I do not have discretionary authority to move outside that cycle.' Devon may not love it, but he can verify it. It is real. Vague reasons feel like excuses. Specific ones feel like walls, and walls are something a person can plan around.

Second, name his value explicitly. 'You closed 4 of our top 6 accounts this quarter. That is not a small thing, and I am not pretending it is.' Numbers matter here. If you say 'you've been doing great work,' that is noise. If you say '4 of 6 top accounts,' that is a fact. Devon knows you actually looked.

Third, give him a real path. 'Here is what I can do. I will document this conversation, flag your request formally for the January cycle, and I want us to agree on the 2 or 3 things that make the case airtight by then.' This is not a promise. It is a plan. Plans have steps. Steps give people a reason to stay in the room.

If there is something you can offer now, say what it is. A one-time bonus. An extra week of PTO. A title change that positions him for the next level. Not as a substitute for the raise, but as a signal that you are not just managing him out of the conversation.

The Mistakes That Cost You Good People

Jordan, a VP at a fintech startup in Austin, thought he handled it well. He told his top engineer the raise was 'definitely on the table for next quarter.' The engineer waited. Next quarter came. Nothing. He resigned in October, 2 weeks before the holiday sprint. Jordan lost 6 months of institutional knowledge and paid a recruiter $18,000 to replace him.

The 4 mistakes managers make in this conversation:

Over-promising to soften the no. 'I'm going to fight for you' means nothing without a specific action attached to it. Devon needs to know what fighting looks like. A calendar invite to a comp review meeting is fighting. A vague promise is noise.
Making it abstract. Saying 'the company just isn't in a position right now' puts Devon in a passive relationship with a faceless institution. He came to you. Keep it between you 2.
Skipping the ask. Strong managers end this conversation with a question. 'Is there something beyond the number that I should know about? Is this about comp, or is something else going on?' Sometimes a 15% ask is actually about feeling undervalued. Sometimes it is about a competing offer Devon has not mentioned yet. You need to know.
Not writing anything down. Send Devon a short recap after the meeting. 'As we discussed, I am formally documenting your compensation request for the January cycle. Here are the 3 criteria we agreed on.' That email costs you 5 minutes. It costs him nothing and gives him something to hold.

The Close

Devon is not asking for a miracle. He is asking to be seen. Say no with precision, give him a real timeline, and leave him with something specific to work toward. That is how you keep a strong performer through a freeze. The managers who lose people in these moments are almost never the ones who said no. They are the ones who said nothing that mattered.