# Celebrate milestones without it feeling automated
> How to mark work anniversaries and birthdays with consent, a manager’s own note and a card the team signs, so the day feels noticed, not scheduled.
Audience: HR leads and managers at growing companies
Canonical: https://shuffl.ai/playbooks/celebrate-milestones
A message from a bot that says “Happy 3rd work anniversary!” tells someone a database noticed. Recognition people remember tends to come from people: when Gallup asked employees who gave them their most memorable recognition, 28% named their manager and 24% a senior leader or CEO.[^gallup-recognition-2016]
So let a tool handle the dates and the reminders, and let people write the words. This playbook covers consent, which milestones to mark and how, and how to make managers’ notes easy to write.
## Why it matters
Median tenure with a US employer was 4.1 years in January 2026, and 20.6% of wage and salary workers had been with their employer a year or less.[^bls-tenure-2026] Many people won’t reach a fifth anniversary with you, which makes the first one count.
Only 22% of US employees say they get the right amount of recognition.[^gallup-2024-retention] A milestone is a moment you already know is coming. It’s an easy one to get right.
**Milestones come sooner than you think**
- 4.1 median years with their current employer, US wage and salary workers, January 2026[^bls-tenure-2026]
- 20.6% had been with their employer a year or less[^bls-tenure-2026]
- 28% named their manager as the source of their most memorable recognition[^gallup-recognition-2016]
## Ask first, and keep the details small
This isn’t legal advice. Birthdays are personal data, and a birth year reveals age. In the US, for example, the Age Discrimination in Employment Act protects people aged 40 or older from age discrimination,[^eeoc-age] which is one more reason not to collect the year at all. Check the rules where you employ people.
- Ask before you share anything beyond a private note, and ask separately for birthdays and anniversaries.
- Make no the easy answer. Nobody should have to explain it.
- Collect a birthday’s month and day only. Never import it from payroll and never ask for the year.
- Keep ages and exact dates out of public posts. Years of service are usually fine.
- Let people change their mind any time, and cancel anything still scheduled when they do.
## The plan
- Fix start dates first. Rehires, acquisitions and contractors who converted often have the wrong one. Decide whether anniversaries count from the latest start or the first hire.
- Decide what each milestone gets. Every year: a private note and a manager message. First year and every fifth: a team card or a post in a channel, if the person agreed.
- Give managers a heads-up a week before, with the date and a prompt for what to write.
- Ask teammates to sign a shared card in the week before. Keep it a surprise until the day.
- Send on the day, in the person’s own time zone, during their working hours.
- Never post as the manager. The note only counts if they wrote it.
## An example
A 150-person company turns on anniversaries and birthdays. About 60% of people agree to share their anniversary in #general, and about 40% their birthday. Everyone else gets a private note only.
Before launch, HR finds 12 people from an acquisition whose start dates all read the same day, and fixes them. Each week about three anniversaries come up. Managers get a heads-up a week ahead with a prompt; most write two or three lines about something the person did that year.
For a fifth anniversary, eight teammates sign a card. The person opens it on the day and replies in the thread to thank each of them by name.
## Common mistakes
- Posting birthdays in a public channel without asking first.
- Storing birth years, or showing ages, when the day is all you need.
- Celebrating from a wrong start date after a migration or acquisition.
- A templated message with no human note from the manager.
- Treating a fifth anniversary the same as a second.
## A manager’s anniversary note
```text
Happy [N] years, [name].
One thing from this year I keep thinking about: [a specific piece of work and what it changed].
Something I’ve seen you get better at: [a skill or habit].
What I’m looking forward to with you next year: [a project or goal].
Thank you for [one line in your own words].
```
## Do this in Shuffl
1. Open Celebrations from the HR workspace and pick a starter, such as Private anniversary notes. It fills in the settings; nothing is turned on yet.
2. Under Start dates, choose whether anniversaries count from the latest start date or the first hire date, and fix the dates listed as looking wrong.
3. On each card, choose who hears about it: a private note to the person only, also a post in a Slack channel, or also a message to each of their teammates. Shared posts go out only for people who chose Share it.
4. Write the message with {name} and {years}, or {name} for birthdays, and choose the send time.
5. Check Preview, then choose Turn on. Managers get a Slack heads-up a week before each shared day, and teammates are asked to sign a card.
6. Use Upcoming to see the next 60 days and whether each person’s day is shared or private.
Guide: [Celebrate work anniversaries and birthdays](https://shuffl.ai/docs/markdown/celebrations)
- [For administrators](https://shuffl.ai/docs/celebrations#administrators)
- [Start dates](https://shuffl.ai/docs/celebrations#start-dates)
- [Who sees what](https://shuffl.ai/docs/celebrations#who-sees-what)
- [For managers](https://shuffl.ai/docs/celebrations#managers)
## Common questions
### Should we celebrate birthdays at all?
Ask. Some people love a channel post and some would rather nobody knew. Make sharing a birthday opt-in, ask separately about anniversaries, and keep a private note for everyone who says no.
### Which anniversaries deserve more?
Usually the first year and every fifth. Every year can get a short private note and a message from the manager; the bigger years get a team card or a channel post.
### Is it fine to store employees’ birthdays?
Not legal advice, but a good default is to collect only the month and day, never the year, and only from people who choose to share it. Check data protection rules where you employ people.
## Glossary
- [Work anniversary](https://shuffl.ai/glossary/work-anniversary)
- [Employee recognition](https://shuffl.ai/glossary/employee-recognition)
- [Employee experience](https://shuffl.ai/glossary/employee-experience)
- [Belonging](https://shuffl.ai/glossary/belonging)
## Related playbooks
- [Build a recognition habit that lasts](https://shuffl.ai/playbooks/markdown/recognition-habit)
- [Plan a new hire’s first 90 days](https://shuffl.ai/playbooks/markdown/first-90-days)
- [Handle a leaver well](https://shuffl.ai/playbooks/markdown/when-someone-leaves-well)
## Sources
[^gallup-recognition-2016]: Gallup, “Employee Recognition: Low Cost, High Impact”, June 2016, updated January 2024. https://www.gallup.com/workplace/236441/employee-recognition-low-cost-high-impact.aspx Employees were asked to recall who gave them their most meaningful and memorable recognition. The page gives no sample size or dates for that survey.
[^bls-tenure-2026]: US Bureau of Labor Statistics, “Employee Tenure Summary”, September 24, 2026. https://www.bls.gov/news.release/tenure.nr0.htm January 2026 supplement to the Current Population Survey, sponsored by the US Department of Labor’s Chief Evaluation Office. Wage and salary workers.
[^gallup-2024-retention]: Gallup, “Employee Retention Depends on Getting Recognition Right”, September 2024. https://www.gallup.com/workplace/650174/employee-retention-depends-getting-recognition-right.aspx Rachael Yi. Joint research with a recognition company; Gallup tracked the careers of nearly 3,500 employees from 2022 to 2024.
[^eeoc-age]: US Equal Employment Opportunity Commission, “Age Discrimination”, Undated. https://www.eeoc.gov/age-discrimination Regulator’s summary of the Age Discrimination in Employment Act.
Agent documentation index: https://shuffl.ai/llms.txt