TillyGen and Confluence

What this is about

Confluence is where companies keep their institutional memory: spaces per department, pages with edit history, attachments with versions. Stakeholders who will never open a production tool do read Confluence. The workflow therefore splits cleanly — TillyGen turns the briefing into shot list, storyboard, schedule and call sheet; Confluence records what the organization needs to know about it: who approved which version, what the budget frame was, which decisions were made in which meeting. The exported PDFs attach to the page, and the page history answers later who knew what, and when.

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 production page carries a decision log — date, decider, affected part of the plan — while the plan itself stays one click away in TillyGen
• Exported plan PDFs attach to the page as new attachment versions, so the approval of March 12 stays retrievable in April
• Stakeholders read a management summary on the page instead of the full call sheet — written once, at milestone level
• Page permissions follow the existing space setup, which spares the production team from building its own access model

Step by step

This order gets you there fastest:

1. Create the production page in the relevant space with three fixed sections: summary for stakeholders, decision log, and attached plan versions.
2. Attach the current TillyGen exports — schedule and shot list PDF — and link the live plan for readers who want the working state.
3. After every approval meeting, add one decision-log row and upload the approved PDF as a new version of the same attachment.
4. Point questions from outside the team to the page first; if the answer is missing there, the page — not a mail thread — gets updated.
5. Close the page at wrap with the final plan attachments and a short delta note: what shifted between first approval and shoot, and why.

Common pitfalls

What most often goes wrong in practice:

• Stakeholders comment on a PDF attached three weeks ago while the plan has moved on twice since — feedback arrives against a ghost version
• Plan details copied into page prose: every schedule change now demands a wiki edit, and someday someone forgets one

With TillyGen

Confluence answers what the organization decided; TillyGen answers what the production will do. Attachments carry frozen states from the second world into the first — the working state never lives on the page.

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.