TL;DR — A work anniversary deserves more than an automated congratulations email, but most teams only manage that for the people someone remembers to flag. This guide covers how to run anniversary videos as a repeatable system, so every milestone gets marked without relying on anyone's memory.
- Anniversaries are predictable dates — treat them as a recurring process, not a one-off event.
- Tie the ask to the milestone number; a one-year message differs from a ten-year one.
- Automating the reminder, not the message itself, is what actually scales.
On this page
Why anniversaries get missed even when everyone means well
Nobody forgets a work anniversary on purpose. It gets missed because nobody owns the reminder. In a small team, a manager might remember by instinct. Past about twenty people, instinct runs out, and the only anniversaries that get marked are the big round numbers someone happened to notice on a dashboard.
The fix is less about enthusiasm and more about plumbing: a standing process that surfaces the date automatically, far enough ahead that someone has time to collect a few messages before the day itself.
Setting up a recurring process
Most HR systems already hold start dates. Pull a list of anniversaries coming up in the next thirty days once a month, and treat each one as a small task: pick a prompt, send a link to a short list of close colleagues, and have something ready by the date. For teams that use Zapier-style automation between their HR system and messaging tools, this check can run itself — a monthly trigger that posts a reminder in a private channel is enough; the messages themselves still need a person to collect.
What to ask for, by milestone
| Milestone | What tends to land |
|---|---|
| 1 year | A short welcome-still-applies message from close teammates; keep it light. |
| 3-5 years | A specific memory or a note on how the person has grown into the role. |
| 10+ years | Messages from people across different points in their time there, including former colleagues who have since moved on. |
Who should contribute
For a one-year anniversary, a handful of close teammates is enough. For a longer tenure, widen the circle: a former manager, someone from a different team they once worked closely with, or a colleague who has since left the company entirely. Longer tenures carry more history than the current team alone can offer.
Keeping it from feeling like a form letter
The risk with any recurring programme is that it starts to feel automated even when a person is behind it. Vary the prompt by milestone rather than reusing the same question every year, and let the length of the reel scale with the occasion — a one-year mark does not need the same production as a ten-year one.
How to do this in Whoosh
Set up one recurring anniversary campaign with a prompt that adjusts by milestone, and reuse the same link every time a date comes up. Clips land in one place, so compiling a short reel for a milestone takes minutes rather than a fresh setup each time.
Start freeFrequently asked questions
How far ahead should we start collecting messages?
About a week is usually enough for a small group of contributors; give more lead time for a longer tenure with a wider circle to ask.
Should every anniversary get a full video?
Not necessarily — a short message or two might suit a one-year mark, with a fuller reel reserved for round numbers like five or ten years.
Can this run without HR chasing it manually every month?
A simple automated reminder pulling upcoming dates from the HR system removes most of the manual tracking; a person still needs to send the request and compile the result.
What if someone doesn't want attention drawn to their anniversary?
Ask first, privately, rather than assuming — some people prefer a quiet note over a wider celebration.