A Translator's Guide to 'Per My Last Email'
A Translator's Guide to "Per My Last Email"
"Per my last email" is four words that say everything except what they appear to say.
What they appear to say: I am helpfully directing you to information I already provided.
What they actually say: I have told you this before. You did not read it, or you did not act on it, or you are now raising a question that should not need raising. I am holding this against you. Here is the receipts.
The phrase has become famous enough that most people now know the subtext. Knowing it has not diminished its use. If anything, the explicitness of the subtext is the point. The message communicates precisely because everyone in the thread understands exactly what is happening beneath the surface.
This guide covers the full taxonomy of passive-aggressive professional email. The worked examples are real patterns, not invented ones. You will recognise most of them.
Why Email Is the Natural Habitat of Passive Aggression
A meeting allows tone, expression, and real-time correction. An email does not. Once sent, the words sit there. They can be forwarded. They can be stored. They can be used in an HR conversation six months later.
This creates an interesting constraint. The email must communicate something — disagreement, frustration, a rebuke — while maintaining a surface that cannot be directly accused of anything. The passive-aggressive email is an act of precision engineering. Every word is chosen to be deniable while still landing exactly where it was aimed.
The medium also has a time dimension that meetings do not. In a meeting, you cannot wait three days before responding. In an email, you can. The length of the delay carries information. The tone of the response carries more. A one-sentence reply to a detailed request communicates something. So does a reply that arrives at 11pm on a Sunday.
The Canon: Phrases and What They Actually Mean
"Per my last email..."
Decoded: You did not read it. Or you did, and you are asking again anyway. Either way, I am noting this.
When it arrives: You have asked a question that was answered in a previous message. Usually happens when an email chain has grown long enough that the earlier message is several scrolls down, or when the previous email was read quickly and the relevant detail was missed.
The escalation version: "As outlined in my email of [specific date]..." — this is the receipt version. A date has been cited. The paper trail is being made explicit. This is a more serious version of the same rebuke.
"Just looping in [name] for visibility."
Decoded: I am escalating this. The person being looped in is someone whose presence will change the dynamic of the conversation.
When it arrives: When the conversation is not going in the direction the sender wants. When a request has been declined, delayed, or ignored. When the sender wants the recipient to know that someone above them is now watching.
The soft version: "Copying [name] as they may be helpful here." Same mechanism, warmer wrapper.
The important detail: "For visibility" is doing the work. Visibility means awareness. Awareness means accountability. The person being looped in now knows what you said and when you said it.
"Happy to reconnect on this if helpful."
Decoded: The ball is in your court. I have done my part. Any failure to progress this from here is yours.
When it arrives: Near the end of a chain where the sender has provided information, made a request, or raised a concern, and the recipient has not moved. This phrase hands ownership of the next step back to the recipient in writing.
Worked example:
Hi James,
Happy to reconnect on this if helpful — I just want to make sure we're not losing momentum before the end of the month.
[Name]
Translation: James. I said what I needed to say. You have not responded. I am giving you one more chance to respond before I find another way forward. The "end of the month" is a soft deadline I have inserted to make my urgency legitimate.
"As previously discussed..."
Decoded: We have been through this. The fact that we are going through it again is something I am noting.
When it arrives: In a situation where an agreement, direction, or decision was reached in a meeting or phone call, and a subsequent email implies that the discussion never happened.
The important detail: "Previously discussed" is doing two things simultaneously. It is reminding the recipient of the agreement, and it is establishing on the record that the discussion happened. If the matter later goes to HR or to a formal review, this email has created a trail.
"For future reference..."
Decoded: Do not do that again.
When it arrives: After a procedural misstep — an email sent to the wrong person, a request that bypassed the correct channel, a communication that happened at the wrong level. "For future reference" is the polite corporate equivalent of a formal correction.
The full version: "For future reference, the correct process is to submit the request through the team inbox, which is monitored by [name]." The level of specificity in this sentence is proportional to the size of the correction being delivered.
"I believe this was covered in my correspondence of the [date]."
Decoded: I told you. Twice. On a specific date I have noted. Here is the proof.
When it arrives: When the sender has anticipated that the recipient might dispute the history of the conversation, and has prepared accordingly. The citation of a specific date signals that records have been kept.
This is the most formal version of the "per my last email" family. It does not appear often, but when it does, the person writing it is serious.
"Happy to walk you through the process if that would be helpful."
Decoded: You should already know this. I will explain it again because I have to, but I want it noted that this is additional work I should not be doing.
When it arrives: When a colleague has asked a question that is answered in existing documentation, onboarding materials, or prior communication. The offer to "walk you through" sounds generous. It is designed to communicate that the question should not have needed to be asked.
"Keen to get your thoughts on this by end of week."
Decoded: I need a response by Friday. I have phrased it as a desire rather than a request because the direct version sounds demanding, but Friday is the actual deadline.
When it arrives: When a decision, review, or approval is needed within a specific timeframe. "Keen to get your thoughts" is softer than "please respond by Friday" but they mean the same thing.
The escalation version: "Happy to escalate to [name] if timing becomes a constraint." This email now has a consequence attached to non-response. Act by Friday or someone senior finds out.
"I want to make sure nothing falls through the cracks here."
Decoded: Something is at risk of falling through the cracks and I believe it is your responsibility to prevent that.
When it arrives: When a project or task is not progressing as expected, and the sender is positioning themselves as the responsible party who identified the risk. The sentence sounds collaborative. It is assigning blame in advance of the outcome.
"I'll leave this with you."
Decoded: This is now entirely your problem.
When it arrives: At the end of a chain where the sender has provided their view, made their request, and received an unsatisfactory response. The sender is formally disengaging while recording that the matter exists and that they raised it.
Worked example:
Hi Sarah,
Thanks for the context. I'll leave this with you.
[Name]
This is four sentences of which the only meaningful one is the last. "Thanks for the context" is acknowledgment. "I'll leave this with you" is transfer of ownership. The matter is documented. The sender is absolved. Good luck, Sarah.
How to Read an Email Chain Like a Translator
When you receive a chain that seems charged but cannot articulate why, look for these signals:
The formality shift. If a usually casual correspondent switches to "Dear [Full Name]" or starts signing off with their full title, the register has changed. Something was wrong in the conversation before this email arrived.
The BCC. You cannot see it, but it exists. When someone is BCCing a manager, their tone sometimes shifts subtly. Look for language that sounds slightly more careful than usual, more on-the-record. The BCC is being written for two audiences.
The timestamp. An email arriving at 6am or 11pm carries information. So does a reply that takes four business days when it usually takes four hours.
The specificity of dates and references. When an email starts citing specific dates, specific meeting references, or specific email subjects, a paper trail is being built. This is not a casual conversation anymore.
The absence of a greeting. Dropping "Hi [name]" and going straight to the content is a subtle signal. Not always hostile — sometimes just efficient. Context determines which.
A Note on "Best"
"Best" as an email sign-off is neutral in most contexts. "Best regards" is slightly warmer. "Kind regards" has a formal ring. "Regards" alone, with nothing before it, means the sender has reduced the warmth of the sign-off deliberately.
"Thanks" as a sign-off when you are not thanking the person for anything is ambiguous. It can be warm. It can also be the minimum viable sign-off — present because it would be more charged to omit it.
"Thanks in advance" is not a sign-off. It is a request masquerading as a sign-off. It assumes the requested action will be completed and thanks you for the completion preemptively. This is aggressive. Politely worded, but aggressive.
The Last Word
The most useful thing to know about passive-aggressive email is this: the person writing it is usually expressing something real.
"Per my last email" comes from genuine frustration. "For future reference" comes from genuine exasperation. "I'll leave this with you" comes from genuine exhaustion. The indirectness is not dishonesty — it is the person trying to express something real inside the constraints of a professional context that does not allow direct expression.
That does not make it comfortable to receive. It does make it worth understanding.
The words say one thing. The meaning is something else. Now you can read both.
Circle Back turns this into a daily puzzle. Four phrases, four decodes, nine in the morning. Play today's.