Salary Review Outcome Email to an Employee: 8 Templates
The short answer
A salary review outcome email states the decision in the first line, gives the numbers (current, new, effective date), explains the reason in one or two sentences, and names the next decision point. When there is no increase, give the real reason and a dated next review, not vague reassurance. Follow with a conversation.
Eight copy-paste templates for a salary review outcome email to an employee: raise, small raise, no raise, off-cycle, promotion and pay band.
On this page
- 01When should you send a salary review outcome email?
- 02What should a compensation review email say?
- 03What does a good salary review email look like in practice?
- 04Template 1: Increase awarded
- 05Template 2: Increase below expectation
- 06Template 3: No increase this cycle
- 07Template 4: How do you tell a strong performer there is no raise this year?
- 08Template 5: Off-cycle salary adjustment
- 09Template 6: Promotion with a raise
- 10Template 7: How do you explain a pay band to an employee?
- 11What should you do if there is no reply?
- 12How do you keep outcome emails consistent across a whole team?
- 13Where AI Emaily fits
A salary review outcome email to an employee is the written record of a decision that matters a great deal to one person and that you have probably made many times. That gap in weight is where most of these emails go wrong. They are either padded with warm filler that hides the number, or so clipped that the employee reads the cold tone as the real message.
Below are eight templates covering the cases you will actually meet: an increase, an increase smaller than expected, no increase, no increase for a strong performer, an off-cycle adjustment, a promotion with a raise, a pay band explanation and a follow-up when nothing comes back. Each uses the same placeholders: [CURRENT], [NEW], [EFFECTIVE DATE], [BAND POSITION] and [NEXT REVIEW].
When should you send a salary review outcome email?#
Send it after the conversation, not instead of it. For anything other than a plain increase at or above expectation, tell the person live first, in a one-to-one, and use the email as the written confirmation within the same day. Learning a no-raise decision from an email arriving in the inbox is the fastest way to turn a disappointing outcome into a trust problem.
For a straightforward increase, email is fine as the first notice, as long as it lands before any payroll change shows up. Nobody should discover their new salary from a payslip.
Timing matters more than polish. Send outcomes on a day when you can take a follow-up conversation, which usually means not at 5 pm on a Friday. If outcomes go to a whole team, send them in one window so nobody spends a weekend wondering what colleagues already know.
What should a compensation review email say?#
Every version in this post is built from the same five parts. If a draft is missing one, the employee will ask about it in a reply, and you will have written the email twice.
| Part | What goes in it | What to avoid |
|---|---|---|
| Decision | The outcome in the first sentence: increase, no increase, or adjustment | Opening with praise or context before the answer |
| Numbers | [CURRENT], [NEW], percentage if useful, [EFFECTIVE DATE], and the pay period it first appears in | Rounding, ranges or leaving the date open |
| Reason | One or two sentences tied to performance, scope, budget or band | Referring to unnamed higher-ups or vague company circumstances |
| Position | [BAND POSITION] where your company uses bands, and what moves it | Quoting other people's pay or hinting at it |
| Next step | [NEXT REVIEW] date, what will be assessed, and who to talk to | Open-ended promises such as 'we will look at this again soon' |
What does a good salary review email look like in practice?#
Three habits separate a good one from a forgettable one. First, it is short. Anything above roughly 200 words for a plain outcome means the reasoning is hiding something or the email is doing the manager's emotional work.
Second, it does not apologise for the decision or reopen it. 'Unfortunately' and 'I am sorry' belong in the conversation. In writing they read as a door left open that the employee will push on.
Third, it is the same email you would be comfortable having read out in a pay equity review. Pay decisions are subject to anti-discrimination rules, and the written reason should be one you can defend on its merits. The U.S. Equal Employment Opportunity Commission lists equal pay among the types of discrimination it covers, linked from its employers page (as of October 2026), and the Department of Labor's Wage and Hour Division covers wage rules such as overtime and minimum wage. This post is not legal advice, so check local rules if you are unsure.
Template 1: Increase awarded#
Use this when the raise is at or above what the employee expected. Keep it plain. Do not turn a good outcome into a speech.
Template 2: Increase below expectation#
Use this when you know the number is lower than the person hoped for, whether because they asked for more or because last year's rise was bigger. Name the gap rather than pretending it is not there.
Template 3: No increase this cycle#
Use this when budget, a freeze or band position means nobody in the group is getting a rise. The email should not read as a judgement on the individual if it is not one, so say that clearly.
Template 4: How do you tell a strong performer there is no raise this year?#
This is the hardest version, because the real reason is often uncomfortable. It might be that the person is already above the band maximum for their level, or that budget went to another group, or that the company froze pay. Whatever it is, say it.
Vague reassurance is what damages trust here. 'We really value you and hope to do more next year' tells a strong performer nothing, and strong performers have options. Give the actual reason, state what is and is not in your control, and name the next decision point with a date.
If the reason is that they are at the top of their band, the honest message is that the route to more pay is a bigger role, not a better performance in the same one. Say so, and say what the path looks like. Do not promise a promotion you cannot approve.
Do not promise what you cannot approve
Template 5: Off-cycle salary adjustment#
Use this for a mid-year change outside the normal review: a market correction, a retention adjustment or a scope change that does not warrant a new title. The key is explaining why it is happening now, and what it means for the next scheduled review.
Template 6: Promotion with a raise#
Use this when title and pay change together. State the title first, then the pay, because the employee will read both and wants to see them paired. If the team announcement is going out separately, say when.
Template 7: How do you explain a pay band to an employee?#
Employees often ask where they sit and what moves them, and a vague answer feeds speculation. This is the follow-up to send when someone asks. It explains the structure without disclosing anyone else's pay.
What should you do if there is no reply?#
Silence after a pay outcome rarely means acceptance. After a no-raise or below-expectation email, it usually means the person is thinking, upset or job-hunting. Do not read it as agreement.
Wait two working days for a reply to a good-news email, and send nothing at all if the person is on leave. For a difficult outcome, do not wait for an email response. Book the conversation in person the same day.
Template 8 is the short check-in for when the outcome email gets no response and no meeting has happened. It does not chase a reaction. It offers a time.
How do you keep outcome emails consistent across a whole team?#
The practical risk of review season is not one bad email. It is that eight emails written over three days drift: one explains the reason, another does not, one gives the effective date and the others forget. Employees compare notes, so inconsistency reads as unfairness even when the decisions were fair.
A short checklist helps more than a longer template. Before sending, confirm that each email states the decision first, has all five placeholders filled, gives a reason you could repeat to the person's face and names a dated next step.
- Fill every placeholder before sending, and search the draft for any remaining square brackets.
- Check the effective date against what payroll has actually been told.
- Have someone in HR or finance confirm [NEW] and [BAND POSITION] before the email goes out.
- Keep a copy of each sent outcome with the date of the conversation that preceded it.
Where AI Emaily fits#
Outcome emails are repetitive in structure and sensitive in content, which makes them a poor fit for a fully automatic tool and a good fit for one that drafts and waits. We build AI Emaily, and its drafting works from reply templates and the Personal Context you write yourself, so a saved outcome template can fill in the employee, the figures and the date for each person.
Each draft stays in review until you approve it. Nothing about a pay decision is sent without you reading it, and you can edit a draft the way you would edit anything you wrote yourself. It does not decide the number, the reason or the tone for you. AI Emaily offers a 7-day free trial on Pro and Autopilot, with a card required.
Frequently asked
See it in AI Emaily
Keep reading
Sources
Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.