What do I do if I accidentally CCed the recipient on the share link?

Acknowledge it lightly and ask them to play along on delivery day. A short DM saying 'you might have seen the link, please pretend you did not, the real moment is Friday' is the cleanest move. Do not start over with a new link; you will lose half the original signers and the card will read thinner than the spoiled-but-warm version. The recipient is almost always willing to perform the small social work of being surprised at the planned moment.

Should everyone on the team contribute the same amount to a group gift?

No. Set a suggested range with a soft floor and a soft ceiling — twenty to fifty dollars covers most workplace contexts. New hires and people on the edges of the relationship should be welcome to pay the floor, and senior contributors who want to give more should give it as a separate side gift rather than as a visibly larger contribution to the pool. Anyone who cannot afford the floor in a given week should be allowed to opt out without explaining themselves. The amounts stay private; the card mentions the gift as 'from the team' rather than itemising contributors.

Is it rude to sign a group card with just 'best wishes' and my name?

Not rude. Less than ideal as the whole card. As one line among fifteen, a short polite signature is fine; as the only signature from somebody who actually knew the recipient well, it reads as a calibration miss. The fix is not to apologise for being brief — it is to add one specific reference, even a small one (a habit you will miss, a single moment, a hallway conversation). Brevity with one specific detail beats a paragraph of generalities every time.

Should I mention why the recipient is leaving in the card?

Only if they are leaving voluntarily for a happy reason and have made the new role public. For involuntary departures (layoff, firing, burnout, family reasons), keep the card focused on what the recipient contributed and not on why they are going. The recipient is going to read the card on what may already be a hard day; the card is not the right forum for processing the circumstances. Save private feelings for a private follow-up message.

What is the right time of day to schedule a card delivery?

Between 8:30 and 9:00 in the recipient's local timezone, on the actual day of the occasion. Send to the personal email rather than the work one if you have it, because the work inbox often gets disabled at the end of the recipient's last day. Avoid late-evening deliveries, which feel hurried, and avoid scheduling-in-your-own-timezone errors that land the card at 3am on the recipient's side. If you are unsure of the timezone, ask one of the recipient's close colleagues rather than guessing.

What if I genuinely barely worked with the person — should I sign at all?

Yes, with a short and honest line. 'Best of luck with what is next, sorry our paths did not cross more' is more genuine than a manufactured paragraph and more welcome than a blank space on the card. The recipient can tell the difference between an honest short line and a polite filler paragraph, and the honest short line adds to the card's texture without overclaiming. The exception is if you have actively never met the person; in that case, signing creates an awkward closeness that does not exist, and skipping is fine.

All articles

Group Cards

Group Card Etiquette: The Rules Nobody Wrote Down

Daniel Pierce

May 28, 2026

The first group card I ever received showed up in my own inbox three days early. I was leaving a small content agency in Wellington in early 2021, and somebody on my team had forwarded the share link into a Slack channel I was still a member of because nobody had thought to remove me yet. I clicked it before I realised what it was. The card was half-finished. Six signatures, two cover-image options the organiser was still deciding between, my own name spelled Maia rather than Maya in the heading. I read the six lines, closed the tab, sat with it for ninety seconds, and did the only thing I could think of, which was to message the organiser and pretend I had not seen anything. I did see it, of course, and so on the Friday when the finished card arrived I had to perform a slightly hollow version of being surprised. I have organised about sixty group cards since then, and a fair number of those mistakes have been mine rather than somebody else's. The unwritten rules below are the ones I have collected the hard way. None of them are in the platform help docs. All of them have a specific failure behind them.

Start a group card in 30 seconds

Free. No signup needed.

Jump to section11 sections

One commercial disclosure before any of this

RecoCards is a group-card platform, and I work on it. That is the bias I am writing from. The mechanic-level rules below (PIN the delivery, schedule for the recipient timezone, do not paste the link into a channel the recipient is in) are easier to follow on a platform that supports them, and ours does. The etiquette rules underneath the mechanics are platform-agnostic. They apply to a paper card passed around an office in Tukwila, a Hallmark mailed across state lines, a Slack thread of forty messages somebody pretends is a card. The product fixes some of the failure modes; the human ones it cannot fix. The honest version of this article is that most of what goes wrong with a group card has nothing to do with which website you used.

Rule 1: Do not CC the recipient. Ever. Check twice.

The single most common failure I have seen, by a wide margin, is the share link landing in a channel or thread the recipient is still a member of. I have done this. I have watched three other people do this. The pattern is always the same: you build the card on a Tuesday, you are in a hurry to post it before the end of the day, you paste the link into the team Slack channel, and the recipient (who is leaving on Friday and whose access has not been revoked yet, because IT moves slower than anybody's last week) sees the message in their notification tray. The card was warm. The mechanic was wrong. The surprise was over before it began.

The fix has three layers. The first is to check the channel members before you paste. Open the channel sidebar. Read the names. Look for the recipient. Do this even if you are sure they are not in the channel, because the version of you that is sure is the version of you that has not been burned yet. The second layer is to send the link by DM or by individual email rather than by channel post, especially in the last week before a farewell. The third layer is to use a platform with a PIN-protected delivery, so that the link itself does not give away the assembled card even if it leaks. The PIN is the only mechanic that survives accidental forwarding by a well-meaning third party. I rely on it now and I no longer rely on my own memory.

One narrow exception to the do-not-CC rule, because the absolute version is wrong. For the recipient who is also a card organiser by trade (the office EA, the people-ops person, the team lead who runs every other team's farewell cards), occasionally the kindest move is to tell them up front that a card is being made for them and to ask whether they want a surprise or a heads-up. Some people genuinely prefer to know. Most do not. Ask first if you are not sure.

Rule 2: Pick who gets invited before you start posting

The version of this problem that nobody talks about: the contractor who has worked alongside the team for nine months and gets skipped because nobody knows their last name, nobody is sure if they count as part of the team, and nobody wants to be the person who awkwardly asks. The recipient opens their card on Friday, scans the signatures, and notices the gap. They are too gracious to mention it. They notice anyway. It changes how the card lands.

I have left people off cards I organised. Naveed, a contractor who worked with my team for most of 2022 on a vendor onboarding project, did not get invited to sign the farewell card I built for one of his closest collaborators on our side, because I never thought to add him. He was on the same Zoom calls as the rest of us, four days a week, for nine months. I just forgot to put him on the list. The recipient asked me about it the following week, quietly, in the gentlest possible way. I did the thing one is supposed to do, which is apologise and stop pretending the omission did not matter. The fix for next time is to write the invite list before you build the card, on paper or in a doc, and to specifically ask yourself: who is the person who worked with the recipient that the org chart does not capture? The cross-functional partner. The vendor counterpart. The intern from last summer. The remote teammate who joined for forty minutes a week and never spoke up. The person who used to be on the team and moved last quarter.

If you are organising the farewell for a coworker you also do not know well, the same rule applies in reverse: ask their closest work friend to help you build the list. They know who the contractor is. They know the intern's full name. They know the partner in legal who quietly helped on a launch. Two heads on the invite list catches what one head misses, and the recipient never sees the working draft. There is a longer piece on the mechanics of running the card itself in our guide on how to make a group card everyone signs — the invite-list question is the part most articles undertreat.

Rule 3: Sign the card with the right amount of warmth for your actual relationship

This is the rule most people fail not from carelessness but from anxiety. The signer who barely knew the recipient writes a three-paragraph note to compensate, and the recipient reads it and feels the stretch. The signer who knew the recipient well writes 'best wishes!' and signs their name, because they froze, and the recipient reads it as cold. Both are calibration errors. The fix is to match the warmth to the actual relationship and to refuse to apologise for it either way.

If you barely worked with the recipient, one or two sentences is right. 'Best of luck wherever this goes — sorry our paths did not cross more' is honest and welcome. A paragraph from a near-stranger reads as performance. If you worked closely with the recipient, two to four sentences with a specific reference is the shape. A specific moment, a habit you will miss, an open door for next time. Five sentences in either direction risks turning the card into a monologue. The middle case (recurring-meeting colleague, cross-functional partner, neighbouring-desk floor mate) is the awkward one; the cluster piece on what to write in a card for a colleague leaving walks through the calibration in more depth than I can here.

One inconvenient line I will admit. I have signed a few cards where, honestly, I did not have a specific thing to say, and I wrote a polite generic line and moved on. The polite generic line is fine when you know it is what you have. It is not fine when it is the only thing on the card next to fifteen other generic lines. The card-level texture is the responsibility of the whole group, not any one signer. If your line is going to be 'best of luck', sign it anyway, because the alternative (not signing at all) reads worse to the recipient than another short line in the mosaic.

Rule 4: Do not mention the firing, the burnout, the layoff, the reason

If the recipient is leaving voluntarily for a better job, mention the new job. If the recipient is leaving for any reason that is not a happy one (laid off, fired, burnt out, fired-but-officially-resigned, returning to school after a hard year, leaving for family reasons they have not made public), do not mention the reason. The card is not a place to litigate why the leaver is going. The card is a place to honour what they did while they were here.

The pattern that goes wrong: somebody on the team writes 'sorry it ended this way' or 'you deserved better' or 'we will miss you in spite of how this happened', and the recipient opens the card on what is already the worst Friday of their year and reads the line as a small public confirmation that everyone knew, everyone discussed it, everyone has an opinion. Whatever you actually think about why the leaver is going, the card is the wrong forum. Save it for the private follow-up message or the coffee a month from now. The card belongs to the public, sanitised, kind version of the goodbye, regardless of what the back-channel version says.

The same rule applies in the reverse direction. If the recipient has very visibly been promoted past somebody else on the team, do not joke about the loser of that race in the card. If the recipient is leaving because they fell out with a manager who is also on the team, do not throw shade at the manager in the signature. The card is a small public artefact. It is going to be read by the recipient at least once and possibly archived. It is not the place to express your in-group grievance, however tempting.

Rule 5: The money question (when there is a group gift attached)

A group card with a pooled gift has its own etiquette layer the card-alone version does not. The two most common failure modes I have watched, both more than once: the boss contributing far more than anyone else, which then becomes visible and embarrassing for everyone; and the new hire who started two weeks ago being expected to chip in the same as the team lead who has worked with the recipient for five years. Both fail for the same underlying reason, which is that the suggested amount is set by someone in the middle of the seniority distribution and does not flex for the edges.

The cleaner pattern is to set a suggested-amount range with a soft floor and a soft ceiling. Twenty dollars is the floor; fifty is the ceiling for most workplace contexts. The new hire pays twenty. The senior contributors pay fifty. The boss, if they want to give a larger gift, gives it separately on the side rather than throwing eighty into the group pot where the gap becomes part of the gift's story. Anyone who genuinely cannot afford the floor amount in a given week is allowed to opt out without explaining themselves, and the organiser does not list contributors-by-amount inside the card. The card mentions the gift as 'from the team' and leaves the amounts out of the public record. There is more on the mechanics of actually collecting the money without the chase in our guide on how to collect money for a group gift.

One sub-rule that catches people. If the recipient is the boss, the gift contribution rules invert. Direct reports should not be expected to chip in for a gift to their own manager, because the power dynamic makes the ask coercive even when it is not meant that way. A signed card from the reports is the right artefact in that direction. A pooled monetary gift from reports to manager is not. The exception is a major life event (a retirement after fifteen years, a wedding, a baby), and even then the contribution stays voluntary and the boss is not told the breakdown.

Rule 6: Send it on time, in the recipient's timezone, to the right inbox

The card that arrives a day late reads as an afterthought no matter what the words inside say. The card that arrives at 3am their time because the organiser scheduled it in their own timezone reads as careless. The card that lands in a work inbox that gets disabled at 5pm on the recipient's last day reads as a small institutional shrug. All three are fixable with thirty seconds of attention at the schedule-the-delivery moment.

The rule I have landed on, after a few mis-fires: deliver at 8:30am in the recipient's local timezone, on the day the moment is actually happening (their last day, their birthday, their work anniversary, the morning of their retirement party). Deliver to the personal email rather than the work one whenever you have it, because the personal inbox survives the offboarding. The platform should let you schedule for the recipient timezone explicitly; if it does not, double-check the conversion in your head and add a buffer if you are tired. I have personally scheduled a 6am card more than once because I forgot which direction Pacific to Eastern goes when I am scheduling it from a coffee shop in Seattle.

Rule 7: The surprise survives or it does not, but do not over-engineer the recovery

Sometimes the surprise is going to get spoiled. Somebody forwards the link. Somebody mentions the card in front of the recipient in a hallway. Somebody adds the recipient to a CC by mistake. Once the spoil has happened, the right move is to acknowledge it lightly to the recipient and move on, not to pretend it did not happen and not to start over with a new card. 'Heads up, you might have seen the link to the card we are putting together — please pretend you did not, the actual delivery on Friday is the real moment' is a clean line. It treats the recipient as an adult, names the awkwardness, and lets them perform the small social work of being surprised on Friday without you having to escalate the situation.

The version of this that goes wrong is when the organiser, mortified, tries to rebuild the card from scratch with a new link and asks everyone to re-sign. This always loses signatures, because half the original signers will not re-sign, and the recipient ends up with a thinner card than the spoiled-but-warm version would have been. Live with the small spoil. The card is still going to land.

Rule 8: Sign with your name, not your title

This one I have a small opinion about. The card signature that reads 'From the leadership team' or 'Best, the Engineering Org' lands flatter than the card signed by individual people with their actual names. The reason is that the recipient is opening the card to feel seen by specific people. The institutional voice signature is a way of being there without being there. It is the equivalent of an HR-generated work anniversary email that mentions no specific thing the person did.

If you are the senior person on the team and you want the card to carry a corporate weight, sign it with your name and let the corporate weight follow from that. 'Helena, VP of Engineering' is a real signature. 'From the Engineering leadership team' is not. The same applies to remote signers who feel awkward writing under their full name because they barely know the recipient: write something short and sincere and sign with your first name. Anonymity reads as distance, even when it is meant as humility. The cluster piece on how to write a shout-out covers the same rule in the public-praise direction, and it applies here too.

Rule 9: The recipient's job is to receive it gracefully. Yours is to give them the room to.

Most etiquette guides treat the card as a one-way artefact: organiser builds, signers sign, recipient receives. The recipient side has its own small etiquette layer that the organiser can make easier or harder. The card that lands at 8:30am on a day already full of meetings does not give the recipient room to actually read it; they will skim, they will mean to come back, and they will not. The card that lands on the recipient last day and demands an immediate public thank-you forces them into a response they are not ready to write. The card that mentions the gift attached in the heading rather than the body forces the recipient to thank you for the gift before they have absorbed the messages.

The kindness is to give the recipient time and to set the expectation that no public response is needed. 'No reply needed, take your time, this is yours to keep' is a sentence the organiser can include in the delivery email, and it converts the card from a small social obligation into a small gift. The recipient can write back if they want, or not, or write back next week, or write back to one specific signer rather than the whole team. The piece on how to respond to a farewell message covers the recipient side of this in more depth, for the cards where the recipient does want to write back.

Turn it into a group card without breaking the rules

Most of what goes wrong with group cards happens at the platform-mechanic level (the link leaks, the schedule mis-fires, the recipient is in the channel) or at the calibration level (the warmth is wrong for the relationship, the contributor amount is wrong for the seniority, the timing is wrong for the day). The mechanic-level failures are mostly platform-fixable. A group card online with multiple signatures that PIN-protects the delivery, schedules for the recipient timezone, and lets you build the invite list before posting the link removes most of the surprise-spoil failure mode. You can create a card online in a couple of minutes; the longer parts are writing your own first signed message and double-checking the invite list against the org chart your platform cannot see.

The calibration-level failures are on the organiser and the signers, and no platform fixes those. For a farewell specifically, a virtual farewell card in board layout holds the eight or twenty signatures gracefully and gives each signer their own small canvas, which encourages the right kind of specificity. For a workplace milestone, a kudos board the team signs is the better fit; it is the same mechanic with a different cover. If you are still figuring out who the card is even for and what shape it should take, the companion piece on employee spotlight ideas covers the recognition-layer calibration in more depth than this etiquette piece tries to.

One last thing, off-topic and probably just for me. I keep an old voice memo on my phone from August 2022, recorded by accident when I forgot to lock the screen at a leaving drinks for somebody named Eitan, who had been on our team for three years and was moving back to Tel Aviv to be closer to his parents. The memo is twenty-eight minutes long. The audio is mostly bar noise and a single conversation in the foreground between two of his coworkers, one of whom is reading aloud, badly, from the group card we had organised, trying to remember which line each signer had written. They are laughing. They are also slightly sad, in the way that bar conversations get at hour two. The card is sitting on the table between them. I never told either of them I had the recording. I have not listened to it more than twice. The reason I keep it is that the cards I have helped organise are mostly things I never see again after the delivery moment, and that recording is the only evidence I have that one of them ever actually got carried into the rest of somebody's life, even for a single bar night. The etiquette of group cards is mostly about not embarrassing anybody. The whole point of group cards, which the etiquette is in service of, is the bar conversation two weeks later, which the etiquette mostly will not reach.

Frequently asked questions

What do I do if I accidentally CCed the recipient on the share link?: Acknowledge it lightly and ask them to play along on delivery day. A short DM saying 'you might have seen the link, please pretend you did not, the real moment is Friday' is the cleanest move. Do not start over with a new link; you will lose half the original signers and the card will read thinner than the spoiled-but-warm version. The recipient is almost always willing to perform the small social work of being surprised at the planned moment.
Should everyone on the team contribute the same amount to a group gift?: No. Set a suggested range with a soft floor and a soft ceiling — twenty to fifty dollars covers most workplace contexts. New hires and people on the edges of the relationship should be welcome to pay the floor, and senior contributors who want to give more should give it as a separate side gift rather than as a visibly larger contribution to the pool. Anyone who cannot afford the floor in a given week should be allowed to opt out without explaining themselves. The amounts stay private; the card mentions the gift as 'from the team' rather than itemising contributors.
Is it rude to sign a group card with just 'best wishes' and my name?: Not rude. Less than ideal as the whole card. As one line among fifteen, a short polite signature is fine; as the only signature from somebody who actually knew the recipient well, it reads as a calibration miss. The fix is not to apologise for being brief — it is to add one specific reference, even a small one (a habit you will miss, a single moment, a hallway conversation). Brevity with one specific detail beats a paragraph of generalities every time.
Should I mention why the recipient is leaving in the card?: Only if they are leaving voluntarily for a happy reason and have made the new role public. For involuntary departures (layoff, firing, burnout, family reasons), keep the card focused on what the recipient contributed and not on why they are going. The recipient is going to read the card on what may already be a hard day; the card is not the right forum for processing the circumstances. Save private feelings for a private follow-up message.
What is the right time of day to schedule a card delivery?: Between 8:30 and 9:00 in the recipient's local timezone, on the actual day of the occasion. Send to the personal email rather than the work one if you have it, because the work inbox often gets disabled at the end of the recipient's last day. Avoid late-evening deliveries, which feel hurried, and avoid scheduling-in-your-own-timezone errors that land the card at 3am on the recipient's side. If you are unsure of the timezone, ask one of the recipient's close colleagues rather than guessing.
What if I genuinely barely worked with the person — should I sign at all?: Yes, with a short and honest line. 'Best of luck with what is next, sorry our paths did not cross more' is more genuine than a manufactured paragraph and more welcome than a blank space on the card. The recipient can tell the difference between an honest short line and a polite filler paragraph, and the honest short line adds to the card's texture without overclaiming. The exception is if you have actively never met the person; in that case, signing creates an awkward closeness that does not exist, and skipping is fine.