How Many Revisions Should a Freelancer Include?

The right number of revisions is a set number you decide before the project starts and write into the agreement — not an open door you leave and hope the client uses gently. For most fixed-price freelance work, a small, named allowance (many freelancers land on two rounds, some on three) plus a clear rule for what happens after is enough. The exact number matters far less than the fact that it is agreed, in writing, before any work begins.

"Revisions" here means rounds of feedback-and-change on delivered work, not the normal back-and-forth of doing the job. The problem this solves is a familiar one: a project that was profitable on paper quietly stops being profitable somewhere around the fifth "just one small tweak." The fix is not to refuse changes. It is to decide, in advance, how many are included and what a further round costs.

What number should you actually pick?

Pick the smallest number that lets a reasonable client get to a result they are happy with — then say what happens after it. For a lot of freelance work that is two rounds: one to react to the first draft, one to polish. Detailed or subjective work (branding, design direction, long-form writing) sometimes warrants three. Beyond that, you are usually not buying quality, you are absorbing indecision.

A few things that should move the number:

• How subjective the work is. Visual and creative work draws more rounds than, say, a technical build with a clear spec. Price the rounds into the number.
• How well-defined the brief is. A vague brief guarantees more revisions. If the brief is fuzzy, tighten the brief rather than padding the revision count.
• How you charge. On a fixed price, revision limits protect your margin. On an hourly or day-rate basis, revisions are simply billed time and the "limit" is really just a heads-up that the meter is running.

Whatever you choose, the number is a decision you make once and reuse, not something you renegotiate from scratch each project.

A revision limit is not a way to do less work. It is a way to keep the price you quoted honest, so "done" means the same thing to both of you.

Write the revision policy into the agreement

State the allowance, and what a further round costs, in the same document the client signs — not in a follow-up email after the friction starts. A limit that lives only in your head is not a limit; it is a disappointment waiting to happen. Here is a clause you can adapt:

Revisions. This project includes two rounds of revisions on delivered work. A "round" is one consolidated set of feedback returned together. Additional rounds, or changes to work already approved, are quoted separately as a change order before that work begins.

Two details in there do quiet, heavy lifting. Defining a round as one consolidated set of feedback stops the drip of ten separate one-line emails each counting as its own pass. And naming what happens after — a change order — means the later conversation is a reminder of an agreed term, not a fresh negotiation you are starting from behind.

This is the up-front side of a calm project, and it belongs with the other things you settle before any billable work: our freelance project kickoff checklist walks through the full set.

What to say when a client asks for "one more round"

Lead with a yes, then point at the agreement — warmly and matter-of-factly. The tone is "here is how we handle this," never "you have broken the rules." Something like:

Happy to take another pass at this. We are past the two rounds included in the original scope, so this next one comes in as a quick change order — same as we agreed at the start. It will lay out what is changing and the cost, and we will get going as soon as you approve it.

Notice what that does. It treats the extra round as normal, billable work rather than a favor or a fight. You are not policing the client; you are following the process you both signed up for. If you want a deeper library of these scripts for the moment a request drifts past scope, our guide on how to tell a client something is out of scope covers the wording.

Turn the extra round into a change order

When a request lands past the revision limit, the move is always the same: write it up as a short change order, get it agreed, then work. A change order names the added work, what it costs, and any effect on the timeline, and the client approves it before you start. It converts "is this included?" into a documented decision — which is exactly what keeps the original price honest. We cover the anatomy of one, with a copy-paste template, in how to write a change order for a freelance client.

The reason to reach for a change order rather than a stern email is that it moves the decision back to where it belongs — before the work — and leaves a record. An electronic signature with a timestamped record is recognized under modern e-signature laws such as the U.S. E-SIGN Act and UETA, and Canada's PIPEDA Part 2. It is a simple electronic signature, the right tool for everyday freelance agreements: it means "what did we agree to?" has a documented answer instead of two competing memories.

How Drift Catch handles this

Drift Catch is built around exactly this seam. You set the deliverables and the revision limit up front, the client e-signs, and the scope locks to what they signed — with a full audit trail. From that point on, a round beyond the agreed number is visibly extra rather than ambiguous, and you turn it into a change order in the same place the original agreement lives. Setting scope and revision limits is part of every plan, including Free; raising and e-signing change orders is part of the Solo plan and up. On the Pro plan, once you connect Stripe, you can also collect payment on a change order inside Drift Catch — and require the extra to be paid before that work opens, so an unpaid "go ahead" simply waits.

You can see that flow in our guide to freelance software that locks scope after signing, and for the wider pattern behind all of this, what scope creep is and how to stop it goes deeper.

The short version

Decide the revision number before the project starts, keep it small, and write it into the agreement along with what a further round costs. Define a round as one consolidated set of feedback so the count cannot be nibbled away. When a request goes past the limit, lead with a yes and turn it into a signed change order. Do that consistently and revisions stop being the thing that quietly eats your margin — they become a normal, priced part of the work.

This is general business information, not legal or financial advice. For revision, scope, and contract language that fits your specific situation, check the rules in your region or have a professional review it.