Key Points in This Guide
- 1How unlimited revision clauses are worded and how to spot them
- 2Why "until client satisfaction" is the most dangerous phrase in freelancing
- 3How to define a revision vs a new deliverable
- 4Setting revision rounds: what is reasonable by project type
- 5Change order mechanisms that protect your time
- 6Template revision limit language you can use
"Unlimited revisions until satisfied" sounds like good customer service. In a freelance contract, it is a trap. Without clear revision limits and a change order mechanism, a single client can demand months of additional work at no extra charge, invoking the unlimited revisions clause every time. This guide explains how to identify unlimited revision risk, how to set reasonable limits, and how to handle scope creep when it happens.
Revision Limits by Project Type: Industry Standards
The number of revision rounds you should include depends heavily on the type of project. Creative projects with high subjectivity (branding, video) warrant slightly more rounds than technical projects with objective acceptance criteria. These are the industry standards that most professional freelancers use:
| Project Type | Standard Revision Rounds | What Counts as a Revision | What Triggers a Change Order |
|---|---|---|---|
| Logo / branding | 2–3 rounds | Adjustments to presented concepts | New direction, new concept, color scheme change |
| Website design | 2 rounds per page/section | Feedback on presented mockups | New pages, new features, platform change |
| Copywriting | 2 rounds | Edits to submitted draft | Complete rewrite, new angle, new audience |
| Video editing | 2 rounds | Cuts, timing, music adjustments | New footage, new script, format change |
| Web development | 1 round per milestone | Bug fixes on delivered functionality | New features, scope additions |
| Photography editing | 1 round | Color/crop adjustments on delivered set | Re-shoot, new locations, new subjects |
| Illustration | 2 rounds | Adjustments to approved sketch or color | New composition, new subject matter |
How to Define "Revision" in Your Contract
The word "revision" is the problem. Clients interpret it to mean "any change I want." You need to define it narrowly and specifically in the contract. A revision should be defined as: consolidated feedback submitted in a single document or session, requesting modifications to the existing approved direction.
A "new direction" — changing the concept, target audience, style, or scope — is not a revision. It is a new deliverable that requires a change order. Put this distinction explicitly in the contract: "A 'revision' consists of adjustments to the approved direction submitted in a single consolidated feedback document. Changes to the approved direction, scope, or deliverable specifications constitute a change in scope and require a written change order."
Also define how feedback must be submitted. "Revisions must be submitted in a single written document within 5 business days of delivery. Feedback submitted in multiple installments over multiple sessions shall count as separate revision rounds." This prevents the drip-drip pattern where clients send three emails of "one more thing" spread over two weeks.
💬 Script: Responding when a client asks for a "quick" change beyond the revision limit
"We've completed the two revision rounds included in our agreement (your feedback on [date] and the second round on [date]). Additional changes are billed at my standard rate of $[rate]/hour. I can get started on this right away — please approve the attached change order for $[estimated cost] and I'll turn it around within [timeframe]. If this is urgent and you need it today, I can also do it now and invoice you at the end of the month at the same rate. Just reply with 'approved' and I'll start immediately."
The "Until Satisfied" Trap — and How to Escape It
"Until client satisfaction" is the most dangerous phrase in any freelance contract. It makes your payment conditional on a subjective standard that the client — not you, not a court — controls. A difficult client can always claim dissatisfaction, even on objectively excellent work.
Replace "until client satisfaction" with objective acceptance criteria tied to the brief. For a website: "Client shall provide written acceptance within 5 business days of delivery, or provide specific written feedback identifying how the delivered work deviates from the approved scope in Exhibit A. Failure to provide written feedback within 5 business days shall constitute acceptance."
The deemed-acceptance language is critical. Without it, a client can simply go silent and neither accept nor reject your work indefinitely, blocking payment. A 5-business-day deemed acceptance clause is widely accepted in professional contracts and courts enforce it consistently.
💡 Add this to your payment terms immediately
DEEMED ACCEPTANCE. Client shall review each deliverable and provide written acceptance or specific written feedback within five (5) business days of delivery. If Client does not provide written feedback within the review period, the deliverable shall be deemed accepted and the corresponding milestone payment shall become due immediately. This single clause eliminates most payment delays caused by client non-response.
Have a contract to review?
Upload your contract now and get an AI risk analysis in under 90 seconds.