Approving a website should mean more than agreeing that a picture looks good. You need to know what happens when someone opens the menu, reads your services, taps a button, or tries to contact you.
At StandWatch Digital, you review a working preview before your website goes public. We build it on a separate development site and give you a link. You can click through every page on your phone and computer, much as a visitor would.
Fonts and colors are approved first. Then you review the working website, request changes, and give final approval after testing. Nothing goes public until you say it is ready.
That order gives you a chance to judge the site as a website, not just as a design.
First, agree on the visual direction
Fonts and colors set the direction before you review the working pages. Is the text comfortable to read? Do the colors feel right for your business or organization? Does the overall style fit what you want people to understand about you?
You do not need to know design terminology to answer those questions. “This heading feels too formal” or “The smaller text is hard for me to read” is useful feedback.
Approving that direction does not replace reviewing the finished pages. A color choice in isolation is one decision. Seeing that color behind a paragraph, beside a photograph, or on a button is another.
Then, use the working preview
The preview is separate from your public website. Its purpose is to let you review the build before launch.
Open the link on your computer, then on your phone. Start on the homepage and follow the paths that matter to your visitors. If you offer services, read a service page and find the next step. If your site introduces an author, speaker, or ministry, check the information people need before buying a book, making an inquiry, or planning a visit.
You are not being asked to review code. You are checking whether the site says the right things and lets people do what they came to do.
Our How We Work page explains where this review fits between the build and final approval.
Read the words as carefully as the design
A polished page can still contain an incorrect detail. Review names, phone numbers, email addresses, service descriptions, prices where shown, and any dates or locations.
Check the photographs too. Are they the right images? Do their captions identify the right people, places, or work? Does the wording describe what you actually offer, without implying a service you do not provide?
You bring knowledge of your business that a builder cannot infer from a layout. We can build a clear page, but you are the person who can confirm that its description is accurate.
Try reading the homepage as someone who has never heard of you. What do you do? Who is it for? What should that person do next? If the answers take too much explanation, tell us where you got stuck.
Check the phone experience, not just the smaller layout
On your phone, use the menu, follow links, and tap the main buttons. Read a longer page from top to bottom. Look at photographs and headings where the layout changes.
A useful review asks practical questions: Can I read this without zooming? Can I find the information I need? Is this button where I expect it? Is a heading or image cut off?
Your phone review adds a real-use perspective to our testing. It does not make you responsible for technical checks. Before launch, we check every form, page, and link against our launch checklist.
If you notice a problem, include the device you used and what happened. “The menu did not open on my iPhone” is much easier to investigate than “Mobile is broken.”
Make each change easy to find
When you request a change, identify the page and the section. Include the current wording or a screenshot if it helps, then describe what you want changed.
For example:
“On the Services page, under the second heading, replace the first sentence with: [your corrected sentence].”
Or:
“On my phone, the Contact button overlaps the image near the bottom of the homepage.”
These are examples of useful feedback, not rules you have to master. A short list is enough. Specific notes let us fix the right item without guessing what you meant.
Also separate a correction from a new request. Fixing an incorrect phone number is different from adding a booking system. If a request changes the agreed scope, the written proposal or agreement governs the project. Our Terms explain that distinction.
Final approval is a separate step
A preview review and permission to launch are different decisions. You may like the design and still need to correct a service description or replace an image.
Our process includes testing and final approval before deployment. That is the point to confirm that the requested corrections are in place and the site is ready to represent you publicly.
Approval is not a promise that a website will never need another edit. It means the agreed build is ready to launch. After deployment, we provide 30 days of edits to the approved site, up to two rounds. CMS setup and training follow that edit period, so you can manage your content yourself. Major changes are quoted separately.
You should recognize your business when it goes live
A working preview makes the review concrete. You can read the actual pages, try the navigation, and see the site on the devices you use.
Our job is to build and test it. Your part is to confirm that the content and presentation reflect your business, tell us what needs changing, and decide when it is ready.
The first time you see your finished website should not be the moment the public sees it too.