Few conversations make managers more nervous than “I would like to talk about my salary.” The request is normal, and how you handle it affects trust, retention and fairness across your team. This guide answers the questions managers ask most: what to do first, how to check whether the request is reasonable, and how to give a clear answer, even when it is not the one the employee hoped for.
What should I say in the moment?
Do not agree, refuse or improvise numbers on the spot. Thank the person for raising it, ask them to explain their case, and agree on a date for your answer. Something like: “I am glad you brought this up. Tell me what you have in mind, and I will come back to you by Friday of next week.” Listening first shows respect and buys you time to prepare.
How do I prepare?
- Understand the case. Is it about performance, a bigger role, the market, or a personal cost-of-living squeeze? Each calls for a different answer.
- Review the evidence. Look at recent results, scope growth, feedback and the last salary change.
- Check the process. Find out what your company allows outside the regular review cycle and who must approve.
How do I benchmark the request?
Compare the salary against three things: the pay range for the role, what peers on your team earn for similar work and performance, and external market data from salary surveys. Use ranges, not single numbers, and consider location and experience. If the person is paid well below the market, the request may be justified even without a performance change. If they are already at the top of the band, the honest conversation is about promotion, not a raise.
How do budget and pay bands affect my answer?
Know how much room you have before you reply. Check the salary band for the role, the person’s position within it, and whether your department has unspent budget. A raise inside the band is usually a simple approval. A raise above the band needs a case for promotion or an exception, and a plan for the people paid the same. Never promise what you cannot approve; a promise you later retract does more damage than a clear no.
How do I say yes, not now or no?
Saying yes
Be specific: the new amount, the effective date, and what it reflects. Put it in writing and thank the person for their work. Do not hint that the raise is a favour.
Saying not now
This is the most abused answer, so make it concrete. Explain the real constraint, such as a frozen budget or the review cycle, and agree on measurable goals and a date to revisit, for example in three months. “Maybe later” with no date is a polite no, and employees can tell.
Saying no
Be direct, kind and clear on the reason: the pay is already competitive, the scope has not changed, or the budget does not allow it. Then say what would change the answer, and offer a path forward. Avoid comparing the person with colleagues or citing their private circumstances.
What timeline is reasonable?
Acknowledge the request within two working days, and give your answer within one to two weeks. If approval takes longer, say so and update the employee anyway. Silence is read as refusal.
What should I document?
- The date of the request and what the employee said.
- The evidence and benchmarks you used.
- The decision, the reasons and any agreed follow-up.
Short, factual notes protect both sides, keep your reasoning consistent over time, and help the next manager who inherits the file.
What if I cannot raise the salary?
Money is not the only lever, but offer alternatives only if they are real and not a substitute for a conversation. Options include a one-off bonus, a clearer promotion path, training or certification budget, flexible hours or remote days, extra leave, a stretch project with visibility, or a defined date for a salary review. Ask what the person values most; the answer is often surprising.
How do I keep it fair?
Decide on criteria first and apply them to everyone: role, performance, scope, experience and market position. Check who has asked and who has not; the people who ask loudest are not always the ones most underpaid. Compare the outcome with similar roles to catch gaps by gender, ethnicity or tenure before they become pay equity problems. Many jurisdictions now require pay transparency, so assume that someone will eventually compare numbers.
Tools that help
A spreadsheet works for a small team. If you manage more people, a system like FulcrumGrid HR Suite can keep salary history, review notes and approvals in one place, so each decision is documented and comparable. The tool does not make the decision, but it makes a fair one easier to prove.
Listen first, check the facts, decide against clear criteria, and give a timely answer with a next step. Even a no handled this way keeps trust intact.
Frequently asked questions
Should I give a raise to keep someone who threatens to leave?
Rarely as a reflex. Counter-offers can reward ultimatums and upset colleagues. If the person is truly underpaid, fix it on the merits, ideally before they have one foot out the door.
How often can employees ask for a raise?
There is no fixed rule, but once or twice a year is typical. Outside the regular review, a significant change in responsibilities or market pay is a fair reason to reopen the topic.
What if the employee quotes a colleague's salary?
Do not confirm or discuss another person's pay. Focus on their own role, band and performance, and explain how pay decisions are made in general.
Is it acceptable to offer a bonus instead of a raise?
Yes, when the issue is temporary or the budget is capped, but be honest that a bonus is not a permanent increase. It should not replace a fair base salary for sustained work.
FulcrumGrid HR Suite
Keep pay decisions fair and documented
FulcrumGrid HR Suite helps you track salary history, review notes and approvals in one place, so every pay conversation starts from the facts.