The user acceptance testing process is the set of steps that takes a system from “tested by QA” to “accepted by the business”. It has four phases: planning, design, execution and closure. Done well, it catches the gaps between what was built and what users need before release. Done badly, it is rushed, under-staffed and ignored, and the problems show up in production instead.
This guide walks through each phase, then covers the mistakes I have seen derail UAT and how to avoid them. For the bigger picture, start with our complete guide to user acceptance testing. If you want something to copy, use the UAT template and the UAT checklist.
Table of Contents
ToggleWhy the UAT process matters
UAT is the final check before the product reaches the market. End users try the product in a realistic environment and confirm that it meets their requirements. It finds gaps between the requirements and the real product, defects that earlier testing missed, and usability problems that only show up when real people do real work. It also gives users a say, which is feedback you cannot get any other way. For a clear example of a UAT approach, see Stanford’s project office guidance.
The UAT process at a glance
| Phase | Main goal | Key outputs |
|---|---|---|
| 1. Planning | Agree scope, people, environment and schedule | UAT plan, team, environment requirements |
| 2. Design | Turn business scenarios into test cases and daily plans | Scenarios, test cases, questionnaires, execution plan |
| 3. Execution | Run the tests, log defects and fix them | Test results, defect log, daily reports |
| 4. Closure | Review results, decide and sign off | Test summary, go or no-go decision, lessons learned |
Phase 1: UAT planning
Thorough planning is what makes a UAT cycle succeed. Cover these points:
- Estimate and prepare resources. Know how many users, how many days and what tools you need.
- Define the UAT environment. It should resemble production, with the right data and integrations.
- Identify business users and form a dedicated team. Confirm that the users are available for the whole cycle, not just on the first day.
- Review project documentation and requirements so the team understands what was agreed.
- Identify and prioritise key business scenarios. You will not test everything, so choose the flows that matter most.
- Run a shake-down test. Before UAT starts, check that the environment works and is ready.
Phase 2: UAT design
- Analyse business scenarios and review coverage. Check that the scope covers every critical function and business scenario, and fix any gaps.
- Review the process and the system integration testing (SIT) results. Walk the UAT team through the procedure so everyone is aligned. Review the SIT results to understand the issues already found and make sure serious defects are fixed before UAT starts.
- Prepare the plan and questionnaires. Questionnaires guide business users, and capture feedback, observations and suggestions. Prepare a daily execution plan that says which scenarios will be tested each day and what the expected outcomes are.
Write clear acceptance criteria at this stage. See user acceptance criteria with UAT examples for how.
Phase 3: UAT execution
- Hold a short daily stand-up. Align the team, raise blockers and plan the day.
- Walk through the scenarios. Show business users the intended flow and expected results before they start.
- Execute the test cases. Run them in order, following the procedure, and record the actual results.
- Complete the questionnaires. Users record observations and suggestions that test cases do not capture.
- Log defects. Record each defect in a tracking system, with clear steps to reproduce it.
- Triage defects daily. Hold a defect triage session with the UAT team and developers to set priorities and plan fixes.
- Report progress. Share the number of test cases run, defects found and overall status with stakeholders.
- Back up the environment each day. A clean, consistent environment keeps results reliable.
Phase 4: UAT closure
Closure wraps up the testing and turns it into a decision.
- Hold a formal UAT review meeting covering coverage and execution results.
- Consolidate user feedback and defect reports, and decide what to do about open issues.
- Assess whether the system is ready for production, and make a go or no-go decision.
- Prepare the test summary and record lessons learned.
- Archive the documentation, including test results and defect logs.
- Get formal sign-off from the stakeholders so deployment can proceed.
Common mistakes in the UAT process
1. Unclear requirements and acceptance criteria
Without clear criteria, nobody can say whether the product meets users’ expectations, and arguments about “is this a defect or a change request?” slow everything down. Agree the requirements and acceptance criteria early, and write them so that each one can be tested. In one project I worked on, the product reached system integration testing and UAT without clear acceptance criteria, and issues came to light late, which delayed deployment.
2. Stakeholders not involved enough
End users are the main stakeholders in UAT, so without their commitment the test is worth very little. On one project in the early 2010s, business users were not properly involved, and on any given day about half of them simply did not turn up. Involve users early, get their managers’ commitment in writing and schedule testing time in their diaries.
3. Poor communication and a late team
On one retail project the UAT team was formed only two days before the cycle started, and then there were constant problems with the availability of business users. Coordination becomes harder again when third-party providers or product vendors are involved. Set up communication channels and the UAT team well before the start date.
4. Not enough coverage and depth
A plan that skips important scenarios lets defects through. Build test plans around the real business processes, covering both normal paths and exceptions.
5. Weak defect tracking and reporting
Tracking defects in emails and spreadsheets leads to lost issues and no clear status. Use a proper defect tracking and reporting process, so everyone sees the same list and priorities.
UAT best practices
- Write clear requirements and acceptance criteria before testing starts.
- Involve stakeholders early and confirm their availability for the full cycle.
- Set up clear communication, with a daily stand-up and a single place for status.
- Cover all critical business processes in the test plan, not only the happy path.
- Use a proper defect tracker and triage defects every day.
- Prepare the environment and data properly, and never use a raw copy of production data.
- Close formally, with a summary, a go or no-go decision and written sign-off.
UAT process FAQ
What is the UAT testing process?
It is the process of validating software with end users before go-live, using real-world scenarios and agreed acceptance criteria, to confirm that it meets business needs.
What are the steps of acceptance testing?
Planning, scenario and test case design, test data and environment setup, execution, defect tracking and retesting, reporting, closure and sign-off by the business.
How many steps are there in UAT?
Teams describe it in different ways. A common view is eight steps: plan, define acceptance criteria, design test cases, prepare the environment and data, execute, manage defects, report and sign off. This guide groups them into four phases.
How do you write a UAT test plan?
Define scope, objectives, roles, the environment, the schedule, test data, defect handling and sign-off criteria, and align them with business needs. The UAT template gives a structure to start from.
Who performs UAT?
Business users, domain experts or clients perform UAT, supported by a coordinator and the QA team. Developers fix the defects it finds.
What is a UAT checklist?
A checklist that confirms test cases are covered, data and environment are ready, roles are assigned, defects are managed and sign-off criteria are defined. See our UAT checklist.
Is UAT part of the SDLC?
Yes. It is the final validation phase before deployment.
What is the difference between UAT and QA testing?
QA testing checks technical correctness against the specification. UAT checks that the product solves the users’ real business problem.
What are the UAT exit criteria?
Typically: all critical test cases are executed, no open critical defects, the acceptance criteria are met and business owners have signed off.
How do you make the UAT process faster?
Plan early, keep scope focused on critical business scenarios, run a shake-down test before users arrive, triage defects daily and keep the environment stable. Most delays come from late staffing and unclear criteria, not from the testing itself.
Part of our guide to User Acceptance Testing (UAT). Start with the complete User Acceptance Testing (UAT) guide, or read the related articles:
Want more testing guides in your Google results? Add Testmetry as a preferred source.



