Change an event to out of office in Google Calendar and what guests see

An event already sits on the calendar, holding Thursday and Friday, and it now needs to become an Out of office event so that meeting invitations stop landing inside it. The edit screen offers a title, a time, a location, guests, a description, and a color. It offers no way to turn that event into an Out of office event.

That is not a missing button. It is a rule, and knowing the rule turns a frustrating hunt into a two minute rebuild.

The type is fixed at creation and cannot be edited later

Google Calendar treats Out of office as an event type, not as a label or a colour. Every event carries a type, and the published list is short: a default event, a birthday, an event generated from Gmail, Focus time, Working location, and Out of office. Google's reference for the event resource states the constraint in one line: the event type cannot be modified after the event is created.

This is why the search for a conversion setting never ends well. There is no hidden menu item, no keyboard shortcut, and no third party extension that can reach past it, because the restriction sits in the data model rather than in the interface. Different types also allow different fields, so an existing event carries properties that an Out of office event is not allowed to have, and properties it is missing.

The same rule explains two related dead ends. An Out of office event cannot be moved to another calendar, because moving an event changes its organizer and that operation is limited to default events. And an event brought in from an external file arrives as a default event regardless of what it was before.

So the practical answer to changing an event to Out of office is always the same shape. Create a new Out of office event for the same dates, then delete the old one. Everything below is about doing that without losing what the original event was carrying, and about the settings that decide what other people experience.

Where the option appears, and why some accounts never see it

Out of office, Focus time, and Working location are only available on primary calendars, and only to some Google Calendar accounts. That sentence covers two separate failures that look identical.

The first is the calendar. If a secondary calendar is selected in the create dialog, such as a project calendar or a shared team calendar, the Out of office choice does not appear. Switching the calendar field back to the primary one makes it visible again.

The second is the account type. Out of office is a Google Workspace feature rather than a feature of every Google account, which is why a personal address can show the ordinary event form with nothing beside it while a work address on the same Mac shows the full set. A Workspace administrator can also disable the feature for a domain, and in that case no client side change brings it back. The request goes to whoever administers the domain.

Two checks settle it quickly. Open the create dialog, click More options, and look at the row of event types across the top. If Task and Appointment schedule appear but Out of office does not, the account is the reason rather than the calendar. Then switch the calendar selector to the primary calendar and look again. If the option appears, the calendar was the reason.

There is one more distinction worth making before rebuilding anything. An Out of office event is not the same as a Gmail vacation responder. The calendar event declines meeting invitations; the Gmail setting replies to email. Turning on one does nothing to the other, and the pair is usually needed together.

The three decline behaviours, and which one to choose

The decline behaviour is the reason to use this event type at all, and it has three settings rather than the on and off switch most people expect. Google's field documentation names them precisely.

The first declines nothing. The event blocks the time visually and marks the account as away, but invitations continue to arrive and sit unanswered. This is the right choice for a day away that still contains one meeting that must be kept.

The second declines every conflicting invitation, including the ones that were already on the calendar before the Out of office event existed. This is the setting that surprises people, because creating the block can send declines for meetings that were accepted weeks earlier.

The third declines only new conflicting invitations that arrive while the Out of office event is present. Existing meetings are left alone. For most vacation blocks this is the setting that matches intent, and it is the one to reach for when the days being blocked already contain accepted meetings that somebody else will reschedule.

A message can be attached to the decline, and Google describes it as the response message used when an existing event or a new invitation is automatically declined. That text is the only thing the other person reads, so it carries the whole explanation. Dates and a name to contact instead are worth more than a sentiment. Leaving it empty sends a bare decline, which reads as a rejection rather than as an absence.

What guests actually see

Three separate things happen on the other side, and confusing them causes most of the awkwardness around this feature.

Anyone who looks at the calendar, with permission to see event details, sees the Out of office event by name across the blocked days, shown in a distinct style rather than as an ordinary busy block. Anyone with only free and busy access sees busy time with no title.

Anyone who tries to invite the account to a meeting inside the block sees a decline on their own copy of the event, with the attached message attached to it, and their copy of the invitation shows the response status as declined. The four response states Calendar tracks are no response yet, accepted, tentative, and declined, and an automatic decline writes the last of those.

Anyone who was already on a meeting inside the block sees nothing at all, unless the second decline setting was chosen. This asymmetry is the practical difference between the settings, and it is invisible in the create dialog.

One behaviour is worth stating because it catches organizers out. A decline does not remove the meeting from anyone else's calendar. The meeting proceeds with one fewer attendee, so a block that is meant to stop a meeting from happening still needs a message to the organizer.

What can still be edited once the block exists

The type is frozen, but almost nothing else is. This is worth knowing because it removes the temptation to delete and rebuild every time something shifts.

The dates and times can be changed freely, including dragging the block wider in a week view. A block created for Thursday and Friday extends to cover Monday without any loss of behaviour, and the decline setting continues to apply to the new range.

The decline mode itself can be changed after the fact. Switching from declining nothing to declining new invitations starts the automatic replies from that moment forward, and switching in the other direction stops them. The decline message can be rewritten at any time, and the new text is used for every decline sent afterwards. Declines already sent are not revised, so a message that named the wrong return date needs a direct correction to the people who received it.

The title and color are editable, which matters more than it sounds. The title is what colleagues read on a shared calendar, so a block called Out of office does less work than one that names the return date.

What cannot be added is a guest list. Out of office events do not carry attendees, so telling people is a separate act: a message, a shared calendar they already watch, or an ordinary event created alongside the block.

Out of office compared with the alternatives

Blocking time has four common shapes, and they are not interchangeable.

Approach	Blocks the time	Declines invitations	Sends a message	Calendar it works on	Type editable later
Out of office event	Yes	Optional, three modes	Yes, custom text	Primary only	No
Focus time event	Yes	Optional, three modes	Yes, custom text	Primary only	No
Busy all day event	Yes	No	No	Any calendar	Not applicable
Working location entry	No	No	No	Primary only	No

Focus time is the closest relative. It carries the same three decline modes and the same message field, and it adds a chat status that can be set to available or do not disturb. The difference is presentation rather than mechanics: Focus time reads as heads down work, Out of office reads as absent.

A busy all day event remains the only option for anyone whose account does not offer Out of office, and it is the right fallback rather than a poor one. It shows as busy to scheduling tools, it appears on shared views, and it can live on a secondary calendar. What it does not do is answer invitations, so the inbox still needs attention.

Working location is sometimes reached for by mistake. It records where work is happening rather than whether it is happening, and it does not block time or affect invitations at all.

One column in that table is worth reading twice. Out of office lives on the primary calendar only, so a team that blocks absence on a shared calendar is using the busy all day row whether it meant to or not. How desktop calendars differ in what they can show for each of these event types is set out in Compared with other calendars.

Rebuilding the block without losing anything

The rebuild is short, and the order matters because the decline behaviour fires when the new event is saved.

First, open the existing event and copy anything that needs to survive: the exact start and end, the description, and any list of people who should be told. Out of office events do not carry guests, so a block created from a meeting loses that list, and the people on it need an ordinary message.

Second, create the Out of office event for the same dates before deleting anything, and pick the decline mode deliberately. If the block covers meetings that are already accepted and should stay accepted, choose the mode that declines only new invitations.

Third, delete the original event. If it had guests, deleting it sends a cancellation, so decide whether that cancellation is wanted before clicking. If the original was a placeholder with no guests, deletion is silent.

Recurring blocks need one extra decision. A repeating Out of office event stores the time zone in which the repetition is calculated, which means a weekly block created in one zone and viewed from another keeps its original local time rather than shifting. For a recurring block that should always mean local afternoon, create it in the zone that will be lived in.

Finally, set the Gmail vacation responder separately, and give both the same dates. The calendar half answers meetings; the mail half answers everything else.

A block built this way is only useful if it is actually seen, which is where the reading surface matters more than the create dialog. The order for connecting an account and deciding which parts stay in the browser is laid out in the Guide.

What to change first

Open the existing event, copy its dates and description, then create a fresh Out of office event on the primary calendar with the decline mode set to new invitations only, and delete the original last. If the option is missing entirely, a busy all day event plus a Gmail vacation responder covers the same ground, and a native Mac calendar such as Caltimate keeps that block visible in the menu bar without opening a browser tab to check.