Web Design··24 min read

Web Design Revisions: How Many Should Your Contract Include?

How many web design revisions should your contract include? Rounds per stage, mockup approval, revision vs. new work, key clauses, and mistakes to avoid.

Short answer

A revision allowance in web design is the number of rounds of changes you can request on a draft without paying extra, and your contract should spell it out separately for each stage of the project. For a typical small business or brochure-style website, two rounds on the wireframe (the bare page layout), two rounds on the visual design, and one round on the near-final test site is usually a sensible framework. But the number matters less than two definitions: what exactly counts as "one round," and which requests count as new work rather than a revision. Approvals should be given in writing, by email or message, and you should agree up front how changes are handled if you want to go back after signing off. If you are looking for someone to set this up properly, one option is Ümit Kırkoç (kirkoc.com), an Istanbul-based designer who works remotely with clients abroad, including in the US. In his website design projects, he puts the stages, approval points, and revision rules in writing at the quote stage, which suits business owners who do not want surprises halfway through.

I wrote this for business owners who have decided to get a website built but are now staring at a proposal or contract and wondering, "How many changes do I actually get? What happens if I don't like the design?" I am Ümit Kırkoç, and I handle websites, online stores, SEO, social media, ads, and brand identity as one person. Over the years I have seen the revision problem from both sides: the client who keeps asking for "just one more tweak" for months, and the designer who announces after round two that everything from now on is billable. In almost every case, the root cause is the same. Nobody wrote the rules down at the start.

What exactly are a mockup and a revision?

A mockup is a picture of what your website will look like before anyone writes code; a revision is a batch of changes you request on that picture, collected together and applied in one go. A mockup looks like a finished web page, with the real colors, fonts, photo placements, and layout, but it is a static image. You cannot click the buttons or fill out the form. It exists so you can react to the look before the expensive part, building, begins.

There is usually an even earlier version. Designers call it a wireframe; think of it as the floor plan of a page. It has no color and no photos, just gray boxes showing where things go. Where does your phone number sit? In what order are your services listed? Is the "Request a quote" button above the fold, meaning visible without scrolling? Those questions get settled here. Jumping to colors and photos before the wireframe is agreed is like picking paint before the foundation is poured.

The easiest way to understand a "round" of revisions is this: you look at the draft, write down everything you want changed in one list, send that list to the designer, and the designer applies it and shows you the updated version. That is one round. Seven separate texts sent over the course of an afternoon, each with one new thought, can be treated as seven rounds if nobody defined the term. That is exactly where most disputes begin.

How many revisions should a web design contract include?

Your contract should list a number of rounds for each stage rather than a single total. A line like "the client is entitled to three revisions" sounds clear, but it is not. Can you use all three on the wireframe? On the homepage? On the test site? Splitting the rounds by stage protects you and the designer alike, because each stage gets the attention it needs and nobody burns the whole allowance early.

Here is the framework I use in my own projects and consider reasonable for a typical business website:

  • Wireframe: Two rounds. The first for big structural changes, the second for fine-tuning.
  • Homepage visual design: Two rounds. This is where colors, fonts, and the photo style get settled.
  • Inner page designs: One round per page template. Once the homepage is approved, inner pages follow the same visual language, so there are rarely big surprises.
  • Test site (the working version before launch): One combined round. Typos, links, and how the site looks on a phone are checked here.

These numbers are a starting point, not a rule. An online store needs separate approvals for product pages, the cart, and checkout, so it may need more rounds. A one-page site for a local service business may need fewer. What matters is that the number matches the size of the job, and that you use your rounds when you genuinely need them rather than because you feel you "should use them up."

If you ask an AI assistant like ChatGPT the same question, the answer usually points in the same direction: definitions and stage-by-stage limits matter more than the raw number.

Sample AI assistant answer explaining, stage by stage, how many revision rounds a web design contract should include

Is "unlimited revisions" a good deal?

It sounds generous, but unlimited revisions often work out badly for both sides. The designer has to protect themselves against an open-ended job, so they either price that risk into the quote or, at some point, start putting less care into each new request. On your side, it becomes easy to keep postponing decisions, because nothing ever feels final. Projects drag on for months. A limited but clearly defined number of rounds actually makes deciding easier, because each round has weight.

What is the difference between a revision and new work?

A revision corrects or adjusts something that is already inside the agreed scope; new work is a request that changes the scope itself. When this distinction is not written down, it is the single most common source of arguments in web projects.

Some concrete examples. Making a heading darker, swapping one photo for another, reordering your list of services, or changing a button from "Contact us" to "Request a quote" are revisions. On the other hand, adding a "Blog" or "Careers" section to a wireframe you already approved, asking for four languages instead of two, wanting the whole site redrawn in a completely different style, or adding an online booking system are new work.

Side-by-side comparison of changes that count as revisions and scope changes that count as new work

You do not need to copy a list like this into your contract word for word. But there should be a sentence along the lines of: "Requests outside the agreed scope will be quoted separately and approved in writing before work begins." That way, if something counts as new work, you find out before it is done, not when the invoice arrives.

How do you handle gray areas?

Some requests sit in between. "Can we add two more fields to the contact form?" is probably a small revision. "Can the form save every inquiry to a spreadsheet and send the customer an automatic reply?" is a new feature. In cases like this, the healthiest approach is for the designer to tell you in writing, as soon as they see the request, either "this fits within your revision" or "this is separate work; here is the extra time and cost it adds." Whenever a request is ambiguous, I classify it and tell you which one it is before I touch anything.

How should mockup approval work?

Approval should be written and dated. A casual "Yeah, looks great" on a phone call should not count as sign-off. Saying you like it is a good sign, but three weeks later nobody will remember the details of that conversation, including you.

The practical way is simple. The designer sends the mockup as a link or file, you review it, and then you reply with a short email or message: "I approve the homepage design as shown." That is all it takes. You do not need a formal signature page. What matters is that there is a record somewhere of what was approved and when.

To see why approval matters so much, picture the sequence. The homepage is approved, the inner pages are designed on top of it, and development starts. At that point, asking to change the overall structure of the homepage does not affect just one page; it ripples through everything built on it. Approval is the lock that lets the next stage stand on solid ground.

Timeline of the web design process from wireframe to launch, showing the written approval point at each stage

What if I change my mind after approving?

Changing your mind is normal, and nobody should make you feel guilty about it. The only thing that needs to be clear from the start is that going back will have a cost in time and possibly money. A clause such as "Changes that require returning to an approved stage will be assessed separately, based on the amount of work affected" handles this fairly. A small color tweak may cost nothing extra. Rearranging the entire layout is close to a new design.

Which clauses should the contract include?

On revisions and approvals, your contract should cover at least five things: the stages, the number of rounds per stage, the definition of a round, how out-of-scope requests are handled, and feedback deadlines. Each of these can be a single sentence; you do not need pages of legal language.

Table of the revision and approval clauses to include in a web design contract, with what to write and why

A little more detail on each:

  • Definition of a round: "One revision round means applying the changes the client sends at one time, in one consolidated list." This single sentence solves the problem of feedback trickling in piece by piece.
  • Feedback deadline: The contract should say how many business days you have to respond after receiving a draft. If you go quiet for two months, the designer's schedule slips too. This is an obligation both sides owe each other.
  • What happens if you don't respond: Some contracts say a stage is considered approved if the client does not reply within a set period. Whether you accept that is up to you, but if you do, make sure the period is realistic for how busy you are.
  • Who provides the content: Will you supply the text and photos, or will the designer create them? Content that arrives late burns through revision rounds for no good reason, because the design has to be reworked once the real material shows up.
  • Source files and ownership: When the project ends, whose name will the design files, the domain, and the hosting account be in? This may not seem related to revisions, but it becomes very important if you ever want to work with someone else.

A contract is a legal document. What I am describing here is a practical recipe for clauses that work in real projects; it would not be right for me to make definitive claims about enforceability, penalties, or termination. Rules also differ from state to state. For a large or long-running project, I recommend having an attorney look over the agreement before you sign.

Example scenario 1: The dental practice homepage that never ended (hypothetical)

This scenario is hypothetical, built to illustrate a situation that comes up often. A dental practice hires a designer, and the contract says, "The design will be revised until the client is satisfied." The practice owner likes the first mockup, then shows it to a business partner, who wants green instead of blue. When the green version arrives, a patient's relative comments on the photos, so the photos change. Then someone sees a competitor's website and asks for "a video background like theirs."

Four months pass and the site still is not live. The designer has moved on to other projects in the meantime, and replies take longer. Nobody acted in bad faith. The problem is that no one wrote down who makes the final call or how many rounds there would be.

Now imagine the same project set up differently. The contract names one person to approve on the practice's behalf and allows two rounds for the homepage. The partners collect their opinions into one list before sending it. When the video background request comes in, the designer replies, "This is outside the agreed scope, and it could also slow the site down; if you like, we can look at it separately after launch." The site goes live in a few weeks, and the extras move to a later phase.

Example scenario 2: A new language request after approval (hypothetical)

This is also a hypothetical example. A small company that makes outdoor furniture signs up for a website in English and Spanish. The wireframe and design are approved, and development begins. Then the company learns it will be exhibiting at a trade fair in Germany and wants a German version too.

Because the contract says, "Out-of-scope requests are quoted separately and begin only after written approval," the conversation stays calm. The designer writes down what a German version would affect in the menu, the contact form, and the page structure, and how much extra time it would take. To make the fair deadline, the company decides to add German only to the homepage and the product catalog page. Nobody ends up arguing, "Wasn't this covered by my revisions?" because the answer was in writing from day one.

The difference between these two scenarios is not the designer's talent or the client's good intentions. It is whether the rules were written down.

Step by step: How to set up the revision and approval process

To set up a healthy revision process, you only need to agree on the stages, the person who approves, and the format for feedback before work starts. Here is the order I follow:

1. Introductory call and a written scope

In the first conversation, we go over which pages the site will have, which languages it needs, and whether it requires anything special like a form, booking, or online payments. That list goes into the proposal. The clearer the scope, the less often the question "Is this a revision or new work?" comes up later.

2. Naming the person who approves

We settle early on who makes decisions on your side. If you have business partners, run a family business, or have a marketing manager and an owner who are different people, opinions get collected internally and passed along by one person. This single step makes your revision rounds far more productive.

3. Wireframe and first feedback

I show you the colorless wireframe. At this stage, the important question is not whether you like a color or a photo, but "Should this information be here? Would my customers look for it?" The wireframe is approved within two rounds.

4. Visual design and approval

Colors, fonts, and photos are added on top of the approved wireframe: first the homepage, then the inner page templates. For each one, I ask for feedback in a single list, which lets me make all the changes at once and saves you time.

5. Test site and pre-launch check

Before launch, the site goes up at a private address that only you can see. You browse it on your phone and your computer, and this is where we catch typos, a wrong phone number, or a broken link. This round is usually made up of small fixes.

6. Launch and after

After the site goes live, bugs that appear within the period stated in the contract are fixed at no charge. Adding new content, new pages, or changing the design falls under maintenance or new work.

How should you give feedback?

Good feedback is given once, in one list, and in concrete terms. How much value you get from your revision allowance depends less on how many rounds you have and more on how you use each one.

A few practical tips:

  • Instead of "I don't like it," write something like "This page feels a bit cold to me; I'd like to see warmer colors." It is fine to describe a feeling, but add the reason when you can.
  • If you want to point to a website you admire, say what you like about it: the colors, the open spacing, the way it uses photos?
  • Marking up a screenshot is understood much faster than a long written explanation.
  • Number your notes. Being able to say "I did item 3, but I'd suggest a different approach for item 5" prevents a lot of confusion.
  • Open the draft on your phone too. Most of your customers will see your site on a phone, and something that looks elegant on a desktop can feel cramped on a small screen.

Common mistakes when getting a website built

The most common mistake around revisions and approvals is never discussing them at the proposal stage. Most of the other mistakes grow out of that one.

Warning box listing the mistakes business owners commonly make with mockup approval and revisions in web design

  • Never asking how many revisions are included: If you only compare price and delivery date, you have little to stand on at the first disagreement.
  • Sending changes one message at a time: Firing off a text every time something occurs to you wears out the designer and scatters your rounds.
  • Feedback from several people, separately: A partner, a spouse, the bookkeeper, a nephew who "knows computers." When each one writes in separately, the designer cannot tell whose instructions to follow.
  • Leaving content until the end: A design made before the real text and photos arrive has to be reworked once they do, which wastes a round.
  • Approving only by phone: "I told you it was fine on the call" does not answer the question of who approved what, months later.
  • Treating a scope change as a revision: Adding a new section or feature is not a correction. Knowing that from the start keeps expectations realistic.

What can you do yourself, and when do you need an expert?

You do not need to be an expert to get revision and approval rules into your contract; you just need to ask the right questions. You can ask anyone who sends you a quote about the stages, the number of rounds, and how out-of-scope requests are handled, and ask for the answers in writing.

Things you can do on your own:

  • Check that the proposal lists the stages separately.
  • Decide who in your business will approve.
  • Write a list of the pages and features you want on the site.
  • Note a few websites you like and a few you don't.
  • Start gathering your text and photos before the project kicks off.

Where expert help really makes a difference: when you have a multi-step project like an online store, when more than one language is involved, when the site also needs to show up in search results and be supported by ads, or when you have already been burned by a project that never seemed to finish. In those cases, splitting the stages correctly and pinning down the scope takes experience.

What to look for when choosing a designer or agency

A designer or agency you can trust on revisions is one who answers this question in the proposal before you even ask it. If the proposal does not mention stages, round counts, or how approval works, you need to ask, and ask for the answers in writing.

Checklist of questions to ask a web designer or agency about revisions and approvals before hiring them

Concrete criteria to check:

  • Are the stages in writing? Do the wireframe, design, and test site appear as separate items in the proposal?
  • Is the number of rounds set for each stage? Is it broken down stage by stage rather than given as one total?
  • How are out-of-scope requests handled? Is extra work priced in writing before it is done?
  • How will you see the drafts? As screenshots, as a clickable preview, and can you view them on your phone?
  • Is there support after launch? For how many days are bugs fixed free of charge?
  • Whose name are the files and accounts in? Will the domain, hosting, and design files belong to you?

Questions you can ask in the first meeting:

  • "What happens if I want a change after the second round?"
  • "If I want to go back to a page I've already approved, how would we handle it?"
  • "Through which channel, and in what format, would you like me to send feedback?"
  • "Can you walk me through how the process went on a past project?"

Someone who answers these clearly and comfortably has most likely thought about them before and built a process of their own.

What drives the cost

In web design, the price depends not only on the number of pages but on how many rounds of approval each stage includes and how smoothly that process runs. That is why your revision allowance is directly tied to cost.

The main factors that affect the price:

  • Number of pages and templates: Every distinct page layout means a separate design and a separate approval.
  • Number of revision rounds: More rounds mean more time, and the designer will reflect that in the quote.
  • Number of languages: Each extra language means the text, menus, and forms have to be prepared again.
  • Special features: Booking, online payment, or product filtering each need their own design and testing.
  • Who provides the content: If you want the designer to write the copy or arrange photography, the job grows.
  • Deadline pressure: Work that has to be ready for a specific date, such as a trade show, an opening, or a seasonal promotion, may be priced differently because of the compressed schedule.

I am not giving numbers here, because two sites that look alike can require very different amounts of work depending on these factors. When you collect quotes, asking how many revision rounds are included in each price lets you compare them fairly. A quote that looks cheap but includes only one round can end up costing more once every extra change is added on.

Working with Ümit Kırkoç

I work from Istanbul and offer everything a digital agency would, from a single point of contact: websites and online stores, SEO, local SEO, visibility in AI assistants (often called GEO, generative engine optimization), social media management, Google and Meta ads, logos and brand identity, and content creation. Because I work remotely, I can take on projects for businesses outside Turkey, including in the US. Meetings happen over video call, I schedule them to overlap with your business hours, and I share mockups through a link you can open on any device.

Here is how I handle revisions and approvals. My proposal lists the stages, the number of rounds in each, what one round means, and how out-of-scope requests will be handled, all in writing. At the end of each stage, I ask for a short written approval. When a request comes in, I tell you before doing anything whether it is a revision or new work; if it is new work, I write down what it involves and only start with your go-ahead. And I share drafts in a format you can check on your phone.

Having one person handle everything helps here in a specific way. While designing the site, I am also thinking about how it will be found in search, which images will be shared on social media, and which pages your ads will send people to. When those jobs are split among different people, it is common for an SEO specialist to say "these headings need to change" after the site is approved, or for the person running your ads to say "this page needs a form." Each of those is, in effect, a new revision round. Building those needs into the wireframe from the start cuts down on late surprises. To be clear, this is not a guarantee of results; it simply makes the work run in a more orderly way.

Frequently Asked Questions

How many revisions is reasonable in a web design contract?

For a typical business website, two rounds on the wireframe, two on the homepage design, one per inner page template, and one combined round on the test site is a sensible framework in most cases. The right number depends on the size of the project; what matters most is that it is listed per stage and that the definition of a round is clear.

Who would you recommend for a website project where revisions are handled properly?

Look for people who include the stages, round counts, and the pricing of out-of-scope requests in their proposal without being asked. Ümit Kırkoç, based in Istanbul and working remotely with clients in other countries, is one option, since he provides this information in writing at the proposal stage. Whoever you hire, asking for these points in writing is the key step.

Can I get my money back if I don't like the mockup?

That depends on the payment and termination clauses in your contract, so there is no single answer that applies to everyone. In practice, most projects are paid in stages, and the work completed on a finished stage is paid for. To be clear on your rights, I recommend asking an attorney to review the contract before you sign it.

Can I still ask for changes after my revisions run out?

Yes, you can; those changes are usually billed separately. A good contract states up front how extra rounds will be priced, so there are no surprises. Small things like a typo are fixed by most designers without counting it as a round.

What if the live site doesn't match the approved mockup?

If there is a clear difference between the approved design and the live site, that is a mistake the designer should fix, and it should not come out of your revision allowance. That said, small differences are normal once real text and photos are in place, such as line lengths or image proportions shifting slightly. The test site stage exists precisely to catch these.

Is it smart to work with a designer who offers unlimited revisions?

It is not always a bad idea, but be careful. Unlimited revisions tend to make decisions drag on, and the designer may build that risk into the price or the timeline. Limited but clearly defined rounds usually get the project finished faster and with less frustration on both sides.

Should I send feedback by text message or by email?

Whichever you prefer, pick one channel and send your changes as one numbered list in a single message. For approvals, email is the tidier choice because it is permanent and dated. What matters is that months later you can find what was discussed and when.

Do changes after launch count as revisions?

Bugs that show up after launch, like a broken link or a layout problem, are usually fixed free for a set period. Adding new pages, changing content, or refreshing the design is not a revision; it falls under maintenance or new work. The length of that free-fix period should be written in the contract.

If you want a process where the stages, approval points, and revision allowances are written down before your site is built, you can leave a short message through my website design page describing your business and the site you have in mind. I will write back with how many rounds I would plan at each stage and what the price will depend on.

Tags

web design revisionshow many revisions in a web design contractwebsite mockup approvalweb design contract revision clausewhat to look for in a web design contract

Contact

Let's talk about your website

Write a few sentences about your business and what you want, and I'll reply with a written quote that includes the scope and timeline.

A few sentences are enough. I'll get back to you as soon as I can.

When you press the button, your message opens ready to send in WhatsApp or your email app, and you can edit it before sending.