Give usable edit feedback

What this is about

An editor cannot act on adjectives. Punchier, cleaner, more premium, less corporate — each of those words describes a reaction and hides its cause, so the editor guesses, changes something, and the same note comes back on the next version with more frustration attached. A note becomes workable the moment it contains three parts: a position in the timeline, a description of what you noticed there, and the effect you wanted. The fix stays with the person who knows what footage exists, which is never the person writing the note.

The order matters more than the tools. Skip a step and you usually notice two steps later — by which point the fix costs several times as much.

What runs differently here

Where this differs from the general case:

• Every note needs a timecode; without one, the editor first has to search for the problem you already found
• Describe the effect on you, not the repair — 'I lost the thread here' beats 'cut two seconds'
• Prescribing a fix hands over your weakest idea and quietly cancels the editor's best one
• One line, one problem: bundled notes come back half-solved and there is no way to tell which half
• Name what works too, or you will lose a moment you loved to a fix you asked for

Step by step

This order gets you there fastest:

1. Watch the full cut before writing a single note. Feedback typed during the first viewing records surprise rather than judgment, and most of it dissolves quietly on the second pass.
2. Give every note a timecode in the format the editor works in, and quote the line or describe the shot so the note still makes sense in the next version.
3. Split each note into observation and intent: what you noticed, and what the viewer should feel there instead. Leave the how to the person who knows the timeline.
4. Rank the list into blocking, improving and personal preference. Unranked notes get worked from top to bottom, which means your priority depends on where you happened to type it.
5. Delete contradictions before sending. When two notes ask for opposite things, decide which one wins — an editor cannot resolve your team's disagreement from inside the software.
6. Add two or three sentences about what already works and why. Protecting good choices is part of the note set, otherwise the next version fixes your complaint and loses your favourite moment.
7. Send once, in one document, from one named person. Notes arriving through three channels across two days turn a single revision round into three overlapping ones.

Common pitfalls

What most often goes wrong in practice:

• Adjective-only notes: punchier, cleaner, more premium, less corporate
• Voice messages the editor has to transcribe before a single edit happens
• Writing the solution instead of the problem and then being disappointed by the literal result
• Adding new notes to sections the previous round already approved

With TillyGen

When a note says the film feels off-message, the agreed goal and target audience are one click away in TillyGen — so the discussion becomes a comparison against something written down rather than an exchange of tastes.

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.