TillyGen and Apple Calendar

What this is about

Apple Calendar is not a team tool; it is the private schedule of people who work for many productions at once. A freelancer juggles three clients a month, and double bookings are their existential risk. The workflow with TillyGen is accordingly personal: when a production confirms dates, the freelancer blocks them in Apple Calendar — including travel days and prep — with the call time in the title and the call sheet reference in the notes. iCloud carries the entry from Mac to iPhone to the watch that buzzes at 5:30. The production's plan stays with the production; the freelancer's calendar guards their side of the deal.

An integration is good when nobody talks about it any more: the data is where it is needed and nobody exports anything.

What runs differently here

In planning terms, that means:

• Dates arrive from the call sheet or shared plan link and get blocked immediately — a pencil hold gets its own tentative event
• Travel and prep days go in as separate entries, because a shoot day without its travel day is a booking error waiting to happen
• The event note carries the plan link and the production contact, so the answer to any question is one tap from the lock screen
• iCloud sync means the date declined on the Mac at home is also declined on the phone when another client calls

Step by step

This order gets you there fastest:

1. When a production sends the plan or call sheet from TillyGen, block every date it implies — shoot, travel, prep — before replying with a yes.
2. Mark unconfirmed requests as tentative entries; a hold that is invisible in the calendar will be double-booked by Thursday.
3. Write call time and location into the event title and the plan link into the note, so the set morning starts without searching mails.
4. Set the alert to leave-by time, not to call time — the difference is the drive, and the drive is where mornings fail.
5. When the production reschedules, move the whole block — shoot plus travel plus prep — and confirm the new dates back in writing.

Common pitfalls

What most often goes wrong in practice:

• Only the shoot days blocked, not travel and prep — the calendar shows free days that are not free, and another client books them
• The production moved a day and the freelancer's calendar still shows the old one; both sides believe they are right

With TillyGen

The production's schedule lives in TillyGen and reaches the freelancer as call sheet, plan link and calendar dates; Apple Calendar is where the freelancer defends those dates against the rest of their working life.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.