Skip to content
henshu

Free guide · Review checklist

Send a review your client can finish.

A practical client video review checklist, with a ready-to-copy review request and a clear process for closing each feedback round.

Try the sample workspace. No signup needed for the demo.

Before you send the link

A useful review starts before anyone presses play. The client should know what they are deciding, which version to watch, and when the team needs an answer. Run this checklist before every external round.

  • The correct cut is uploaded and its version is clear.
  • The team has checked playback, sound, text, and obvious export problems.
  • The review link and access work for the intended reviewer.
  • The round has a purpose: story, structure, polish, or final approval.
  • One person will combine the client team’s feedback.
  • The deadline includes a time zone and leaves time for revisions.

Copy this review request

Hi [name],

[Video title], version [number], is ready for [type of review].

Please watch: [review link]
For this round, please focus on: [two or three decisions].
Already agreed: [items that are no longer open].

Please leave timecoded notes on the review and combine your team’s feedback by [date, time, time zone].

[Decision maker] will confirm the final set of changes. We plan to share the next cut on [date].

Thanks,
[name]

During the review

Write one actionable point per comment. Include the moment, the problem, and the requested outcome. “At 00:12, the product name is hard to read. Please make it larger” is easier to act on than “The text feels off.” If two reviewers disagree, the producer should ask the decision maker to resolve the choice before the editor starts.

Before the next version

Separate required changes from new scope. Give every agreed change a clear owner, then check the next cut against those notes. Do not silently carry unresolved questions into the next round. Call out anything you could not change and explain why so the client can make a decision.

Close the round

Ask for an explicit approval or a final list of remaining changes. Record who approved which version and when. Confirm the export and delivery destination, then assign that final step. If more work is requested later, give it its own date and scope instead of replacing the meaning of “approved.”

See how your next job could flow.

Open the demo, follow a task, and try the next handoff. The sample work is yours to explore.