How Many Revisions Should a Freelance Contract Include?

There is no universal number of revision rounds that every freelance project should include.

Two rounds may be sensible for one job and completely unrealistic for another.

The more important question is:

Does the contract make clear what counts as a revision, how many are included, and what happens after that?

Why revision limits matter

A fixed project fee is usually based on an expected amount of work.

If the client can request changes indefinitely while the fee stays fixed, the effective value of the project can fall dramatically.

Revision terms help distinguish:

• correcting the agreed deliverable;
• refining it within the original brief;
• changing direction;
• requesting entirely new work.

What is a revision round?

A revision round usually means one consolidated set of requested changes followed by an updated version.

But the contract should ideally make that clear.

Otherwise, “two rounds” could become:

• ten separate emails;
• changes from five stakeholders;
• new requests arriving after each update.

Ask whether feedback must be consolidated and who is authorised to give it.

Are two revisions enough?

Sometimes.

For example, a small design project might reasonably include:

• initial concept;
• first revision round;
• second revision round;
• final delivery.

A complex software project, long report or branding exercise may need a different structure.

The number should reflect the work.

Watch for unlimited revisions

Phrases such as:

revisions as requested by the Client

or:

revisions until the Client is fully satisfied

can leave the workload open-ended.

That does not automatically mean the clause is unreasonable, but the commercial commitment becomes harder to price.

See Freelance Unlimited Revisions Clauses: What Should You Look Out For? for the broader issue.

What happens after the included rounds?

A useful contract may state that additional revisions are:

• charged hourly;
• quoted separately;
• treated as a change request;
• subject to a new timeline.

Without that mechanism, both sides may disagree about whether extra changes are included.

Define what is not a revision

A client changing the colour of an agreed element is different from deciding to add a new feature.

Examples that may be better treated as new scope include:

• extra pages;
• new formats;
• additional languages;
• a new audience;
• new functionality;
• a completely different concept.

The boundary between revision and scope change should be understandable.

Client delays matter too

Revision clauses should also work with deadlines.

If the client takes three weeks to provide feedback, does the freelancer still have to meet the original final date?

Consider whether the agreement addresses:

• feedback deadlines;
• schedule changes;
• availability after long delays.

Questions to ask before signing

Check:

• How many rounds are included?
• What counts as one round?
• Must feedback be consolidated?
• Who can request changes?
• What happens after the limit?
• Are new deliverables treated separately?
• Do client delays move the schedule?

So how many revisions should you include?

Enough to make the project workable, but not so many that the scope becomes indefinite.

The right number depends on the service, fee, process and client.

Clarity matters more than picking a magic number.

PactRivet can highlight revision and acceptance wording in your contract so you can see whether the project has a clear endpoint or an open-ended change obligation.

Related guide

For a broader look at this area, see Freelance Unlimited Revisions Clauses: What Should You Look Out For?.

PactRivet provides general information and questions to consider. It is not legal advice.