For an employee
Employees can tell the difference between recognition and a template with their name dropped in. An appreciation letter that actually lands names the specific work, not the job title — what they did, what it cost them, and what it meant for the team. Here's how to write one that doesn't read like HR copy.
Write a letter"Great job on Q3" tells an employee you noticed a number, not their work. People remember the late nights, the problem they solved that no one else saw, the way they held the team together during a hard stretch — and they notice when none of that shows up in the letter meant to thank them for it.
Specific recognition also does something generic praise can't: it tells the employee exactly what to keep doing, because you've named the actual behavior that mattered.
Name the moment, not the role. "You stayed late three nights in a row to fix the launch bug" says more than "you're a great engineer" ever could, because it proves you were watching.
Then say what it meant beyond the task itself — for the team, for a client, for you personally as their manager. That's the sentence they'll remember.
Not their general competence — the actual project, decision, or moment where their work made a visible difference.
Effort, time, a hard conversation they had, a risk they took. Naming the cost is what makes the recognition feel earned rather than automatic.
Tell them what their work meant for the team, the client, or the company — the effect that outlasted the task itself.
A few lines to borrow when the blank page feels heavy.
You rewrote the whole proposal the night before it was due, without being asked, because you knew it wasn't good enough yet. That's the kind of standard that's impossible to teach and rare to find.
For a project well done
You're the person everyone on this team quietly relies on, and I don't think you hear that often enough. This team runs the way it does because of the work you do without anyone noticing.
For steady, quiet work
Answer these and you are most of the way to a letter.
What specific project, decision, or moment made you want to write this?
What did it cost them — time, effort, a risk, a hard call — that most people wouldn't see?
What effect did their work have beyond the task itself — on the team, a client, or you?
Name a specific contribution rather than a general compliment, mention what it cost them in effort or risk, and connect it to its wider impact on the team. Specificity is what separates recognition from a form letter.
One real example of their work, an acknowledgment of the effort behind it, and a clear statement of the impact it had. Skip generic praise like "great job" — name the actual thing.
Match your normal working relationship with them. A closer relationship can carry warmth and informality; a more distant or senior relationship calls for something closer to formal. Either way, specificity matters more than tone.
Yes. Answer three questions about their specific contribution and its impact, and Saidto writes a letter in your voice — free to try, with tones ranging from warm to formal.
Answer three honest questions about their work, and Saidto turns it into recognition they'll actually remember.
Write a letter →