TillyGen and Notion

What this is about

Teams that run on Notion give every production a page: client details, crew contacts, moodboard links, notes from every call. That page is where a new team member starts reading. TillyGen plugs into this hub in two ways. The shot list CSV imports as a Notion database, which gives departments filterable views inside the wiki they already use. And the plan itself — the connected chain from brief to call sheet — stays in TillyGen, represented on the page by a share link rather than a copy that would start aging immediately.

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:

• The shot list CSV imports as a database; views filtered by location or shoot day live next to the meeting notes that discuss them
• The production page links to the TillyGen plan, so 'where is the current schedule' has a one-click answer inside the wiki
• Decisions from calls get logged in Notion with a date and the shot numbers they touch — the numbers come from the plan
• A production template page makes the next project start with the same structure instead of a blank canvas

Step by step

This order gets you there fastest:

1. Create the production page from your template: sections for contacts, decisions, references, and one prominent link to the TillyGen plan.
2. Import the shot list CSV as a Notion database and add the views departments ask for — by set, by day, by cast presence.
3. Log every decision with date, owner and affected shot numbers on the page; the discussion lives in Notion, the consequence lives in the plan.
4. After plan changes in TillyGen, update the imported database at milestones — delete and re-import is faster and safer than editing rows by hand.
5. At wrap, the page becomes the production's memory: what was decided, when, and why — with the final plan PDFs attached for the archive.

Common pitfalls

What most often goes wrong in practice:

• Someone edits rows in the imported Notion database and believes they changed the plan — TillyGen never heard about it
• The production page mirrors so much plan detail in prose that every schedule change now requires editing three paragraphs of wiki text

With TillyGen

Notion holds the knowledge around the production, TillyGen holds the plan inside it. The share link and milestone CSV imports connect the two without either becoming a copy of the other.

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.