What do you write in a card for a remote coworker you never met in person?

Anchor the card in a specific remote-work artifact instead of a physical memory. Search your Slack or Teams history for the time they unblocked you at an odd hour, name the doc they wrote that you still use, or reference the recurring meeting they made bearable. "The runbook you wrote is still load-bearing for the team" lands far harder than "great working with you." The texture of a remote relationship lives in the tools, not in a hallway, so go find it there.

Is it okay to write a short card for a remote coworker I barely worked with?

Yes, and it is often the more honest choice. If you went looking through your shared channels and genuinely found nothing specific, a short true line beats a strained paragraph. "We didn't overlap much, but the few times we did you made it easy. All the best at the next place" is two sentences and reads as respectful rather than empty. Remote coworkers are unusually good at spotting a sentence with no real referent behind it.

How is a card for a remote coworker different from one for an in-office coworker?

The difference is where the evidence lives. In-office relationships leave physical memories: lunches, hallway chats, a desk you walked past. Remote relationships leave a written record instead: Slack threads, shared docs, code reviews, recurring video calls. That record is more searchable and more specific than memory, which is an advantage if you use it. The failure mode is reaching for the in-person texture that does not exist and writing a generic line when a specific one was a search away.

Should I mention that we never met in person?

Avoid framing it as an apology like "sorry we never got to meet." That makes the whole relationship sound like a deficiency. If you want to acknowledge the distance, do it through a specific remote moment or a light observation: "we never shared a room and still got a lot done" honours what actually happened. The distance was the setting, not the story; keep the focus on the real thing you did together.

What is a good closing line for a remote coworker's farewell card?

Make the open door concrete rather than vague. "Add me on LinkedIn, I want to see what you build next" or "send me your new email, let's stay in touch for real" beats "hope our paths cross again someday." For remote coworkers the paths often do cross again, just on a different screen in a different org, so a specific invitation is more honest than a wistful one. Match the closer to how close you actually were.

All articles

Workplace Cards

What to Write in a Card for a Remote Coworker (When You Never Shared a Room)

Emily Hartwell

May 28, 2026

Make the list of what you do not have. No hallway where you bumped into them on the way to the printer. No shared lunch, no birthday cake in a conference room, no desk you walked past a thousand times. No memory of how they take their coffee, because you have never been in a kitchen with them. You worked with this person for two years and you could not pick their normal speaking voice out of a lineup, only their video voice, which is a slightly different thing. So when the farewell card link lands in the team channel and your block is blank, the easy thing to reach for is the one line that fits a person you have never met: great working with you, good luck out there. I have written that exact line for a remote coworker and felt it go hollow as the pen moved. The thing I got wrong, and the thing this article is about, is that the texture is there. It is just stored in different places than the corridor. It is in the Slack thread where they unblocked you at a strange hour, the doc they wrote that you still open, the one meeting they made bearable. You have to go and find it in the tools instead of the building.

Start a group card in 30 seconds

Free. No signup needed.

Jump to section7 sections

The corridor is gone, and the corridor is where most card advice lives

Almost every guide to writing a coworker card assumes a shared physical life. It tells you to recall the lunch, the after-work drinks, the time you both got stuck in the elevator, the desk plant they over-watered. None of that exists for a remote relationship, and the absence is exactly why the remote-coworker card defaults to filler. You reach for the corridor, find nothing there, and write the line you would write for a stranger.

The honest starting point is that a remote relationship is real but differently shaped. You did not share a room. You shared a tool stack. Two years of standups over video, a few hundred Slack messages, the docs you both edited, the pull requests you reviewed, the one channel that was mostly the two of you arguing pleasantly about a naming convention. That is the relationship. It is thinner in some ways than an in-office one and oddly thicker in others, because remote work leaves a written record that the corridor never did. The corridor evaporates. The Slack thread is still searchable. Most of the good lines for a remote coworker are sitting in your own search history right now.

One commercial disclosure up front. RecoCards, where this is published, is a group-card platform, and the back half of this article points at our product as the way the practical version of the card gets sent (the geometry of a distributed team signing one card is precisely the thing we built for). The diagnostic and the worked lines below do not depend on the platform. Use them on whatever card is in front of you.

Where the texture actually lives (the remote-work artifacts to mine)

Before you write anything, go open the tools. Not to copy and paste, but to remember. The remote relationship left evidence, and the evidence is more specific than your memory of it. Five places to look, in rough order of how often they pay off.

The Slack or Teams thread where they unblocked you at an odd hour. This is the single richest vein for a remote coworker. Search their name in your DMs. You will almost certainly find a moment where you were stuck at 9pm, or stuck before a release, or stuck on a Friday, and they answered when they did not have to. The hour matters. Naming the specific late reply ("the Thursday you answered my panicked DM at 10:40pm about the migration") is the remote equivalent of "you stayed late to help me", and it is verifiable, which makes it land.

The doc they wrote that you still open. Distributed teams run on writing. Someone on your team wrote the onboarding doc, the runbook, the architecture decision record, the one Notion page everyone links to. If that person is the leaver, you have a gift: name the doc. "I still open the deployment runbook you wrote in 2024 about once a week" is a sentence that tells the recipient their work outlived their tenure, which is the highest compliment a remote contributor can get.

The recurring meeting they made bearable. Every distributed team has the standing call that would be unbearable without one specific person in it. The one who cut the tangents. The one who actually read the doc beforehand. The one whose camera-on energy at 8am held the rest of the call together. You sat in that meeting with them more than you sat anywhere with anyone in your office life. It counts.

The async review that was unusually generous. Code review, doc review, design review, a markup on your draft. Remote work converts a lot of mentorship into written comments, and a generous reviewer leaves a trail. If someone consistently left you the kind of review that made the work better instead of just correct, that is a thing to name, and almost nobody names it because it does not feel like a "moment." It is.

The one time their world leaked into the frame. The single most human thing about remote coworkers is the accidental glimpse. The kid who wandered into the shot. The dog that barked through your one-on-one. The bookshelf behind them you spent six months reading the spines of. The power cut that turned their camera into a candlelit silhouette for ten minutes while the meeting carried on. These are the closest a remote relationship gets to the corridor, and a card can reference one of them with real affection.

The diagnostic: which kind of remote coworker is this

The card changes depending on how much real overlap you had, and remote teams blur this more than in-office ones because everyone is equally a tile on a screen. Three honest categories.

The close remote collaborator. You worked the same projects, you DMed daily, you knew their schedule and their on-call rotation and the name of their dog from the meetings. Distance was a logistics fact, not a relationship fact. Write this card the way you would write for a coworker you sat next to, because functionally you did. Lean on the specific artifact. You have plenty of material.

The adjacent remote coworker. Same team or same org, overlapping meetings, a handful of shared threads, mutual respect, no real social closeness. This is the most common remote case and the one the generic line was invented for. You have one or two specific things if you go look. Find one. Build the card on it.

The remote coworker you genuinely do not know. You were both on the all-hands. You overlapped in two channels. You have maybe exchanged six messages, all of them logistical. The honest move here is the short true line, not manufactured warmth. "Our paths barely crossed, but the few times they did you made it easy. All the best at the next place" is more respectful than a fake paragraph. The piece on what to write when you do not know someone well goes deep on this exact problem, and most of it applies double over distance.

Worked lines by occasion and overlap

Each line below is illustrative. Swap in your own artifact, your own hour, your own doc. The point is the shape, which is: name the specific remote thing, then the wish, then stop. Skip the adverbs.

Farewell, close remote collaborator

You worked alongside them through a screen for a long stretch. The card can carry weight. Anchor it in the written record you actually share.

Two years of standups and I never once saw your apartment in daylight, only that lamp behind you. The release we shipped in March does not happen without your 11pm replies. Go be brilliant somewhere that deserves you.
You answered my DMs faster than people sitting ten feet from me ever did. I am going to miss the little green dot next to your name. Best of luck, and stay reachable.
The runbook you wrote is load-bearing for the whole team and you are leaving it behind like a gift. Thank you. The next place is lucky.
Going to miss arguing with you about variable names at 9am.
We never shared a building and somehow you are one of the people I worked closest with here. That is the strange math of remote, and you were the proof it can work. Send me your new address, the real one.

Farewell, adjacent remote coworker

Real respect, light social ties. One specific reference does all the work. Two sentences is plenty.

You were the only person in the Tuesday sync who had actually read the doc, and the meeting was thirty percent shorter and better for it. Best of luck out there.
I will remember the design review where you left me three comments that made the whole flow click. Wishing you a team that notices that about you.
From across the org chart and three time zones, thank you for the work I did get to see. Go well.
Your camera-on energy at the 8am standup held that call together more than you know. The standup will be quieter and worse. All the best.
The naming-convention thread we went back and forth on for a week is one of my favourite small things about working here. Onwards.

Work anniversary or appreciation, remote coworker

No exit, just recognition. The why-now should be the first sentence so the card does not float.

Three years of you on the calendar, mostly as a tile in the top-right corner, and the on-call handoffs you wrote were the cleanest I have ever inherited. That is a real skill and I do not think anyone has told you. Telling you now.
Wanted to put this somewhere that does not scroll away in Slack: the doc you wrote on the deploy process saved me an entire week in my first month. Happy anniversary. The writing outlives the meetings.
You make the worst recurring meeting on my calendar survivable, and that is a contribution nobody puts in a perf packet. I am putting it here.

The accidental-glimpse line (use sparingly, but it lands)

When a small piece of their real life leaked into the frame and it became a tiny shared thing, the card can reference it with affection. Calibrate to whether they would smile or wince.

I will genuinely miss your dog interrupting our one-on-ones at the worst possible moment. Give him a treat from the Seattle office that does not exist.
Six months of staring at the bookshelf behind you and I still want to know if you actually read all of them. Best of luck, and good taste.

What to skip: the lines that give the distance away

Some lines are not wrong so much as they announce that you reached for the corridor, found it empty, and wrote the stranger card anyway. The recipient, who is also remote and has received a dozen of these, reads them as exactly that.

"Great working with you." The canonical empty line. It is the one I wrote and the one that taught me to write this article. With a specific artifact in front of it, it is fine. As the entire card, it tells the remote coworker you could not find anything in two years of shared tools, which is rarely true and always findable.

"Sorry we never got to meet in person." This one feels warm and is quietly a little sad in the wrong way. It frames the entire relationship as a deficiency, a thing that did not happen, rather than the real thing that did. If you want to gesture at the distance, do it through a specific remote moment, not through an apology for the absence of a physical one. "We never shared a room and still got a lot done" beats "sorry we never met."

"Hope our paths cross again someday." Fine as warmth, weak as a closer, because for remote coworkers the paths probably will cross again, just on a screen, in another org, in a Slack you both end up in. Make it concrete. "Add me on LinkedIn, I want to see what you build next" is a real open door. The vague version closes the thing it pretends to open.

The fake-intimacy stretch. "You were one of the best people I have ever worked with" from someone who exchanged forty logistical Slacks with the leaver reads as a stretch, and over distance the stretch is more visible, not less, because there is less shared context to cushion it. Calibrate the warmth to the actual overlap. A modest true line reads as sincere. A big line with nothing under it reads as the thing it is, which is a guess dressed up as feeling.

The genuine limits (sometimes you really don't know them)

Here is the inconvenient part, and the place where most card-writing advice lies to you. Sometimes you go and look in all five tools and you find nothing, because there is genuinely nothing there. You shared an employer and a couple of channels and that is the whole of it. The advice industry will tell you to dig deeper and write something heartfelt anyway. I think that is wrong. A heartfelt paragraph about a person you do not know is a small lie, and remote coworkers, who live their work lives inside written records, are unusually good at reading the difference between a sentence with a real referent and a sentence without one.

The honest move is to write something small and true. "We didn't overlap much, but the few times we did, you were easy to work with. Wishing you well at the next place." One or two sentences. Sign it. That is not a failure of effort. It is a correct read of the relationship, and it sits more comfortably on the card than a paragraph straining for a closeness that was never there. The longer treatment of this exact judgment call is in the colleague-leaving card guide, and the calibration logic carries over almost wholesale.

Turn it into a group card the whole distributed team signs

The remote-coworker card has a geometry problem that the in-office card never had, and it is the opposite of the usual one. In an office, the paper card on a desk misses the remote people. For a remote leaver, there is no desk to pass the card around, and the team is scattered across time zones, so the default fallback is a thread of replies in a channel that scrolls away by Friday. The leaver gets a wall of "this!" reactions and three thoughtful messages buried in standup chatter, and nothing they can keep. The written record that made the relationship real is also the thing that makes the goodbye disposable.

A virtual farewell card online fixes that. One link, dropped to the actual distributed team rather than posted in a channel, and each person writes their own block on their own time, in their own time zone, when they have a minute to go open their Slack history and find the real thing. The teammate in another country writes the line about the 11pm unblock. The cross-functional partner writes the one about the generous review. You can create a card online in a couple of minutes, schedule the delivery for the morning of the last day in the recipient's local time, and seed it with your own specific opening line so the tone is set before the rest of the team signs. If the occasion is recognition rather than a goodbye, a kudos board with unlimited signers is the same mechanic with a warmer cover.

If the leaver was specifically a remote teammate you worked closely with, the farewell messages for a remote teammate bank is the closest companion to this piece. For the surprise-spoil and invite-list mechanics that distributed teams get wrong constantly, the group card etiquette guide is worth a read before you post the link. And if you are trying to make recognition a habit across a remote team rather than a one-off farewell, the employee recognition piece makes the wider case.

One last thing, off-topic and probably just for me. There is a coworker I worked with for almost three years entirely over video, named Priscilla, who lived eight time zones away and whose face I have seen more than I have seen most of my actual friends, and whom I would not recognise on a street. We never met. The company did an offsite once that we both meant to go to and both missed for separate boring reasons. She left in late 2024 and I wrote her a decent card, I think, anchored on a spreadsheet she built that I still use. What I keep coming back to is that I know the exact sound of her doorbell, because it went off twice in nearly every call we ever had, and I know it was a delivery roughly half the time because she would mouth "sorry, one sec" and come back holding a parcel. I do not know what city the doorbell is in. I could not point to it on a map. But I would know that doorbell anywhere, and that is the strangest, smallest, most real piece of evidence I have that the remote thing was a relationship and not just a series of meetings. The corridor never gave me anything like that.

Frequently asked questions

What do you write in a card for a remote coworker you never met in person?: Anchor the card in a specific remote-work artifact instead of a physical memory. Search your Slack or Teams history for the time they unblocked you at an odd hour, name the doc they wrote that you still use, or reference the recurring meeting they made bearable. "The runbook you wrote is still load-bearing for the team" lands far harder than "great working with you." The texture of a remote relationship lives in the tools, not in a hallway, so go find it there.
Is it okay to write a short card for a remote coworker I barely worked with?: Yes, and it is often the more honest choice. If you went looking through your shared channels and genuinely found nothing specific, a short true line beats a strained paragraph. "We didn't overlap much, but the few times we did you made it easy. All the best at the next place" is two sentences and reads as respectful rather than empty. Remote coworkers are unusually good at spotting a sentence with no real referent behind it.
How is a card for a remote coworker different from one for an in-office coworker?: The difference is where the evidence lives. In-office relationships leave physical memories: lunches, hallway chats, a desk you walked past. Remote relationships leave a written record instead: Slack threads, shared docs, code reviews, recurring video calls. That record is more searchable and more specific than memory, which is an advantage if you use it. The failure mode is reaching for the in-person texture that does not exist and writing a generic line when a specific one was a search away.
Should I mention that we never met in person?: Avoid framing it as an apology like "sorry we never got to meet." That makes the whole relationship sound like a deficiency. If you want to acknowledge the distance, do it through a specific remote moment or a light observation: "we never shared a room and still got a lot done" honours what actually happened. The distance was the setting, not the story; keep the focus on the real thing you did together.
What is a good closing line for a remote coworker's farewell card?: Make the open door concrete rather than vague. "Add me on LinkedIn, I want to see what you build next" or "send me your new email, let's stay in touch for real" beats "hope our paths cross again someday." For remote coworkers the paths often do cross again, just on a different screen in a different org, so a specific invitation is more honest than a wistful one. Match the closer to how close you actually were.
How do you organise a goodbye card for a remote teammate across time zones?: Use an online group card with a shared link instead of a channel thread that scrolls away. Send the link directly to the distributed team, let each person write their own block on their own time, and schedule the delivery for the morning of the last day in the recipient's local timezone. Seed it with one specific message first so the tone is set, and check the invite list against the people who actually worked with them, not just the ones in the busiest channel.