What the Out of office event type actually does
Create an event → choose Out of office (on the event-type row) and the event changes species: it renders as a solid block, and — the headline feature — automatically declines every invitation that overlaps it, existing and future, with a message you set. Colleagues browsing your calendar see the block; schedulers get an instant, polite no without you ever seeing the invite.
Two behaviors worth knowing before you rely on it: the auto-decline fires immediately on creation for meetings already on the books (a heads-up in your team channel spares the confusion), and the event blocks the entire span visually — this is by design, since it signals "don’t plan around gaps".
The decline message is the whole product
The default text is serviceable; a good one carries three facts — you’re out, when you’re back, who covers what:
"I’m out until Monday, Jan 19, with no calendar access. For release questions: Dana. Anything else keeps until I’m back — please re-invite me for the following week if it needs a meeting."
The last clause quietly does the rescheduling for you: people re-book into your return week instead of waiting for you to untangle a pile of declined threads.
Setups beyond vacation
The focus day that defends itself
A monthly deep-work day gains teeth as an Out of office block titled honestly: "Focus day — auto-declining; Slack me if urgent". Unlike a normal busy block, it cannot be booked over by someone who didn’t look. Use sparingly — one day a month reads as discipline, every Friday reads as unavailable-as-identity (Workspace’s separate Focus time type, with optional auto-decline, is the daily-use tool).
Part-time and compressed weeks
Working four days? A recurring Out of office every Friday makes the schedule self-enforcing: nobody needs to remember, because the calendar declines for you. Set the recurrence exactly like any event (weekly, on Friday), write a message that names your working days, and the pattern teaches itself to the org within two weeks.
Guarding the edges of a trip
Start the OOO at noon the day before travel and end it at noon the day after return. The half-days absorb packing and re-entry — and prevent the classic 9:00-the-morning-back meeting that makes vacations feel like they end early.
What Out of office does not do
It does not answer email (pair it with Gmail’s vacation responder — the two are separate systems), it does not cascade to recurring meetings you organize (delegate or cancel those yourself), and it does not show a reason to free/busy viewers — they see busy, not "on leave", so external clients may still email expecting same-day replies. The Gmail responder covers that last gap.
Re-entry is the underrated half of time off: the first morning back is a wall of what moved while you were out. A toolbar view like Calendar Extension for Google Calendar™ turns that first check into a day strip you can absorb with coffee in hand — what’s today, what’s next, what got re-booked into your return week.
Frequently asked questions
Yes — on creation it declines all overlapping events, including ones you had accepted, and notifies organizers with your message. That instant burst of declines is why you announce the OOO in chat first; the calendar is efficient, not gentle.
Split the block around it: end the first OOO event before the meeting and start a second one after. There is no per-meeting whitelist. For a single important call inside a vacation week, two OOO events with a one-hour gap is the clean pattern.
It is available on Workspace and personal Google accounts in the newer event editor — but not on secondary/subscribed calendars you don’t own, and not in some older mobile app versions. Create on your primary calendar in the web editor and the type row appears.
They receive the decline with your message — that part works across organizations. What they cannot see is the OOO on your calendar itself (external free/busy shows plain busy), so pair the calendar block with Gmail’s vacation responder for people who email instead of inviting.