What is UAT for websites? A plain explanation
UAT turns up in proposals and project plans, often without explanation. It stands for user acceptance testing, and for a website it means one simple thing: before launch, the client checks the site does what they need, and says yes.
What UAT means
User acceptance testing is the final check before launch, done by the people the website is for. That means the client and, ideally, the people who will use it day to day.
The question UAT answers is simple: does this site do what we need it to do? If the answer is yes, the client accepts the site and it goes live.
UAT vs QA
| QA | UAT | |
|---|---|---|
| Done by | The agency or build team | The client and real users |
| Asks | Did we build it right? | Did we build the right thing? |
| Checks | Links, forms, layouts, speed, browsers | Real tasks, content, business needs |
| When | Throughout the build, and before UAT | Last, just before launch |
| Ends with | A site ready for the client | A written sign-off |
QA should come first. If clients spend UAT finding broken links, they lose trust and the real business checks get skipped.
A simple example
A bakery's new site is on staging. The agency has done its QA. For UAT, the owner, the person who takes orders and a regular customer each get the review link and a short list of tasks:
- Find this week's opening hours on your phone.
- Order a birthday cake for Saturday collection.
- Find out whether the shop sells gluten-free bread.
- Send a question through the contact form.
The order-taker notices the cake form doesn't ask for the name to write on the cake. The customer can't find the gluten-free information without scrolling past three photos. Neither is a bug; both are things only real users would catch. They leave a comment on the exact spot, the agency fixes both, the owner checks again, and signs off.
How to run UAT on a website
- Finish QA first. Fix what you can find yourself.
- Write the tasks. Five to ten real things people will do on the site, in plain words.
- Pick the testers. The client plus two or three people who will really use the site.
- Share one link. Staging on a review link where testers click anything to comment, with no account. Ask them to try on their phone too.
- Set a window. For example, comments in by Thursday.
- Sort and fix. Label comments as must-fix or nice-to-have, assign them, and resolve each one with a reply.
- Get sign-off in writing. A short message or an approval on the review link that the site is accepted.
What sign-off should say
Keep it short and specific: which version or date of the site is accepted, that it meets the agreed scope, and that further changes will be quoted separately. Our guide to getting client website approval covers the wording and what to do when sign-off stalls.
Common mistakes
- Skipping QA and letting clients find the broken links.
- No task list, so testers browse aimlessly and comment on colours.
- Only the boss tests, and the people who use the site daily find the problems after launch.
- Feedback scattered across email, chat and calls, so things are missed.
- No end date, so UAT quietly turns into another design round.
For everything else to check before going live, see the website launch checklist.
Questions
What does UAT stand for?
User acceptance testing. It is the stage where the people who asked for the website, or will use it, check it meets their needs before it goes live.
What is the difference between QA and UAT?
QA (quality assurance) is the build team checking the site works as designed: no broken links, forms submit, layouts hold on every screen. UAT is the client checking the site does what they need. QA asks "did we build it right?" and UAT asks "did we build the right thing?"
Who does UAT on a website project?
The client, and ideally a few people who will really use the site: the person who answers the contact form, the person who updates the blog, someone from sales. The agency prepares the test and fixes what comes up.
How long does UAT take?
For a small business site, often a few days to a week, including fixes. Larger sites with many stakeholders take longer. Agree a window in advance so it doesn't drag on.
What happens at the end of UAT?
The client signs off, usually in writing, confirming the site is accepted and ready to launch. Anything new after sign-off is treated as a change request.
Run UAT on a review link. Testers click anything on the staging site to comment, and you track every item to resolved.
Start a free review