Every freelancer knows the project that never ends. The design is approved, then un-approved. The article is final, then rewritten three more times. The cause is almost always the same: the contract said revisions included without saying how many, or what a revision is. A revision limit is not about being difficult. It is about defining done, so both sides know when the work is finished.

The standard limit is two rounds of revisions on a defined deliverable. Two rounds are enough for genuine improvements and short enough to keep the project moving. One round feels stingy to clients; three rounds invite endless tinkering. State the number in the proposal and the contract, and define a round: one consolidated set of feedback, delivered in writing, within a stated number of business days. Feedback dribbled in one comment at a time over three weeks is not one round. It is three.

The harder part is defining what counts as a revision and what counts as new work. A revision corrects or refines work that matches the agreed brief. New work changes the brief: a different audience, a different format, a different concept, or a feature that was never discussed. Write this distinction into your terms with an example, because clients do not see the difference until it is spelled out. When a request crosses the line, the reply is calm and specific: happy to do it, here is what it costs, here is how long it takes.

Enforcement is mostly about timing. Raise the limit at the start, not in round four. When the client sends the first revision, reply with what round this is and how many remain. When the limit is reached, send a short message: we have used the two included rounds, and further changes are billed at your hourly rate, with an estimate before you start. Clients rarely argue, because the rule was agreed before the work began and the accounting is transparent.

Some clients genuinely need more revisions, and that is fine: the policy is not a punishment, it is a price list. Offer a revision retainer or an hourly rate for extra rounds, and let the client choose. The clients who value endless changes will pay for them, and the clients who do not will suddenly become much better at consolidating their feedback. Either way, you stop working for free.

Track revisions like you track hours. At the end of each project, note how many rounds it actually took and which clients burned through the limit fastest. That data tells you where your briefs are weak, which clients need a higher price, and whether your limit should move from two rounds to three for a specific service. A revision policy is a business tool, not a wall: it exists so the work ends well instead of fading into resentment.

Revision limits differ by service, and your template should reflect that. Writing usually needs two rounds: one for structure and one for polish. Design often needs three, because visual feedback is harder to consolidate and clients react to what they see. Video editing usually needs two, tied to a locked script, because changing the script after the edit is new work, not a revision. Set the number per service in your price list, so the client sees the limit as part of the package rather than a rule invented mid-project. The policy also protects the client, because a defined endpoint forces decisions instead of letting a project drift through endless small changes that nobody tracks.