Work Anniversary Message Examples, Sorted by Who's Sending and Which Year It Is

A good work anniversary message names one specific thing the person did in the past year, says why it mattered, and looks forward briefly. Keep it to two to four sentences. Tenure is the occasion, not the compliment: "You rebuilt our onboarding flow" lands; "Happy 3 years, thanks for all you do" doesn't.

Below you'll find copy-paste examples sorted first by who is sending the message (manager, peer, leadership, HR) and then by milestone (first year, five, ten, twenty-plus), plus remote employees and short LinkedIn comments. Every example has placeholders in brackets; the one-line note under each tells you what to put there so it doesn't read like a template.

What makes a work anniversary message land

Almost every anniversary message fails in the same way: it could have been sent to anyone. The fix is not warmer adjectives, it's evidence. One concrete contribution, named precisely, tells the recipient that someone actually noticed their work, which is the whole point of marking the date in the first place.

A simple structure works for nearly every sender and every milestone:

1. 1The occasion in a few words: "Happy two years on the team."
2. 2One specific contribution: a project, a decision, a habit, a moment. Name it.
3. 3Why it mattered: who it helped, what it changed, what it made easier.
4. 4A short forward look (optional): something you're glad they'll be around for.

If you can't think of a specific contribution, that's useful information. Spend five minutes looking at their last few months of work (closed tickets, shipped projects, Slack threads where they unblocked someone) before you write. If you manage them and still can't find anything, the anniversary is a signal to schedule a proper conversation, not just send a card.

Manager to direct report

A manager's message carries the most weight because it's the closest thing to an official record of how the person is seen. It should be the most specific message they receive that day. Send it privately first, then decide whether a public mention is also appropriate; the private note is the one that matters.

• "Happy two years, [Name]. The way you handled the [client/project] escalation in [month] is still the example I point new people to. I'm really glad you're on this team."
• "[Name], three years today. You took [process] from something we all dreaded to something that just works, and nobody asked you to. Thank you. Looking forward to what you do with [upcoming project]."
• "Happy anniversary, [Name]. This year you moved from doing the work to shaping how the team does it, especially [example]. That shift is exactly what I hoped for when we talked about growth last spring."
• "Four years, [Name]. I've relied on your judgment more than you probably realize, most recently on [decision]. Thanks for being the person who asks the uncomfortable question in the room."

Why it lands: each message references something only this manager would know, and the third ties back to a growth conversation. If you run regular one-to-ones, the anniversary is a natural moment to revisit goals; our list of one-on-one meeting questions has a section on career reflection that pairs well with an anniversary check-in.

Peer to peer

Messages between colleagues can be lighter and more personal than a manager's, and they often mean more precisely because nobody required them. The best peer notes reference a shared experience: a launch you survived together, a habit you've borrowed from them, a time they helped you specifically.

• "Happy work anniversary, [Name]! I still use the [spreadsheet/checklist] you built during [project]. Glad I get to work with you."
• "[X] years! You were the first person who actually explained [system] to me in a way that made sense. I've passed that explanation on to at least three new hires."
• "Happy anniversary. [Launch/quarter] would have gone very differently without you catching [issue]. Here's to more of those saves."
• "Congrats on [X] years, [Name]. Our Tuesday syncs are the most useful half hour of my week."

Why it lands: it's about the working relationship, not the company. A peer doesn't need to evaluate performance, just show that the person's presence makes their own job better.

Leadership to the whole company

When a founder, executive or department head recognizes someone in an all-hands channel or company newsletter, the audience is everyone, so the message also signals what the organization values. That makes specificity even more important: praise for "dedication" teaches nothing, while a named contribution tells the whole company what good work looks like.

• "Please join me in congratulating [Name] on five years with us. [Name] built our first [system] with two people and a deadline, and it still handles [scope] today. Thank you, [Name]."
• "Ten years ago this week, [Name] joined as [original role]. Since then they've [two concrete achievements]. Many of you have been onboarded, mentored or rescued by [Name] at some point. Drop a note in the thread if that's you."
• "This month we're celebrating [Name] ([X] years), [Name] ([X] years) and [Name] ([X] years). One line each on what they've built: [Name]: [contribution]. [Name]: [contribution]. [Name]: [contribution]."

Why it lands: the second example invites colleagues to add their own stories, which turns a one-way announcement into something the person will actually reread. The third shows that batching monthly anniversaries still works, as long as each person gets a real sentence rather than a name in a list.

HR and people team templates

People teams usually send anniversary messages at scale, often automated through an HRIS or recognition tool. Templates are fine here, but build them with a slot the manager is expected to fill. A fully automated message with no human detail is better than nothing only if nobody notices it was automated, which they will.

It's also worth checking which years your program actually marks. Many traditional service-award programs start at five years, which SHRM has pointed out can leave out a large share of younger employees whose typical tenure is shorter. Acknowledging year one and year three, even with just a message rather than a gift, closes that gap at almost no cost.

Email or HRIS notification template

"Hi [Name], happy [X]-year anniversary at [Company]! [Manager name] shared this about your year: '[one specific sentence from manager].' Thank you for everything you bring to [team]. [Details of any milestone benefit or gift, if applicable.] — The People Team"

Heads-up prompt to the manager (sent a week ahead)

"[Name] on your team reaches [X] years on [date]. Could you reply with one sentence on something specific they did this year? We'll include it in their anniversary note. If you'd like to mark it in your next one-to-one or team meeting, now's a good time to plan."

Why it lands: the week-ahead prompt is the real mechanism. It means the manager is never surprised by the date and the employee never receives a message that sounds like it came from a database.

Messages by milestone

Different years carry different meanings. A first anniversary is about settling in; five years is about impact; ten and beyond is about institutional memory and the people someone has shaped. Adjust the emphasis to match, but keep the same rule throughout: name something real, and don't make it about the calendar.

First anniversary

The first year is when someone goes from new to trusted. Acknowledge the learning curve and point to the moment they stopped needing help and started giving it.

• "Happy one year, [Name]! It's hard to remember the team before you joined. [Specific thing] is now something we just count on you for."
• "One year in. You came in knowing nothing about [domain] and now you're the one people ask about [topic]. That's a fast year."
• "Congrats on your first anniversary. Your fresh-eyes question about [process] in month two led to [change]. Keep asking those."

Five years

By five years, someone has usually outlasted several reorganizations and has visible fingerprints on how things work. Name something that exists because of them.

• "Five years, [Name]. A good share of how this team works, from [practice] to [practice], started with you. Thank you."
• "Happy five-year anniversary! I looked back at what you were working on in your first year versus now: [then] to [now]. That's a big arc."
• "Five years of [Name] means five years of [recurring contribution, e.g. the cleanest handoff docs in the company]. We notice, and we're grateful."

Ten years

A decade is long enough that the person has likely trained people who now train others. Recognize the ripple, not just the output.

• "Ten years, [Name]. Some of the best people on this team learned the job from you, and it shows in how they work. Thank you for a decade of that."
• "Happy 10th anniversary. You've seen [Company] through [major change] and [major change], and you've been a steady presence through both. That matters more than a job description can capture."
• "A decade! Share your favorite [Name] story in the thread below. I'll start: [short story]."

Twenty years and beyond

At this stage, the risk is sliding into remarks about age or retirement. Don't. Focus on judgment, relationships and history the person carries, and treat them as someone with a future at the company, not a retrospective.

• "Twenty years, [Name]. When we need to understand why something is the way it is, you're who we ask, and you always have the context and the patience. Thank you."
• "Congratulations on 25 years. You've helped shape [Company] across [number] leadership teams, and your read on [clients/product/customers] is still the one we trust most."
• "[X] years is remarkable, and so is the fact that you're still the one pushing us to try [new thing]. Here's to the next chapter."

Remote and distributed employees

Remote colleagues miss the incidental recognition that happens in an office: the cake in the kitchen, the passing "congrats" in the hallway. That makes the written message do more work, and it makes public acknowledgement in a shared channel more valuable than it would be in person, because it's the only version of the hallway they get.

• "Happy [X] years, [Name]! Working across [time zones] isn't easy, and you've made async collaboration look simple, especially your [written updates/handoffs]. Thanks for keeping us all in sync."
• "Congrats on [X] years. I realized I've never actually been in the same room as you, and you're still one of the people I trust most on this team. That says a lot."
• "Happy anniversary, [Name]! Keep an eye on your mailbox this week." (Pair with a physical card or small gift if your company allows it.)

For a remote team, a short video call where a few colleagues each say one line can replace the office moment. Keep it under ten minutes and make it optional for the person being celebrated; some people would genuinely prefer the written version.

Choosing the channel and the timing

The same words can feel generous in one place and awkward in another. Before you post publicly, consider how the person tends to handle attention. Some people love a busy congratulations thread; others find it excruciating and would much rather have one thoughtful private note from their manager.

Public post vs private note

• Private note (DM, email, card): the default for managers, and the right place for anything reflective or personal. Always send this even if you also post publicly.
• Team channel: good for peers and managers when the person is comfortable being visible. Short, specific, invites others to add their own.
• Company-wide channel or newsletter: best for milestone years (5, 10, 20+) or when batching a month's anniversaries. Ask first if you don't know the person's preference.
• LinkedIn: public to their whole network, including people outside the company. Keep it professional and never reveal anything the person hasn't shared themselves.

Timing

Send it on the day, or the last working day before if it falls on a weekend or holiday. A day late is fine with a light acknowledgment ("I'm a day late, but..."); a week late looks like an afterthought, so if you've missed it, fold the recognition into your next one-to-one or team meeting instead of sending a belated message. Managers should put direct reports' anniversary dates in their calendar with a reminder a few days early, so the specific example isn't written in a rush.

How to avoid the awkward version

Most anniversary missteps come from reaching for something to say when you don't have anything specific. The mistakes below are common enough that it's worth checking your draft against them before you send, especially for longer tenures and public posts.

• Don't mention age or imply retirement. "You've been here longer than some of our interns have been alive" or "Still going strong!" can land badly, especially at 20+ years.
• Don't make it about the company. "Thanks for five years of helping [Company] hit its targets" centers the business. Center the person.
• Don't quantify loyalty. Lines about "sticking with us" can read as a reminder that others left. Praise what they did, not the fact that they stayed.
• Don't reveal private details. Leave out salary, promotions not yet announced, health, family or leave history, particularly in public channels.
• Don't overdo jokes. Humor works between close peers; from a senior leader in a public channel, it's safer to be warm and specific.
• Don't send a template with the brackets still in it. It happens more than you'd think. Read it once more before you hit send.

If the relationship is strained, or the person is currently in a difficult performance conversation, keep the message short and sincere rather than skipping it. A brief "Happy [X] years, [Name]. Thanks for your work on [project]" is honest and appropriate.

Short LinkedIn comment versions

LinkedIn flags work anniversaries based on the start date listed on the person's profile, and the alert now appears in connections' Notifications tab rather than the main feed, with a prompt to send a quick congratulations. Because so many people accept that default, even one extra sentence of detail makes your comment stand out and reads as genuine attention.

• "Congrats on [X] years at [Company], [Name]! Still thinking about your talk on [topic]."
• "Happy work anniversary! [Company] is lucky to have you on [area]."
• "[X] years! Great to see the work you've been sharing on [topic]."
• "Congrats, [Name]. Working with you on [project] was a highlight of my time at [Company]."

If you want to say something more substantial and public about a colleague's work, a LinkedIn recommendation lives on their profile permanently, while a comment disappears into the feed. See our LinkedIn recommendation examples for how to write one that's specific enough to be useful to a future employer.

Replying to anniversary congratulations on LinkedIn

When your own anniversary comes around, you'll get a batch of messages, many of them LinkedIn's auto-suggested text. You don't have to reply to each one individually, but a brief acknowledgement is courteous, and a considered reply to anyone who wrote something personal can reopen a useful professional relationship.

• For auto-suggested messages: a quick "Thanks, [Name]! Hope things are going well at [their company]." is plenty. A thumbs-up reaction is also acceptable.
• For personal messages: match their effort. "Thank you, [Name]. That [project] feels like a long time ago now. How's [their current thing] going?"
• For former colleagues: use it as a reason to reconnect. "Thanks! It's been ages. Would love to hear what you're working on. Coffee next month?"
• For comments on a post you made: reply to the first several individually, then a general "Thank you all for the kind words" is fine.

If you'd rather not be congratulated at all, look under Settings & Privacy, then Visibility, for the "Share profile updates with your network" option, which LinkedIn describes as controlling whether your network is notified about job changes and work anniversaries. Menus change often enough that it's worth checking what's currently there rather than relying on an old guide.

For people teams: turning anniversaries into content

Anniversaries are one of the few recognition moments that arrive on a predictable schedule, which makes them ideal raw material for internal communications. With a light process, each milestone can feed a spotlight post, a newsletter section and a small refresh of the team page, without adding much work for anyone.

Spotlight posts

For milestone years, send the employee three or four short questions a couple of weeks ahead: what they're proudest of, what's changed since they started, one thing they'd tell their first-week self. Combine their answers with the manager's one-line contribution and you have a spotlight post. Our guide to employee spotlight ideas covers the wider recognition formats and has full question banks; this article is deliberately narrower, focused on the anniversary message itself.

A recurring newsletter section

A monthly "Milestones" block, with one real sentence per person, is among the more reliably read parts of an internal newsletter because readers are looking for names they know. If you're building or reviving a newsletter, see our internal newsletter ideas for how to structure recurring sections so they don't go stale.

Refreshed team-page and profile photos

An anniversary is a natural, low-pressure trigger to update someone's photo. Five years is long enough for a haircut, glasses and a whole wardrobe to change, and team pages quietly fill up with portraits that no longer look like the people in them. Offer a photo refresh as part of milestone years, and keep the style consistent with the rest of the page.

For format choices, from individual headshots to group shots, see our staff photo ideas, and for how to lay out the page itself so a mix of old and new photos doesn't look broken, read our guide to team page design. The first helps you decide what photos to take; the second helps you display them.

A simple operating calendar

1. 1Monthly: export upcoming anniversaries from your HRIS for the next 30 days.
2. 2Two weeks before a milestone year: send the employee spotlight questions and ask whether they want a public post.
3. 3One week before: prompt the manager for their one-sentence contribution.
4. 4On the day: manager sends the private note; people team posts or batches the public version.
5. 5End of month: roll the month's milestones into the newsletter and update any team-page photos that were refreshed.

Always ask before publishing. Some employees prefer not to have their tenure broadcast, and respecting that preference is itself a form of recognition.