A contract says three revision rounds. The client interprets that as three complete redesigns, while the design team understands it as three refinements within one direction. Both believe their interpretation is reasonable, and the dispute often emerges late in the project.
The solution is not simply to add more rounds, but to define a round, distinguish direction changes, consolidate feedback, and confirm additional work.
01 Define One Round as One Consolidated Feedback Submission
The client's internal team should discuss first, then a designated owner submits all comments together. Scattered messages from different people over several days should not become unlimited micro-rounds.
The design team should respond to each comment with its proposed treatment, creating a traceable record.
02 Separate Direction Changes from Detail Revisions
Color, letter spacing, images, and local copy are usually details. Replacing the positioning, rebuilding the structure, or adopting a different visual route changes direction.
Reversing a confirmed direction affects completed pages and systems and requires reassessment.
03 Evaluate the Logic During Proposals Before Refining Details
First decide which direction best supports the objectives, users, and use cases, then refine it. Polishing every direction equally consumes budget and slows decisions.
Clients can raise questions and concerns, but should not combine unrelated parts from several concepts.
04 Match Revision Rounds to Project Complexity
A simple logo or page may include two or three rounds. Complex brand systems and product designs can define rounds by stage. Long-term iteration is better managed monthly or by workload.
There is no universal industry number; scope and decision mechanisms matter.
05 Exceeding the Limit Does Not Require Immediate Conflict
First determine whether the design failed an agreed standard, requirements changed, or new content was added. Fix design defects; price changes in client objectives or scope separately.
Both sides should rely on documentation rather than emotion.
06 Reduce Final Rework Through Staged Acceptance
Confirm requirements, prototypes, visual direction, complete design, and development review step by step. Do not move deeply into a later stage before the previous one is accepted.
Stage approval does not prohibit correcting errors; it locks the foundation already agreed upon.
Revision Classification
| Type | Example | Typical Treatment |
|---|---|---|
| Design defect | Missing states, inconsistency, or conflict with approved requirements | Fix without treating it as added scope |
| Detail revision | Color, spacing, images, or local copy | Count toward agreed rounds |
| Direction change | Replacing style, structure, or positioning | Reassess fees and schedule |
| Added scope | New page, feature, or language | Change order or supplemental quote |
| External change | New regulations, APIs, or platform rules | Jointly assess responsibility and impact |
Frequently Asked Questions
Are three revision rounds enough?
They are enough for most clearly scoped projects, but should be assigned by stage with direction and details distinguished.
Does a design mistake count as a round?
Work that conflicts with approved requirements or contains an obvious omission should generally be fixed, not treated as a new client revision.
Can clients send comments in group chats at any time?
Discussion is fine, but the designated owner should consolidate and submit formal revisions to prevent conflict and duplication.
How should work beyond the included rounds be priced?
Price it by workload, page, hour, or added stage, with written approval in advance.
Can the visual style change after direction approval?
Yes, but it is usually a significant change that affects the schedule and budget.
| Service | View |
|---|---|
| Related service | Contact JVDS Design Studio |
| Design work | View selected work |
| Project inquiry | Contact JVDS Design Studio |
Link copied
