← All posts

Building a pipeline for serial animation

  • 128
  • 24

How we structure dailies, naming, and handoffs so episodic teams stay fast without sacrificing quality.

Serial work lives or dies on predictability. We standardize folder trees, shot prefixes, and review links so everyone spends less time hunting assets.

Dailies stay short: director notes, blocking risks, and next-day priorities only — recorded in one sheet the whole floor trusts.

When a vendor joins mid-season, they inherit the same LUT stack, naming bible, and Slack channels as the core crew. No shadow folders, no duplicate "final_final" exports.

We also snapshot pipeline health weekly: throughput, retake rate, and average note-to-publish hours. Spikes trigger a 30-minute retro before they become culture.