workflow
Shot tracking and stage-integrated production management
Stop-motion production map
Definition
Shot tracking and stage-integrated production management is the workflow that keeps each stop-motion shot, schedule, crew assignment and physical shooting unit synchronized as work moves between production offices and animation stages. It turns the schedule into a live operational map of what is shooting, what is blocked, who is needed next and what downstream work depends on the current state.
Overview
A stop-motion schedule is not useful if it exists only as an office document. In LAIKA's official `Day in the Life of a Production Management Intern` cross-post, Production Management Intern Bryce Clyde describes beginning with desk work tracking shots and schedules, then going onto stages where animators, riggers and set dressers are working, updating crew cards, breaking down gear and helping wherever needed. The evidence is narrow — it describes one intern's routine, not the entire department — but it shows the essential bridge: production tracking is continuously checked against the physical state of the stages rather than maintained separately from them.
LAIKA's own production-technology material explains why that bridge matters at feature scale. An Autodesk University presentation on LAIKA's automated resource leveling and scheduling describes the schedule as a way to obtain the right resources, prioritize work and communicate across departments and shops. Its production model links tasks and dependencies to physical and digital assets, shots, employee positions and shooting units. In that structure, a delay is not merely a date moving on a chart: it can change which puppet build, set part, artist position or stage unit must be available downstream. Centralized scheduling makes those dependencies visible enough to rebalance before they become a stage failure.
The same pattern appears independently outside LAIKA. HouseSpecial's Production Coordinator job description for stop-motion work requires maintaining shot-tracking boards and schedules, communicating schedule changes, distributing dailies notes and reference material, and staying close to art leads so work remains on track. That independent production description prevents the LAIKA intern profile from being mistaken for a studio-specific ritual. The transferable mechanism is a feedback loop between the planned production state and the observed stage state.
For practical use, the tracking system should therefore be organized around decisions rather than paperwork volume. A shot record needs enough state to answer what is ready, what is waiting, what changed, who must know and which dependent task is affected. Stage contact matters because stop motion is dominated by physical dependencies: a set can occupy a unit for days, a puppet or rig may exist in limited copies, and a schedule change can strand an animator even when the database itself looks complete. Production management closes that gap by repeatedly reconciling the database with the real floor.
Shot length changes the arithmetic of the schedule. Interviewed during the Wildwood release-week studio visit, LAIKA head of animation Brad Schiff compared two of the studio's features: Missing Link had 1,800 shots, and Wildwood had 2,900, 900 of them a second or less, because the film was cut like live action. His planning point is that setup does not scale with duration: a 12-frame shot takes as long to set up as a 120-frame one, even though the animator will finish it in two days. It follows (our reading, not his words) that a tracking system should count setups and stage occupancy rather than seconds of screen time. A cut built from many very short shots multiplies the stage turnovers, lighting resets and puppet moves that production management must sequence, even when the running time does not change.
Workflow
- 1. Define each shot as an operational production record with its current status, scheduled unit, required people, required physical/digital assets and known predecessor dependencies.
- 2. Track schedule changes and shot progress centrally, but treat the schedule as a hypothesis about the floor rather than an unquestionable source of truth.
- 3. Reconcile the tracker against the animation stages regularly: confirm which shots are actually active, what crews are present, what gear or assets are missing and whether the next planned handoff is still realistic.
- 4. Update crew assignments, shot status and schedule dependencies immediately when the physical stage state changes, and communicate the change to the departments whose work moves because of it.
- 5. Preserve dailies notes, reference material and production-status changes with the shot so that later teams can reconstruct why a schedule or assignment changed instead of seeing only the latest date.
- 6. Use dependency-aware scheduling and resource leveling at larger scale, but keep human stage reconciliation in the loop: automation can balance declared resources and dates only after the production system accurately represents what is physically happening.