The short version
- If you are writing an out-of-office, write one that carries information rather than regret. Examples below, for four situations.
- Three rules: no apology, a real return date, and specific decision authority rather than "contact my colleague".
- Never say "I will reply when I am back" without saying what happens in the meantime. That sentence is the whole problem in seven words.
- The best version of this is not an auto-reply at all, and it is worth knowing what that looks like.
Out-of-office messages default to apology because that is the register the genre established. They can carry considerably more information for the same number of words, and the difference is felt by whoever receives them.
"My OOO says 'I'll reply when I'm back'. That is a delay, not an answer."
Three rules
No apology. Taking leave is not an imposition and apologising for it teaches everyone that it is. Drop "sorry for any inconvenience" entirely.
A real date, and say what happens on it. "Back on the 14th" is better than "back soon", and "back on the 14th, replying from the 15th" is better still, because it is honest about the first day being triage.
Specific authority, not a name. "Contact Marek" makes the reader guess whether Marek can help. "Marek can approve invoices up to 5,000 and answer anything about the payments work" tells them whether to bother.
Four examples you can copy
Two weeks of annual leave. "I am on leave until 14 September and not reading messages. Marek Nowak is covering payments and can decide anything within the current sprint, including refunds up to 500 euros. The Q4 roadmap discussion waits for me; I will pick it up on the 15th."
One day off. "Off today, back tomorrow morning. Nothing is blocked on me today. If something urgent comes up on the payments work, Marek has context."
Long leave. "I am on parental leave until March. Priya Raman is the owner of data engineering while I am away and makes all decisions in that area. Please do not route things to me: she has the full picture and I will not be reading this."
External or customer-facing. "Thank you for your message. I am away until 14 September. For anything about your account, Sara Bakker is the right person and can help with everything I would. She is at [email protected]. If it can wait, I will pick it up on the 15th."
Note what all four share: a date, an explicit statement about whether messages are being read, and a named person with defined authority. Note also that the long-leave example actively discourages routing to the absent person, which is the only version that works over months.
The version that is not an auto-reply
Every example above is an improvement on the standard apology, and all of them still do the same fundamental thing: they tell the sender when to expect an answer instead of giving one.
The alternative is for your work to answer. With StandIn, the ninety-second brief you confirm at the end of each day is what your StandIn speaks from while you are off: current state, open questions, blockers, next actions, decisions and why. Someone who asks where the migration stands gets the answer in your words, with a source under it, clearly labelled as your StandIn, on the day they asked. It never guesses, and when the answer is not in your brief it says so and names who to ask, which is the same redirect as your auto-reply except that it only fires when the record genuinely cannot help.
Then the auto-reply becomes unnecessary rather than better written, which is why the wedge is retire your out-of-office.
Five common mistakes
- "I will have limited access to email." This means you are working. It invites people to try, and they will.
- "For urgent matters, call my mobile." Either you are off or you are on call. Pick one, and if it is genuinely the latter, define urgent.
- No date. "Currently away" leaves the sender unable to plan, which is the only thing your auto-reply could have given them.
- A deputy who has not agreed to it. Naming someone without telling them is how people discover they are covering by receiving a stranger's escalation.
- Leaving it on after you return. Common, and it teaches people that your auto-replies are not worth reading.
Common Questions
What should an out-of-office message say?
A real return date, whether you are reading messages, and one named person with specific authority rather than a vague redirect. Leave out the apology and any suggestion that you might be partly available.
Should I say I will have limited email access?
No. It is either true, in which case you are working through your leave, or it is a hedge that invites people to try anyway. Say plainly whether you are reading messages.
How do I write one for a long leave?
Name a full owner rather than a cover, and actively discourage routing things to you. Over several months, anything that waits for your return is stale by the time you read it, so the message should redirect rather than queue.
Is it rude to leave out an apology?
No. Nobody reading it feels wronged by your holiday, and the apology mainly signals that leave requires justification. A clear, informative message reads as more considerate than a regretful one.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.