What should you write in a work anniversary message?

One specific thing the person did or does, and what it changed. The anniversary is the occasion, not the content. A message that only mentions the number of years reads as an obligation met. If you can swap the recipient’s name for a colleague’s and the message still works, it isn’t finished.

How long should a work anniversary message be?

One to three sentences is usually right. Length signals effort, but only up to a point: past about four sentences most messages start restating themselves. A short message with a concrete detail beats a long one made of general praise.

Should a work anniversary message be public or private?

Public, in most cases. Recognition posted where colleagues can see it does two jobs at once. It thanks the person, and it shows everyone else what the company treats as valuable. Keep it private if the person has said they would rather not be singled out.

What do you say for a first work anniversary?

Focus on the change. A first year is the biggest visible shift most people go through at a company, from asking where things are to being asked. Naming that arc means more than congratulating the milestone.

Should peers send them, or only managers?

Peers, and it often lands harder. Recognition from someone with nothing to gain by giving it reads as more sincere, and peers see the work managers don’t.

Recognition messages

Work Anniversary Messages: 14 Examples for Every Milestone

A work anniversary message usually congratulates the calendar rather than the person. These are written to name something real.

Why the date is worth more than an automated post

Companies tend to mark the anniversary and stop there. A post goes up, a few people react, and nothing in it tells the person anything they didn’t already know: that they have been employed for a year.

That’s a wasted opportunity rather than a harmless one. A work anniversary is one of the few moments where it is socially normal to tell a colleague what their presence has been worth, and people keep specific praise for a long time. The gap between “Happy 3rd anniversary!” and “you’ve built half of what replaced that spreadsheet” is the difference between a notification and something somebody screenshots.

How to write one that lands

The examples below are grouped by how long the person has been there and who is writing. Edit them. The detail is the point, and the detail has to be yours.

If you’re stuck, answer one of these instead and write that down:

What is this person the go-to for?
What would get slower, or break, if they weren’t here?
What did they do this year that nobody asked them to do?

14 messages you can send

Two years today, Priya. The thing I keep coming back to is how you handle a half-finished brief. You ask the one question everybody else was avoiding. Glad you’re here.
Peer, 1 to 2 years
Names a habit instead of a duration.
Happy work anniversary, Sam. One year of quietly making the Monday standup make sense. 🎉
Peer, 1 year, light
Short and warm, and still points at something only Sam does.
Three years, Marcus. You joined when we were still arguing about the roadmap in a spreadsheet. You’ve built half of what replaced it. Thank you.
Manager, 3 years
Uses shared history the recipient will recognise.
Five years today, Anna. I still think about the week you rewrote the billing tests. Half the team has never seen a billing bug because of it.
Peer, 5 years
Points at a consequence the recipient may not know they had.
Happy first anniversary, Tom. You went from asking where everything was to being the person we ask. That’s a big year.
Manager, 1 year
Describes a change over time, which is what an anniversary is for.
Ten years, Jo. You’ve outlasted three office moves, two rebrands and every version of our CRM. More to the point, you’ve been the person new starters go to on day one, every one of those years.
Manager, 10 years
Earns the length with detail rather than stating it.
Four years today. Thank you for being the person who asks “what does the customer actually see?” in every design review. It changes the answer every time.
Peer, 4 years
Quotes them, which is more specific than describing them.
Happy work anniversary, Elena. Two years of taking the messy problems nobody volunteered for. I notice, even when it isn’t in a ticket.
Manager, 2 years
Acknowledges invisible work, which is what most people want noticed.
Six years, Dan. You’re the reason “ask Dan” is written into four separate runbooks. Sorry about that, and thank you.
Peer, 6 years, humorous
Humour that still contains a real compliment.
One year in, Nadia, and you’ve already changed how we run retros. New people are supposed to take longer than that to leave a mark. 🌱
Peer, 1 year
Frames speed of impact rather than length of service.
Happy anniversary, Chris. Seven years, and you still send the clearest incident write-ups in the company. Newer engineers learn how to think from them.
Manager, 7 years
Connects one habit to its effect on other people.
Three years today. Thank you for the code reviews that make me a better engineer without making me feel like a worse one. That balance is rare.
Peer, 3 years
Names a difficult skill precisely.
Eight years, Laura. You joined this team when it was four people in a corner. Whatever is good about the culture now, you’re most of the reason.
Manager, 8 years
Credits culture, which is usually thanked in the abstract and rarely attributed.
Happy work anniversary, Ben. Two years of picking up the on-call nobody wants over Christmas. It’s noticed, and it matters.
Peer, 2 years
Recognises a specific cost rather than general contribution.

What makes one land

Name one thing. ‘You ask the question everyone else avoided’ does more than ‘you’re a great teammate’, because only one of them could be about a particular person.
Say what it changed. The recognition people keep tells them about an effect they could not see themselves.
Match the length to the relationship. A one-line note from a peer reads as warm. The same line from a manager on a ten-year anniversary reads as an afterthought.
Send it where colleagues can see it. The same words in a public channel are worth more than in a DM, because they also tell everyone else what is valued here.
Don’t save it for the date. A message two days late with something specific in it beats one on the day with nothing.

Questions people ask

What should you write in a work anniversary message?: One specific thing the person did or does, and what it changed. The anniversary is the occasion, not the content. A message that only mentions the number of years reads as an obligation met. If you can swap the recipient’s name for a colleague’s and the message still works, it isn’t finished.
How long should a work anniversary message be?: One to three sentences is usually right. Length signals effort, but only up to a point: past about four sentences most messages start restating themselves. A short message with a concrete detail beats a long one made of general praise.
Should a work anniversary message be public or private?: Public, in most cases. Recognition posted where colleagues can see it does two jobs at once. It thanks the person, and it shows everyone else what the company treats as valuable. Keep it private if the person has said they would rather not be singled out.
What do you say for a first work anniversary?: Focus on the change. A first year is the biggest visible shift most people go through at a company, from asking where things are to being asked. Naming that arc means more than congratulating the milestone.
Should peers send them, or only managers?: Peers, and it often lands harder. Recognition from someone with nothing to gain by giving it reads as more sincere, and peers see the work managers don’t.