Overemployed Calendar Sync: Keep J1 and J2 From Colliding

Two jobs, two calendars that cannot see each other. Here is how to stop the clashes, and what each setup leaves behind on each employer’s side.

Jakub Beneš

Jakub Beneš

Founder, CalendarPipe · October 13, 2026 · 8 min read

To keep two jobs' calendars from colliding without leaking one into the other, mirror only busy time between them, as blocks titled "Busy" with the description, location, attendees, and call link stripped. Run the mirror in both directions so each employer sees that an hour is taken and nothing about who took it. Do the setup from a personal device. Where an employer blocks third-party calendar apps, deliver the blocks to that side as plain email invitations instead of connecting the account. One caveat matters more than any setting: there is no setup that leaves zero trace on either employer's systems. The useful question is which trace you can live with, and this post goes through each one.

The problem is the Tuesday at ten

If you're overemployed, J1 and J2 each believe they own your whole working week. Neither calendar can see the other. Nothing warns you until two meetings start at once and a message asks whether you're joining.

The usual fixes on r/overemployed are all manual: two laptops side by side, comparing calendars by eye, placeholder blocks copied on Sunday night, a paper planner. They work until something moves. The J2 standup slides to 10:30, your hand-made J1 block stays at 10:00, and now you're holding time you don't need while the time you do need looks free.

The obvious next step is a sync tool. That's where most advice stops, and where the real risk starts.

Why the usual sync tools are the wrong shape

Most calendar sync tools, CalendarPipe's direct mode included, work by OAuth-connecting each work account so they can read and write events. For an ordinary job that's fine. For two jobs, it has three problems:

  1. It copies too much by default. A verbatim mirror puts "Acme: Q4 pricing for the Contoso pitch" into the other company's calendar, together with the attendee list and the Zoom link. That is exactly the cross-pollination people keep two laptops to avoid.
  2. The grant is visible to the admin. Google Workspace admins can list every third-party app a user has authorized. In Microsoft 365, a user's consent creates an enterprise application in Entra ID and an audit entry. Neither one names the other job, but both say a calendar tool can read your work calendar.
  3. It's often blocked anyway. Many Workspace and 365 tenants disable third-party consent org-wide, and the connect button ends at "Your administrator has disabled access for this third-party app."

So the right shape is a thin mirror: times cross over, nothing else does. Each employer side is connected in the way that leaves the least trace.

What each employer can see, setup by setup

This table answers the question every overemployed reader actually has. "Admin" means the IT team of the employer whose account is involved.

SetupWhat lands on that employer's systemsCan their admin turn it off?
OAuth-connect the work account (most tools)A third-party app grant on your account, listed in the admin consoleYes, and often already off
Publish the work calendar as an ICS feedA published-calendar setting on your account; the feed URL works for anyone who has itYes, publishing can be disabled
Share the work calendar to a personal accountAn external share on your account, visible in sharing settingsYes, external sharing can be disabled
Invitation delivery (CalendarPipe)Meeting invites in your inbox, from your name at an outside address, invitations@calendarpipe.comOnly by blocking that sender
Two laptops, comparing by eyeNothingNothing to turn off

Read the last row honestly. If even an invitation from an outside sender is too much for one of your employers, the two-laptop method is the only one with a zero footprint, and no tool will beat it. Everything else trades a small, specific trace for not getting double-booked. You pick the trace.

Also note what no row contains. In none of these setups does either employer get the other employer's name, meeting titles, colleagues, or links, as long as the mirror strips them. That part is up to the rule, not the employer.

The setup: two thin pipes, one in each direction

Do all of this from a personal laptop or phone, never from a managed device. CalendarPipe runs in the browser, so there's nothing to install on either employer's hardware.

  1. Connect J1 and J2 in the least visible way each one allows. If an employer permits it, an OAuth connection is the most reliable. If it doesn't, or you'd rather not leave a grant, use a published ICS feed of that calendar as a read-only source. Google, Microsoft, and Apple over CalDAV are all supported, and the two employers don't have to use the same provider.
  2. Create a rule from J1 to J2 and a second rule from J2 to J1. Each direction has its own rule, so you can be stricter one way than the other.
  3. Strip each copy down to a busy block. The rule replaces the title with "Busy" and clears the description, the location, and the attendees before anything is written. The video call link lives in the description, so it never leaves the original calendar either.
  4. Write to the locked-down side by invitation. If an employer blocks third-party apps, or you just don't want to connect that account for writing, set that rule's delivery mode to invitation and point it at your work email. Each block arrives as an ordinary meeting invite that you accept. Nothing is authorized on that account.
  5. Activate both rules. On Pro they re-check every 5 minutes and look 90 days ahead. When the J2 standup moves to 10:30, the J1 block moves with it on the next run. When a meeting is cancelled, its block disappears.

A word on the label. Plenty of guides suggest "Personal Commitment" or "Doctor" for placeholder blocks. For this use case, plain "Busy" is the better choice: it's what a calendar shows for any private event anyway, and it invites no follow-up questions. The title is just a string in the rule, so you can use whatever reads as normal at each company.

Make the rule fit the way you actually work

The rule is a small function, so the mirror can be as picky as you need. These are the ones overemployed setups use most:

  • Only busy events cross. A J2 lunch marked free stays put and doesn't eat a J1 slot.
  • Skip what you haven't accepted. Invites you've left unanswered or declined don't block the other calendar.
  • Drop all-day events, so a J2 offsite or company holiday doesn't wipe out a J1 day unless you want it to.
  • Limit to working hours, so an evening J2 deploy window doesn't block anything J1 would never book anyway.

The visual and AI rule builders cover these without writing any code. One limit, so nobody is surprised: a rule changes what a block says, never when it happens. The block always covers exactly the hours of the real meeting, because a block at the wrong time is worse than no block.

When two meetings still collide

Sync stops new clashes from being booked. It can't undo the ones that already exist, or a meeting someone books over a visible block anyway. A few habits do the rest:

  • Hold recurring time early. Put your own recurring focus blocks on each calendar in the hours you know the other job needs. A visible hold gets respected far more often than an empty slot.
  • Keep camera-on meetings apart. If one meeting must overlap, make it one where you're a listener, not a presenter.
  • Decline with a neutral reason. "I have a conflict, can we do 2pm?" is a sentence everyone hears daily. It needs no explanation.

How this compares with other tools

Multical, Reclaim, and OneCal can all mirror busy time between calendars, and all three are reasonable products. All three connect every calendar through OAuth, so they don't help on a tenant that blocks third-party apps, and each one leaves a grant on both work accounts. If both employers allow app connections and the grant doesn't bother you, any of them will do the basic job. See the Reclaim and OneCal comparisons for the details.

CalendarPipe differs in two places that matter for two jobs. First, invitation delivery: you can write to an employer's calendar without connecting it. Second, the field-by-field control over what crosses. The two-company setup shows that mirror event by event. If one of your employers is the locked-down one, the post on blocked OAuth goes deeper on invitation delivery.

Read your contract first

Holding two jobs is legal for most private-sector workers in the US, but your contracts are what count. Moonlighting clauses, conflict-of-interest policies, and IP-assignment terms can all forbid it, and government and regulated roles have stricter rules. Check before you set anything up. A calendar tool keeps your schedule straight. It doesn't change what you've signed.

What it costs

Two connections and one rule fit the free plan, which is enough to mirror one direction every 15 minutes, 14 days ahead. Mirroring both ways needs two rules, and invitation delivery is a Pro feature, so most overemployed setups end up on Pro: $4/month or $40/year, with a 14-day free trial. Pro also syncs every 5 minutes and looks 90 days ahead.

Wrapping up

The safest calendar setup for two jobs isn't the one with the most features. It's the one where each employer learns the least. Mirror only the hours, strip everything else, set it up from your own device, and write to the locked-down side by invitation. Then pick the trace you're comfortable with from the table above, knowingly.

Start at CalendarPipe, and the docs walk through each step.

— Jakub

Frequently asked questions

How do I sync calendars for two jobs without leaking details?

Mirror only busy time. Create a one-way rule from each job’s calendar to the other that replaces every title with "Busy" and clears the description, location and attendees before writing. Each employer then sees that an hour is taken and nothing about the other company, its people, or its meeting links.

Can my employer see that I use a calendar sync tool?

It depends on how the work account is connected. An OAuth connection appears as a third-party app grant in the Google Workspace or Microsoft 365 admin console. With invitation delivery, nothing is connected, but your inbox receives meeting invites from invitations@calendarpipe.com under your own name. Only comparing two calendars by eye on separate devices leaves no trace at all.

What if one employer blocks third-party calendar apps?

Write to that side by invitation. Busy blocks arrive at your work email as ordinary meeting invites that you accept, so there is no consent screen and nothing for an admin to approve. To read that calendar, use a published ICS feed if the employer allows one.

Will a moved or cancelled meeting update the other calendar?

Yes. Synced blocks are tracked, so when a meeting moves, its block moves on the next run, and when it is cancelled the block is removed. On Pro that happens within 5 minutes, and the rule looks 90 days ahead.

Is being overemployed legal?

For most private-sector workers in the US it is legal, but your employment contracts decide. Moonlighting, conflict-of-interest, and IP-assignment clauses can forbid a second job, and government roles have stricter rules. Read your contracts before setting anything up.

Mirror the hours, nothing else

Two rules, one in each direction, turn every busy meeting into a plain "Busy" block on the other calendar, with titles, attendees and links stripped. Write to a locked-down employer by invitation instead of connecting it. Both directions and invitation delivery are Pro, at $4/month, free for the first 14 days.

Start the 14-day trial