The answer, briefly
Ask once, by email, in a message that takes thirty seconds to answer. Collect month and day only — never the birth year. Collect the home address in one field, not five. Make opting out one word. Then store the list somewhere access-controlled and refresh it once a year during an existing HR cycle.
Most birthday programs die here, not at the card stage. The gesture is easy. Getting fifty people to send you their address is the part nobody warns you about.
Why this is harder than it looks
Three things make people hesitate before they reply:
“Why does work want my home address?” Employees are conditioned to be suspicious of data requests. If you don’t say what it’s for, some fraction will assume the worst and quietly not respond.
“Do I want people knowing my age?” This is why the birth year is a landmine. Asking for a full date of birth converts a friendly request into something that feels like a background check.
“Is this optional?” Some people are genuinely private about birthdays — religious reasons, family history, or simple preference. If opting out feels socially costly, they’ll give you a fake date or ignore the email.
Solve all three in the ask itself and your response rate goes from about 60% to over 90%.
The rules
Month and day only. You need to know when to send a card. You do not need to know how old anyone is. Collecting birth year creates age data you have no business reason to hold, which is bad practice under general data-minimization principles and creates unnecessary exposure in an age-discrimination context. There is no upside. Don’t ask for it.
One address field, not five. “Street address, apt/unit, city, state, ZIP” as five separate required fields triples the abandonment rate versus a single paste-in box. Let people paste the address the way their phone autofills it.
Say exactly what it’s for. One sentence. “So we can mail you a birthday card.” That’s it. Specificity is what makes the request feel normal.
Make opting out trivial. One line, no explanation required, no follow-up. If someone opts out, they’re off the list permanently and nobody mentions it again.
Say who sees it. “Only [name] and [name] have access to this list.” People relax when the blast radius is defined.
Don’t tie it to anything. No survey attached. No engagement questions bundled in. The moment this becomes a form, it becomes a task.
The email template
Copy this, change the bracketed parts, send it.
Subject: Quick ask — your birthday (and mailing address)
Hi all,
We’re starting something small: everyone on the team gets a real birthday card in the mail on their birthday. No agenda, no catch — we just think it’s a nice thing to do.
To make it work I need two things from you:
- Your birthday — month and day only. I don’t want the year and won’t ask for it.
- The mailing address you’d like the card sent to.
You can just reply to this email with both. Takes about fifteen seconds.
If you’d rather not participate, reply with “no thanks” and I’ll take you off the list — no explanation needed, and I won’t follow up about it.
Only [Name] and I will have access to this information, and it won’t be used for anything other than mailing cards.
Thanks, [Name]
Why this version works: it explains the purpose in the first sentence, pre-empts the age concern before anyone has to raise it, gives a two-word opt-out that costs nothing socially, and names the humans who can see the data. It also doesn’t oversell. “We just think it’s a nice thing to do” does more work than three paragraphs about culture would.
What fields to actually collect
Keep the list to five columns:
| Field | Example | Notes |
|---|---|---|
| Full name | Marcus Chen | As it should appear on the envelope |
| Birthday (MM/DD) | 04/17 | No year, ever |
| Mailing address | 412 Oak St Apt 3B, Denver, CO 80205 | One field |
| Card message | “Happy birthday, Marcus!…” | Optional if you use a universal message |
| Status | Active / Opted out / Departed | Makes the annual audit trivial |
That’s the entire schema. Anything more and you’ve built an HRIS nobody asked for.
Build it in a spreadsheet from the start, because a spreadsheet is what any card service will ask you to hand over. Delivered Cards takes exactly this file as a bulk upload — names, birthdays, addresses — reads it, flags rows that look wrong, and shows you every line on screen to correct before you pay. There is no field for year of birth in the system at all, which means the version of this list you collect is the version you upload.
Where to store it
Not in a shared drive folder everyone can open. Not in a Slack thread. Not in the personal inbox of whoever happens to be running this.
A single access-controlled spreadsheet, with a named owner and a named backup, is enough for most teams under a few hundred people. Home addresses are personal information — several state privacy laws treat them as such — and the standard here isn’t complicated: limit who can see it, don’t copy it around, and delete rows for people who’ve left.
If your company already has an HRIS with home addresses in it, use that as the source of truth and don’t create a second list.
Getting the stragglers
Expect 60–70% on the first email. To close the gap:
One reminder, one week later, and only to non-responders. Same message, shorter. “Quick nudge on this — takes fifteen seconds. Or reply ‘no thanks’ and I’ll drop it.”
Then stop. After a second ask, further follow-up becomes pressure, and pressure on a birthday program is self-defeating. Move non-responders to a “no data” status and leave the door open — someone who sees a colleague get a card in March will often send you their info in April, unprompted. That’s the best possible way to grow the list.
Ask new hires during onboarding. Add the two fields to whatever onboarding form you already use. This is the single highest-leverage change: it means the list maintains itself going forward instead of requiring an annual campaign.
Before you send the first email, it’s worth knowing roughly where this is heading — how employee birthday cards work covers the mechanics, and what the program costs per employee covers the budget conversation you’ll have after.
The annual refresh
People move. Addresses go stale at roughly 10% per year in the US, and a card sent to an old apartment is worse than no card — it’s a near-miss the employee never even learns about.
Attach the refresh to something that already happens: open enrollment, annual review season, the January all-hands. One line in an existing email — “if you’ve moved in the past year, reply with your new address” — is sufficient. Don’t build a separate process for this.
Also audit for departures at the same time. Nobody wants a birthday card from a company they left in March.
Common questions
Is it legal to ask employees for their birthday? Asking is generally fine. The caution is around collecting birth year and age data, which you have no need for in a card program. Month and day only sidesteps the issue entirely — and it’s worth confirming your vendor doesn’t require the year either, because some do. If you operate in a jurisdiction with strict employee data rules, or you’re unsure, loop in counsel — but the volume of data here is very small by design.
What if someone gives me a PO Box or a work address? Fine. Mail it wherever they say. The point is that they receive it.
Should I ask about the card message too? Only if you’re personalizing per person. For teams over about thirty, a single universal message is genuinely better — it’s honest about what it is, and it removes the biggest ongoing time cost.
How do I decide between vendors before collecting anything? Our HR buyer’s guide to birthday recognition covers the category. Worth reading first if you haven’t chosen — why consistency matters more than the gesture shapes what you actually need.
What if the CEO’s address feels awkward to ask for? Ask everyone the same way, in the same email. The consistency is the point. A program where leadership is exempt sends a strange signal.
Once you have the list
The collection is a one-time cost. The ongoing cost is the part that determines whether the program survives past June — because a list is only useful if something acts on it every single month, on time, without anyone remembering.
Delivered Cards takes the list and does exactly that. You upload the spreadsheet once, pick a card, and write your message. We print and mail a real card to each person’s home ahead of their birthday, every year, for $5 per employee per year — with your company’s return address on the envelope. It renews annually on its own, and adding a mid-year hire takes about thirty seconds from your account.
The bulk upload is built for lists of ten or more; below that you can add people one at a time at the same price.