TillyGen and Adobe Premiere Pro

An editor who opens a project and finds bins named after the shot list starts cutting an hour earlier. That hour was earned in pre-production.

What this is about

Premiere Pro is where the footage becomes the film: bins organize clips, sequences hold the cut, markers carry notes. None of that structure invents itself — it either mirrors the production plan or it mirrors chaos. The TillyGen shot list gives the edit its skeleton before the first clip imports: scene and shot numbering becomes the bin structure, the storyboard PDF answers what the intended frame looked like, and the shot list marks which takes were planned as safety versus essential. The connection is disciplined naming and an open PDF, and it outperforms most technical bridges.

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:

  • Bins named after the TillyGen scene numbers let the editor find coverage by plan position instead of by scrubbing thumbnails
  • The storyboard PDF docked on the second monitor settles 'was this the intended framing' without a call to the director
  • The shot list CSV doubles as a logging sheet during import — each row checked off as its material is confirmed present
  • Missing coverage shows up on day one of the edit, while a pickup shot is still cheap to organize

Step by step

This order gets you there fastest:

  1. Export shot list and storyboard from TillyGen as PDF and CSV before handing off to post — the handoff is a package, not a hard drive alone.
  2. Build the Premiere bin structure from the scene numbering in the shot list, one bin per scene, before importing a single clip.
  3. Import the footage and check it against the shot list rows; every missing take gets flagged today, not discovered in week two.
  4. Keep the storyboard PDF within reach during the rough cut and compare intended frames when a scene refuses to assemble.
  5. Feed deviations back: shots that were planned but never worked inform the next production's shot list in TillyGen.

Common pitfalls

What most often goes wrong in practice:

  • The edit starts before anyone checked footage against the shot list — the missing insert surfaces when the client asks where it is
  • Bin names invented fresh in post, so plan numbers and project numbers describe the same shots in two dialects

With TillyGen

TillyGen defines what should exist; Premiere reveals what does. Keeping the plan's numbering alive inside the project is what lets those two truths be compared at every stage of the cut.

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

Does TillyGen export sequences or projects for Premiere?

No — the handoff is shot list and storyboard as PDF and CSV. The editor builds the bin structure from the plan's numbering; the discipline, not a file format, is the bridge.

What does the editor gain from pre-production documents?

Orientation and an early warning system: coverage checked against the plan on day one, intended framings answerable without meetings, and missing shots flagged while pickups are still affordable.

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.