Handle freelance revisions by defining them before the project starts: a fixed number of rounds, a clear description of what counts as a revision, a feedback deadline, and a price for anything beyond that. Projects drag when revisions are open-ended, feedback arrives in scattered pieces, and nobody has agreed what “done” means.
This article gives you the structure, sample wording for proposals and emails, and a way to respond when a client pushes past the limits. None of it requires being rigid. It requires being clear early, so you do not have to be firm late.
Why revisions drag on
Endless revisions rarely come from bad intentions. They come from missing structure:
- No defined round count. If the proposal says “revisions as needed,” the client reasonably assumes there is no limit.
- Vague feedback. “Make it pop” or “something feels off” can be reworked forever because there is no way to tell when it is fixed.
- Too many reviewers. Each stakeholder sends separate, sometimes contradicting notes.
- Moving goalposts. The brief changes midway and the “revisions” are really new work.
- No feedback deadline. Three weeks of silence, then a new batch of changes, and the schedule slips.
Most of these are scope and process problems, which structure fixes more reliably than patience. The scope side is covered in setting a project scope that does not drift.
Define a revision in writing
Decide what a round means for your kind of work. A typical definition: a round is one consolidated set of feedback from the client on a delivered draft, followed by one updated version from you. “Consolidated” stops feedback from arriving in ten emails, each counted as a new round or demanding an instant reply. Published freelancer guidance commonly suggests one or two included rounds, but defining the term matters more than the number.
Then separate revisions from other changes:
| Type | Example | How to treat it |
|---|---|---|
| Revision | Adjusting wording, color, or layout within an approved direction | Included, up to the stated rounds |
| Rework | Replacing a concept the client approved earlier | Billable as additional work |
| New scope | Adding a page, deliverable, or feature not in the proposal | Quote separately |
| Correction | Fixing your own mistake against the brief | Free, and not counted as a round |
The last row shows fairness and makes clients more comfortable with the limits.
Sample proposal language
“This project includes two rounds of revisions. A round is one consolidated set of written feedback from [client name] on the delivered draft. Feedback received in several messages will be combined into one round. Additional rounds, or changes that depart from the approved brief, are billed at [rate] per hour or quoted as a separate fixed fee before work begins.”
And on timing: “Feedback is due within five business days of each delivery. If feedback is not received within ten business days, the project may be paused and rescheduled based on my availability.”
These are plain and easy to point to later, but whether such terms are enforceable depends on your contract and local law, so have a qualified professional review your standard agreement on larger projects. For everything else a proposal needs, see what a freelance proposal should include.
Build revisions into the schedule and price
Revisions are real work, so the quote should show it. If production takes 15 hours and you expect two rounds, estimate hours for those rounds up front. Your own time tracking will tell you what share of production time a round usually takes in your field; there is no standard figure. If a client wants unlimited revisions, price the risk, or propose a retainer where ongoing changes are part of the arrangement. A hybrid works too: include two rounds in the base fee and charge an hourly rate beyond that. How to price freelance work without undercharging covers building that buffer.
Make feedback easier to act on
Better feedback shortens projects. When you deliver a draft, give the client a frame:
- Say what kind of feedback you need now. “At this stage I need your view on direction and structure; wording comes next round.”
- Ask for a single owner. “Please send consolidated feedback from your team in one message.”
- Ask for specifics. “If something feels off, tell me what you expected or share an example.”
- Set a date. “Please send feedback by Thursday so we stay on track for the launch on the 20th.”
Even three questions (what works, what does not, what is missing) can replace vague comments with something actionable.
Conflicting feedback
When two reviewers disagree, do not choose a side. Send both comments back: “I received two directions on the headline. Could you confirm which to use? I will implement it in this round.” The decision goes back where it belongs.
When the limit is reached
Eventually a client will ask for a change after the last round. Treat it as a normal business step. “Thanks for the notes. We have completed the two rounds included in the proposal. I am happy to make these changes. From the list I estimate about three hours, or $X. If you would like to go ahead, I will start once I have your approval.”
The tone is helpful and specific, with no apology, and it offers a path forward. You may choose to absorb a small change as goodwill; if so, say it is one-off: “I have made this small change at no charge. Further changes follow the process in the proposal.” If a client keeps pushing past limits, the issue is bigger than revisions; see setting better boundaries with clients.
Close the project cleanly
A defined ending prevents “just one more thing” requests.
- Send a final delivery message listing every deliverable and stating the project is complete once approved
- Ask for written approval, even a one-line “Approved, thanks”
- Tie final payment to delivery or approval with a date, and consider an acceptance window for silent clients, for example “If I do not hear back within seven days, the deliverables are considered accepted”
- Offer a short support window for corrections to your own errors if it makes sense
- Offer a follow-up project or retainer for later changes instead of leaving them open
Keep a copy of the approved version and the approval message. They make any later disagreement easier to settle.
A short checklist before each project
- The number of rounds is written into the proposal
- “Revision” is defined, along with what counts as new scope
- There is a feedback deadline and a plan for silence
- One named person consolidates feedback
- The price includes time for the rounds you expect
- There is a defined approval step at the end
If any answer is no, fix it before work starts. Adding structure at the proposal stage is easier than adding it after the first conflict.
Where this comes from
This article is based on commonly published freelancer guidance on revision policies, which recommends limiting included rounds, defining a round as one consolidated set of feedback, separating revisions from new requests, and pricing extra rounds in advance. It also applies general project-management practice. No regulator sets a standard here. Sample wording is illustrative and is not legal drafting. Contract rules vary by place, so have a qualified professional review your terms.
General information, not legal, tax, or financial advice.