The third round of changes on a fixed-price project is where most freelancers realize they should have said something two rounds ago.
Revision requests aren't the problem. The problem is that by the time a revision request becomes a pattern, the terms for handling it were never set.
Set the Terms Before the Work Starts
The revision policy belongs in the contract or project agreement, not in a message after the client has already asked for the fourth round of changes. A standard clause covers three things: how many rounds of revisions are included, what counts as a revision versus a new request, and what the rate is for work outside that scope.
One to two rounds is standard for most freelance work. More than that on a fixed-price project is usually a sign that either the brief was unclear or the client's expectations weren't properly set — both of which are easier to prevent upfront than to manage after the fact.
The Distinction That Matters
A revision is a change to something that was delivered but didn't meet the agreed brief. A new request is a change to the brief itself — a different direction, a new requirement, something that wasn't part of the original scope.
Clients often don't distinguish between the two, not out of bad faith but because they don't think in project management terms. The freelancer's job is to notice the difference and name it clearly: "This change goes beyond the original scope — happy to do it, and I'll send a revised quote for the additional work." Said once, calmly, this is usually enough. Most clients operating in good faith will accept it without friction.
How to Respond — and When to Push Back
For requests within scope: acknowledge, confirm what needs to change, give a realistic timeline, and deliver. No negotiation needed, no commentary on whether the change is an improvement.
For requests that extend scope: acknowledge the request, note that it's outside the original brief, and provide a clear path forward — a revised quote for the additional work, or an explanation of what would need to be removed from the current scope to accommodate the new request without extra cost. This conversation is uncomfortable the first time. After that, it becomes routine.
When revision requests become a pattern — each one seemingly reasonable but collectively reshaping the entire deliverable — stop and reset. Summarize what's been delivered against the original brief, note that the requests have moved beyond that scope, and have a direct conversation about how to proceed. Avoiding this conversation because it feels confrontational is how fixed-price projects become unprofitable halfway through.
What Good Revision Terms Actually Prevent
Freelancers who rarely have revision conflicts aren't the ones who never get revision requests. They're the ones who defined the terms clearly enough at the start that most requests either fit within scope or get handled as straightforward additional work — without the friction that comes from trying to establish rules after both sides already have a position.
The contract clause takes five minutes to add. The conversation it prevents can take hours and cost the working relationship entirely.
Related Guides
Online Jobs in the Philippines
Freelancing in the Philippines
Comments
Post a Comment