Two-way calendar sync: what it should mean (and how to tell if yours really does it)

You open your work calendar, see the copy of Thursday’s dinner, and push it back an hour. Done. Except your personal calendar still says 7, so that’s when your partner books the babysitter. And the copy on your work calendar? The next morning it says 7 again too. Your edit didn’t fail with an error. It just quietly didn’t count.

If that’s happened to you, your sync tool probably isn’t broken. It’s doing exactly what it was built to do. It just isn’t what “two-way” sounds like.

What most “two-way” sync actually is

Most tools that sell two-way (or “bidirectional”) calendar sync are running two one-way syncs pointed at each other. Calendar A’s events get copied to B. Calendar B’s events get copied to A. Each copy has an owner, the calendar it came from, and the copy is treated as read-only.

That design is common, and it isn’t hidden: several of the best-known sync services say plainly in their own help docs that changes to a copy don’t go back to the original. Day to day, it means:

• Edit a copy, and the original doesn’t change. Sometimes the copy keeps your edit, so the two calendars now disagree. Sometimes the next sync overwrites it back.
• Delete a copy, and the original stays. Often the copy comes back on the next sync, because as far as the tool is concerned the original still exists.
• Which calendar you’re “allowed” to edit depends on where the event was born. Fine if you remember where every event started. Most people don’t.

So “two-way” in this sense means events flow both ways. Changes only flow one way: from the original to its copy.

What true two-way sync means

True two-way sync treats both calendars as real. There’s no copy you’re not supposed to touch:

• Edits on either side reach the original. Move the copy of Thursday’s dinner on your work calendar, and the dinner on your personal calendar moves too.
• Deletes on either side reach the original. Delete the copy, and the event is gone from both calendars. This is the part that surprises people: there’s no “safe” side to delete from.
• Conflicts get resolved, not ignored. If the same event changes on both calendars before a sync, the tool has to pick an answer and make both calendars agree. A common rule is last write wins: the more recent edit is kept. A better one merges first. If you changed the time on one side and the location on the other, both changes survive, and last write wins only settles a real collision on the same field.

The test of true two-way sync isn’t whether events show up on both calendars. It’s whether you can stop caring which calendar an event started on.

A three-step test you can run on any sync tool

You don’t need to dig through anyone’s help docs to find out which kind you have. Create a throwaway test event on calendar A (not a real meeting; step two deletes things), wait for its copy to appear on calendar B, then work through the steps below. It works for any pair: Google Calendar and Outlook, two Google accounts, Outlook and iCloud.

1. Edit the copy’s title. On calendar B, change the copy’s title to something obvious, like “TEST EDITED.” Wait for a sync, then look at calendar A.

• True two-way: the original on A now says “TEST EDITED.”
• Read-only copies: A still has the old title. Check B again after the next sync; the copy may have reverted.

2. Delete the copy. On calendar B, delete the copy. Wait for a sync.

• True two-way: the event is gone from A too.
• Read-only copies: the original is still on A, and the copy often reappears on B.

3. Edit both sides within a minute. Make a fresh test event. Change its time on calendar A, and within a minute change its title on calendar B. Then do it again, this time changing the title on both sides to two different things.

• True two-way: in the first round, both changes survive: new time and new title, on both calendars. In the second, one title wins and both calendars show it.
• Read-only copies: whatever you did to the copy disappears.
• Broken: the two calendars disagree and stay that way, flip back and forth, or you end up with two events.

Two tips. Give each step a few minutes before you judge it, and longer if one of the calendars is iCloud: iCloud doesn’t announce changes, so every sync tool has to check it on a timer. And look again the next day. Some tools reconcile slowly, and an edit that seemed to stick can be reverted hours later.

When you don’t want true two-way

True two-way is the right answer when you genuinely live in both calendars. It’s the wrong answer for plenty of setups, and read-only copies aren’t a flaw when they’re what you actually asked for.

• One calendar is the master. A booking calendar, a team calendar you only reflect, a calendar you mirror for an assistant. You want one-way sync here: the destination is a reflection, and if someone edits or deletes a copy, the sync should put it back. That’s exactly the read-only behavior above. The problem is only when it’s sold as two-way.
• Work and personal should know about each other, not leak into each other. Your work calendar should see “Busy” at 3 p.m., not “Dr. Patel, dermatology.” If those “Busy” blocks were fully two-way, an innocent edit to one would have nowhere sensible to go; you don’t want it renaming your appointment “Busy.” This is what twocal’s Projection mode is for: each calendar shows the other’s events through its own privacy filter, and edits to the copies don’t flow back to the originals.
• You delete copies to tidy up. Some people prune the copies on their work calendar to keep it readable. In a true two-way pair, that deletes the real event. If that’s your habit, set up a rule that skips those events so they never get copied in the first place.

Recurring events, honestly

Repeating events are where calendar sync gets hard, for every tool. “Move just this Tuesday’s standup” doesn’t edit an event; it creates an exception inside a series, and Google, Microsoft and Apple each store those exceptions differently. Before you trust any tool with two-way sync, run the test above on one occurrence of a repeating event too.

Here’s where twocal stands. Between Google and Microsoft calendars, twocal syncs each occurrence on its own, so a change to one occurrence travels like any other edit. iCloud has one limit we haven’t solved: in Mirror mode, if you edit or delete a single occurrence of a repeating iCloud event on the other calendar, that change stays on that side and iCloud keeps the original. twocal shows it on the pair page, so it’s never a silent difference. The workaround is to make single-occurrence changes in Apple Calendar itself; changes made there flow everywhere.

A few events can’t be edited by anyone, Google’s birthday events for example, so those only ever sync one way.

How twocal does it

Most “two-way” sync tools treat the copies as read-only; twocal doesn’t. Every pair runs in one of three modes, which you pick per pair:

• Mirror is true two-way sync. Both calendars are fully editable, and edits and deletes on either side reach the original: title, time, location and description all flow back. Different fields edited on each side merge. The same field edited on both sides is settled by last write wins. (Providers record edit times coarsely, so two near-simultaneous edits can settle either way, but both calendars end up agreeing.) And a delete beats a concurrent edit, so deleted events don’t crawl back.
• Projection keeps two calendars aware of each other, with a filter in each direction: the work and personal “Busy” setup. The copies stay hands-off.
• One-way copies one calendar onto another and keeps the copy faithful to its source.

It works across Google, Microsoft 365/Outlook and iCloud. Google and Microsoft changes arrive by push notification, so pairs of Google and Microsoft calendars sync in seconds. Our reliability dashboard is public, and there’s a free trial, so you can run the three-step test on twocal before you trust it with a real meeting.

For the full mechanics of Mirror and Projection, see two-way sync now has two modes. If one of your calendars lives in Apple Calendar, here’s how syncing iCloud with Google and Outlook works, and where its limits are.