Common baseline
1-2 rounds
Enough for refinement, not reinvention.
Revision limits should not feel hostile. They should help both sides understand what kind of feedback is included, when decisions become final, and when a new direction becomes new scope.
Common baseline
1-2 rounds
Enough for refinement, not reinvention.
Key distinction
revision vs new direction
This is where most disputes start.
Protection
approval states
Approved work should not reopen casually.
A revision should refine an agreed direction. If the client changes the goal, audience, structure, feature set, or creative concept, that may be new scope.
There is no universal number, but fixed-price work needs a limit. More subjective work may need clearer feedback moments, not unlimited rounds.
If approval does not change the project state, it is not very useful. Approved work should be the basis for the next step, not an invitation to restart.
Many freelancers start with one or two rounds, then price additional rounds. The right number depends on project complexity and how subjective the work is.
Usually no. A new concept or direction changes the scope because it asks for different work, not refinement of the agreed work.
Tie feedback to milestones and windows. Late feedback can be accepted as a paid change or moved into a future phase.
EasyScope