TillyGen and Microsoft Teams

What this is about

Microsoft Teams bundles chat, meetings and files for organizations that live in Microsoft 365. For an internal video production this means: the channel is where marketing, communications and the video team meet, the approval happens in a scheduled meeting with the plan on screen, and every file uploaded to the channel is actually stored in the team's SharePoint site. TillyGen supplies the documents this machinery moves around — schedule, shot list and call sheet as PDF — while the plan logic stays outside the Microsoft stack, in the tool built for 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

In planning terms, that means:

• The channel's files tab is a SharePoint library underneath, so permissions and versioning follow rules IT has already set
• Approval meetings run in Teams with the exported schedule PDF shared on screen — the decision lands in the meeting notes and then in the plan
• A Teams workflow with an incoming webhook can announce plan updates in the channel when wired to the TillyGen API
• The call sheet posted in the channel reaches colleagues who would never install a production tool

Step by step

This order gets you there fastest:

1. Set up a channel for the production inside the existing team, so membership and permissions are inherited instead of rebuilt.
2. Upload the TillyGen exports to the files tab — one folder, stable filenames, and SharePoint's version history keeps the older states.
3. Run approvals as Teams meetings with the schedule PDF on screen; write the outcome into the meeting notes and then into TillyGen.
4. Post plan changes as channel messages with the fresh export attached, so the update and the document arrive together.
5. For recurring updates, connect the TillyGen API to a Teams workflow webhook — the channel then reports changes without manual posts.

Common pitfalls

What most often goes wrong in practice:

• The call sheet circulates in private chats instead of the channel — the file exists four times, three of them outdated
• An approval spoken in the meeting but never written down: two weeks later nobody can prove which schedule version was approved
• Uploading exports into personal OneDrive instead of the channel, where the team's permissions do not reach

With TillyGen

Teams moves the documents and hosts the decisions; TillyGen keeps the plan those documents came from. Every approved change has two addresses: the meeting note that records it and the plan that executes it.

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.