"Unlimited revisions" is the most expensive sentence a freelancer can put in a contract. The second most expensive is nothing at all, because no revision policy means the same thing, just implied.
This post gives you a complete revision policy in two versions (formal for the contract, friendly for the proposal), then breaks down the six revision disasters each line exists to prevent. Take the clause, adapt the numbers, ship it with your next quote.
The Formal Clause (Paste Into Your Contract)
Revisions.
- Each deliverable includes up to two (2) revision rounds at no additional cost.
- A "revision round" is one consolidated set of written feedback on a delivered item, provided within five (5) business days of delivery. Feedback from all stakeholders must be gathered into a single document or thread; feedback submitted separately or after the window closes constitutes a new round.
- Revisions address adjustments to work performed against the agreed brief. Requests introducing new deliverables, features, pages, audiences, or functionality not present in the brief are new work, priced separately via change order regardless of remaining rounds.
- Additional revision rounds beyond those included are billed at $[rate]/hour, estimated in writing and approved by Client before work begins.
- If no feedback is received within ten (10) business days of a delivery, the deliverable is deemed accepted, and the project proceeds to the next milestone.
- Revision rounds apply per deliverable and do not transfer between deliverables or phases.
Six numbered lines. Each one exists because a specific, common disaster happens without it. We will walk through all six, but first the version for people who are not lawyers.
The Friendly Version (For Proposals and Kickoff Emails)
Contract language protects you legally; a plain-English version protects the relationship. Put this one in the proposal or the kickoff email:
How feedback works on this project
Every delivery includes two rounds of revisions, and I want you to use them well. Here's the rhythm:
- After each delivery, you'll have 5 business days to collect feedback from everyone on your side into one list. One list = one round, so it pays to loop in every voice early.
- I'll turn each round around within [X] days.
- "Make the header darker" is a revision. "Let's add a pricing page" is a new item, and I'll quote it separately so it never eats into your included rounds.
- Need a third round? No problem, I'll estimate the hours before starting so there are no surprise line items.
- If I don't hear back within 10 business days, I'll take that delivery as approved and keep the project moving so your deadline stays safe.
Same rules, zero legalese. Clients read this and hear "organized," not "defensive." For how this framing lands in the larger pricing conversation, see why unlimited revisions destroys project math.
The 6 Mistakes the Clause Prevents (Line by Line)
Mistake 1: Never defining what a "round" is
The disaster: you include "two rounds of revisions." The client sends feedback Monday, more Tuesday, a Slack voice note Wednesday, and their cofounder's thoughts Friday. Is that one round or four? You have no answer, so it becomes one round, forever, and round one lasts a month.
The fix is line 2. A round is one consolidated batch, inside a window. The count is objective. Nobody has to argue about it, the calendar does the arguing.
Mistake 2: No consolidation window
The disaster: feedback trickles. Every trickle interrupts your other work, and slow feedback quietly extends the project by weeks while your fee stays fixed. The 39-day payment cycles freelancers already suffer (covered in the late payment problem) get even longer when delivery dates slide.
The fix is the 5-day window in line 2. It forces stakeholder alignment onto the client's side of the fence, where it belongs. The people who need to agree on the header color are all employed by the same company; you should not be the person mediating between them one email at a time.
Mistake 3: Treating new work as a revision
The disaster: round two arrives containing "also, we'd like a blog." A blog is not a revision, it is a new deliverable, but because it arrived inside a feedback document, it slides into the round. You are now building unpriced features inside a fixed fee.
The fix is line 3, the most valuable sentence in the clause. Revisions adjust delivered work; new scope gets a change order. When the blog request lands, your reply starts with "great idea, that's a new item, here's the quote," and the clause you both signed is what says so, not your mood that day. The full defense against this pattern lives in scope creep prevention strategies.
Mistake 4: No price for extra rounds
The disaster: the two free rounds end. The client wants a third. With no pre-agreed price, you either absorb it (unpaid work) or negotiate from scratch mid-project (adversarial, at the worst possible moment, with delivery hostage to the outcome).
The fix is line 4. Round three had a price from the day the contract was signed, back when everyone liked each other. Enforcing it is not a confrontation, it is administration: "sure, third round, that's about 4 hours, so $340. Green light?"
Mistake 5: No acceptance deadline
The disaster: you deliver, the client goes quiet. Three weeks later they resurface with feedback, but you have rotated onto other projects, the context is cold, and your schedule was built assuming this milestone was done. Silence has become an unpaid project extension.
The fix is line 5. Silence has a meaning now: after 10 business days, the delivery is accepted and the train keeps moving. In practice you will rarely enforce it coldly; its real function is that clients who know the deadline exists stop going quiet.
Mistake 6: Rounds that pool across the whole project
The disaster: the contract says "four revision rounds" with no per-deliverable scoping. The client spends all four on the logo, then arrives at the website phase with zero rounds left and every expectation of revising anyway. You will not hold that line, and both of you know it.
The fix is line 6. Two rounds per deliverable resets the meter at each phase. Budgets stay small, local, and enforceable, instead of one big pool that evaporates early.
Introducing the Policy Mid-Project
If you are reading this halfway through a chaotic project, do not try to apply the clause retroactively. Pick the next natural checkpoint, a milestone delivery works best, and send this:
Quick process note before the next phase: to keep the remaining feedback rounds efficient, I'll be running them as consolidated batches. After each delivery, gather everyone's comments into one list within 5 business days, and I'll turn the full round around at once. It keeps the timeline honest and makes sure nobody's feedback gets lost in a thread.
Nobody reasonable objects to that paragraph, because it reads as project management, which is exactly what it is. The enforcement teeth stay in the contract for next time.
The Point of All This
A revision policy is not about limiting feedback. Good feedback makes the work better and the two included rounds exist to be used. The policy is about pricing the difference between feedback and drift, so that "just one more pass" has a number attached, and the number was agreed before anyone was tired or annoyed.
Write the clause once. It will out-earn most of your marketing.
Try the free tool
This article walks through the problem; the free tool turns the answer into a copy-pasteable output in 30 seconds. No account, no signup.
→ Use the Revision Policy Generator
Want this across every project?
Briefance saves every brief, scope check, change order, and revision counter against the client and project. Free plan: 3 briefs/month.