Shot Readiness Checklist

What it does

The Shot readiness panel on the shot grid summarizes whether this shot is structurally ready to leave the building: folders, department tasks, published elements, and delivery status.

How to read it

The pill shows X/4 ready. Each row is green (pass) or red (needs attention):

• Shot folders present - pipeline reported on-disk shot folders.
• Department tasks complete - required departments at 100% or final status (expand for per-dept breakdown).
• Elements published - every cache/asset/plate on the shot has a lead-published version.
• Delivery ready - delivery status is approved or delivered.

What to do

Fix red rows top to bottom: sync folders, finish or reassign dept tasks, publish missing elements on the Element Versions page, then advance delivery when comp is blessed.

Overview

Four green/red checks on the shot page before delivery.

Steps

1. Confirm show/seq/shot context on the task or shot page.
2. Update task status as work progresses (WIP → review → approved).
3. Publish through the pipeline path - avoid ad-hoc paths on NAS.
4. Check dependencies / where-used before changing shared assets.

Gotchas

• Renaming shots/tasks does not automatically rewrite disk paths.
• Dependency edges may lag legacy depends_on fields until sync runs.

Cross-links

• Published Versions & Dependencies - see Help Center
• Production Flow Guide - see Help Center
• Delivery & Wrap - see Help Center