Commercial guide for product designers
Design revision clauses that keep feedback inside the agreed scope
Define revision rounds, consolidated feedback, approvals, and change requests without making the design process unnecessarily rigid.
A useful revision clause distinguishes refinement from a new request. It gives the client room to respond while protecting the designer from an engagement that quietly expands after every review.
01
Define what counts as a revision
A revision adjusts work within an approved brief or direction. New screens, new user flows, a different product direction, or a return to an already approved stage are usually new scope rather than another revision round.
Practical distinction
Changing hierarchy and copy within an approved checkout flow is a revision. Adding subscription management and team permissions is additional scope.
02
Count rounds and require consolidated feedback
State how many revision rounds are included for each stage. One round should mean one consolidated response from the agreed client decision-maker, not separate comments arriving indefinitely from several stakeholders.
- —The number of included rounds
- —Who provides final consolidated feedback
- —The response window for each review
- —What happens when feedback arrives late
03
Close approved stages deliberately
Approval should allow the next stage to begin and close earlier decisions unless both parties agree to revisit them. Record whether approval happens by email, a signed milestone, or written confirmation in the delivery tool.
Tie payment to a recognizable decision such as approved direction, prototype approval, or final handoff—not simply to time spent inside a design file.
04
Move material changes into a change order
When feedback changes the deliverables, cost, or delivery date, document it separately. A change order preserves the original agreement and makes the new decision visible to both parties.
Put this into the agreement
A practical final check
- 01List the revision rounds included at each design stage.
- 02Define a round as one consolidated client response.
- 03Set review and approval windows.
- 04Name examples of revision work and additional scope.
- 05Use a signed change order when cost or delivery changes.
Editorial standard
Written from the workflow the product actually supports.
- Prepared by
- The Censiq product team, which designs and maintains the agreement, invoicing, retainer, and reminder workflows described in this guide.
- Review method
- Product-specific statements were checked against the current Censiq workflow. No customer outcome, legal result, or payment-speed claim is inferred.
- Dates
- Published August 13, 2026. Last reviewed August 17, 2026.
- Corrections
- Found something inaccurate? Email support@getcensiq.com.
Continue with a related guide
All independent professionals
Milestone billing based on events a client can recognize
Read guideDevelopers
Developer deposit structures that protect the start of a project
Read guideGeneral operational information only. This guide is not a substitute for legal, tax, or financial advice.