One round of revisions is one complete designer response to one complete set of client notes, not a count of individual change requests. Changing three colors and moving a headline in one batch of feedback is one round, not four. A working definition matters less as a rule to recite than as something tested against the edge cases that actually cause arguments: a clarifying question, a late "one more thing," and a request big enough not to be a revision.
What Starts a Round
A round starts when the client delivers a complete, if imperfect, set of notes on a version you have shown them. It does not start every time a message arrives. A single clarifying question, "does the logo need to stay on the left in the mobile version," is not a round starting, because it is not feedback on the work, it is a request for information needed to finish the work already in front of them. A typo catch is not a round either, since it is a correction, not a judgment about the design. Both are handled without touching the round count. A round begins specifically when the client has looked at a version and told you, in whatever form, what they want changed about it, which is part of why asking for feedback in a specific, structured way makes the round count easier to track in the first place: a scattered, vague answer is harder to recognize as "complete" than a focused one.
What Ends a Round
A round ends when the designer delivers a complete response to that complete set of notes, not when the client stops sending messages. This distinction matters because clients do not always deliver feedback in one tidy message. A note that arrives an hour after the main batch, still addressing the same version and the same review session, belongs to the round that is already open. It is a continuation of the same conversation, not a new one. The round closes when the designer's response goes back, and the count only advances from there.
The "Just One More Thing" Case
This is the edge case that causes the most friction, because it feels to the client like a small, costless addition and can feel to the designer like scope quietly expanding. The test is timing and continuity, not size. A follow-up sent the same day, still about the version already under review, is part of the round already in motion, whether it is one small note or three. A note that arrives after the revised version has already been delivered and approved, reopening something that was considered settled, is a new round, even if it is equally small. The line is not how big the ask is. It is whether the conversation it belongs to is still open.
The "Let's Try Something Totally Different" Case
Occasionally a note is not a revision at all. "Can we try a completely different layout concept" is not asking for a version of the current direction with changes, it is asking for a new direction from a blank page. The test here is whether the request can be satisfied by adjusting the existing file, or whether honoring it means starting over. If it is the second, it should be named plainly as a new concept, priced and scoped as such, rather than folded quietly into the current round's count. Treating it as a revision under-values the actual work and sets a precedent that a full pivot costs the same as a color change.
Why This Needs to Be Written Down Before Round 1, Not Argued at Round 3
None of these edge cases are controversial once stated plainly, but stating them after a dispute has already started is much harder than stating them before one exists. A definition agreed at the start of a project, in writing, in the proposal or the contract, means round three's disagreement about whether something counts gets settled by pointing at a sentence both sides already agreed to, rather than by two people arguing about what feels fair in the moment. This is not legal advice, and a written agreement's enforceability depends on the actual contract language and the jurisdiction it sits in; a designer who wants that language to hold up should have a professional review the actual clause rather than relying on a blog post's wording. What this piece can responsibly offer is the working definition itself, something to bring into that conversation with a lawyer or into your own proposal template, not a substitute for either. It is one part of the larger habit of settling things in writing before they become disputes, the same discipline that runs through every stage of the solo design project process.
From Definition to Count: What This Sets Up
A clear definition is only useful once it is actually being tracked against real rounds on a real project, and that is a separate skill from stating the definition itself: deciding how many rounds a project includes, what happens when a client goes over, and how to communicate that plainly without it becoming a confrontation. The definition in this piece is the foundation that method depends on. Getting clarity on what a round is comes first, because without it, counting rounds accurately is impossible no matter how careful the tracking system is.
FAQ
What counts as one round of design revisions?
One complete designer response to one complete set of client feedback on a given version, regardless of how many individual changes that feedback contains. Three small changes made from one batch of notes is one round, not three.
Does a clarifying question count as a new round?
No. A question asked to finish the current version, rather than feedback judging a completed version, does not start or end a round.
Does a late "one more small thing" count as a new round?
Not if it arrives while the current round is still open, meaning the reviewed version has not yet been revised and returned. If it arrives after that version was delivered and considered settled, it is a new round.
Is asking for a completely different design direction a revision?
Usually not. If the request cannot be satisfied by adjusting the current file and instead requires starting over, it is a new concept, which should be scoped and priced separately rather than counted against the existing revision allotment.
Should the definition of a revision be written into a contract?
Yes, ideally before the project starts, in the proposal or agreement both sides sign. This article is not legal advice; for actual contract wording, have a qualified professional review the clause for your situation and jurisdiction. The definition here, tested against the make it pop style of vague feedback and other edge cases, is meant as a starting point for that conversation, not a finished legal document.