What do you write in a work anniversary card for an employee?

Pick one specific contribution from the past year (or the relevant year tier) and name it directly. "Thank you for the way you rebuilt the onboarding process in your first quarter" beats "thank you for your hard work" because it tells the employee you actually noticed. If you can't think of a specific, ask their previous manager or a senior teammate for one before you write the card — it's worth the extra step.

How do you congratulate an employee on a 5-year work anniversary?

Reach back into year two or three by name. A five-year milestone earns more than a one-year-style line, because the employee has seen reorgs, manager changes, and at least one bad quarter. Name a specific moment from earlier in their tenure that you genuinely remember, then connect it to the standard they set now. "The migration you led in 2022 is the reason we didn't have to redo it last year" works because it spans the half-decade.

Should work anniversary messages be public or private?

Both, but for different reasons. The private note from the manager is where the specific, slightly vulnerable observation goes — the contribution you've been quietly ignoring, the thing only you noticed. The public version, in a team channel or all-hands, exists to tell the rest of the team why this employee deserves recognition. They're different messages; don't try to make one do both jobs.

What's a good 1-year work anniversary message for a new employee?

Name one moment in the past twelve months when they were unmistakably the right hire, and signal that year two is where the role grows. Avoid "welcome to the team" energy — they're a year past that. "You came in promising you'd untangle the data pipeline, and you did" works because it references a specific commitment they kept.

What should you avoid writing in a work anniversary message?

Avoid anything that could be copy-pasted to a different employee without changing a word — "thank you for your hard work and dedication," "we appreciate everything you do," "you're a valued member of the team." Avoid framing it as a LinkedIn post (the audience is one person, not a feed). And avoid summarising long tenure as "a decade of dedication" — pick one anchor moment per five years instead.

How should a manager handle a 10-year work anniversary differently?

Long tenure deserves specificity per era, not summary. A ten-year employee has worked through at least two manager changes and probably one reorg — name the anchor moment only you (or a previous manager) witnessed, and acknowledge the institutional memory they carry. The honest line "the version of this place without you would be a different place" beats "a decade of dedication" by a wide margin, because it's true and it's specific.

All articles

Workplace & Recognition

52 Work Anniversary Messages for an Employee (Manager Voice)

Sarah Whitfield

May 23, 2026

Most work anniversary messages a manager sends to a direct report land somewhere between an HR template and a LinkedIn post — and the employee can tell which one it is by the second sentence. "Thank you for your hard work this year" reads as a calendar reminder fired off between meetings. "Thank you for the way you took over the Atlanta onboarding when nobody else could" reads as someone who actually pays attention. The 52 lines below are written manager-to-employee, segmented by year tier and by use case (team-wide announcement, the card the team adds to, the contribution you've been ignoring), and they all assume the same thing: specificity is the whole game.

Start a group card in 30 seconds

Free. No signup needed.

Jump to section9 sections

The corporate-filler test

One quick filter saves most of these messages. Read the line you're about to send and ask: could this exact sentence be sent to any of the eleven other people on the team without changing a single word? If yes, it isn't a work anniversary message — it's filler with the employee's name pasted at the top. The fastest way out is to name one thing they did that you specifically remember. Not an abstract trait. A moment, a project, a meeting, a save.

The second filter is the LinkedIn test. If the line reads like it could be screenshot and posted publicly as evidence of your good management, the employee will quietly mark it as performance rather than recognition. The audience for a work anniversary note is one person. Write it that way.

The lines below all pass both filters in their structure — but the version you actually send needs your own specifics dropped in. The brackets and italics in the lists below are where to do that work.

1-year work anniversary messages (settled in, finding their stride)

The first year is the hardest one to write well because the employee is still proving things and still uncertain whether they're nailing it. A good 1-year message does two jobs: it names a specific moment from the last twelve months where they were unmistakably the right hire, and it signals that the next year has room to grow into. Avoid "welcome to the team" energy — they're past that.

One year in, and the thing I keep coming back to is the way you handled [that escalation in March]. You weren't six months in, and you handled it like someone who'd been here three years. Happy first anniversary.
Happy 1-year. The shift I've watched in you between month three and now isn't subtle — you stopped asking permission for the right things and started asking it for the right ones.
It's been twelve months and your [weekly design review prep] is now the standard the rest of the team measures themselves against. That's a rare first-year arc. Congrats on year one.
One year. You came in promising you'd figure out the [data pipeline] mess and you did. Thanks for not letting me forget you'd said it out loud.
Happy first work anniversary. The honest review: you've moved from "shows promise" to "team relies on you" faster than anyone I've onboarded in three years. Year two is where you stretch.
One year in. The moment I stopped worrying about whether you'd land it was [the customer call in July] — you handled a question I would have fumbled. Glad you're here.
Year one. You've earned the part of this job where you stop checking with me on the things you already know the answer to. Lean into that this year.
Happy 1-year — the team is better at [code review etiquette] than it was before you joined, and that's a thing you did on purpose. Don't think I missed it.

5-year work anniversary messages (a half decade is specific)

Five years is a real number. The person has seen at least one reorg, at least one bad quarter, probably one manager change. The 5-year message should reach back far enough to prove you actually remember — pick a project from year two or three by name, not a vague "so much you've contributed." If you have to invent the specific, you don't know them well enough to be sending this, and you should ask their previous manager for one before you write.

Five years. The shortlist of things you've quietly held together in that time would be longer than this card, but at the top of it is [the migration in 2022] — the version of this team that didn't fall over that quarter is the version you built.
Happy 5-year anniversary. You've outlasted two of my managers and one of yours, and the thing that hasn't changed is the standard you set for what "done" means around here.
Five years in. The promotion you're due is the one I've been chasing for you since [the Q3 review last year]. The half-decade earns you the seat at the table, finally.
Five years. I've watched you grow from [the new engineer asking about logging conventions] into the person juniors quote when I'm not in the room. That's a rare arc, and the credit is yours.
Happy 5-year. You were here when this team was four people and you'll be here when it's twenty. The DNA of how we work is partly yours.
Five years. The half-decade lines I keep wanting to write all sound like a LinkedIn post — so instead I'll say the real thing: [the way you trained Maya] changed what this team is capable of, and nobody outside of us will ever know that. I do.
Half a decade. I owe you a longer conversation than this card has room for, and we'll have it this week. For now: thank you for the five years, and for being the person on the team I can ask a question I don't know the answer to.

10-year and 15-year work anniversary messages

Long-tenure messages are the easiest to write badly, because the temptation is to summarise — "a decade of dedication" — which is exactly the line they've heard from every manager before you. Don't summarise. Pick one specific thing per five years and name it. A ten-year employee can hold three or four anchor moments; pick the one only you witnessed.

Ten years. I wasn't here for the first seven, but I've been told, more than once, that [the way you handled the 2017 acquisition integration] is what kept half this team from quitting. That kind of contribution doesn't show up in any review system, and I want you to know it's seen.
A decade. You've worked for three managers, two CTOs, and outlasted the org chart twice. The continuity in this place is partly because you decided not to leave.
Happy 10-year. The institutional memory you carry is a real asset — not in a flattering way, in a measurable one. Onboarding times for senior hires drop when you're on the welcoming committee.
Ten years. The thing nobody else can name about you anymore is the one I want to: [your refusal to ship anything that hadn't been load-tested] shaped the engineering culture here. The juniors don't know it came from you. I do.
Fifteen years. The half of this company I've watched you mentor — directly or by accident — is somewhere north of forty people. That's a number worth saying out loud.
Happy 10-year — the version of this place without you in it would be a different place, and I don't mean that as a compliment to anyone other than you.
Ten years and counting. The honest version of this card: you're the person on this team I most don't want to lose. I won't say it again in front of you, but I wanted it in writing once.

The contribution you've been quietly ignoring

Every team has a person whose most valuable work doesn't show up in the dashboard. They unstick other people. They write the doc nobody asked for. They make the meeting half as long. The work anniversary is the one moment of the year you can name that work out loud without it being weird, and the employee almost always knows you've been overlooking it. This is the section that's slightly contrarian about how recognition usually works — the celebrated work isn't always the most important work.

Year [three]. The thing I should have said two years ago: the [runbook] you wrote in your first six months has saved this team more hours than any project anyone's been promoted for. Thank you for writing it. I owe you for not naming it sooner.
Happy work anniversary. The unglamorous truth is that you're the reason on-call doesn't ruin people's weekends anymore. That's not in any of your goals. It should be.
Year [four]. You're the person juniors come to before they come to me, and that's been true for at least two years. I've watched it happen. The investment you make in other people's work shows up everywhere except your performance review, which I plan to correct.
Happy anniversary. The work you do in [the weekly architecture review] — calmly disagreeing with senior engineers without it turning into a thing — is the highest-leverage skill on this team, and I'm not sure it's ever been said to you in writing. So: it's said.
Year [two]. The fixes you ship that don't have your name on them — because you handed the PR to someone else to merge — are visible to me even when they're invisible to everyone else. Thank you for the generosity.
Happy work anniversary. I want to name a thing nobody else will: the way you handle [the difficult stakeholder in Sales] has prevented at least two derailments I know of. That kind of work doesn't trend on Slack. It should.
Year [six]. The reason new hires ramp faster on this team than the company average is because of the documentation culture you built before anyone called it that. I'd like that on the record.
Happy anniversary. The honest version: half of what gets celebrated in this team gets celebrated because the foundations you laid in [2021] made it possible. The foundations don't get applause. I'm applauding them now.

For a team-wide announcement (the message that travels well)

Sometimes the work anniversary message has a second audience: the team Slack channel, the all-hands, the company-wide newsletter. These lines need to do something specific that a private note doesn't — they need to tell the rest of the team why this employee deserves the recognition, in a way that doesn't sound like inside baseball but also doesn't sound like a press release. Keep one named contribution at the centre. Cut every word that could apply to anyone else.

Three years ago today, [Priya] joined this team — and most of the reason our incident response is now thirty per cent faster than it was is because she rewrote the runbook in her first quarter and nobody's needed to rewrite it since. Happy work anniversary.
Marking five years today for [Daniel], who is the reason the design system exists, the reason the design system is documented, and the reason juniors stop asking me about colour tokens. Half a decade and still the most generous reviewer on this team.
A year today for [Sam]. The shortest version of what she's done in twelve months: she walked in, fixed the analytics pipeline in her second week, and has been quietly fixing other things ever since. Year one in the books.
Today is [Marco's] 10-year work anniversary. For those joining in the last eighteen months: the on-call rotation that works is the one he designed. The deploy process that works is the one he designed. He'd hate me saying it, which is partly why I'm saying it.
Two years for [Aisha] today. In that time she's onboarded six engineers, two of whom now run their own teams. We don't have a metric for that and we should.
Marking seven years today for [Tom]. The shortest accurate sentence: nothing on the SRE side falls over in a way it would have fallen over in 2018, and that's mostly his work. Happy anniversary.
Today is [Hannah's] 1-year work anniversary. The thing I'll say publicly that I've already said privately: she was a better hire on day three hundred than she looked on day one, which is the right direction for the curve to bend. More to come.

Short lines for the card the whole team adds to

When the whole team is signing one card alongside your manager-level message, your line is one of many. The shape changes: the team's lines are usually the longer, warmer ones, and the manager line lands cleanly when it's short, dignified, and specific in one beat. Eight to fifteen words is the right range. Save the paragraph for the private message you send separately.

Year [five]. Best hire on this team. Thank you.
Three years. The team is a better team for it.
Happy work anniversary. Glad I get to manage this work with you.
One year. You've earned every bit of it. Year two starts now.
A decade. The version of this place without you doesn't exist for me.
Year [four]. The standard you set is the standard the team meets.
Happy anniversary. The promotion conversation we're about to have is overdue.
Year [two] in. The bet I made hiring you is paying back every quarter.

General manager-voice lines (for any milestone)

For the cases where the year doesn't matter as much as the message — the employee who's between milestones, or the one whose anniversary you almost missed and want to mark anyway. These work as standalone notes, as Slack DMs, or as the opening line of a longer message you tailor below.

The thing I most appreciate about managing you is the thing I shouldn't have to write down — but for the work anniversary, here it is: I trust your judgement on the calls I can't see.
The work you do is good. The reason I keep this job is partly because the work you do is good. Happy anniversary.
You make me a better manager by being a clear, generous, slightly impatient employee. I'll take that trade every year. Happy anniversary.
The shortest review I can write of your tenure here: you do what you say you'll do, and the rest of the team has started copying it. Thanks for the year.
Happy work anniversary. The line I won't put in your formal review is that you're easier to manage than I deserve, and I notice.
You've been here long enough that I've stopped framing things as "new" with you. That's a milestone. Happy anniversary.
The work anniversary message I'd write if I had more time would name [the specific thing] from [the specific month]. For now, the short version: I see it, I value it, and we'll talk this week.

Turn it into a group card

A work anniversary message from a manager lands harder when it isn't the only message the employee gets. The team they've worked alongside for a year, five years, or a decade has things to say that you don't — the specific moments only their desk neighbour saw, the inside jokes from the project you weren't on, the gratitude juniors carry because they were mentored without realising. Your manager note sits at the top; the team's notes do the work underneath.

A free anniversary ecard makes that practical even when the team is split across three time zones and two offices. One link, sent to everyone the employee has worked with this year, and each person writes their own line on their own time — none of the desk-to-desk paper card awkwardness where half the team is missing because they're remote or out that day. You can create a card online — and the same pattern works for retirement milestones when the work-anniversary becomes a retirement card in a couple of minutes, set delivery for the morning of the anniversary, and let people contribute asynchronously.

If you're the one organising for a direct report, seed the card with your own message first — pick a line from the year-tier section above and personalise it with the actual specifics from their last twelve months. The team will write something proportionally honest in response. For the wider case where recognition isn't tied to a year-count but to a habit, the employee recognition piece covers why the team-signed card outperforms the manager email for almost every milestone. And if you're trying to build the culture of recognition that makes anniversaries land easier in the first place, a multi-signer group ecard for the team is the cheapest experiment to run.

Frequently asked questions

What do you write in a work anniversary card for an employee?: Pick one specific contribution from the past year (or the relevant year tier) and name it directly. "Thank you for the way you rebuilt the onboarding process in your first quarter" beats "thank you for your hard work" because it tells the employee you actually noticed. If you can't think of a specific, ask their previous manager or a senior teammate for one before you write the card — it's worth the extra step.
How do you congratulate an employee on a 5-year work anniversary?: Reach back into year two or three by name. A five-year milestone earns more than a one-year-style line, because the employee has seen reorgs, manager changes, and at least one bad quarter. Name a specific moment from earlier in their tenure that you genuinely remember, then connect it to the standard they set now. "The migration you led in 2022 is the reason we didn't have to redo it last year" works because it spans the half-decade.
Should work anniversary messages be public or private?: Both, but for different reasons. The private note from the manager is where the specific, slightly vulnerable observation goes — the contribution you've been quietly ignoring, the thing only you noticed. The public version, in a team channel or all-hands, exists to tell the rest of the team why this employee deserves recognition. They're different messages; don't try to make one do both jobs.
What's a good 1-year work anniversary message for a new employee?: Name one moment in the past twelve months when they were unmistakably the right hire, and signal that year two is where the role grows. Avoid "welcome to the team" energy — they're a year past that. "You came in promising you'd untangle the data pipeline, and you did" works because it references a specific commitment they kept.
What should you avoid writing in a work anniversary message?: Avoid anything that could be copy-pasted to a different employee without changing a word — "thank you for your hard work and dedication," "we appreciate everything you do," "you're a valued member of the team." Avoid framing it as a LinkedIn post (the audience is one person, not a feed). And avoid summarising long tenure as "a decade of dedication" — pick one anchor moment per five years instead.
How should a manager handle a 10-year work anniversary differently?: Long tenure deserves specificity per era, not summary. A ten-year employee has worked through at least two manager changes and probably one reorg — name the anchor moment only you (or a previous manager) witnessed, and acknowledge the institutional memory they carry. The honest line "the version of this place without you would be a different place" beats "a decade of dedication" by a wide margin, because it's true and it's specific.