Use cases

Two jobs. One is much bigger than the other.

Synchronic exists to keep you from being booked twice. Group scheduling is a smaller feature that helps once other people are involved.

Primary use case

Prevent double bookings

For anyone running more than one calendar: a client account, a studio account, a personal one.

Who this is for

  • Freelancers with a calendar per client.
  • Consultants juggling a retainer and their own practice.
  • Anyone holding a contract role alongside their own business.
  • People whose booking page reads only one of their calendars.
Calendars to check before saying yes One
Meetings Synchronic moves or renames None
Details shared between calendars Just busy
The problem

The gap between your calendars

Every calendar is confident about its own events and blind to everything else. That blind spot is where double bookings live.

  • 1 A client call sits on your Outlook calendar at 2 PM Thursday.
  • 2 Your Google Calendar has nothing there, so 2 PM reads as free.
  • 3 A second client picks 2 PM from your booking page.
  • You find out when both of them join at once.
Thursday, 2:00 PM
Double booked
Google Calendar you@acme-client.com Free
ThursdayMar 13
Design review Acme Corp
New booking · 2 PM Accepted
Outlook you@studio.co Busy
ThursdayMar 13
Client call Northwind retainer

Two meetings, one hour

The calendars never talked to each other, so both bookings look fine on their own.

The fix

A busy block on the other calendar

When an event is accepted on one connected calendar, Synchronic adds a busy block at that time on the others. The hour stops being offered.

Thursday, 2:00 PM — Outlook has the meeting, Google gets the block
Google Calendar you@acme-client.com Connected
ThursdayMar 13
Design review Acme Corp
Free
Busy Synchronic 2–3 PM
Draft handoff Acme Corp
Outlook you@studio.co Connected
ThursdayMar 13
Studio standup Studio
Client call Northwind retainer

2:00 PM still looks open on Google Calendar

Your Outlook client call is invisible here, so someone could book the same hour.

2:00 PM now shows as busy on both calendars

Synchronic saw the Outlook call and added a matching busy block to Google Calendar.

  • Event on Google Calendar
  • Event on Outlook
  • Busy time added by Synchronic
  • The block covers the same start and end time as the real meeting.
  • It says you are busy — the meeting title and guests are not copied over.
  • Cancel the meeting and the block comes off too.
  • Works across as many connected calendars as you need.
The result

One answer to "are you free?"

Your calendars agree, so you can accept a meeting without checking three places first.

Before Conflict possible
Google Calendar Free
Thu
Free
Outlook Busy
Thu
Client call 2–3 PM

Each calendar only knows its own events. The same hour reads as free in one place and busy in the other.

After Busy on both
Google Calendar Busy
Thu
Busy Synchronic 2–3 PM
Outlook Busy
Thu
Client call 2–3 PM

Synchronic adds a busy block where it is missing. Your meetings stay where they are — only the blocked time is new.

  • Event on Google Calendar
  • Event on Outlook
  • Busy time added by Synchronic
Secondary use case

Find a time for group meetings

Share one link instead of trading messages about who can make Tuesday.

Create a meeting link, offer a few times, and send it to everyone involved. Each person marks when they are available. You look at the answers and confirm the time that works.

  • 1 Create the link. Name the meeting and offer a few times.
  • 2 Send it out. Participants do not need an account to reply.
  • 3 Collect availability. Everyone ticks the times they can make.
  • 4 Confirm one time. You choose and send the invite.

Group scheduling collects availability from other people. It does not replace double-booking prevention on your own calendars.

3 of 3 replied Tue 10 AMWed 2 PMThu 9 AM
YOYou
DRDana
MKMarcus
Wed 2 PM works for all three

Start with the double bookings.

Connect two calendars and let Synchronic keep your busy time in both.

Nothing changes on your calendars until you connect one.