What's the difference between a defect and a new request?

A defect is something that differs from what was originally agreed — wrong information, a missing agreed feature, a broken element. A new request is something you've decided you'd like that wasn't part of the original brief. Defects are corrections; new requests may affect scope and cost.

Why can't I just send feedback as I spot things?

Sending feedback in stages means your designer may already be working on a revised version before your later comments arrive, leading to missed changes and extra rounds. One consolidated list lets everything be addressed in a single efficient pass.

What should I write if I don't like something but can't explain why?

Use the location–observation–request format and be honest: describe what you see and what feeling or problem it creates, even if you don't know the technical fix. For example: 'Hero section, background colour — it feels too dark and serious for our brand — please can we explore a lighter option?' Your designer can suggest solutions.

Do I need to check every link myself?

Yes. You are the person who knows where each link should go. Your designer can confirm a link is live, but only you can confirm it points to the correct destination — the right product page, the right PDF, the right external site.

What if I notice something new I'd like after I've already submitted my feedback?

Hold it. If your revision round hasn't been actioned yet, add it to your list and resend the complete updated document. If work has already started on your submitted feedback, raise the new item separately and be transparent that it's an addition — your designer can advise on the best way to handle it.

How to Give Useful Feedback on a One-Page Website Preview

When your designer sends a one-page website preview, it can feel overwhelming to know where to start. A structured approach saves time, reduces back-and-forth, and gets you a better result faster.

The Five Areas to Check (In This Order)

Work through the preview methodically rather than clicking around randomly. A consistent sequence means nothing gets missed.

Content accuracy — Are all names, addresses, prices, job titles, and dates correct?
Links and buttons — Does every CTA, nav anchor, and external link point to the right place?
Mobile reading — Open the preview on your actual phone. Is text readable without zooming? Do images crop awkwardly?
Agreed deliverables — Cross-reference the original brief. Is every section, feature, or element you agreed on actually present?
Preferences — Only after the above, note anything you'd like to change about colour, wording, or layout.

Separate a Defect From a New Request

This distinction matters more than most clients realise. A defect is something that differs from what was agreed — a wrong phone number, a missing section, a broken link. A new request is something you've decided you want that wasn't in the original brief — a new colour scheme, an added testimonials block, different copy.

Defects are corrections and should be fixed as part of the agreed work. New requests may affect scope, timeline, and cost. Label each comment clearly as one or the other. If you're unsure, ask rather than assume.

Use the Location–Observation–Request Format

Vague feedback like 'the top bit looks off' forces your designer to guess. Instead, use three short pieces of information for every comment:

Location — Where exactly? ('Hero section, main headline' or 'Contact form, submit button')
Observation — What do you see? ('The phone number reads 0207 not 0208')
Request — What should happen? ('Please update to 0208 555 0134')

A complete example: 'Services section, second card heading — it says 'Boiler Repair' but we agreed on 'Boiler Servicing' — please change to Boiler Servicing.' That one sentence gives your designer everything they need with no follow-up questions.

Why You Should Send One Complete List, Not Several Emails

It's tempting to fire off comments as you spot them, but piecemeal feedback creates a real problem. Each time a designer reopens a file to action a single note, they risk introducing a knock-on change elsewhere — and each round of amends takes time to check and export.

More importantly, a revision round is most efficient when it's treated as a complete batch. If you send three emails over two days, you may receive an updated preview that fixes the first email but was already in progress before your second and third arrived. Consolidate everything into one document or message before sending.

Reviewing on Mobile: What to Actually Look For

Don't just glance at it — scroll the entire page slowly on your phone. Common issues to watch for:

Text that's too small to read comfortably without pinching
Buttons that are too close together to tap accurately
Images that are cropped in a way that loses important detail
Sections where content overlaps or runs off the edge of the screen
Long unbroken paragraphs that look fine on desktop but are exhausting on mobile

Checking Agreed Deliverables Against the Brief

Pull up whatever document or email thread captured your original agreement — a proposal, a scope document, a sign-off email. Go item by item. If you agreed on a FAQ accordion, an embedded map, a specific form, or a particular section order, confirm each one is present and working as described.

If something is missing, that's a defect. Note it using the location–observation–request format and flag it as a defect, not a preference. Don't assume it will appear later — a preview should reflect everything agreed at that stage.

A Quick Feedback Checklist

All text proofread for accuracy (names, numbers, addresses, dates)
Every link and button tested
Full page reviewed on a real mobile device
All agreed sections and features present
Defects listed separately from new requests
Every comment written in location–observation–request format
All feedback compiled into one single document before sending