At a glance
| Document type | Employer letter template |
|---|---|
| Issued by | Employer |
| Templates included | 5 ready to use versions |
| Download format | Word (.docx) |
| Statutory reference | None cited on this page |
| Last reviewed | 26 August 2026 |
| Maintained by | Engage HR editorial team |
Appreciation letter, commendation on record and a reward
These three get used as though they were the same gesture. They differ in what the organisation is committing to, and picking the wrong one either overpromises or underdelivers.
| Appreciation letter | Commendation on record | Reward or spot bonus | |
|---|---|---|---|
| What it is | A written note naming a contribution and its effect. | A formal entry in the employee file, usually approved above the reporting manager. | Money, leave or a benefit given for a specific contribution. |
| Who issues it | The reporting manager, or a function head for cross-team work. | HR, on the recommendation of the manager and an approver. | Whoever holds the budget, on an approved recommendation. |
| Does it affect anything later | Only as context. It carries no weight of its own. | Yes. It is visible at appraisal, in promotion cases and in disciplinary history. | Yes, and it is a payroll or benefit event with its own tax treatment. |
| Turnaround expected | Days. It loses most of its value after a fortnight. | Weeks, because it goes through an approval. | One payroll cycle, and the employee will notice if it slips. |
| Where it goes wrong | Sent so routinely that nobody reads it. | Promised verbally and never recorded. | Announced before the approval is in place. |
Standard appreciation letter format
An appreciation letter is short by design. Six parts, and the whole thing fits on one page.
- Header. Company letterhead, date, employee name, employee code and designation. The employee code matters because this ends up on a file.
- Opening line. What the letter is for, in one sentence, naming the work rather than the quality.
- The specifics. The project, account, period, incident or figure. This is the paragraph that carries the letter, and the one most drafts skip.
- The effect. What the contribution produced for the customer, the team or the business. One or two sentences.
- The acknowledgement. A plain statement that the organisation has noted it. No conditions, no requests, no forward-looking targets.
- Signature block. Name, designation, and a copy line showing who else has received it and where it has been filed.
Keep it to one page. A two-page appreciation letter is usually a project summary with a compliment at the top, and the employee reads it as the former.
5 letter templates
Appreciation Letter for project or release delivery
The general case. The detail that makes it work is the constraint the person delivered under, not the delivery itself.
[Company Name] [Company Address] Date: [Date] To [Employee Name] Employee code: [Employee Code] Designation: [Designation] Department: [Department] Subject: Appreciation for your contribution to [Project Name] Dear [Employee Name], I am writing to record our appreciation for your work on [Project Name], which went live on [Go Live Date]. You took ownership of [Specific Workstream] after [Circumstance, for example a change in scope or the loss of a team member], and carried it through to delivery within the original date. Specifically, you [Named Contribution, for example rebuilt the reconciliation logic and cleared the backlog of [Number] open defects before the cut-over]. You also [Second Named Contribution]. The result was that [Stated Effect, for example the migration completed with no customer downtime and [Team or Function] was able to start on schedule]. Work of this kind is visible to us and is noted on your record. Thank you. With appreciation, [Manager Name] [Designation] [Company Name] Copy to: [Function Head Name], Human Resources Filed to: employee record, [Employee Code]
Appreciation Letter for team or group appreciation
Address it to the team but name individuals inside it. A group letter with no names in the body is the version people forward once and forget.
[Company Name] [Company Address] Date: [Date] To The [Team Name] team [Department] Subject: Appreciation for [Event or Period] Dear team, I am writing to thank the [Team Name] team for the way you handled [Event or Period, for example the [Quarter] close, the [Customer Name] escalation, or the [Season] volume peak]. Between [Start of Period] and [End of Period] the team handled [Volume or Workload Measure] against a normal load of [Baseline Measure], and did it while [Constraint, for example running one person short or working through a platform migration]. Several contributions are worth naming. [Name One] [what they did]. [Name Two] [what they did]. [Name Three] [what they did]. [Name Four] [what they did]. The outcome was [Stated Effect, for example every case closed within the committed response time, with no escalation reaching the customer]. This has been noted with [Function Head Name] and a copy of this letter goes to each of your records. With appreciation, [Manager Name] [Designation] [Company Name] Copy to: [Function Head Name], Human Resources
Appreciation Letter for long service or work anniversary
The risk here is a letter that could have been generated from a date field. Name something from the period, or do not send it.
[Company Name] [Company Address] Date: [Date] To [Employee Name] Employee code: [Employee Code] Designation: [Designation] Date of joining: [Date of Joining] Subject: [Number] years with [Company Name] Dear [Employee Name], This month marks [Number] years since you joined [Company Name] as [Joining Designation]. I want to record our appreciation for that. Over this period you have moved from [Joining Designation] to [Current Designation], and taken on [Named Expansion of Scope, for example ownership of the [Region] territory and responsibility for [Number] junior colleagues]. Along the way you [Named Contribution from the period, for example built the [Process or System] that the whole function now runs on]. What people who work with you consistently say is [Specific Observation, for example that you will pick up an unowned problem rather than route it]. That is not a small thing over [Number] years. Thank you for the time you have given this organisation, and for the way you have given it. With appreciation, [Signatory Name] [Designation] [Company Name] Copy to: Human Resources Filed to: employee record, [Employee Code]
Appreciation Letter for customer save or service recovery
Use this where someone took a situation that was going badly and turned it. Say what the situation was, including that it was going badly.
[Company Name] [Company Address] Date: [Date] To [Employee Name] Employee code: [Employee Code] Designation: [Designation] Department: [Department] Subject: Appreciation for your handling of the [Customer Name] situation Dear [Employee Name], I am writing to record our appreciation for how you handled [Customer Name] between [Start Date] and [End Date]. The account came to you after [Circumstance, for example a failed implementation and a written complaint from the customer's [Role]]. You [Named Action, for example took the calls yourself for [Number] consecutive days, published a daily written status, and rebuilt the [Deliverable] over a weekend]. The customer's [Role] wrote on [Date of Feedback] to say [Summarised Feedback]. The account has since [Outcome, for example renewed for a further [Term] and agreed to act as a reference]. Recovering an account in that state is harder than winning a new one, and it is noticed here. With appreciation, [Manager Name] [Designation] [Company Name] Copy to: [Function Head Name], Human Resources Filed to: employee record, [Employee Code]
Appreciation Letter for work outside the role
For contributions with no line in the job description: mentoring, an internal tool, running the committee nobody volunteered for.
[Company Name] [Company Address] Date: [Date] To [Employee Name] Employee code: [Employee Code] Designation: [Designation] Department: [Department] Subject: Appreciation for [Named Contribution] Dear [Employee Name], I am writing about work you have done that sits outside your role, and which I did not want to pass without a written note. Since [Start Date] you have [Named Contribution, for example run the induction sessions for every new joiner in [Department], built and maintained the [Tool or Tracker] the team now depends on, or served on the [Committee Name] and handled [Specific Responsibility]]. This has taken roughly [Time Commitment, for example [Number] hours a month] on top of your own workload, and it has produced [Stated Effect, for example [Number] new colleagues brought to productive work faster, or a manual process removed from [Number] people's week]. None of it appears in your job description. All of it has been useful, and it is on record. With appreciation, [Manager Name] [Designation] [Company Name] Copy to: [Function Head Name], Human Resources Filed to: employee record, [Employee Code]
What it has to contain
| Element | Why it matters |
|---|---|
| The specific work, named | This is the whole letter. A named project, account, period, incident or figure is what tells the reader the letter was written about them. Without it the document is interchangeable, and employees can tell within one line. |
| The effect the work had | Recognition without consequence reads as politeness. Saying what the contribution produced for the customer, the team or the numbers is what makes it recognition of a result rather than of effort. |
| The date, and a date close to the event | The letter is a record, so it needs a date on it. It also needs to arrive while the connection to the event is still live. Recognition that reaches someone two months later is read as an administrative task someone finally got to. |
| Employee name, code and designation | The letter goes on a file. Without the identifiers it cannot be matched to the right record, and a letter that cannot be filed correctly is a letter that stops existing when the manager leaves. |
| A signature with a designation | Who is doing the appreciating changes what the letter means. A note from the direct manager and a note from the function head are different signals, and an unsigned circulation reads as neither. |
| A copy line | Recognition that only the recipient sees does half its job. Copying the reporting line and HR is what puts the contribution in front of the people who make decisions about the person later. |
How to write one
- Decide whether a letter is the right response. Ask what the person is actually owed. If the contribution warrants money, a title or a corrected workload, a letter sent instead of those things reads as a substitute. Send the letter alongside the right response, not in place of it.
- Write down the facts before writing the letter. List the project, the dates, the constraint, what the person did and what it produced. If that list comes out empty, the appreciation is about a general impression, and a letter is the wrong vehicle for one.
- Name the constraint the person worked under. Delivering on time is ordinary. Delivering on time after the scope changed and the team shrank is not. The constraint is usually the part that makes the contribution worth a letter, and the part drafts leave out.
- Cut every conditional sentence. Remove anything that reads as a request, a target or a hint about what comes next. An appreciation letter with an ask in it converts into the ask, and the appreciation is discounted.
- Send it within the week. Set a working rule that a letter goes out within five working days of the event it recognises. Beyond that the letter still gets read, but it stops feeling like a response and starts feeling like an exercise.
- Copy the reporting line and file it. Send a copy to the function head and to HR, and attach it to the employee record. This is what makes the contribution visible at appraisal, in a promotion case, or to a manager who inherits the person a year later.
- Say it out loud as well. Tell the person before or as the letter arrives, and where it is appropriate, say it in front of the team. A letter that arrives with no conversation attached reads as documentation rather than as thanks.
Why most appreciation letters do not work
The failure is almost always the same one. The letter describes a person rather than an event.
A letter that says someone is committed, hardworking and a pleasure to work with tells the reader nothing they did not already know about how the sender feels, and nothing at all about what happened. Because the same sentences would fit any employee in the organisation, the recipient reads the letter as a category rather than as a message, and the effect is closer to receiving a form than to being thanked.
The fix is mechanical. Take the draft and delete every sentence that does not contain a proper noun, a number or a date. What remains is the letter. If nothing remains, the sender does not actually know what the person did, which is a different problem and one a letter will not solve.
The second failure is volume. Recognition works on scarcity: a letter means something because it is not sent every week. Organisations that run recognition as a monthly quota discover within two cycles that people have stopped reading them, at which point the genuine letter and the routine one are indistinguishable.
Appreciation letters and the appraisal record
An appreciation letter carries no formal weight. It is not an entitlement, it does not bind the employer to anything, and by itself it does not change a rating, a band or a pay decision.
What it does is supply evidence. Appraisal conversations run on what the manager can remember and what the file can show, and both are weaker than people assume nine months after the event. A dated letter naming a specific contribution is the thing that survives a reorganisation, a change of reporting line, and the ordinary fading of memory.
That is an argument for filing rather than for sending more. Two well-documented letters on the record are worth more to an employee at appraisal than a dozen generic ones sitting in an unsearched inbox.
It also cuts the other way. Where an organisation has issued appreciation letters to someone whose performance is later said to be inadequate, the letters are part of the record too. That is not a reason to withhold recognition. It is a reason to make sure the letter says what was actually good, rather than making a general claim about the person. It is also a reason to raise performance concerns when they arise, instead of letting them build up quietly alongside the praise.
Signatories and the copy list
The signature is part of the content. The same words mean different things depending on where they come from.
A note from the direct manager says that the person closest to the work noticed it. That is the most common and usually the right signature, because it is the one with the detail behind it. A note from a function head or a business head says the contribution was visible two levels up, which is a stronger signal and should be used sparingly enough to stay strong.
Cross-functional work is the case people handle worst. Where someone from another team carried the work, the letter should come from the person who benefited, and it should be copied to that person's own manager. A letter of thanks from a team the employee does not report to is the only way that contribution reaches their record at all.
On copies, the working rule is: the recipient, their reporting manager, the function head where the contribution was visible at that level, and HR for filing. Wider circulation is a separate decision. Announcing recognition to a whole department is effective and also public, and some people find it uncomfortable. Where there is any doubt, ask.
Cadence, and how to keep the currency
The practical question most organisations get wrong is how often. There is no correct number, but there are two failure modes with recognisable symptoms.
Too rare, and recognition becomes an event so unusual that receiving one is awkward and not receiving one is read as a judgement. The symptom is that people can name who got the last letter and when, across the whole department.
Too frequent, and it becomes administration. The symptom is that people cannot remember whether they received one this quarter.
A workable approach is to tie letters to events rather than to a calendar. Something happened, it was outside the ordinary run of the job, and it is worth a written note. That produces an uneven distribution over time, which is correct, because contributions are unevenly distributed over time. It also removes the pressure to find someone to recognise in a quiet month, which is where the generic letters come from.
One caution about running this through a recognition platform. The tooling makes sending easy, and easy sending drives volume up until the currency is spent. Where a platform is used, it is worth keeping the written letter as a separate, rarer instrument from the points, badges and peer nudges, so that the two do not collapse into one another.
Common mistakes
| Mistake | Why it causes trouble | What to do instead |
|---|---|---|
| Praising qualities instead of work | "Your dedication and positive attitude are valued" could be sent to anyone in the company. Employees read it as a template, and it lowers the value of every later letter from the same signatory. | Replace every adjective with a fact. Name the release, the account, the shift, the number. If no fact survives the edit, do not send the letter. |
| Attaching a request to the appreciation | A letter that thanks someone for a delivery and then mentions the next deadline turns into the deadline. The recognition is read as the setup rather than the point. | Keep the letter to what has already happened. Anything about future work goes in a separate conversation on a different day. |
| Sending appreciation where money or a title was expected | Where someone has carried a vacant role for months, a letter reads as the organisation acknowledging the debt and declining to settle it. This produces more resentment than silence would have. | Deal with the substantive claim first. Once that is settled or has a date, the letter is welcome rather than insulting. |
| Automated or bulk recognition | Letters generated from a milestone field, or sent to everyone on a project regardless of contribution, teach people the letters mean nothing. After that, a genuine one cannot be distinguished from the noise. | Cap the volume. If a manager is sending these monthly to the same team, the bar has drifted and the currency has already been spent. |
| Never filing it | The letter lives in one inbox. When the manager moves on, the record of the contribution goes with them, and the employee has to argue their own history at the next appraisal. | Copy HR on every letter and attach it to the employee record as a matter of routine, not as a favour. |
| Recognising the visible contributor only | The person who presented the work gets the letter and the two people who did the difficult part get nothing. This is noticed immediately by everyone except the sender, and it is corrosive. | Before sending, ask who else touched this and what they did. Name them in the letter or send them their own. |
Frequently asked questions
What should an appreciation letter to an employee include?
The employee's name, code and designation, the date, the specific work being recognised with its project name or period, what that work produced, a plain acknowledgement, and a signature with a designation. Everything else is optional, and the specific work is the part that carries the letter.
How long should an appreciation letter be?
One page, and usually less. Four short paragraphs is enough: what the letter is for, what the person did, what it produced, and thanks. Longer letters tend to be project summaries with a compliment attached, and they read that way.
Does an appreciation letter carry any legal or contractual weight in India?
No. It creates no entitlement to money, promotion or continued employment, and no statute requires or governs it. Its value is evidential and cultural: it records a contribution on the employee file, where it is available at appraisal or in a promotion case.
Should an appreciation letter go on the employee record?
Yes. A letter that stays in one inbox disappears when the manager or the employee changes teams. Copying HR and attaching the letter to the employee record is what makes the contribution visible to whoever assesses the person later.
Who should sign an appreciation letter?
Usually the reporting manager, because they have the detail. A function head or business head signature is a stronger signal and should be kept for contributions visible at that level. For cross-functional work, the letter should come from the team that benefited and be copied to the employee's own manager.
Can an appreciation letter be sent by email?
Yes, and email is usually better because it is faster and it creates its own record. Send it as the body of the message rather than as an attachment nobody opens, and copy the reporting line and HR on the same message.
How is an appreciation letter different from a reward or bonus?
A letter acknowledges. A reward transfers something of value and is a payroll or benefit event with its own approval and tax treatment. Sending a letter where a reward was warranted reads as a substitute, which is the most common way appreciation backfires.
How often should managers send appreciation letters?
Tie them to events rather than to a calendar. If a manager is sending them on a monthly schedule to the same team, the bar has drifted and people have stopped reading them. Uneven timing is correct, because the contributions that warrant a letter are unevenly spread.
Keeping recognition on the record in Engage
Engage attaches appreciation letters to the employee record instead of leaving them in a manager's mailbox. The contribution stays visible when the reporting line changes, and it is there at the next appraisal without anyone having to search for it. Managers can see what has already been sent to a person and when, which is the check that stops recognition drifting into a monthly routine.
Book a demo