Feedback is useful when everyone sees the same version
A comment can be perfectly clear and still be applied to the wrong cut. Keep the discussion connected to the file being reviewed.
Put the note where the issue happens
A time-linked comment on a video, an image annotation or a PDF-page note gives the next person a place to start. Use replies to preserve the discussion rather than collecting disconnected messages in several channels. When feedback becomes work, create or follow the connected task so the change can be tracked without losing its original context.
Approval belongs to the reviewed file
A new upload is a new review decision. Do not treat an earlier approval as permission to deliver an unseen replacement. Inspect the version selected for review and the version marked for delivery. Shared links also deserve attention: send the intended audience the permitted material and revoke a share that is no longer needed. The useful outcome is an identifiable approved file, not simply an inbox with fewer messages.
Put it into practice
Feedback and approval belong to a particular file version. Uploading a new version must not imply that it has inherited an earlier approval.
- Upload supported media and wait until processing reports it ready. Open the intended version.
- Add comments at the relevant time, image area or PDF page. Use replies and resolution to retain the discussion context.
- Share through the scoped review flow and inspect the approved version before delivery. Revoke an unneeded share using the available control.
Try this next
Open one active review. Confirm the selected version, unresolved comments and intended final delivery before asking for approval.
June–October 2026 editorial series. Issue dates organise the series; they are not feature launch dates.