Out of office in Google Calendar: stopping invites while you are away

Most people reach for out of office in Google Calendar the evening before a trip, and discover two things at once. The option is not where a normal event lives, and it does something more aggressive than blocking time. An out of office entry is the only thing in Calendar that answers other people on your behalf, which makes it useful and makes it worth understanding before a week of invitations hits it.

The confusion in this topic comes from four different features being described with the same words. Out of office, focus time, working hours and an ordinary busy event all mark you as unavailable, and only two of them refuse anything. What follows separates them using Google's own documentation, then covers the settings inside an out of office entry that decide whether meetings already on the calendar survive.

Out of office is a distinct type of event

An out of office entry is not a normal event with a special title. Google's Calendar API describes events as carrying an eventType, and the documented values are birthday, default, focusTime, fromGmail, outOfOffice and workingLocation. The reference is explicit that the type is fixed at creation: it cannot be modified after the event is created.

That single line explains a common frustration. An ordinary event cannot be converted into an out of office entry after the fact. Rewriting the title to "OUT OF OFFICE" changes nothing about how Calendar treats it. The entry has to be created as the right type from the start, and an existing block has to be deleted and recreated.

The behaviour that comes with the type is what makes it worth the extra step. Google's help page for availability states the effect plainly:

When you indicate that you're out of office, your calendar will automatically decline all meetings during that time. Source: support.google.com

Declining is an action taken on your account by Calendar, without you present. The organiser receives a real decline, the seat opens up, and the meeting either moves or happens without you. No other kind of calendar block does this.

Creating one, and the two settings buried inside it

The entry point is the date row rather than the grid. On a computer, click the first date you will be away at the top of the calendar, then choose Out of office from the row of event types. Pick the dates, and note that a time can be specified rather than the whole day if only an afternoon is affected.

Two options at the bottom of that panel matter more than the dates. The first is the repeat control next to "Does not repeat", which turns the entry into a recurring one. That is how a regular non working day gets handled once instead of being recreated every week. The second is the line offering to change your decline settings and edit your decline message, and skipping past it is the single most common mistake in this whole topic.

The decline message is a real reply, not a note to yourself. The API describes it as the response message to set if an existing event or new invitation is automatically declined by Calendar. Whatever sits in that box is what a colleague reads when their meeting request bounces, so a sentence naming the return date and an alternative contact does more work than the default text.

Finish with Save. The entry then appears on the calendar as its own kind of block, and the declining starts from the moment it exists rather than from the start of the trip.

Three decline behaviours, not one

The phrase "automatically decline all meetings" hides a choice. Out of office entries carry a setting the API calls autoDeclineMode, and it has three documented values.

Setting	What happens	When this is right
declineNone	Nothing is declined. The entry marks the time and stays quiet.	Visibility only, when a colleague still needs the option to book a slot
declineAllConflictingInvitations	Every conflicting invitation is declined, including meetings already accepted before the entry existed	A genuine absence where nothing on the calendar will happen
declineOnlyNewConflictingInvitations	Only invitations that arrive while the entry exists are declined. Existing commitments survive	Most cases, because a recurring meeting scheduled months ago is not automatically cancelled

The distinction between the last two is the one that catches people. Choosing the wider setting over a week that already held three accepted meetings sends three declines, and nobody is asked first. The narrower setting leaves those three in place and only protects against new requests. Neither is wrong, but the wide setting applied to a past-heavy week produces messages that look like a change of mind.

Focus time uses the same mechanism, with a documented default worth knowing: by default focus time declines new and existing meetings, and a setting exists to decline only new meeting invitations. Out of office offers the same control in the panel below the decline message.

What out of office does not do

It does not reply to email. That belongs to Gmail's own vacation responder, which is configured separately and runs on its own dates. Setting one and not the other is how a colleague receives an automatic decline for a meeting and a normal looking silence in their inbox on the same afternoon.

There is a narrow overlap, and its conditions are specific. Google documents that if you use Gmail for work or school and show when you are out of office, Gmail updates your calendar status, and when someone emails you that status is sent to them. Two requirements sit alongside it. The out of office event must last the entire day or extend past your regular working hours, and the sender must have access to your calendar to see the status at all, which means the calendar has to be shared with them. A short afternoon entry produces no status, and neither does one on a calendar a stranger cannot see.

The feature also depends on the kind of account. Google's page on working hours and availability states that these settings apply if your account is through a work or school organisation, and that an administrator can turn the option off for the organisation. On a personal account there is no out of office event type to choose. The nearest substitute is an ordinary all day event, which occupies the slot in any free and busy lookup and declines nothing.

Availability also differs between the types. The 2021 release that introduced repeating out of office entries lists a broad set of editions, including Business Starter, Business Standard and Business Plus, Enterprise Standard and Plus, and Education Fundamentals and Plus. Focus time is documented for a narrower set, which is why one option can appear in the event row while the other is missing.

The four blocks, compared honestly

Feature	Refuses invitations	Sends a message	Visible to others
Out of office	Yes, with three modes	Yes, an editable decline message	Yes, as its own block
Focus time	Yes, new and existing by default	Yes	Yes
Working hours	No, the organiser only sees a warning	No	Shaded when somebody schedules with you
Ordinary busy event	No	No	As a busy block, subject to sharing settings

Read down the first column and the design becomes clear. Working hours is a hint for a human to read. Out of office and focus time are instructions carried out by software. The choice between those two is really about duration and intent: focus time protects recurring hours inside a working week, and out of office covers whole days when nothing will happen.

What colleagues actually see

The entry declines reliably, and how much of it anyone can read depends on a setting made somewhere else entirely. Google's sharing permissions decide that, and the two levels most calendars use behave very differently. A calendar shared as "See only free/busy (hide details)" lets people find out when you are busy and hides the names and details of what is there. A calendar shared as "See event details" shows the names, times, places and descriptions.

The consequence is that an out of office block can be doing its job while looking anonymous. A colleague checking a calendar shared at the free and busy level sees a solid block with no label, has no way to tell an absence from a long meeting, and reasonably assumes the time might open up. The decline arrives later and reads as a surprise. Sharing the calendar at the detail level, or simply telling the team the dates, removes a round of guessing that no setting inside the entry can fix.

The organiser's side is worth knowing too. Working hours gives whoever is scheduling a warning when a time falls outside a guest's hours, which the 2019 release describes as a notification shown to the event creator. That warning is the only advance signal in the system. An out of office entry produces no warning at the moment of booking, so an organiser who ignores or never sees the grid shading finds out by receiving the decline.

Where it fails in practice

The entry is tied to one calendar. Google's API documentation notes that only default events can be moved between calendars, and that outOfOffice entries are among the types that cannot. An out of office block created on a personal calendar cannot be dragged to a work calendar later, and the invitations that need declining arrive on whichever account colleagues use.

Copies made by syncing tools lose the behaviour entirely. Any service that mirrors events between accounts writes a plain busy block on the far side, because the special properties do not travel. Google's own documentation makes the same point about importing: only events with a type of default may be imported, and a non default event that is imported has its type changed with the type specific properties dropped. A mirrored out of office block therefore looks correct to a person and declines nothing.

Travel days deserve their own entry rather than being folded into the trip. A flight at seven in the evening leaves a working day that is genuinely bookable until mid afternoon, and covering the whole date declines meetings that could have happened. Two entries, one for each end of the trip, keep the real hours open. The same gap logic applies to ordinary weeks, where the time needed to get between two places is the part no block represents. The Travel time page covers how that gap gets held open instead of assumed.

One last check belongs in the routine. Because the decline message is stored on the entry rather than on the account, a recurring out of office entry keeps sending whatever sentence was written the first time. A message naming a date that passed two months ago is worse than no message, so reading it once a quarter is worth the minute.

What to change first

Open the existing out of office entry and read the decline setting and the message. If it is set to decline everything, decide deliberately whether meetings already accepted should be cancelled, and switch to declining only new invitations if they should not. If nothing is set up yet, create the entry for the next absence with the decline message written before the dates, since a Mac calendar app or a browser both save whatever is in that box unchanged. Then set Gmail's vacation responder for the same dates, because Calendar will not answer email.