Overview

When Shan delivers a first cut (v1) or revised cut (v2+) via Frame.io, this workflow provides structured feedback she can act on without follow-up questions. The process includes end-to-end review, timestamped commenting, and pattern analysis to promote recurring issues into permanent Editing Rules.

Before You Start

Frame.io link to the cut (from Shan's Slack message)
LF-XX storyboard edit map (Google Sheet — the source of truth for planned structure)
Access to the Production Feedback Notion DB
~1 hour of uninterrupted focus time

Steps

Watch the cut start-to-finish at 1x speed in Frame.io. Don't pause. Don't leave comments yet. Form a gut verdict on the overall arc: does the cut deliver the message in the right flow?
Rewatch and leave a timestamped Frame.io comment for every issue you spot. State what's wrong, what you want fixed, and link any references if needed.
Skim the cut one more time and find 2–3 moments Shan genuinely nailed. Leave one Frame.io comment prefixed "WHAT'S WORKING:" with specific bullets of what she got right.
In Frame.io, use "Print comments" to export all comments sorted by timecode. Save PDF to: areas/content/long-form/scripts/LF-XX/feedback/{section-slug}-v{N}-YYYY-MM-DD.pdf
Review the exported PDF and for each comment ask: "Is this a one-off, or would I write this same feedback on a future video?" For patterns, create a new row in the Production Feedback DB with Type = Editing Rule, Source = Self-Review, Status = Active.
Send Shan a Slack message with verdict (1 sentence on cut status), issue count (total comments left), and any new Editing Rules promoted to the DB.
Append to areas/content/long-form/scripts/LF-XX/LF-XX-production-process-log.md with date, version reviewed, comment count, verdict, new rules promoted, and time spent.

Quality Check

All Frame.io comments include clear problem statement and fix request
At least 2–3 positive "WHAT'S WORKING" notes included
PDF exported and saved to correct file path structure
Any pattern issues promoted to Notion Production Feedback DB as active Editing Rules
Shan received clear Slack verdict with scope and new rules
Production process log updated with review details

Common Issues

Skipping the first pass: Don't jump straight into commenting - the end-to-end watch catches structural/flow problems that moment-by-moment review misses
Only negative feedback: Without positive notes, Shan may rewrite parts that were actually good - always include "WHAT'S WORKING" comments
Missing pattern promotion: If you'd write the same feedback on 2 different videos, promote it to an Editing Rule in the DB
Vague verdict: Be specific about cut status - "needs polish pass on visuals" vs generic "needs work"

Video Cut Review and Feedback