TillyGen and SharePoint

What this is about

SharePoint is the governed layer of Microsoft 365 storage: document libraries with enforced versioning, permission inheritance, retention policies, and metadata columns that make a thousand documents findable. Corporate video units and regulated industries store their production records there because compliance demands it, not because it is pleasant. In this workflow, TillyGen produces the record-worthy documents — approved schedules, final call sheets, milestone plans — and the library preserves them under rules the organization already audited. The working state stays in TillyGen; SharePoint holds what must survive.

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 production library enforces versioning, so every uploaded plan PDF keeps its predecessors retrievable without anyone thinking about it
• Metadata columns — project, client, approval status, date — turn the archive into a queryable record instead of a folder pile
• Permission inheritance from the site means the legal and audit teams see approved plans without per-file sharing
• Retention policies decide how long production records live — a decision made once by governance, not per project

Step by step

This order gets you there fastest:

1. Agree with IT on one library for production records, with metadata columns for project, client, approval status and date.
2. Upload TillyGen exports at defined moments — approved plan, locked schedule, final call sheets — and fill the metadata on upload.
3. Use the same filename per document type so SharePoint versioning stacks states instead of scattering files.
4. Point auditors and legal to the library, never to mail attachments; the library's version history is the authoritative timeline.
5. Let retention policy do the forgetting — records expire by rule, and nobody deletes production history by hand or by accident.

Common pitfalls

What most often goes wrong in practice:

• The library becomes a dumping ground for working files — drafts drown the approved states the archive exists to protect
• Metadata skipped on upload: two years later, finding the approved plan for one client production means opening forty PDFs

With TillyGen

TillyGen is where plans change; SharePoint is where changed plans go to become record. Only approved states cross over, carrying metadata — and that one-way rule is what keeps the archive trustworthy.

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.