How to give clear feedback on website design drafts

A design draft is your chance to shape the website before it goes live.

This post shows you how to review a mockup step by step and send one clear list of changes.

First, know what a mockup is and what your package covers

A mockup is a picture of your website before it is built. It shows the layout, colours, text and images. This is the cheapest time to change things, because nothing has been coded yet.

Before you start reviewing, read your written scope. GreatWeb lists, for every package, what is included, what is not, how many revisions you get and how long the work takes. A revision round means one set of changes the designer makes after you give feedback.

Here is how three of the listed website packages compare:

Find your own package and note the revision count. If you have two rounds, treat each one as valuable. Do not spend a round on one small fix.

Also note the page limit. If your package has five pages, every comment you write should fit inside those five pages. This single check saves a lot of confusion later.

Review the draft in a fixed order

Most people look at a draft once, feel that something is not right, and write a vague message. Instead, go through the draft in the same order every time. Make one pass for each point below.

1. Purpose. Does the first screen tell a visitor what you do and what to do next? A landing page, for example, is meant for one offer and one clear call to action. Check that the page does exactly that.
2. Content. Read every word. Check your business name, services, spellings, timings and contact details. Wrong facts are the most important thing to catch.
3. Structure. Are the sections in a sensible order? Can a visitor find the contact form or the WhatsApp button without hunting for it?
4. Look and feel. Now judge colours, fonts and images. Do this last, because it is the part most affected by personal taste.
5. Mobile view. Many visitors will open your site on a phone. Ask for the phone layout of the draft, or check that it is shown, and review it as a separate pass.

Why this order? Content and structure problems are costly to fix late. Colour and font changes are quick. If you start with colours, you may use up your attention and miss a wrong phone number.

Take your time. Review in two or three short sittings instead of one long one. Tired eyes skip spelling mistakes.

Write each comment as a change, not a feeling

A comment such as the top part is not nice gives the designer nothing to act on. A good comment has three parts: where, what and why.

Notice that the clear versions name the page, name the part of the page and say what should happen. The reason helps the designer find a better solution if your exact idea does not fit.

If you do not know how to describe a problem, describe what the visitor should be able to do. For example, a customer should be able to call you with one tap on a phone. The designer can then choose the best way to show it.

Avoid comparing with other websites without saying what you liked. Saying you want the same look as another site is unclear. Say instead which part you liked, such as the spacing, the order of sections or the size of the buttons.

Separate must-fix items from preferences

Not every comment has the same weight. Sort your list into two groups before you send it.

• Must fix: wrong facts, missing contact details, broken layout on phone, anything that confuses a visitor.
• Nice to have: a slightly different shade, a different icon, a small spacing change.

Put must-fix items first. If your revision limit is tight, this tells the designer what matters most. It also stops you from using the last round on cosmetic changes while a real error stays on the page.

Then check your list against the scope. If you ask for a new page, a shop feature or a section that is not in your package, that is a change in scope, not a revision. GreatWeb's package details show what is included and what is not, so read them first. Raise any scope change early, so you can talk about it openly before it affects the timeline.

Send one consolidated list, and involve everyone first

The biggest mistake small businesses make is sending feedback in pieces. One message on Monday, three more on Tuesday, a voice note on Wednesday. This is confusing, and each message may end up counted as a new round.

Follow these steps instead:

1. Share the draft with everyone who has a say, such as a partner, a manager or a family member who helps with the business.
2. Ask each person to give you comments by a fixed date.
3. Combine them in one document. Remove repeated points. Where two people disagree, you decide.
4. Number every item. Numbers make it easy to refer to a point later, for example when you check the revised draft.
5. Send it in one message by email or WhatsApp, with the page names clearly written.

With GreatWeb you talk to the person who plans and designs your project, and there is no account manager passing messages along. That helps, because you can ask a short question before you finalise your list. A two-minute clarification is better than a wasted round.

After the revised draft arrives

Do not look at the new version in a general way. Open your numbered list and tick off each item one by one. Then check that the changes did not break something nearby, such as a heading that now wraps badly on a phone.

If something is still wrong, it goes into the next round, again as a single list. If you have used all your rounds, ask about the next step before the project stalls. Because scope and limits are written down before any money changes hands, you can raise this calmly and plan for it.

Finally, approve only after you have read the content once more. After launch, errors in text or contact details are yours to catch too, so it is better to find them now.

Key takeaways

Frequently asked questions

How many revisions do I get?

It depends on the package. The website packages list either 2 or 3 revisions, and the bigger packages list 3. Check the full scope of your own package for the exact number.

What counts as a revision round?

A revision round is one set of changes made after you give feedback. That is why one consolidated list is better than several small messages.

Can I ask for a new page during review?

A page beyond your package limit is a change in scope, not a revision. Mention it early so it can be discussed and agreed before work continues.

What if I cannot explain what I dislike?

Describe what the visitor should be able to do or understand on that page. You can also ask a short question before sending your list, since you talk directly with the person doing the work.

Should I send feedback on WhatsApp or email?

Either works, since GreatWeb is reachable by WhatsApp, email or a call. Use whichever lets you send a clear, numbered list in one message.