Review deliverables and request changes

Specific feedback helps the team make the right change. Keep discussion connected to the current asset and distinguish file review from milestone approval.

Open the current version

Confirm the file name, version and client account. Read its description and any review instructions before commenting. Earlier comments may describe an older version; check the history before assuming they still apply.

Add useful feedback

For supported PDFs and images, place feedback on the relevant page or area. Video and audio comments can include the current playback time. Website review can use page-specific annotations where supported. If a site or video refuses embedding, open its direct link and return to the file conversation with a precise reference.

Resolve and review again

State what needs to change and how to verify it. When a new version is ready, compare it with the requested changes. Resolve the appropriate discussion only when the change has been checked. A resolved comment is not automatically an approval of the whole project.

Approve the right work

Use the approval control offered for the asset or milestone, with the intended version and role. A milestone can have its own start/finish approver and gates. If changes are needed, use the configured request-changes path and provide a clear note. See milestones.