A client sends your finished logo, article or website page back with one line: "Can you make it pop more?" You reread it three times and still have no idea what to change. Nothing wrecks a freelance project's profit like vague feedback, because every guess costs you hours you won't be paid for.
Revisions are a normal part of the work. The goal isn't to avoid them. It's to make them specific, limited and fair to both sides. This guide shows how to set that up before you start, how to read feedback that sounds unclear, and what to do when requests keep coming.
Why revisions go wrong
Most revision trouble comes from three causes, and only one of them is the client being difficult.
- No agreed definition of "done". If the brief never said who the audience is, how long the piece should be or what success looks like, the client will judge it by taste.
- Feedback arrives in pieces. One comment on Monday, another on Wednesday, a third from the client's boss on Friday. Each round feels small, but together they become a rewrite.
- You never stated a limit. Clients can't respect a boundary they haven't heard. Many assume revisions are unlimited because nobody said otherwise.
Fixing these three things solves most problems before they begin.
Set revision terms before you start
Put revision terms in your proposal, contract or the first message of the project. If you already use a simple contract, add these lines to it. Our guide on freelance client onboarding covers where this fits in the first week.
- Number of rounds. For example: "The price includes two rounds of revisions."
- What counts as a revision. Fixing errors, adjusting wording or colours, and tightening within the agreed brief are revisions. Changing the topic, audience, format or direction is a new scope.
- How feedback is delivered. "One consolidated list per round, from one person." This single line prevents the Friday-boss problem.
- Turnaround. State how quickly you return a revision, and how quickly the client must send feedback before the project is paused or counted as accepted.
- Extra rounds. State what happens after the included rounds: an hourly rate or a fixed fee per extra round.
Say it politely and plainly. Something like: "To keep the project on schedule, I include two revision rounds. Feedback works best as one combined list. Additional rounds are charged at my hourly rate, and I'll confirm the cost before starting."
If you quote by the hour instead, the issue changes shape, since extra edits are simply billed time. Our post on hourly or fixed-price quoting helps you decide which suits the job.
Reduce revisions before the first draft
The cheapest revision is the one you prevent. Three habits help.
Ask for examples
Ask the client for two or three pieces of work they like and one they dislike, plus a sentence on why. Taste is hard to describe but easy to recognise.
Send a rough version first
For anything that takes more than a few hours, share an outline, a sketch, a set of headlines or a sample section before the full work. A client who approves a direction at 10% effort can't easily say at 100% that it's the wrong direction. Treat this approval as a checkpoint and write it down, even in a one-line email.
Confirm the brief back to them
Before starting, send a short summary: audience, purpose, length or format, tone, deadline and deliverables. Ask them to reply "confirmed" or correct it. This takes ten minutes and gives you something to point to later.
How to turn vague feedback into usable tasks
"Make it better", "It doesn't feel right" and "Can it be more professional?" are not instructions, but they do contain information. Your job is to translate them without arguing.
- Ask what they were expecting. "Which part felt off, the opening, the tone or the structure?"
- Offer choices. People find it easier to pick than to describe. "Do you want it warmer and more casual, or more formal and concise?"
- Ask for one example. "Is there a piece whose tone you'd like this to match?"
- Repeat the plan back. "So I'll shorten the intro, replace the technical terms with plain words, and keep the rest. Is that right?"
If the client replies with new direction rather than clarification, that's the moment to separate a revision from a change of scope. Do it calmly, as below.
Revision or new scope? A quick test
| Request | Usually a revision | Usually new scope |
|---|---|---|
| Fix a factual or spelling error you made | Yes, and it shouldn't count as a round | No |
| Change tone, wording or colours within the agreed brief | Yes | No |
| Add a new section, page or deliverable not in the brief | No | Yes |
| Change the target audience after delivery | No | Yes |
| Restart from scratch because the client changed their mind | No | Yes |
| Fix a mistake the client's own information caused | Depends on your terms | Often yes |
Your own errors are on you. Fix them for free and don't count them against the client's rounds. That small fairness makes it easier to hold the line on everything else. For the deeper version of this boundary, read our guide on stopping unpaid extra work from clients, and pair it with the checks in checking AI-assisted work for errors if you use AI tools, so avoidable mistakes don't eat rounds.
A worked example (hypothetical)
Say Amaka, a freelance writer in Enugu, agrees to write a 1,200-word blog post for a foreign client for $90. She estimates five hours of work, and her terms include two revision rounds.
- Round 1: The client says the post "feels too stiff". Amaka asks which section and whether there's a sample tone. The client shares a link to a post they like. She loosens the intro and conclusion. Time: 45 minutes.
- Round 2: The client's manager now wants a section on a different product. This is new scope, not tone. Amaka replies: "Happy to add that. It's outside the original brief, so it would be an extra 400 words at $30. Shall I go ahead?" The client agrees.
- Result: Without the boundary she'd have spent roughly two more unpaid hours. With it, the post paid $120 for about six and a half hours.
These numbers are invented to show the method, not a typical rate or a promise of income. Run your own figures through our guide to finding your real hourly rate.
Running a revision round well
- Collect all feedback first. Don't start editing after the first comment. Reply: "Thanks, I'll start once I have your full list so I can handle everything in one pass."
- Number the changes. Reply with a list: "1. Shorten intro. 2. Replace stats in paragraph 4. 3. Change the button colour." The client can correct you in a minute.
- Keep versions. Save files as v1, v2, v3 so you can show what changed and recover earlier choices if the client reverses a decision.
- Send a change summary. A short note on what you did, and what you didn't do and why, prevents "you missed my comment" arguments.
- Mind your power and data. If a revision call or file upload is time-sensitive, plan around outages. Send the client your expected delivery time with a small buffer rather than promising "within the hour".
When a client keeps asking for more
Some clients use revisions as a way to get extra work. Others are simply unsure what they want. Treat both the same at first, then adjust.
- Remind, don't accuse. "We've completed the two included rounds. I'm glad to continue; extra rounds are billed as outlined in our agreement."
- Offer a path. Give a price for one more round, or suggest a short call to align on direction.
- Pause delivery of final files if needed. On platforms with escrow or milestones, keep releases tied to the agreed deliverable. See our guide on ending a project cleanly for how to close without burning the relationship.
- Learn the pattern. If it repeats with the same kind of client, raise your price or reduce included rounds next time.
If the client simply disappears after the final draft, your terms should say that work is treated as accepted after a stated period of silence. Check how this fits the dispute rules on the platform you use, since those are set by the platform itself.
Common mistakes
- Saying "unlimited revisions" to win the job. It attracts the clients who use them most.
- Getting defensive. Feedback on the work isn't feedback on you. Ask questions first.
- Starting before the brief is confirmed. A misunderstanding found after delivery costs far more than one found in a message.
- Agreeing to changes in chat and forgetting them. Write every agreed change into one message so it can be found later.
- Charging for your own errors. Fix them quickly and free. It protects your reputation and reviews.
Frequently asked questions
How many revision rounds should I include?
Two is a common starting point for small projects, but there's no rule. Use fewer for low-priced work and more for larger fixed-price projects. What matters is that the number is written down and agreed.
Should I give a discount when a client is unhappy?
Not as a first move. First find out what specifically disappointed them. If you missed the agreed brief, fixing it is the remedy. If they changed their mind, that's a new scope. Partial refunds are a business decision, and on platforms with dispute processes you should follow the platform's own rules.
What if the client is on a different time zone and feedback is slow?
State a feedback window in your terms, and build it into your delivery dates. Our post on time zones and foreign clients has scheduling ideas that reduce waiting.
Can I add revision terms after the project has started?
You can, but it's harder. Frame it as a clarification for the next phase or the next project, and apply it firmly from then on.
Your next step
Open your current proposal or contract template today and add five lines: number of rounds, what counts as a revision, one consolidated feedback list, turnaround times and the price of extra rounds. Use it on your very next quote.
Results from any side hustle or online work vary widely, and nothing here is a promise of income. Be wary of anyone who asks you to pay upfront to start earning.