Combining multiple calendars: what it does and where it breaks down

Ask five people what "combining calendars" means and there will be at least three answers. For one it is seeing a Google work calendar and an iCloud family calendar in the same week view. For another it is making sure a dentist appointment in a personal account blocks time on the office calendar. For a third it is moving every event into a single account and closing the others. All three search with the same words, and all three need different machinery.

This article explains what combining multiple calendars actually involves: the three depths it can go to, the data that moves at each depth, the things that stay separate no matter what, and the places where the whole arrangement tends to break down.

Three depths of combining

The useful way to classify a combined calendar is by how far event data travels.

Depth	What moves	Where events live	What other people see
View	Nothing; an app reads each account	Each original account	No change
Busy time	Only the fact that time is taken	Original account, plus blocks elsewhere	The time appears taken
Full copy	The whole event, title and all	Both accounts	Details, subject to sharing

View is the shallowest. The events stay exactly where they were created. A calendar app signs in to each account, reads the events, and draws them on one grid. The person using the app gets one picture of the week. A colleague looking at the work calendar still sees only work events, because nothing was written anywhere.

Busy time exists to change what other people see. When an event appears in a personal calendar, a placeholder marked busy is written into the work calendar. A colleague looking for a meeting slot sees that the time is taken but not why.

Full copy duplicates the event itself, with its title, location and notes, into another account. It is the only depth that produces a single account holding everything, and it is also the one that spreads the most private detail.

Choosing a depth decides two things at once: how convenient the result is, and how far personal information travels. Most frustration with combined calendars comes from wanting the convenience of one depth while expecting the privacy of another.

A combined view is a lens, not a container

At the view depth, the combined calendar holds nothing of its own. It is closer to a saved search across several accounts than to a new calendar. That has practical consequences that are easy to overlook.

Removing the app, or removing an account from it, deletes nothing at the source. The events are still in Google, iCloud or Exchange. Conversely, deleting an event inside the combined view is a real deletion in the account that owns the event, and if that event is a meeting, the change can reach the organizer or other attendees.

The view is also only as current as each connection. An account connected by signing in delivers changes through that account's own sync. A calendar added by subscribing to a published .ics address is fetched on a timer chosen by whatever is subscribing. Microsoft's support page says Outlook.com refreshes subscriptions roughly every 3 hours and Outlook on the web roughly every 6, and that either can take more than 24 hours. Two calendars side by side in the same view can therefore be hours apart in freshness without any visible sign.

What actually travels between calendars

Under the surface, two kinds of information move between calendar systems: event data and free/busy data.

This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol. Source: rfc-editor.org

That format, iCalendar, is what an .ics file contains. A companion standard, CalDAV, published as RFC 4791, defines a standard way of accessing, managing and sharing calendar data in that format. Google and Microsoft also offer their own programming interfaces, and many apps use those instead of, or alongside, the open standards.

The view and full copy depths move event data. Busy time moves only free/busy information, which says when someone is occupied and nothing else. That distinction shows up directly in sharing settings. Google's lowest sharing level is "See only free/busy (hide details)", which its help page describes as letting people find out only when the owner is busy, without names or details of events. A calendar shared at that level, placed into a combined view, appears as a set of untitled blocks. The app is not malfunctioning. The details were never sent.

What a combined calendar does well

Even at the shallowest depth, a combined calendar changes daily work in concrete ways.

• Overlaps between work and personal commitments become visible in one glance instead of two.
• Colour by calendar makes it obvious which account each event belongs to.
• Individual calendars can be hidden temporarily, for a work-only or family-only view.
• New events can be added to any connected calendar without switching accounts, where the account grants write access.

At the busy time depth, the benefit reaches other people. Microsoft 365 offers one built-in version of this. According to Microsoft's support page, one Outlook.com or Google account can be connected to a work or school account in Outlook on the web, and the personal calendar can then be included in the availability shown to people scheduling with the user. No third-party service is involved, though it is limited to a single personal account.

What never merges

A single screen does not turn several accounts into one identity. The gaps show up in three places.

Invitations and responses. A meeting invitation arrives at the account it was sent to, and any reply goes out from that account. Accepting a work meeting from inside a combined view still answers as the work account, which is correct. The mistake that a combined view cannot prevent is creating a new meeting in the wrong calendar, so that invitations go out from a personal address.

Account-level features. Google's help lists features of Google Calendar that are not available in Apple's Calendar app: email notifications for events, creating new Google calendars, and Room Scheduler. Those remain tasks for Google Calendar itself, however the events are displayed.

Behaviour of the combining app. Microsoft's list of known issues for Google accounts added to Outlook includes no support for attachments in events, and a default visibility of "Public" for events created in Outlook, regardless of the Google Calendar setting. Events made inside the combined view can therefore end up treated differently from events made at the source.

Where it breaks down: permissions

Most failed attempts at combining come down to the sharing level. Google offers these levels when sharing with specific people:

• See only free/busy (hide details)
• See event details
• Make changes (see private events as free/busy)
• Make changes and see event details
• Make changes and manage sharing

When the same person owns both accounts, it is tempting to share without thinking about the level. The level should follow the depth. Seeing full details in a view needs "See event details" or higher. Editing one account's events from another needs one of the "Make changes" levels.

Other systems impose their own limits on top. Microsoft's known issues page states that a Google calendar shared with free/busy permissions does not work in Outlook, and that there is a limit of 20 calendars shared with the user.

Where it breaks down: organizations and credentials

Work and school accounts answer to their administrators first. Google's help says that for work or school calendars, the administrator decides whether a calendar can be shared, and that people outside the organization cannot see a calendar that has been made visible only inside it. The same page warns that administrators may be able to see calendars and event details even when the owner has not shared them. That matters for full copy in particular: duplicating personal events into a work account places their details within reach of the organization.

If an organization blocks external sharing, no amount of personal configuration will make a work calendar appear in a personal account. The same applies to third-party apps that need administrator approval to connect. Checking what the organization allows before choosing a method saves repeated attempts that are refused.

Personal accounts have conditions of their own. Connecting iCloud calendars to third-party apps requires an app-specific password, and Apple requires two-factor authentication before one can be created. Apple's support page adds that changing or resetting the main Apple Account password automatically revokes every app-specific password. A combined calendar that stops showing iCloud events on the day of a password change has almost always hit this.

Where it breaks down: deciding where new events live

A combined view lets new events go into any calendar. That flexibility creates a decision that separate calendars never required: where does this event belong?

Every calendar app has a default calendar, and events created without choosing one land there. If the default is a personal account, a meeting with a client goes out from a personal address. If the default is the work account, family plans end up on the office calendar, visible to anyone with access to it.

A one-line rule, written down before combining, removes most of the hesitation. For example: events that invite other people go in the work calendar, events for one person go in the personal calendar, events shared with the household go in the family calendar. Rules based on the nature of the event hold up no matter which screen the event is entered from.

Choosing a depth in practice

Three questions settle the depth for most situations.

Who needs to see the result? If the only person looking is the calendar owner, the view depth is enough, and it involves no copying at all. If colleagues, clients or a booking page need to see the time as taken, busy time is required.

Do the details need to exist in a second place? Very few everyday problems require a full copy. Wanting a record of past events is a different need, and a one-time export and import handles it. Google's help is clear about what that produces, though: imported events do not stay in sync between two accounts, and repeating events imported from a .csv file may show up as a series of one-time events. An import is a snapshot, suitable for an archive and unsuitable for anything that still changes.

Which account is the original? Any arrangement that writes into a second calendar, whether blocks or full copies, needs a clear answer about direction. Edits should always be made in the original, never in the block or the copy, because the next sync pass can overwrite changes made on the receiving side. Deciding this before switching anything on avoids two versions of the same event quietly drifting apart.

Answering these in order usually points to the shallowest depth that does the job, which is also the one with the fewest moving parts and the least private detail in transit.

What to change first

Decide which depth is needed, view, busy time or full copy, before looking at any tool. Then confirm what the organization allows and what sharing level each calendar needs, and write the one-line rule for where new events live. Once events from every account sit on one grid, gaps that were invisible become obvious; the travel time guide covers planning around them, and Caltimate shows how a native Mac calendar brings those accounts into one view.