Risks › Unlimited revisions

Unlimited revisions.
The loop that never ends.

One more tweak. Just a small change. Actually, can we go back to the first version? Vague revision language turns every project into a treadmill.

Draft an agreement that prevents it

Free. No registration. No card. No catch.

What it means

In plain English.

Unlimited revisions is what happens when a contract uses language like "revisions as needed," "until the client is satisfied," or simply doesn't mention revision limits at all. The result: the client can request changes indefinitely, and you have no contractual basis to push back or charge more.

What it looks like

"Can we try a different direction?" after three rounds of feedback. "My business partner had a few notes" after the client approved. "Just a few more tweaks" that add up to a redesign. Each request feels reasonable in isolation.

Why it's so common

Many contracts simply don't address revisions. The word doesn't appear. When there's no definition of what a revision is, or how many are included, the default is: as many as the client wants.

Why it's expensive

Design, writing, video, development — all creative and technical work is revision-intensive. A project quoted at 20 hours can easily run 40 if revisions are open-ended. The rate per effective hour collapses.

Why it's missed

It seems like the polite thing to do. It isn't.

Why missed

Saying "two revisions" feels rigid

It seems like you're telling the client they're limited. In reality, you're protecting both parties from a project that drags indefinitely — which helps neither of you.

Why missed

"Revision" isn't defined

Does a revision mean one comment? A full redirection? A round of feedback on a deliverable? Without a definition, the scope of each revision is unbounded.

Why missed

No change-order mechanism

Even when a revision limit is included, if there's no process for what happens when you hit it, the client just keeps asking and you keep doing.

What can go wrong

The downstream consequences.

Hours multiply, rate collapses

The 10-hour project becomes 25 hours at the same price. Your effective hourly rate drops below what you'd accept if asked directly.

Project never closes

Without a definition of "done," there is no done. The final invoice can't be sent because the project isn't finished — because the client keeps changing things.

Direction reversals

The client approved a direction in round one. In round four they want to go back to it. Unlimited revisions means you can't say "that was already decided."

Resentment builds

Eventually you stop caring about quality. The work suffers. The relationship sours. A clear revision clause protects the relationship, not just the hours.

Red-flag wording

If your contract says any of this, unlimited revisions are already baked in.

These phrases are standard in templated contracts and online generators. They feel collaborative. They're open loops.

Red flag

"revisions as needed"

Needed by whom? For how long? This phrase is a blank check on your time.

Red flag

"until the client is satisfied"

Satisfaction is subjective and indefinitely deferrable. There is no finish line.

Red flag

"reasonable revisions included"

Whose reasonable? No number, no definition of what counts. Effectively unlimited.

Red flag

No mention of revisions at all

Silence on revisions is the same as unlimited. There's nothing to point to when you want to stop.

Red flag

"minor adjustments included"

"Minor" is subjective. The client's minor is your major. Define it in concrete terms instead.

Safer pattern

The clause that writes unlimited revisions out.

Three elements work together: a definition of what a revision is, a count of how many rounds are included, and a change-order process for anything beyond that. All three are short. All three are necessary.

BizDraft includes these by default for any creative or technical project agreement.

The pattern

Define a revision round. "A revision round consists of one consolidated set of feedback submitted by Client in a single communication. Feedback submitted in multiple messages or across multiple days constitutes separate rounds."
Cap the rounds. "Two rounds of revisions are included per deliverable. Each round must be submitted within five business days of delivery."
Define the change-order trigger. "Additional revision rounds beyond the included two are available at [rate] per round, by written change order only."
Treat direction reversals separately. "Changes that reverse a previously approved direction constitute new work, not revisions, and are subject to a separate change order."

Most affected