Revision limits that preserve the relationship
How to set boundaries around edits without making collaboration feel transactional.
Revision limits work best when they explain the rhythm of the project, not when they appear as a penalty after feedback arrives. A useful boundary tells the client when to consolidate comments, what counts as a round and what happens when the agreed work is complete.
Define a round in observable terms
A “round” should mean one consolidated set of feedback on a named deliverable. Say who gathers comments and when the team considers the round complete. This prevents five stakeholders from creating five invisible rounds.
Connect the limit to a review moment: first concept, refined direction and final corrections. Clients can participate more confidently when they know what kind of feedback is useful at each stage.
- Named deliverable
- Single consolidated response
- Deadline and decision owner
Distinguish correction from expansion
Correcting a mistake against the accepted brief is different from changing the brief. Likewise, refining an approved direction differs from asking for a new direction. Write those distinctions plainly before the project starts.
When an edit expands the work, describe the delta and its impact. Clearcut can turn the new request into a short add-on quote while preserving the original baseline.
- Correction against agreed requirements
- Refinement within an approved direction
- New direction, deliverable or audience
Respond while the request is still small
Do not wait until several extra rounds have accumulated. A brief note after the first out-of-scope request is kinder and easier to resolve than a surprise invoice at the end.
Keep the tone factual: what was included, what is now requested and the options available. Boundaries feel less personal when they are connected to a shared record.
- Name the current round
- Show what remains included
- Quote or trade the additional work
