Checklist
Design revision round checklist
A revision round goes wrong when comments arrive in five channels, the scope grows without a conversation and nobody knows which comments were addressed. This checklist gives the round a start, a middle and an end.
Collect
- One channel
Ask the client to put every comment in the review link. A comment in a meeting or a chat is easy to lose and hard to prove.
- Consolidate
Ask the decision maker to consolidate the team's comments before the studio starts. Five reviewers should produce one set of feedback, not five.
- Deadline
Set the feedback deadline and the next version date together. A round without a deadline becomes an open-ended edit.
Triage
- Classify
Mark each comment as a correction, a refinement, a new request or a question. The class decides whether it is in scope and who owns it.
- Scope check
Compare the requests with the agreed deliverables and rounds. A new page, a new format or a new concept is a scope change, not a revision.
- Estimate
Estimate the time for the round and flag anything that moves the delivery date. Send the estimate before the work starts.
Implement and close
- Respond in the thread
Reply to each comment with what changed, what did not and why. The client can see the resolution against the exact comment.
- New version
Upload the new version and link the resolved comments to it. Do not send a new file without the comment trail.
- Close the round
Ask the client to confirm the round is closed or list the remaining items. A round that fades out leaves the next version ambiguous.
Questions
What counts as a revision round?
A round is one consolidated set of client feedback and one studio response. A stream of comments over several days is not one round.
How do I handle a request that is out of scope?
Name it as a new request, estimate the time and cost, and ask the client to approve it before the work starts. Do not absorb it into the current round.
Should the studio reply to every comment?
Every comment that changes the work should have a response. A question can be answered in the thread; a correction should say what changed.
Sources
Reviewed November 3, 2026. Public pages can change; check the source before relying on a date or a price.