TillyGen and OneDrive

What this is about

OneDrive is the personal and small-team layer of Microsoft 365 storage: files sync into Explorer and Finder, sharing follows company policy, and IT already governs who may send what outside the organization. For a corporate video unit this is where the TillyGen exports belong — the schedule PDF next to the brand guidelines, the call sheet reachable for colleagues who have never heard of production software. The planning logic stays in TillyGen; OneDrive contributes what the company already trusts it with: storage, sync and controlled sharing.

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 synced folder makes TillyGen exports appear as normal local files — colleagues open the call sheet from Explorer without learning a new tool
• Sharing rides on existing Microsoft 365 groups, so the marketing department sees the plan the moment it lands, with no new invitations
• External freelancers receive share links governed by IT policy — clarified in prep, not discovered as blocked on shoot morning
• Built-in version history keeps yesterday's schedule PDF recoverable when someone overwrites a file by accident

Step by step

This order gets you there fastest:

1. Agree on one OneDrive folder for the production and sync it, so plan documents show up where the team already works: in Explorer and Finder.
2. Export schedule, shot list and call sheet from TillyGen as PDF into that folder — overwrite the same filename and let version history keep the trail.
3. Grant access through the existing Microsoft 365 group of the team rather than person by person; new colleagues inherit access automatically.
4. Clarify the external-sharing policy with IT during prep: can freelancers receive links, or does the call sheet go out by mail instead?
5. After each plan change in TillyGen, re-export to the same location — the sync distributes the new state without anyone sending a file around.

Common pitfalls

What most often goes wrong in practice:

• A colleague copies the schedule PDF to the desktop 'for quick access' — from then on, two versions exist and the local one wins meetings
• IT blocks external links and nobody tested this before the first freelancer needed the call sheet at 6 a.m.
• Confusing personal OneDrive with team storage: the plan sits in one person's account and vanishes with their vacation or their departure

With TillyGen

TillyGen holds the working plan and its dependencies; OneDrive distributes frozen states of it through the company's own storage rules. One direction of flow — export, never import — keeps the two from fighting.

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.