DIT

What this is about

Data has a duration. A card is not wrapped when the camera stops but when the second verified copy exists, and that clock runs at the speed of the slowest drive in the chain — not at the speed the crew wants to go home.

Every department needs the same plan in a different view. That is exactly where document collections fail: they only ever serve one perspective well.

What runs differently here

In planning terms, that means:

• Copy time scales with codec and frame rate, never with how urgent the wrap is
• Two copies on separate media plus one off-site is the floor before anyone formats a card
• Checksum verification is the step people skip, and the only step that proves the copy

What the plan has to deliver

A production plan is useful to this role when it provides the following:

• Offload windows written into the day, not squeezed in after wrap
• Codec, resolution and frame rate fixed before the storage plan is built
• Power and a usable workspace at the location, not in the back of a van
• A card-return rule the whole camera department knows

Common pitfalls

What most often goes wrong in practice:

• Formatting a card while only one copy exists
• Sizing storage against the runtime of the finished film instead of the recorded material

With TillyGen

TillyGen derives data volume from codec, resolution and shooting hours, so storage and offload windows are planned as items of the day.

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.