How to Respond to a Passive-Aggressive Coworker

You read the message twice. On the surface it is fine. "Per my last email" or "wow, you actually finished on time" or "sure, no problem" followed by silence. Nothing you can point to, nothing you could forward to your manager without sounding petty, and yet your stomach is tight and you have spent twenty minutes drafting a reply you keep deleting. You're not being dramatic. That message was doing something, even if it was built to let the sender deny it.

The short answer to how you respond is this: read what the message is actually asking for before you react to its tone, then reply to the underlying issue in plain, neutral language and leave the bait on the floor. You do not match their energy. You do not escalate. You name the practical thing that needs to happen, you keep a record where it matters, and you stay boring on purpose, because calm is the one move a passive-aggressive message cannot use against you. The rest of this guide breaks that down: what these patterns actually are, the six you'll see most at work, how to pick your tone, and when something has crossed from annoying into a real problem worth documenting.

What passive-aggressive behavior at work actually is (and what it is not)

Passive-aggressive behavior is hostility that travels in disguise. The person has a complaint, a resentment, or a need they will not say out loud, so they express it sideways, through a tone, a delay, a public comment, or a pointed silence. The defining feature is deniability. If you confront it directly, they can say "I was just asking" or "I didn't mean anything by it," and on paper they are right. That gap between what was said and what was meant is the whole point of the technique, and it is why you end up feeling crazy instead of simply annoyed.

The core mechanism: indirect hostility with built-in deniability

Every passive-aggressive message runs on the same engine. There is a real feeling underneath, usually resentment, status anxiety, fear of losing credit, or a wish to avoid an open conflict. Instead of stating it, the person encodes it in something that looks neutral or even polite. "Just making sure this doesn't fall through the cracks again" carries a jab about last time, wrapped in helpfulness. The wrapper is what gives them cover. So when you respond, you are not responding to the words. You are responding to the feeling the words were built to hide, while refusing to take the bait the wrapper offers.

Telling it apart from a genuinely bad day

Not every clipped reply is passive aggression. People get slammed, people get terse, people forget to cc you because they are underwater, not because they are sending a message. The honest read is sometimes that you're overthinking it. The difference is pattern and direction. A bad day is occasional, scattered, and not aimed at you specifically. Passive aggression repeats, it points at you, and it tends to show up where there is an audience or a paper trail. One curt "noted" on a hard Friday is a tired colleague. The same person raising your work in the all-hands channel, leaving you off threads, and answering "sure, no problem" before quietly not doing the thing is a pattern. Wait for the pattern before you decide what you're dealing with.

Why these messages get under your skin

Here is why a single line can wreck an afternoon. Passive aggression attacks two things at once: the task and your standing. The "per my last email" is about the task, sure, but the real sting is the implication that you are careless, that other people can see it, and that you now have to defend yourself without anything solid to defend against. It puts you in a double bind. React to the tone and you look thin-skinned. Ignore it and you feel like you let it land. Either way you lose time and confidence, and the sender pays nothing.

It also exploits ambiguity. Because the hostility is deniable, your brain keeps running the loop, rereading, screenshotting it to a friend, asking "am I imagining this?" That loop is exhausting precisely because there is no clean answer in the text itself. That gap, between what landed in your gut and what you can prove on the page, is the exact thing heed was built to close: you paste the message and it names the pattern so you can stop relitigating it in your head and just respond. Once you can name what a message is doing, it loses most of its power over you. Naming is the first real move, so let's name the patterns.

The six passive-aggressive patterns at work, decoded

Most workplace passive aggression is not infinite variety. It is a handful of moves repeated. When you can recognize the move, you can respond to the move instead of to your own racing pulse. Here are the six you'll see most.

1. The plausible-deniability delay

Trigger phrase: "Oh, I thought you said next week." The deadline slips, the work is not done, and the explanation arrives pre-built with an excuse you cannot disprove. This signals resentment or quiet resistance to the task or to you; the vagueness is deliberate so that the miss can never quite be pinned on them. It is a way to push back without ever saying no.

2. The backhanded compliment

Trigger phrase: "Wow, you actually finished on time." It sounds like praise and lands like a slap, because the real content is the word "actually," which assumes you usually don't. This signals status anxiety or a need to feel superior, delivered as a gift so that any objection makes you look like you can't take a compliment. The criticism is real; the bow on top is camouflage.

3. The public-forum grievance

Trigger phrase: anything that should have been a DM, posted in the channel or raised in the all-hands instead. They never bring it to you privately; they bring it where there is an audience. This signals a desire for leverage, using witnesses as pressure to force a response and to shape how others see you. The setting is the weapon, not just the words.

4. Silent exclusion

Trigger phrase: there isn't one, and that is the point. You're cc-dropped from a thread you were on, left off the meeting invite, looped in late after decisions are made. The absence is the message. This signals resentment or a quiet bid to shrink your role and credit, deniable because "I just forgot to add you" always sounds plausible. Being left out is being told something without anyone having to say it.

5. The "per my last email" pile-on

Trigger phrase: "Per my last email" or "as I mentioned below," sometimes with the old thread helpfully pasted underneath. This is documentation turned into a weapon. It signals a wish to assign blame and build a record, performing diligence while implying you are the one who dropped the ball. The receipts are not for clarity; they are for the audience.

6. The fake agreement, then non-delivery

Trigger phrase: "Sure, no problem," followed by nothing. They agree in the moment to end the conversation, then the work does not arrive and your follow-ups go quiet. This signals conflict avoidance and sometimes buried resentment; saying yes was easier than saying no, and not delivering becomes the no they would not voice. It is compliance used as quiet sabotage.

Choose your register before you type a word

Before you write anything, decide the tone. The single biggest mistake is matching their energy, because a sharp reply hands them the proof that you are "difficult." Pick your register on purpose, based on the relationship, the stakes, and whether anyone else is watching. There are three to choose from, plus the option of saying nothing at all.

Warm: when the relationship is worth protecting

Use warm when this is a colleague you generally trust who is having an off week, or when you need this person's cooperation going forward and the cost of friction is high. Warm gives them an easy off-ramp. You assume the most generous reading out loud, you stay friendly, and you quietly restate what you need. It works because it refuses the fight while still getting the practical point across, and it makes you look like the reasonable one if it ever gets repeated.

Neutral: the default for most of it

Neutral is your workhorse. It is flat, factual, and a little boring, and that is exactly the strength. You answer the task, you ignore the tone entirely, and you give the bait nothing to grab. Neutral is the right call for most public-forum jabs and most "per my last email" pile-ons, because it shows any audience that you are calm and focused on the work while the other person is the one bringing heat.

Firm: when it is repeated or crossing a line

Firm is for patterns, not one-offs. When the behavior repeats, affects your work, or starts to shape your reputation, you name the impact plainly and without apology. You do not get angry; you get clear. Firm draws a visible boundary, ideally in writing, and it often quietly starts the record you may need later. Save it, because used too early it can read as the overreaction they were hoping for.

When strategic silence beats any reply

Sometimes the strongest response is none. If the message is pure bait with no real ask, if replying would only feed a public spat, or if you are too activated to write something you won't regret, you wait. Silence is not losing. Not every jab earns your time, and a non-response denies the sender the reaction they were fishing for. The rule of thumb: if there is a genuine task buried in the message, answer the task and skip the tone. If there is no task, only provocation, you are allowed to let it sit.

When they say nothing is wrong: handling deflection

You finally ask, gently, if everything is okay, and you get "I'm fine" or "no, it's nothing" in a tone that is clearly not nothing. This is the deflection trap. Push harder and you are "making it a thing"; let it go and the resentment keeps leaking sideways. The way through is a two-move script, and the order matters.

First move: name the dynamic, not the person. Describe the pattern you are seeing in the work, not a verdict about their character. "I've noticed a few of the recent threads went out without me on them, and I want to make sure I'm not missing context" is about the threads. "You keep cutting me out" is about them, and it will trigger a defense every time. You point at the observable thing on the table, so there is nothing to deny.

Second move: make it easy and safe to be straight with you. Offer the opening and then stop talking. "If there's something about how we're splitting this work that isn't sitting right, I'd genuinely rather hear it" hands them a door without forcing them through it. You will not always get an honest answer, and that is fine. Your goal is not to extract a confession. It is to make the indirect route less rewarding by calmly, repeatedly inviting the direct one, while you keep your own conduct clean and on the record.

Adjusting for who they are: peer, boss, or your report

The same message means different things, and calls for different responses, depending on who sent it and how much power they hold over you. Read the message the same way every time, but calibrate the reply to the relationship.

Responding to a passive-aggressive boss

With a boss, the power gap changes the math. Firm has to be carefully chosen, because directness that reads as boundary-setting with a peer can read as insubordination from above. Lead with warm or neutral, default to clarifying questions over pushback, and put agreements in writing so expectations are explicit without confrontation. "Just to confirm what I heard, you'd like the draft by Thursday rather than next week, is that right?" turns a deniable "I thought you said next week" into a documented, shared understanding. You are not catching them out; you are protecting yourself by removing the ambiguity they are using. If a boss's passive aggression is steady and affecting your work or standing, that is the situation where quiet documentation and, eventually, a conversation with your own manager or HR becomes the right path.

Handling a peer or your own direct report

With a peer, you are on level ground, so neutral and firm are both fully available, and consistency is your friend. Answer the task, decline the tone, and repeat that pattern until the behavior stops being rewarding. With a direct report, the responsibility flips toward you. Their passive aggression is often a signal of something they do not feel safe saying directly, sometimes about you or a decision you made. Here you do not just deflect; you open the door on purpose. Name the pattern privately and kindly, ask what is behind it, and make it genuinely safe to tell you, because as the manager you are the one with the power to fix the cause. Letting it fester is a leadership miss, not just an annoyance.

When to document it and bring in your manager or HR

Most passive aggression is best handled quietly, between you and the sender, with the registers above. But some of it crosses a line where managing it alone is no longer your job to carry. The threshold is pattern plus impact. When the behavior is repeated, not a one-off; when it is materially affecting your work, your deadlines, or your reputation; or when it edges toward exclusion, targeting, or anything that could be discrimination or harassment, it is time to stop absorbing it and start escalating.

Document before you escalate. Keep the actual artifacts, the emails, the messages, the meeting invites you were left off, with dates, in a place that is yours and not company-controlled if you can. Note what happened, when, who saw it, and the concrete effect on the work. You are not building a case to win an argument; you are replacing "it feels like she's undermining me," which is easy to wave away, with a dated record of specific events, which is not. Facts travel; feelings get dismissed.

When you do bring it to your manager or HR, lead with impact on the work, not with character judgments about the other person. "These three threads went out without me, and here are the two decisions I missed as a result" lands. "He's being passive-aggressive" invites a shrug. Bring the pattern, bring the documentation, and bring what you have already tried. You will be taken more seriously as the calm, organized person who tried to resolve it directly first, which, by following everything above, you genuinely will be.

A worked example: the channel jab, decoded and answered

or get this in about 8 seconds