Define a revision round before work begins
A revision round is easier to manage when both you and your client know what it means. Rather than offering “two rounds of revisions” without explanation, describe a round as one consolidated set of feedback on a presented version, followed by your response to that feedback. This gives the client a chance to review the work with everyone involved before sending comments. It also helps distinguish a planned review from a stream of individual requests arriving over several days.
State how many rounds are included, when feedback is due, and which deliverables the rounds cover. If you are designing a small website, for example, feedback on an approved page layout may be different from a request to design an additional page. Keep the explanation in the project proposal or kickoff notes, then restate it when you present the first draft. A short reminder at the point of review is often more useful than relying on a document sent weeks earlier.
Make feedback easier to give and use
Clients may not know how to comment on creative work. Invite them to describe what is not working and why, rather than asking them to invent a design solution. Questions such as “Which message feels unclear?” or “Is there an audience need this layout misses?” can lead to more useful feedback than a general request for thoughts. Ask for one combined response from the client team when possible, especially if several people must approve the work.
Before making changes, summarize the feedback you received and flag anything that conflicts or needs a decision. For instance, one reviewer may want a quieter visual style while another wants more prominent calls to action. Identifying that tension early gives the client a chance to choose a direction. It also prevents you from using a revision round to produce a version that cannot satisfy the people reviewing it.
Separate refinements from new work
A revision adjusts work within the agreed direction and deliverables. It might involve changing a headline, improving contrast, or refining the spacing of a page already in scope. An additional request changes the assignment itself: a new deliverable, a different audience, a replacement concept after a direction was approved, or a substantial change prompted by new information. The distinction is not always obvious, so focus on what the request would require rather than debating whether it technically counts as a revision.
When a request seems larger than the included rounds allow, acknowledge its purpose first. Then explain what changes in the work plan. You might write: “I can see why a second landing page would help address that audience. The current project covers one page, so I can outline the time and cost for adding another before starting it.” This keeps the conversation collaborative while making it clear that extra work needs a separate decision.
Respond with options, not a surprise bill
Avoid silently completing additional changes and raising the issue afterward. Pause, describe the request in concrete terms, and offer a way forward. Depending on the project, the options might be to replace a lower-priority item with the new request, schedule an additional paid revision round, or treat the work as a separate follow-up project. Give the client enough information about the likely impact on timing and deliverables to make a choice before you proceed.
You can be flexible without making your process unpredictable. A small correction may be quick to accommodate, while a series of small additions can amount to significant work. If you choose to include something as a courtesy, say so plainly: “I’ll include this text change in the current round; any further changes after approval can be scoped separately.” That wording avoids turning an exception into an unspoken expectation.
Keep the decision trail simple
After each round, send a brief recap: which comments you addressed, which decisions remain open, and what version is ready for review. Refer to the agreed scope when needed, but do not make every message sound like a dispute. A shared feedback document or a single email thread can help you avoid losing decisions across calls, messages, and annotated files. Use whatever system the client can follow consistently.
When the final included round is complete, ask for explicit approval or a clearly scoped list of remaining changes. If more work is requested, confirm the new scope and terms before starting it. The goal is not to eliminate changes; creative work benefits from thoughtful revision. The goal is to give both sides a dependable way to discuss changes, make decisions, and finish the project with fewer surprises.
