Most owners are handed a set of mockups, told the project is now waiting on them, and given no idea what they are meant to be looking for. So they do the human thing. They react to the colours, mention the logo looks small, ask if the photo can be warmer, and reply “looks good, go ahead”.
Two months later the site is live and the enquiries are thin. The colours were never the problem. The structure was approved without anyone checking it, because nobody in the room framed the web design mockup approval as a structural decision.
This guide from IZI Digital Marketing sets out what a web design mockup approval actually commits you to, the order to review in, and the wording that gets a useful revision instead of a defensive one. It is written for the person signing off, not for the designer.
Before the detail, here is an outside view on giving design feedback that lands.
How to Give Good Web Design Feedback
Source video: How to Give Good Web Design Feedback on YouTube
PART 1 · DIAGNOSE
What Are You Actually Signing Off?
IN BRIEFA web design mockup approval locks the page structure, the order of information and the position of every call to action. It does not lock colour, photography or wording, all of which stay cheap to change. Knowing which half is expensive tells you where to spend your review time and what a website designer needs from you.
Everything on a mockup falls into one of two buckets, and they carry very different price tags once build starts.
- Expensive to change later: the page structure, what appears above the fold, the order of sections, the navigation, the number of form fields, and where the enquiry action sits on each page.
- Cheap to change later: exact hex colours, photographs, icon style, and most body copy. These are content decisions, and a competent build lets you swap them without touching the layout.
Reviews go wrong because attention flows to the cheap bucket. Colour is easy to have an opinion about. Section order is not, so it slips through unexamined, and it is the one that shapes whether a visitor understands the offer before losing interest.
Not sure whether the structure in front of you is right?
A short outside read on the mockups usually costs less than one wasted revision round. See how a Blueprint review works
BENCHMARK BRIEFING 1 OF 4
What Reviewers Comment On Versus What Matters
IN BRIEFIn a web design mockup approval, feedback volume and feedback value rarely line up. Visual preferences attract most of the comments and change almost nothing commercially, while structural issues attract few comments and decide whether the site earns enquiries. Use the gap below to re-weight your own website design review.
The table shows a typical spread of comments on a first-round mockup, set against how much each category actually affects the result.
| Comment category | Share of comments | Commercial weight | Cost to change after build |
|---|---|---|---|
| Colour and imagery | 35% | Low | Low |
| Logo size and branding | 20% | Low | Low |
| Wording and headlines | 18% | Medium | Low |
| Section order and hierarchy | 12% | High | High |
| Enquiry path and form design | 10% | High | High |
| Mobile layout | 5% | High | High |
Illustrative model by IZI Digital Marketing, built on standard Malaysian web design review and revision practice, 2026.
PART 2 · DIAGNOSE
How to Review a Web Design Mockup, Step by Step
IN BRIEFReview in a fixed order and colour comes last, which is the whole point. Start on mobile, read the page as a stranger would, check the enquiry path, test the layout against real content, then let yourself have opinions about the palette.
Work through these five steps in sequence. Each one is a separate pass over the same mockup, and taking them out of order is how the structural problems get missed.
- Open the mobile version first. Google crawls and indexes sites with its smartphone crawler, as set out in Google’s mobile-first indexing documentation, and most Malaysian visitors will arrive on a phone. If the desktop mockup is the only one you are shown, ask for mobile before commenting on anything.
- Read the first screen as a stranger. Cover everything below the fold. Can someone who has never heard of you say what you sell, who it is for, and what to do next? If not, the problem is the first screen, not the font.
- Follow the enquiry path on every page. Pick any page and count how many actions it offers. One primary action per page works. Four competing buttons means the page has no view about what should happen.
- Drop in your longest real content. Mockups use tidy placeholder text. Paste in your actual longest service name, your real staff photo, your genuine testimonial. Layouts that only work with perfect content will break in week one.
- Now look at colour, type and imagery. Check that body text sits comfortably against its background, the W3C’s contrast minimum guidance sets 4.5:1 as the threshold for normal text, and pale grey on white routinely fails it.
BENCHMARK BRIEFING 2 OF 4
Why Revision Rounds Multiply
IN BRIEFMost included revision allowances are two or three rounds. Projects overrun them for predictable reasons, and nearly all of those reasons are avoidable by the client rather than the designer. Check the allowance in your website design package before the first review, not after the third.
| Round | Most common cause | Relative frequency | Avoidable? |
|---|---|---|---|
| Round 1 | Normal design refinement | Expected | |
| Round 2 | A second stakeholder sees it late | Yes | |
| Round 3 | Real content does not fit the layout | Yes | |
| Round 4 | Scope changed mid-review | Yes | |
| Round 5+ | No one agreed who decides | Yes |
Illustrative model by IZI Digital Marketing, built on common Malaysian web design project scopes and revision terms, 2026.
PART 3 · DESIGN
Approve, Revise or Rescope?
IN BRIEFThree outcomes are available at a web design mockup approval, and picking the wrong one is costly in both directions. Approving a broken structure wastes the build; rescoping a sound design over a colour preference wastes the budget. Match the outcome to what is actually wrong.
DECISION BOX · WHAT TO DO WITH THIS MOCKUP
| Option | Use when | Time cost | Risk if wrong |
|---|---|---|---|
| Approve as is | Structure and enquiry path both hold up | None | High, rebuild later |
| Approve with notes | Structure fine, surface details off | Days | Low |
| Request one full round | Section order or first screen is wrong | 1–2 weeks | Low |
| Rescope the brief | The design answers the wrong question | 3–4 weeks | Medium, cost and delay |
Verdict: Approve with notes if your objections are all in the cheap bucket. Request a full round the moment the first screen or the section order is wrong. Only rescope when the mockup reveals that you and the designer were solving different problems, which is a briefing failure and will not be fixed by more rounds.
Stuck between a revision and a rescope?
That decision is usually about the brief rather than the design, and it is worth an outside opinion before you commit. Talk it through with a consultant
BENCHMARK BRIEFING 3 OF 4
How Long a Mockup Approval Should Take
IN BRIEFA web design mockup approval that drags past two weeks rarely produces a better site, it just moves the launch date. The pattern below shows where the days go and which stage is worth protecting when the calendar tightens.
| Stage | Well run | Stalled | Main risk |
|---|---|---|---|
| Mockup delivered to review start | 1 day | 5 days | Nobody owns the review |
| Structured review by decision maker | 2 days | 2 days | Reviewed in the wrong order |
| Collecting internal opinions | 2 days | 10 days | Opinions arrive one by one |
| Consolidating feedback into one list | 1 day | 4 days | Contradictory instructions |
| Designer revises and resubmits | 4 days | 7 days | Rework on unclear notes |
| Total | 10 days | 28 days | Launch slips a month |
Illustrative model by IZI Digital Marketing, built on standard Malaysian web design project timelines, 2026.
PART 4 · DEPLOY
Who Signs Off and How to Write the Feedback
IN BRIEFOne named person owns the web design mockup approval; everyone else advises. Feedback goes back as a single consolidated list, written as problems rather than solutions, so the designer can apply craft to the fix instead of executing an instruction that may not work.
Two rules do most of the work here, and both are about process rather than design skill.
Name one decision maker before the mockup arrives. Committees do not approve designs, they average them. Others can comment, but one person weighs the comments and sends the final list. Without that, the designer receives five voices and has to guess which one outranks the rest.
Describe the problem, not the fix. “Make the button bigger” is an instruction. “I could not find where to enquire on my phone” is a problem, and it may be solved by position, contrast or wording rather than size. Designers can solve problems well; they can only obey instructions.
BENCHMARK BRIEFING 4 OF 4
Vague Feedback Rewritten as Useful Feedback
IN BRIEFComment phrasing changes the quality of the revision more than comment volume does. The pairs below show the same underlying concern written two ways, with what the designer can actually do about each version.
| Vague version | Actionable rewrite | What changes |
|---|---|---|
| “Make it pop” | “The offer is not the first thing I notice on this screen” | Hierarchy fix, not a colour fix |
| “Looks a bit plain” | “It does not feel as premium as our pricing implies” | Ties the change to positioning |
| “Add more content here” | “Buyers always ask about lead time and we do not answer it” | Names the missing information |
| “I do not like the blue” | “This blue is not in our brand palette” | Separates rule from preference |
| “Move the button up” | “On my phone I scrolled twice before seeing how to contact you” | Gives the designer the real constraint |
Aggregated by IZI Digital Marketing from common Malaysian web design review comments and standard design critique practice, 2026.
THE VERDICT
Approve the Structure, Negotiate the Rest
A web design mockup approval is the last cheap moment in the project. After it, structural change means rebuilding, and most owners spend that moment discussing colour because nobody told them what else to look at.
The fix is not a longer web design mockup approval. It is a differently ordered one: mobile first, first screen as a stranger, enquiry path, real content, then aesthetics. One decision maker, one list, problems rather than instructions. That routine tends to shorten the project rather than lengthen it, because it removes the rounds that exist only to resolve confusion.
If you are still choosing who will produce the mockups, the same structural thinking applies earlier, judging a web design agency’s portfolio is the check that comes before this one. And once the site is live, an SEO audit checklist tells you whether the structure you approved is being found.
FAQ
Frequently Asked Questions
1. What should I check before approving a web design mockup?
Check the mobile version, the first screen, the enquiry path and how the layout holds your real content. Those four decide whether the site works. Colour, imagery and wording can be adjusted after launch at little cost, so they should take the smallest share of your review time.
2. How many revision rounds are reasonable?
Two or three is the common allowance in Malaysian web design scopes, and it is usually enough. Projects exceed it for process reasons rather than design ones, a late stakeholder, real content that does not fit, or no agreed decision maker. Confirm the allowance in writing before the first review.
3. Can I change the layout after approving the mockup?
You can, but it is the expensive change. Approval is the point where structure gets committed to build, so layout revisions afterwards often mean redoing work already paid for. Surface details like colours, photos and copy stay comparatively cheap to change at any stage.
4. Should the whole team review the mockup?
They can comment, but only one person should approve. Multiple approvers produce contradictory instructions and a design that averages everyone’s preferences. Set a single deadline, collect all comments, then have the decision maker consolidate them into one list before it reaches the designer.
5. What if I dislike the design but cannot say why?
Say exactly that, then describe what you expected to feel instead. “It reads as cheaper than our pricing” is workable feedback; “I just do not like it” is not. If the discomfort survives a second look at the brief, the issue is probably the brief rather than the mockup.
Holding a mockup you are not sure about?
Book a free Blueprint consultation, we will review the structure against what the site is supposed to earn, tell you plainly whether it is an approval, a revision or a rescope, and give you the feedback list to send.