guaro mediaMake something worth sharing
Menu
Workflow

Keep track of feedback across several editing rounds

Turn comments from different reviewers and versions into a single traceable list of decisions and completed changes.

A person checking notebook notes beside photographs and a laptop.

Several editing rounds can produce comments in email, screenshots and messages that refer to different versions. The problem is often less about doing the changes than knowing which request still applies. A small feedback log connects each observation to its source version, records the decision and makes the next review easier to follow.

Give each review a fixed reference

Export a clearly numbered review version and tell reviewers which file to use. Include the version in the review message and in the file name. Avoid replacing that file silently with a revised export while comments are still arriving.

For video or audio, ask for a time reference and a short description. For photographs, use filenames or selection identifiers. Screenshots can help explain a layout concern, but keep enough context to identify the correct page or frame.

Collect comments in one working list

Record the reviewer, the referenced version and the requested change in a shared document or your own log. A short table can include an identifier, location, issue, decision and status. Use a system small enough to maintain during the edit.

Preserve the meaning of a comment when you summarise it. Separate an observed problem from the proposed fix: text is difficult to read differs from make the font twice as large. The first may be solved by contrast, spacing or placement instead.

Resolve conflicts before applying changes

When two comments disagree, identify the intended audience and the agreed purpose of the piece. Ask the responsible decision-maker to settle material conflicts when you cannot resolve them from the brief. Do not hide the disagreement by choosing whichever comment arrived last.

Mark requests as accepted, declined or awaiting clarification, with a brief reason where useful. Keep completed changes distinct from open questions. This prevents a later round from reviving an old request without anyone noticing that the situation has changed.

Close the loop on the next version

When you export the revision, record which feedback items it addresses. Recheck the changed areas and their immediate surroundings: moving a title can cover a face, and shortening a scene can leave a subtitle behind.

Give reviewers the new version and a concise list of outstanding decisions. Keep earlier comments tied to their original file so old time references are not mistaken for current ones. Archive resolved rounds when the work is approved, while retaining the decisions that explain the final result.

Version references and explicit decisions keep a feedback log useful. Collect comments in one place, clarify conflicting requests and check the effect of each change. The next round should begin with the current work and a short, accurate list of what remains open.