Feedback Loop

What this is about

A revision round is the unit you count; the loop is how the notes get there. What breaks edits is not the volume of feedback but its shape: five people commenting in three tools, two of them contradicting each other, one replying after the deadline. A workable loop names one tool, asks for timecoded comments, sets a return date, and requires the client side to resolve internal disagreements before the list is sent. Write down that silence is not approval, because an unanswered review link is the most common reason a delivery date slips.

A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.

What runs differently here

Where this differs from the general case:

• One tool, timecoded comments, one consolidated list per round — three rules that remove most edit chaos
• Contradictions get resolved on the client side; the edit is not the place to arbitrate opinions
• State in writing that silence is not approval, and attach a date to every review link

With TillyGen

TillyGen ties every planned deliverable to its review point, so feedback arrives against a version instead of against a memory.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.