How to Write a Two-Sentence Out-of-Office That Tells People What to Do

Anyone leaving for PTO, a conference, or a two-day focus block can write an out-of-office in 10 minutes: two sentences, one return date, one named next step. Run it in ChatGPT, Claude, or Gemini before "I have limited access" trains the whole company to wait.

An out-of-office is not a memoir. It is a routing slip. Sentence one says when you are back. Sentence two says who to contact or what to do now. A third sentence is a novel.

This loop is a skill. Read what a skill prompt actually is. If the last thread is a fight, finish the difficult email reply first. Then set the auto-reply.

Write an out-of-office in five steps

1. Name the window, not the vibe

Instruct ChatGPT, Claude, or Gemini: "Do not draft an out-of-office yet. Write one line: I return on [weekday, date] at [time zone]. No away. No taking some time. If I did not give a date, write UNKNOWN and stop."

UNKNOWN means you still owe a date. A model that invents "next week" is lying on your behalf.

Banned: limited access, currently offline, sorry for the delay in advance, I will do my best to respond, enjoying a well-deserved break.

2. Name one human or one action

Send the date line back. Instruct: "Write sentence two as either one named person with a channel, or one action the reader can take without me. Not both. If I named no backup, do not invent a colleague. Use an action."

Good: "For invoices, email Priya in finance." Good: "The deck is in the shared Q3 folder. I will reply on Monday." Bad: "Reach out to the team if urgent." The team is not a person. Urgent is not a rule.

If the backup has not agreed, do not put their name in. Ask first. An ambush is how you return to a mess.

3. Force two sentences, then stop the model

Now ask for the draft. Hard cap: two sentences. No greeting. No sign-off. No emoji. No list.

Tell the model: "Sentence 1 is the return date. Sentence 2 is the contact or the action. If a banned phrase appears, rewrite the whole thing. Do not add a third sentence for warmth. Do not explain why I am gone."

ChatGPT will add "Thank you for your patience." Claude will hedge about checking in. Gemini will stretch "Monday" into "early next week." Cut all three.

If people must meet while you are gone, that is a calendar invite, not a third sentence here.

4. One human pass against the calendar

Read the two sentences as if you were the vendor who needs a PO today.

Check three traps:

• A date that does not match the calendar hold.
• A backup who does not know they are the backup.
• Limited access hiding in a synonym: "slow to respond," "spotty signal," "checking when I can."

Fix those in your own words. Then send the edited pair back: "Replace only the words I changed. Do not re-expand."

One pass. A second pass is how two sentences become a paragraph about rest.

5. Paste the same two sentences everywhere

Email auto-reply. Slack status. Calendar default reply if you use one. Same words. Do not write a "short Slack version" that drops the date. People will read the short one.

Save the banned list with the loop. Next trip, run the same skill. If you catch a travel itinerary in the auto-reply, you have a newsletter. Stop.

Reusable skill card

Trigger: You are about to flip an auto-reply and the draft in your head still says limited access.

Input: A real return date with time zone, one named backup who agreed or one action the reader can take, plus the banned-phrase list.

Output: Two sentences. Sentence 1 is when you are back. Sentence 2 is who to contact or what to do now. No greeting. No why.

Stop: After one human pass against the calendar. No third sentence. No invented colleague. No limited access, even if the wifi will be bad.

Takeaways

• Two sentences: a return date, then a person or an action. Then paste.
• Limited access is not a plan. Ban it, then ban the synonyms.
• UNKNOWN on the date is better than a model guessing next week.
• Same two sentences in email, Slack, and calendar.