Cutlist Tracker / Conform checklist

Conform

The VFX conform checklist

Conform day is where quiet bookkeeping errors become loud delivery problems. This is the checklist for verifying the renders on disk against the cut - before the online editor does it for you.

What conform actually verifies

Conform answers one question per shot: does what is on disk satisfy what the timeline needs? That decomposes into five concrete checks:

  1. Presence - a render exists for every shot in the cut. Sounds trivial; is the most common failure, because shots enter the cut faster than the tracking sheet updates.
  2. Range - the rendered frame range covers the cut duration PLUS handles on both sides. A shot cut at 48 frames with 8-frame handles needs 64 on disk, not 48.
  3. Continuity - no missing frames inside the range. A render that died at frame 1050 and restarted at 1051 can leave a hole nobody sees until playback.
  4. Version - the version in the timeline is the version intended for delivery. If the cut references v001 while v003 sits on disk, someone chose wrong - or nobody chose.
  5. Orphans - renders on disk for shots no longer in the cut. Not an error, but every orphan is either wasted render time or a sign the cut changed and someone missed the memo.

The checklist, in order

The failure mode is manual sampling. Under deadline, people spot-check five shots and extrapolate. The bounced deliveries are always in the shots nobody sampled - the fix is a check cheap enough to run on every shot, every time.

Cutlist Tracker runs this whole checklist as one click: import the cut, scan the folder, and every shot gets a status - ok, missing, range mismatch, stale version, or not-in-cut - with a CSV and printable report at the end.

FAQ

What are handles and why do they break conform?

Handles are extra frames rendered either side of the cut range so editorial can trim without a re-render. They break conform because the cut length and the required render length differ by 2x the handle count - any check that ignores handles passes shots that are actually short.

How often should conform run?

Every time the cut changes and before every delivery. When the check is manual it happens once, late; when it is one click it happens continuously and conform day stops being an event.

What causes stale versions in the timeline?

The editor cut in the version that existed at edit time, then a newer render landed. Unless someone actively reconforms, the timeline keeps pointing at the old version - which is why the check must compare the cut against the folder, not against memory.

Your cut is the shot list

Import the EDL or OTIO, scan the renders folder, and the conform report writes itself. Flat A$29/mo per studio - 14-day free trial, no credit card.

Try the example cut →

Keep reading