How to Set a Freelance Revision Policy That Protects Time
Define a round, cap the count, and draw the line between refining agreed work and accepting new scope.
The Delivvo team· June 2, 2026 9 min read
Most freelancers do not lose money on the projects that go wrong. They lose it on the projects that go almost right, then keep going. The work is approved in spirit, the client is happy, and then a fourth round of small changes arrives. Then a fifth. None of it feels big enough to push back on, so you absorb it. By the time the file is final, you have worked a week longer than you quoted, and your effective hourly rate has quietly collapsed.
A revision policy is how you stop that slow leak. It is not a way to be rigid or to nickel-and-dime good clients. It is a shared definition of what "done" means, agreed before the work starts, so that nobody has to argue about it at the end. This guide covers what a revision round actually is, how many to include, the line between refining agreed work and accepting a new request, and how to put all of it into your proposal. At the end you will find scripts you can paste and send.
Why unlimited revisions quietly destroy your margin
The promise of "unlimited revisions" sounds generous. In practice it removes the only natural stopping point a project has. When there is no agreed cap, every round of feedback is treated as free, so feedback stops being decisive. Clients defer choices, change their minds, and run experiments on your time because nothing tells them the experimenting has a cost.
This is the freelance version of scope creep, and scope creep is not a fringe problem. The Project Management Institute's Pulse of the Profession research found that 52 percent of projects experienced scope creep, up from 43 percent a few years earlier. PMI has tracked the same upward drift in its own reporting on uncontrolled change. Large organisations with project managers and change-control boards struggle to contain it. A solo freelancer with no policy has almost no chance.
Keep reading
The cost is real money, not just inconvenience. Unbilled revision rounds are hours you have already sold to a future client and given away to a current one. When you stack three of those on top of a fixed-price quote, the project that looked profitable on paper finishes at a loss, and you funded the difference yourself.
What counts as one revision round
Before you can cap revisions, you have to define the unit. A revision round is one consolidated set of feedback delivered against a specific deliverable, returned to you in a single pass. The key word is consolidated. One round is the client reviewing the work, collecting every change they want, and sending them together. It is not a stream of separate messages over four days, each adding one more tweak.
Spell this out, because the difference is enormous for your workload. Ten changes batched into one document is one round. The same ten changes arriving as ten emails is, without a clear definition, ten interruptions and effectively several rounds of context-switching. Define the round as the batch, and ask clients to hold their notes until they have reviewed everything.
A practical definition reads like this: a round is your delivery of the work, the client's single consolidated list of requested changes, and your implementation of those changes. When you send the updated version back, that round is closed. The next set of feedback opens the next round.
How many rounds to include
There is no universal correct number, but two rounds is the sensible default for most creative and digital work. Round one absorbs the big directional feedback. Round two handles the polish. Past that, you are usually no longer improving the work. You are reacting to a client who has not made up their mind, and that indecision should not be free.
Match the count to the work. A logo or a brand mark, where taste varies and the stakes feel high, might justify three rounds. A blog post or a routine landing page rarely needs more than one or two. A large website build should attach revisions to each stage rather than the whole project at once, so feedback stays close to the work it concerns.
Whatever you choose, state it as a number and state what happens after. "This project includes two rounds of revisions. Additional rounds are billed at my standard hourly rate." That single sentence does more to protect your time than any amount of goodwill, because it converts an open-ended obligation into a defined one.
A designer comparing two versions of a layout on screen while taking notes
The line between a revision and new scope
This is the distinction that protects you most, and the one freelancers most often get wrong. A revision refines work you already agreed to do. New scope is a new request. The two look similar in a client's message and feel completely different in your week.
Use a simple test. If the change brings the deliverable closer to the brief you both agreed on, it is a revision. If the change adds something the brief never described, it is new scope. "Make the headline larger and warm up the blue" is a revision. "Can you also design a matching email template" is new scope. "Tighten the second paragraph" is a revision. "Now write three more articles in this style" is new scope.
The reason this matters is that new scope wears the costume of a revision. It arrives in the same thread, in the same friendly tone, often with the words "just" or "quick" attached. If you treat it as a revision, you do unpaid project work and call it feedback. Naming it early, calmly, and without drama is the whole skill. You are not refusing the work. You are pricing it. For a deeper look at how these requests accumulate, this guide on how to stop scope creep is worth reading alongside this one.
Write the policy into the proposal and contract
A revision policy only protects you if the client agreed to it before the work began. Said for the first time at delivery, it sounds like a penalty. Written into the proposal they signed, it is simply the deal. Put it in both the proposal and the contract so there is no gap between the friendly pitch and the binding terms.
Your clause does not need legal language. It needs four things to be unambiguous: how many rounds are included, what one round means, what triggers a billable round, and the rate for extra work. Something like this is enough:
This project includes two rounds of revisions per deliverable. A round is one consolidated set of changes submitted together after you review the work. Requests that fall outside the agreed brief are treated as new scope and quoted separately before any work begins. Additional revision rounds beyond those included are billed at my standard hourly rate.
The phrase "quoted separately before any work begins" is the load-bearing part. It promises the client there will be no surprise invoices, and it promises you that you will never start unpaid work by accident. The revision policy belongs inside your broader project terms, which is one more reason a clear statement of work is worth writing before any project of real size.
Calm scripts for the out-of-scope conversation
When an out-of-scope request lands, the instinct is either to say yes and resent it, or to go quiet and dread the reply. A prepared script removes both. The tone you want is matter-of-fact, never apologetic. You are not delivering bad news. You are answering a pricing question.
For a request that is clearly new scope: "Happy to take this on. It sits outside our original brief, so I'll treat it as a small add-on rather than a revision. It's about two hours of work, which comes to the figure below. Want me to go ahead?"
For a client who has used their included rounds: "We're now past the two revision rounds included in the project. I'm glad to keep refining. Further changes are billed hourly, so I'll send a quick estimate before I start anything. Does that work for you?"
For the "just one quick thing" that is actually a new deliverable: "I can absolutely build that. It's a separate piece from what we scoped, so I'll quote it on its own rather than fold it into this project. That keeps the timeline and the invoice clean for both of us."
Notice what every script shares. It says yes to the work. It names the line without arguing about it. It ends with a clear next step. You are not asking permission to be paid for your time. You are letting the client decide whether the extra work is worth it to them, which is the only fair way to handle it.
FAQ
How many revision rounds should I offer as a freelancer?
Two rounds is the sensible default for most creative and digital work: one for direction, one for polish. Higher-stakes deliverables like brand identity can justify three. Large multi-stage projects should attach revisions to each stage rather than the whole engagement, so feedback arrives close to the work it concerns.
What is the difference between a revision and new scope?
A revision refines work you already agreed to deliver against the brief. New scope adds something the brief never described. The test is direction: a change that moves the deliverable closer to the agreed brief is a revision, while a change that introduces a new request is new scope and should be quoted separately.
Should I ever offer unlimited revisions?
Almost never on fixed-price work. Unlimited revisions remove the project's natural stopping point and encourage indecision, because feedback no longer carries any cost. If you want to signal generosity, offer a clear number of rounds and respond quickly within them. That feels more attentive to clients than an open-ended promise you will quietly resent.
How do I tell a client a request is out of scope without losing them?
Say yes to the work, name it as a separate item, and quote it before starting. Keep the tone factual rather than apologetic. Most clients are not trying to take advantage; they simply do not see the line you see. A calm, prepared sentence that prices the request lets them decide, and decisive clients usually respect the clarity.
Bringing it together
A revision policy is not about saying no. It is about making "done" a shared idea instead of a moving target. Define the round, cap the count, separate refinement from new requests, and write all of it into the proposal before you start. Then the awkward end-of-project conversation never has to happen, because the terms were settled while everyone was still optimistic.
The same clarity helps once money is involved. When your revision terms live in the same place as your contract, your deliverables, and your invoices, a client can see exactly what was agreed and what falls outside it, which is the quiet idea behind a client portal like Delivvo. Set the boundary once, in writing, and you spend the rest of the project doing the work you were actually hired to do.
