The short answer
We send a private preview link. You open it on a computer and a phone, work through a checklist, collect everyone's comments into one message and send it back. When you say approved, we launch. A second person on our team has already checked the work before you see it, but only you know your business, so your review matters.
How a preview link review works
A preview link opens the new version of your site (or page, or change) in a private place, before the public can see it. It is often hosted on a staging site, which is a copy of your website used for testing, so nothing you click on affects the live one. Think of it as a dress rehearsal.
Your project manager sends the link, says what has been changed and what to focus on, and lists anything that is deliberately not final. You review, send feedback, and we make changes. This may repeat. When everything is right you tell us it is approved, and only then do we publish. Each change is listed, so the version you approved is the version that ships.
- 1You receive the preview link with a list of what has changed.
- 2You review on desktop and on a phone, using the checklist below.
- 3You collect comments from everyone who needs to weigh in and send them as one message.
- 4We make the changes and send the updated link.
- 5You confirm approval in writing, by email or in the ticket.
- 6We publish, then check the live site against what you approved.
A client review checklist
Do this once on a computer and once on your phone. Chrome's own documentation says its device simulator is only a first-order approximation of a real phone, so a simulation on your computer is not a substitute for opening the link on your actual phone.
- Facts: every phone number, email, address, opening time, price and name is correct. Click or tap each phone number and email link to check it works.
- Spelling: read every heading and every paragraph slowly. Names of people and places are the most commonly wrong.
- Promises: nothing says anything you cannot deliver or that your regulator would object to.
- Forms: fill in every form with test details and submit it. Confirm the confirmation message appears and ask us whether the email arrived. Use obviously fake details.
- Buttons and links: click all of them. Check they go where you expect, and that links to other pages open the right page.
- Images: they are yours, sharp, and show what the caption says. Check that nobody who should not be shown appears.
- Phone: scroll every page, check text is readable without zooming, buttons are easy to tap and nothing is cut off or overlaps. Rotate the phone too.
- Menu and navigation: every page you expect is reachable and in a sensible place.
- Missing: anything that was on the old site that you want kept is still there, or we have told you it was removed on purpose.
Consolidate feedback before sending it
The most effective thing you can do is send one message that covers everyone. If three people on your side send three separate lists, some of them will contradict each other, and we cannot tell which to follow. Collect comments first, resolve disagreements internally, and send one consolidated list from one person.
Make each item specific. Name the page, say what you see and say what you want instead. "Page is too busy" is hard to act on. "On the services page, the three blue boxes feel crowded on my phone, please cut the text in each to two lines" is easy. How to give feedback goes into this in depth. Number the items so replies can reference them.
Nielsen Norman Group, a UX research firm, suggests sorting comments after a review into three groups: things to do, things to discuss and persuade, and things that need clarifying. That works well here. Tell us which of your comments are firm and which are preferences.
What approval actually means
Approval is your written confirmation that the work shown on the preview link is correct and can go live. It is a clear, simple point in the project. After it, we publish exactly what you approved. If you approve and then see more things to change, those become new requests rather than corrections, so it is worth being thorough before saying yes.
Approval does not mean you have checked every technical detail. We check the technical side, including a second-person review before you ever see the work. It means the content, the facts and the look are right for your business. If you are not sure, say so. "Approved except for item 4" is a perfectly good answer.
Why we check twice
Before you see anything, a second person on our team reviews it. The person who built something is the worst placed to see its mistakes, because they know what it is supposed to say. A fresh pair of eyes catches broken links, typos and layouts that only fail on certain screens. Then you review, because you know your business and we do not.
Two independent checks catch different things. Ours finds technical and consistency problems. Yours finds the facts, the tone and the details only you know. Skipping either one is how errors reach the public.
If you notice something after launch
It happens, even with careful review. First, do not panic and do not assume it is serious. Note exactly what you see, on which page, on which device, and send a screenshot. Then send it through the support form. If it is a mistake in what we built or published, we will correct it and explain what happened. If it is a new change you would like, we will treat it as an update request. Request a website update explains how.
If the site looks wrong right now, try clearing your cache first, because an old version stored in your browser is a frequent cause of apparent problems.
Example: A review that caught a real problem
A restaurant owner reviewed the new site on her phone and noticed the booking button was hidden behind the cookie banner on her model. We had checked several phones, but not hers. Because she told us the phone model, the page and attached a screenshot, we fixed the spacing the same session and re-sent the link. She also tested the booking form with a made-up name and confirmed the confirmation email arrived. The whole review took twenty minutes of her time, and that was the 20 minutes that stopped the problem reaching customers.
When to ask us
Ask your project manager if you are not sure what to focus on, if a preview link does not open or looks broken, or if you need more time with the review. Send feedback in one consolidated message, with numbered items, screenshots where useful and the device you used. If you cannot tell whether something is a bug or a decision, send it anyway and label it a question. Use the support form for anything that is not about a project in progress. See who to contact for the right route.
