Revisions don’t mean you did something wrong. They mean the client is seeing your work with fresh eyes and has feedback. The problem isn’t revisions themselves, it’s unlimited revisions with no clear endpoint. When revisions aren’t bounded, they become a profit killer. The solution is setting clear expectations upfront so revisions feel like a natural part of the process, not scope creep.
Define Revision Limits in Your Proposal
Every proposal should state exactly how many revision rounds are included. Don’t bury it in terms and conditions. Put it right there: “Two rounds of revisions included.”
Be clear what “one round” means. It’s not one change. It’s one complete feedback cycle where the client gives you all their comments, you implement them all, and you send back the revised work.
This matters because it prevents death by a thousand small requests. The client can’t ask for a tweak, get it, ask for another tweak, get it, forever. Instead, they gather all their feedback and send it together.
Some freelancers say “unlimited revisions” to seem generous. Don’t do this. You’ll end up undercharging for your time. The client will feel like revisions never end because they literally don’t. After two rounds, additional revisions should cost extra. That’s standard practice.
Set Expectations During the Kickoff
Repeat the revision policy during your initial conversation. “I include two full rounds of revisions in this price. After that, additional changes will be billed at [rate]. That way we both know what to expect.”
Most clients have no idea what’s normal. They’ve never hired a freelancer before. When you explain revision policy, they accept it because you sound professional and it makes sense.
Also explain the timeline for revisions. “I’ll send the first draft on [date]. You have five days to send feedback. I’ll implement everything and send the revised version on [date]. You have three days to review. I’ll make final changes and we’re done.”
This structure prevents the client from sitting on work for weeks, making you wait, then sending vague feedback. Everyone knows the pace.
Separate Feedback Into Actionable Requests
When a client sends revision feedback, some of it will be clear and some will be vague. Your job is to clarify before you start working.
If they say “Make the blue darker,” you know what to do. If they say “It doesn’t feel right,” ask questions. What doesn’t feel right? The color, the layout, the tone, the structure?
Send a quick email: “I got your feedback. Before I start revisions, I want to make sure I understand. When you said X, did you mean Y or Z?” This prevents wasted work from misunderstanding.
Document what you’re going to change. Send back an email listing the feedback items you received and what you’ll do about each one. If they asked for something outside scope, note that. Then when you deliver the revision, they can’t claim they asked for something you didn’t do.
Bundle Small Changes Together
Clients love asking for tiny tweaks. “Can you move the button down two pixels?” “Change this word to that word?” Done individually, these requests waste your time.
Tell the client, “I’ll gather all the small tweaks and make them together in one batch.” Spend an hour on Friday implementing ten changes at once instead of context-switching all week. This batching increases your hourly rate on revisions. It also prevents endless back-and-forth. The client sees all their requests addressed together instead of one at a time.
Know When It’s a Change Order, Not a Revision
The line between revision and change order is important. A revision is feedback on what you delivered. A change order is a new request or scope change.
Client asks to change the color scheme: revision. Client asks to add an entire new section: change order. Client asks for better wording: revision. Client asks to expand the project to include social media templates: change order.
When something is clearly out of scope, don’t do it for free. Send a quick change order proposal. “This would add about five hours of work. I can do it for $X or we can keep the original scope.”
Most clients will either decide to go ahead and pay, or they’ll decide they didn’t need it anyway. Either way, you’re protected.
Use Tools to Track Revisions
Waco3 works for proposals. Also use tools that let clients comment directly on designs or drafts. Google Docs, Figma, or feedback tools let clients mark up your work instead of explaining in words. This reduces misunderstandings because they point directly at what they mean. You also get a record of what they asked for, which protects you if they later claim they asked for something they didn’t.
Be Kind But Firm
Revisions are normal and clients deserve a smooth process. But be firm when they’re trying to add scope beyond your agreement.
Say it kindly: “I want to make sure you’re happy with this, and I can definitely add that. That’s a bit outside what we agreed, so I’d want to cover it with a change order so we’re both protected.”
Clients respect boundaries. They might push once, but once you’ve said something costs extra, they usually accept it.
Clear revision limits at the start prevent resentment at the end and keep freelance projects profitable.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
