Per My Last Email: A Taxonomy of Passive-Aggressive Office Communication

By the CorporateWords desk · 2026-09-11 · 7 min read

Corporate conflict has a dress code. Open anger is career-limiting, so workplace hostility evolved the way anything evolves under pressure: it got subtle, formal, and plausibly deniable. The result is a genre, the passive-aggressive professional register, in which fury arrives wearing a smile and carrying documentation.

Everyone reads this genre fluently and almost nobody admits to writing in it. This taxonomy names the major species, explains what each is actually doing, and, because this site is a survival guide and not just a zoo, covers the more useful question: when receiving fire, how to tell a real threat from a bad day, and when writing, how to get the protection without the poison.

The reminder family

The friendly reminder is the gateway species. The first one is often genuinely friendly. The second is formal. By the third, 'friendly' is doing hazard duty and your manager has joined the CC line, which is how you know that in this genre, warmth and threat level move in opposite directions. Track the CC field across a reminder sequence and you are watching a countdown timer wearing a smile.

'Just checking in' is the reminder's gentler cousin, and the word doing the work is 'just,' which converts a collection notice into an afterthought. Nobody has ever just checked in. Its sibling 'just bumping this to the top of your inbox' adds the innovation of blaming your inbox's topology rather than you, a kindness with an expiration date.

The correct response to the entire family is the same: answer fast, even if the answer is only a date. Reminder sequences escalate on silence, not on bad news. 'Working on it, you'll have it Thursday' resets the timer. Silence advances it, and the fourth message in a reminder chain is never sent to you alone.

The receipt family

'Per my last email' is the genre's most famous specimen, the corporate duel glove. Translation: I already answered this, you did not read it, and there is now a record that I said so. Its formality is the message; nobody writes 'per' while calm. Adjacent species include 'as previously discussed,' 'as mentioned below' with the below highlighted, and the nuclear variant, 'per my last several emails,' which is one keystroke from a meeting with HR in either direction.

'As discussed' is the receipt family's respectable member, and understanding the difference is the whole game. 'As discussed, you'll own the vendor relationship going forward' converts a hallway conversation into a record, and whoever writes that summary writes the history. Used honestly, it is simply how professionals prevent the amnesia that meetings induce. Used selectively, with convenient edits, it is how territory gets annexed one recap at a time. Read every 'as discussed' email carefully, and correct the record immediately when it is wrong; silence ratifies.

Then there is 'noted,' the one-word acknowledgment that confirms receipt and promises nothing, an airlock of a word. From a peer it is usually just brevity. From your manager, in response to a concern you raised, it means the topic is closed and reopening it will cost you; bring data or let it lie.

The audience family

Some passive aggression is not in the words at all. It is in the routing. The strategic CC adds your manager to a thread as a silent witness, converting a conversation into a hearing without a single hostile word. The escalation is deniable: 'just keeping everyone in the loop.' The countermeasure, if you are the one CC'd at, is to answer well and completely, once, to the whole audience; competence in front of the summoned witnesses defuses the summons.

The BCC is the CC's disreputable relative, surveillance rather than theater, and it has a famous failure mode: the BCC'd party replying-all. Professionals with long careers ahead of them mostly do not use it; forwarding the sent message afterward accomplishes the same witness function without the landmine.

Scheduling has its own dialect. The meeting invite with no agenda from someone senior, the 4:55 PM Friday calendar drop, the recurring one-on-one that suddenly appears with HR as an optional attendee: routing and timing carry messages that no one has to stand behind. Most have innocent explanations. The skill is noticing the pattern without becoming the person who sees threats in every timestamp, a genuine occupational hazard of learning this material.

When to write it, and when to put it down

Here is the honest part. The receipt family exists because documentation genuinely protects people. If commitments around you have a habit of evaporating, if blame at your shop flows downhill and looks for low ground, then 'as discussed' emails and confirmation summaries are not passive aggression. They are seatbelts, and you should write them without guilt, warmly, every time. Tone is the entire difference: 'confirming so we're aligned' and 'per my last email' can carry identical content, and only one of them starts a war.

What is almost never worth deploying is the genre's actual weaponry, the escalating reminder with the growing CC, the cold 'noted,' the formal register aimed at a peer. These read as strength while writing them and as weakness within the week; every recipient decodes them instantly, and rooms have long memories for who fights this way. If something is worth a third pointed email, it is worth a two-minute conversation, which resolves in one exchange what the thread would have inflamed for a month.

And when you receive genre fire, the highest-percentage move is to refuse the register: answer the content plainly, warmly, and completely, as if the barbs were not there. This is not naivete. It is the one response the genre has no counter for, because passive aggression requires a dance partner, and documentation dances alone just fine.