How many revision rounds should you offer?
Why the number matters less than the definition, and how to write a revision clause that actually holds.
Most freelancers pick a number first and define the number later, or never. That is backwards. The number of revision rounds you include matters far less than your written definition of what one round actually is. A project with three vaguely defined rounds will cost you more unpaid hours than a project with one tightly defined round.
This article covers the practical answer: how many rounds to include, how to define a round so it holds up under pressure, and what to do when a client sends feedback in fragments.
The short answer
There is no universal number, and the sources that write the standard contracts do not give you one. The AIGA Standard Form of Agreement instructs designers to spell out, per project phase, "the number of creative directions that you will be showing, the number of revisions or refinements that are included, the format for delivery, the necessary timeframe" (AIGA Standard Form of Agreement for Design Services). The instruction is to state a number, not to use a specific one.
Freelancers Union's contract guidance takes the same position, and its worked example uses two rounds included in the base fee, with a stated rate for anything beyond that (Freelancers Union). Its contract generator leaves the count as a blank you fill in, alongside a per revision rate and a deadline for submitting revision requests (Freelancers Union Contract Creator).
So the working answer for most single deliverable creative projects is two rounds per deliverable, with a defined path to buy more. Two rounds maps onto how creative work converges: one round for structural direction, one round for polish. If your work is genuinely exploratory, add a concept selection step before round one rather than a third round of open ended notes.
Why the definition beats the number
Uncontrolled change is common enough to be a background condition of project work, not an unlucky event. PMI's 2018 Pulse of the Profession found that 52 percent of projects completed in the prior 12 months experienced scope creep or uncontrolled changes to scope, up from 43 percent five years earlier (PMI). It stays near the top of practitioner pain lists in adjacent service industries too: in Moovila's 2025 survey of 263 managed service providers, scope creep was the most cited project challenge at 58.7 percent of respondents, up from 46 percent the prior year (Moovila).
PMI's own guidance is not "include fewer revisions." It is to define both what is inside scope and what is outside it, to set boundaries during planning, and to put the client's responsibilities and the change procedure in the agreement (PMI).
That is the part most revision clauses miss. "Two rounds of revisions included" without a definition of a round invites the drip. The client sends four notes on Monday, two more on Tuesday, remembers something Thursday, and loops in a colleague Friday. You have done four rounds of work and billed for two.
A usable definition of one revision round
Write it in plain language and put it in your proposal, not only your contract. A round is:
- One batch. All feedback from all stakeholders, consolidated into a single submission. Notes arriving after the batch is submitted go into the next round.
- One owner. One named person on the client side collects internal feedback and sends it. You respond to that person, not to five inboxes.
- One window. Feedback is due within a stated number of business days after delivery. Freelancers Union's template includes exactly this: the client must submit revision requests within a set number of days, and the freelancer completes them within a set number of days (Freelancers Union Contract Creator).
- One direction. A round refines the approved direction. It does not replace it. Replacing the direction is new work.
- One format. Notes reference specific elements, pages, or timecodes. "Make it pop" is not a note yet, it is a prompt for a clarifying question.
The last point is where feedback quality does real damage. Nielsen Norman Group describes critiques built on hypothetical scenarios and pseudoevidence rather than observed problems (Nielsen Norman Group). Smashing Magazine's guidance is to frame the problem first, so reviewers know what they are evaluating (Smashing Magazine).
Comparison of revision round policies
| Policy | How it works | Works well for | Main failure mode |
|---|---|---|---|
| Unlimited revisions | No stated cap | Very short, very cheap deliverables where your time exposure is small | No natural stopping point, and margin depends entirely on client temperament |
| Two rounds per deliverable | One structural round, one polish round, extra rounds quoted | Logos, single page sites, short form video, copy decks | Fails if a round is undefined and feedback arrives in fragments |
| Three rounds per deliverable | Adds a final check round | Brand systems, longer edits, multi stakeholder reviews | Round three often becomes a place to reopen direction |
| Rounds per phase | Each phase carries its own allowance, for example two in concept and one in refinement | Multi phase projects with distinct approval gates | Requires real phase sign off, otherwise phases blur together |
| Time boxed revisions | A stated block of revision hours, then hourly | Ongoing retainers, editorial work, technical builds | Requires honest time tracking and a client comfortable with hours |
| Unlimited within a window | Unlimited notes for a fixed period after delivery, then closed | Fast turnaround production work | Encourages a rush of low quality notes near the deadline |
None of these is correct in the abstract. What makes any of them work is the definition of a round and a written path for work that falls outside the round.
A worked example
A freelance designer quotes a logo and basic identity package at 2,400 dollars. Terms: two revision rounds included, one consolidated batch per round, feedback due within five business days, additional rounds at 300 dollars each, new deliverables quoted separately.
Delivery: three concept directions.
Client picks direction B. That selection is the approval gate, not a revision. The designer writes it down in the project record: direction B approved on the 14th, including the wordmark lockup and the two color palette.
Round one feedback arrives as four notes. Tighten the letter spacing, test a darker navy, simplify the mark's inner detail, and try the wordmark at small sizes. All four refine direction B. All four are inside the round. The designer does the work and delivers.
Then three things arrive over the next week.
- On day two, two more notes about the navy. These are follow ups within the same batch window, so the designer folds them into round two rather than treating them as a separate round. The generous read costs little and buys goodwill.
- On day four, the client's new marketing hire asks to "see a version that feels more like direction A." That is not a refinement of the approved direction. It is a return to concept selection. The designer replies with a change request: one additional concept direction, 450 dollars, three business days added to the timeline, approval needed before work starts.
- On day six, the client asks for social profile crops and a favicon. Those are new deliverables, not revisions. They get their own line item, 200 dollars, quoted in the same change request.
The client approves the social crops and declines the new direction. The project closes at 2,600 dollars with both rounds used and no unbilled work. Nothing about the exchange was adversarial, because the categories were set before anyone was annoyed.
Note what did the work here. Not the number two. The definition of a batch, the named approval gate, and a written path for requests that did not fit.
How to write your policy this week
Keep it to six lines in your proposal, in the client's language:
- Each deliverable includes two rounds of revisions.
- One round is one consolidated set of feedback from all reviewers, sent by one named contact.
- Feedback is due within five business days of delivery.
- Revisions refine the approved direction. Changes to the approved direction or new deliverables are quoted as change requests.
- Additional rounds are available at a stated rate.
- Final approval is confirmed in writing before files are released.
Then actually follow it. A policy you waive on the first uncomfortable Thursday is a policy your client correctly learns to ignore.
Where the operational side lives
A revision policy is a sentence. Running it is a habit: logging which round you are in, classifying each incoming request, writing the change request, and getting sign off without turning a small ask into a negotiation.
That is the gap Revision Ledger is built for. It is a 39 dollar set of working documents: a Project Scope Record, a Revision Decision Guide for classifying each request as an included revision, a clarification, or a paid change request, a revision log for Notion and Google Sheets, a client feedback form, a change request template, email scripts, an AI prompt library, and a 15 minute setup guide. If you already have a policy you enforce consistently, you do not need it. If your policy exists mostly in your head, the kit is the version you can run on a live project.
One clarification worth stating plainly: the kit is an operational workflow, not a contract, and not a substitute for legal advice. Contract language for your jurisdiction and situation is a question for a qualified lawyer. What the kit handles is the day to day practice of holding the line the contract describes.