Work Anniversaries for Distributed Teams: How to Make Them Land — Group Card Blog

Work anniversaries are one of the highest-impact recognition moments a company has — and the one most companies fumble worst. The 1-year, 3-year, 5-year, 10-year markers are when employees most consciously reassess where they are and whether they want to stay.

For distributed teams the failure mode is worse than for in-office teams. There’s no cake in the kitchen, no impromptu speech, no card on the desk — so unless someone deliberately runs the moment, it slips by entirely.

Group Card gives distributed teams a way to run anniversaries well inside monday.com, without it becoming a quarterly chore for HR. Here’s the playbook.

Which anniversaries to mark

You don’t have to mark every anniversary equally. A practical structure:

Anniversary	What’s appropriate
1 year	Card from the immediate team (5–10 contributors).
3 years	Card from the immediate team + cross-functional collaborators (15–25).
5 years	Card from a wider circle including skip-level (25–40), plus a more substantial gesture (gift, day off, etc.).
10 years	Whole-team or company-wide card, plus a meaningful gesture.

The point: 1-year is “we see you and we’re glad you’re here”, 10-year is “you are a load-bearing part of this organisation”. The card should reflect that.

Setting the trigger

The hardest part of anniversaries isn’t the card — it’s remembering them in the first place. Two options inside monday:

Add a Start Date column on your people board if you don’t have one. monday’s date columns let you set up automations.
Set up a monday automation that creates a task two weeks before each person’s anniversary, assigned to whoever runs the recognition program (HR, People Ops, or the team lead).

When that task fires, the assignee opens Group Card and creates the anniversary card.

Creating the card

Open Group Card. Click + New Card.
Pick Anniversary as the occasion.
Pick a template. For anniversaries, the templates with calmer, more substantive aesthetics work better than the celebratory ones — this is a “thank you for your commitment” moment, not a birthday.
Set the recipient.
Card title — Group Card defaults to something like “Happy 3-Year Anniversary, Sarah!”. Edit to specify the year count if it didn’t auto-detect.
Cover message — replace the default with something that names the specific year. “Three years of [name] making [team/company] better.”
Delivery date — the actual anniversary date, 09:00 in the recipient’s timezone.

Inviting the right contributors

This is where anniversary cards win or lose. The trap is inviting too many people and getting generic well-wishes; the opposite trap is inviting too few and missing key voices.

For most anniversaries:

Immediate team. Always.
Manager. Always — and the manager should write the longest, most specific message.
Cross-functional partners. People from other teams the recipient has done meaningful work with.
Skip-level. For 3+ year anniversaries.

For 5- and 10-year anniversaries, also invite:

Past managers still at the company.
Mentors or mentees they’ve had over their time.
Founder or CEO for 10-year (a single line from the founder lands harder than ten generic messages).

Smart prompts that work

Group Card’s anniversary smart prompt is something along the lines of “What’s one thing [name] has done that you’d point a new hire to?”. That’s a strong prompt because it forces specificity.

Other prompts to try (you can suggest these verbally / in Slack alongside the card invite):

“What’s one thing you’ve learned from working with [name]?”
“What’s one moment from the last [N] years that captures who [name] is at work?”
“What’s one quality of [name]‘s that you wish you saw more of in everyone you work with?”

The common thread: every good prompt forces a contributor to think of one specific thing. Generic prompts produce generic messages.

Delivery and after

Group Card delivers the card at the scheduled time. The recipient gets a bell notification, opens the card, and scrolls through every message.

Two things to do after delivery that distinguish a thoughtful program from a perfunctory one:

Manager mentions the card in their 1:1 that week. Acknowledge it explicitly — it normalises recognition.
Keep the card accessible. Group Card stores the card after delivery; the recipient can re-open it any time. For 5- and 10-year cards especially, that’s something they’ll come back to.

What to avoid

Anniversaries for people who’ve left. Group Card requires the recipient to be a monday workspace member, and an anniversary card for a departed employee reads as awkward anyway.
Mass anniversary cards. Don’t bundle “people with anniversaries this month” into one card — it dilutes every individual moment. Run one card per person.
Generic “thank you for your service” messages. Specific or skip — there’s no benefit to a card full of “thanks for everything!” messages.