MIDOriginal workplace satire. The out-of-office messages below are invented examples, not forwarded mail or accounts of a real employer.
There was a time when an out-of-office note was a fact. “I am away. I will reply when I return.” A person, absent, with a return date. Somewhere along the way the note stopped describing a day and started describing an org chart.
Today a single absence can cascade. You are out. You have delegated to a backup. The backup is out. The backup has named a delegate, who points you at a team, who points you at a form, who points you at a person who is, in turn, already out. Your absence has become a succession plan. The company has now named a heir apparent to your inbox, and that heir apparent has their own out-of-office.
This note is not about revenge. It is about the moment when an absence note stops informing a sender and starts a scavenger hunt.
Sarah (out) → Priya (backup) → Priya's delegate, Marcus → “see the Coverage Sheet” → the Coverage Sheet names Devon → Devon is on PTO until the 14th → Devon's note says “for anything urgent, contact Sarah.”
The loop is complete. The sender has now emailed their own absence request back to the origin, and every person in the chain has replied from a beach, a child's football match, or a quiet house where someone has finally turned off a phone.
The problem is not that teams share coverage. Coverage is good. The problem is a note that tells a sender nothing they can act on and sends them on a tour of everyone else's vacation. A useful absence note answers three questions and then stops talking.
One of these. Who can help me now, or when I will hear back. Everything else is scenery.
An out-of-office has one job: route the message so it is not lost, and tell the sender the mail will not be answered today. It is not a place to hint that your workload is heroic, that the team is stretched, or that the Coverage Sheet is a living document that changes based on the moon. Those are conversations for a review, not a reply.
Before: “Out of the office through Friday. For urgent matters, please contact my backup Priya, or if she is unavailable, the coverage team, whose current delegate can be found via the shared Coverage Sheet. I will respond on my return.”
After: “Away until Monday. I won't read mail until then. For anything time-sensitive before then, reach Devon at [email protected] — he's covering this week. Otherwise I'll reply when I'm back.”
The revision names one person, gives that person's email, and closes. No chain, no sheet, no detour through a fourth stranger's holiday. The sender gets a single, reachable human and a clear date. That is the entire product.
Before: “I am currently out of the office with no access to email. I have attempted to delegate my responsibilities but have been unable to reach anyone available. Please try again later, or contact whoever is listed on the team wiki under “Coverage,” if that page is up to date.”
After: “Away with no email access until Monday. There is no one covering this week. For anything that cannot wait, contact my manager at [email protected] and note that this came from me. I'll respond when I return.”
This is the honest version. It admits that coverage failed, points to the one person who can actually escalate, and stops. It does not pretend the team has a plan it does not have, and it does not dump the sender back onto a wiki that may be a week stale.
Before: “Out Oct 6–8. Coverage: Priya (primary), Marcus (secondary, via Coverage Sheet), Devon (tertiary). For billing, contact finance. For access, contact IT. For press, contact comms. For everything else, expect a delayed response.”
After: “Away Oct 6–8. For billing, [email protected]. For anything else, I'll reply when I return on the 9th.”
The first version reads like an emergency contact tree. It is trying to cover every case and ends up covering none of them, because a sender who is urgent does not want a menu — they want a name. The second gives one real path and defers the rest honestly. Most messages are not urgent. Most senders just want to know the mail landed somewhere it will be seen.
“[Away dates]. I won't read/reply until [return date]. For anything needed before then, contact [one person] at [email]. Otherwise I'll reply when I return. Thank you.”
Four lines. One name. One date. The hardest part is deleting the rest.
Teams love the long version because it looks responsible. It signals that coverage was considered, that nobody was forgotten, that the absence was handled like a senior operator. But it outsources triage to a spreadsheet the sender cannot reach. A sender who cannot find the coverage page simply stops asking and emails you again in three weeks, when you are out again, and the loop begins.
The short note is not lazy. It is a boundary. It says the absence is real, the return is real, and exactly one person can help in the meantime. If that person is also out, name them plainly rather than forwarding the sender into another void. “Devon is covering but is also away until the 14th — best to hear back Monday” is kinder than a chain that ends where it began.
The worst out-of-office promotes a phantom. “For urgent matters, contact my assistant, who will triage on my behalf.” Your assistant is not your succession plan. They are a person with their own inbox and possibly their own out-of-office. Naming a third party as your proxy without their agreement is a rumor about their availability, and the sender will learn this the hard way, from a reply that says, in so many words, “actually, no one is here.”
If you do name a backup, confirm it with them first. A real “yes, I've got this” beats a fictional one every time.
The out-of-office returns to you. It is three lines, one name, one date. The chain dissolves. Nobody inherits a middle manager they did not ask for, and the sender is not left emailing their own problem back to the start.