TillyGen and Frame.io

What this is about

Frame.io is the review layer of post-production: editors upload versions, directors and clients leave comments pinned to the exact frame, and the feedback history stays attached to each version. It enters the picture after the shoot, when the plan from TillyGen has already done most of its work. That order is precisely the connection — a comment like 'the product close-up is missing' can only be settled against the shot list, and a deadline agreed in a review thread only holds if the schedule allows it.

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:

• The shot list PDF from TillyGen travels with the first uploaded version, so reviewers comment against planned shots instead of vague memories of the treatment
• Version names in Frame.io can carry the scene and shot numbering from TillyGen, which keeps feedback traceable across review rounds
• Deadlines discussed in review threads get checked against the TillyGen schedule before anyone confirms them to the client
• If you script uploads, the TillyGen API can supply shot metadata for consistent naming conventions

Step by step

This order gets you there fastest:

1. Finish shot list and schedule in TillyGen and export both as PDF — this package is the reference every review round gets measured against.
2. Create the Frame.io project for the production and name versions after the scene and shot numbers the TillyGen plan already uses.
3. Share the shot list PDF alongside the first cut so reviewers can point to a planned shot number instead of describing footage from memory.
4. Collect frame-accurate comments in Frame.io; when feedback questions coverage, resolve it against the shot list before promising a new version or a reshoot.
5. Confirm delivery dates from review threads only after checking them against the TillyGen schedule — the plan decides what is realistic, not the thread.

Common pitfalls

What most often goes wrong in practice:

• Review comments that quietly grow the scope — an extra version here, a new end card there — without anyone updating the plan they will be produced against
• Two homes for deadlines: a date in a Frame.io thread and a different one in the schedule, each considered final by half the team

With TillyGen

TillyGen remains the source for shot list and schedule; Frame.io owns the review of what was shot. Changes that survive a review round go back into the plan, so the next version starts from an updated reference.

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.