TillyGen and Outlook Calendar

In a corporation, a date only exists once it is an Outlook invitation. Shoot days from the TillyGen schedule therefore become invitations — with rooms, resources and a required-attendee list.

What this is about

Outlook Calendar is the scheduling machinery of Microsoft-centric companies: invitations that demand answers, meeting rooms booked as resources, delegates managing executives' weeks. An in-house shoot has to pass through this machinery — the studio space is a bookable resource, the CEO's interview slot competes with board meetings, and the facility team wants a calendar entry before they unlock anything. The TillyGen schedule stays the source of the dates; Outlook turns each shoot day into an invitation with the right people and rooms attached. Classic Outlook can also take a CSV of events when the batch is large.

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

Where this differs from the general case:

  • Each shoot day becomes an Outlook invitation with required and optional attendees taken from the call sheet's crew list
  • Studio, meeting rooms and company vehicles get booked as resources on the same invitation, which is how facility teams find out
  • Executives' interview slots go through their delegates — the invitation carries the plan link so the delegate can answer questions
  • For a long series of dates, classic Outlook's CSV import loads the whole schedule batch at once

Step by step

This order gets you there fastest:

  1. Lock the schedule in TillyGen first — invitations sent on a draft schedule teach the company to ignore your invitations.
  2. Create one invitation per shoot day, attendees from the call sheet, and book studio and rooms as resources on the same entry.
  3. Route executive appearances through their delegates early, with the plan link attached, because those calendars fill months ahead.
  4. Watch the responses: a declined required attendee is a planning problem and goes back into TillyGen, not into wishful thinking.
  5. On schedule changes, update the existing invitations instead of sending new ones — the update thread keeps the history in one place.

Common pitfalls

What most often goes wrong in practice:

  • New invitations instead of updates on every change — attendees now hold three competing versions of shoot day two
  • The room resource was never booked because the invitation went to people only, and the studio hosts a sales meeting at call time
  • Declines silently accepted: the schedule still assumes a person whose calendar said no two weeks ago

With TillyGen

TillyGen owns the dates and their reasons; Outlook owns their enforcement in a corporate week. Every response that threatens the plan returns to TillyGen as a planning question, answered there, then reflected in an updated invitation.

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.

Frequently asked

How do many shoot dates get into Outlook without typing each one?

Classic Outlook imports events from a CSV file — export the schedule dates from TillyGen, shape the columns once, and the batch lands in the calendar. Single days are faster typed as invitations.

Who maintains the invitations when the plan shifts?

The same person who maintains the schedule. One owner for both prevents the classic corporate failure: a plan that changed and forty calendars that did not.

How long does it take to get started with TillyGen?

A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.

Can the results be exported?

Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.