Email template
Revision summary email
A revision summary closes the loop. It turns a pile of comments into a short list of changes, decisions and open items, and it gives the client a reason to confirm the round.
When to use it
Send after the studio has uploaded a new version and wants the client to confirm the round.
Subject
{{project_name}} — changes in {{version}}
Body
Hi {{first_name}},
We have uploaded {{version}} of {{project_name}}. Here is what changed from the last round.
Changed: {{changed_list}}
Still open: {{open_list}}
Review the new version here: {{review_link}}
Please confirm the round is closed or tell us what still needs a change by {{due_date}}.
Thank you, {{sender_name}} {{studio_name}}
Before you send
- Keep the changed list short and specific.
- Name the open items instead of implying everything is resolved.
- Link to the exact version.
- Ask for a confirmation, not a vague 'looks good'.
Questions
Should the revision summary list every comment?
No. Group the changes by theme and list the decisions. The full comment trail stays in the review link.
What if a change was not made?
List it as open with the reason. A summary that hides a skipped change destroys trust in the next review.
Can the summary be a PDF?
A short email is easier to read. Use a PDF only when the client or the project requires a formal record.
Sources
Reviewed November 3, 2026. Public pages can change; check the source before relying on a date or a price.