Guide

Block Time on Multiple Calendars (Without the Manual Copy-Paste)

Three patterns for getting one time block to appear across every calendar you own. Only one of them survives a calendar reshuffle without manual cleanup.

Published

You want a 90-minute focus block at 9am Thursday. It needs to show as Busy on your work Google Calendar (so colleagues do not book over it), on your personal iCloud (so your partner does not double-book you at home), and ideally on the Outlook account at the client tenant you bill into part-time.

Three calendars. One time block. How do you keep them consistent?

Pattern 1: Manual copy-paste

How it works: you create the event on calendar A, then re-create it on calendars B and C.

Pros: zero dependencies, works immediately.

Cons:

  • Takes minutes per event.
  • A reschedule means deleting and recreating in three places.
  • You will forget. Repeatedly. The first double-book happens within a month.
  • No history. If you ever want to know how much focus time you actually got, the events are spread across three places.

Verdict: only acceptable for one-off events. Not a system.

Pattern 2: Create on one calendar, subscribe the others

How it works: you create events only on calendar A. Calendars B and C subscribe to a public ICS URL from calendar A.

Pros: events appear automatically across all three.

Cons:

  • ICS subscriptions refresh every 6 to 24 hours. A new focus block does not appear on the subscribed calendars in time to prevent double-booking.
  • Read-only. You cannot edit the event from calendars B or C.
  • Privacy is binary. The ICS URL is either fully public or fully private to you.
  • Calendly and other booking tools that read calendars B or C may not detect the subscription-imported events as conflicts depending on the provider’s caching.

Verdict: better than copy-paste but the lag makes it unreliable for active scheduling. See Calendar sync vs subscription for the full mechanics of why subscriptions are slow.

Pattern 3: Two-way calendar sync

How it works: a sync engine mirrors events between calendars A, B, and C using each calendar’s native API. New events on any calendar propagate to the others in 30 to 90 seconds.

Pros:

  • Fast. Booking tools see new focus blocks almost instantly.
  • Two-way. Reschedule from any calendar; the others update.
  • Configurable privacy. Mirrored events can show as “Busy” with no title or attendees.
  • Per-calendar opt-in. You choose which calendars are in the mirror; the others stay independent.

Cons:

  • Requires connecting each calendar with OAuth or CalDAV. A few minutes of setup.
  • One more service in your stack to trust with calendar access.

Verdict: the only pattern that scales past a few events per week without errors.

Setting up Pattern 3 with SyncCal

The standard setup for “block time on all my calendars”:

  1. Pick one calendar as the source where you create focus blocks. Usually your primary work Google or Outlook.
  2. Connect that calendar to SyncCal as a source.
  3. Connect each other calendar (iCloud, secondary Google, client M365) as a target.
  4. Enable Busy-title rewrite on each target so the focus block appears as “Busy” with no title.
  5. Done. New focus blocks on the source appear on every target in about a minute.

For specific calendar pairs, the integration pages have the platform steps:

Edge case: focus blocks vs real meetings

If you also use an AI scheduler (Reclaim, Motion, Clockwise), the focus blocks may be auto-placed by the scheduler rather than created manually. The pattern is the same: the scheduler writes to your primary calendar, SyncCal mirrors to the others. The scheduler does not need to know about your other calendars; SyncCal handles the propagation.

This combination is covered in SyncCal vs Reclaim, SyncCal vs Motion, and SyncCal vs Clockwise.

What this is NOT

  • A guide to time-blocking philosophy. That is a different conversation; this is the mechanics.
  • A way to force booking tools (Calendly, Microsoft Bookings) to read multiple calendars natively. They cannot. The fix is to mirror everything into the one calendar each tool already reads. See Calendly misses conflicts on your other calendars.
  • A pitch for any specific scheduler. We are sync; we are agnostic on AI schedulers.