# What Is UAT? Meaning, Types, Process, and Examples > UAT is software testing by end users before release. Learn its meaning, types, process, SIT vs UAT, a sample test scenario, and what a UAT document covers. **URL:** https://www.ciptadusa.com/blog/uat-adalah **Type:** blog **Author:** PT Cipta Dua Saudara **Category:** Engineering **Published:** 2026-10-19 **Cover:** https://www.ciptadusa.com/media/uploads/blog/2026-10/1792376219376-uat-adalah-20261019.webp ## Article UAT stands for User Acceptance Testing: the stage of software testing in which end users or business representatives try an application in real-world scenarios to confirm it meets their needs before release. TechTarget notes that UAT is also called application testing or end-user testing, and places it at the end of the testing process, before the software goes into production ([TechTarget](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)). The outcome is a decision: the application is accepted, or it still needs fixes. This article covers what UAT means, its purpose and who performs it, how it compares with SIT and other testing, the types of UAT, the steps to run it, how to write acceptance criteria, a sample UAT scenario and document, and the challenges to plan for. ## What Is UAT (User Acceptance Testing)? According to TechTarget, UAT is a phase of software development in which the software is tested in the real world by its intended audience. The goal is to make sure the software can handle real-world tasks and perform up to development specifications ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)). The Acceptance Testing syllabus from ISTQB, the international software testing certification board, lists UAT as one form of acceptance testing, alongside contractual and regulatory acceptance testing and alpha and beta testing ([ISTQB, PDF](https://istqb.org/wp-content/uploads/2024/11/ISTQB-CT-AcT_Syllabus_v1.0_2019.pdf)). The difference between UAT and other testing lies in the question each one answers: - **Technical testing** (unit, integration, and system tests) asks whether the software was built correctly against the specification. - **UAT** asks whether users can actually use the software to get their work done. TechTarget explains that software can pass every other testing phase and be fully functional, yet still miss its requirements if its intended users do not accept it. Causes include requirements that were not clearly defined for developers, scope changes during development, or software that was not ready for a real-world environment ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)). ## The Purpose of UAT Based on TechTarget's description, UAT serves several purposes ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)): - **Validating business requirements.** When successful, UAT shows that the software meets the defined business requirements. - **Finding issues earlier tests missed.** Users try features with real cases and data, which can surface overlooked features or undetected bugs. - **Preventing faulty, ineffective, or unfinished releases.** Without UAT, software risks shipping with bugs or without a clearly defined goal for end users. - **Increasing transparency with users.** Users see and try the product before its official release. For software built by a vendor, UAT is also the handover point. TechTarget writes that after QA testing, the development organization delivers the product to its client, whose testers run real-world scenarios and sign off when the product meets their requirements ([source](https://www.techtarget.com/it-infrastructure/answer/Quality-assurance-testing-vs-user-acceptance-testing)). ## Who Performs UAT? End users perform UAT, because they know exactly how the software will be used day to day and what changes it needs to fit that daily use. Internal functional experts also help shape UAT cycles, manage the tests, and interpret the results ([TechTarget](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)). On a project, the roles involved can be broken down like this (an illustration of how roles can be split, not a fixed standard): - **Key users from each department**, such as sales admins, warehouse staff, or the finance team, who run the test scenarios. - **A product owner or business process owner** who sets the acceptance criteria and makes the final call. - **A business analyst or QA** who prepares scenarios and test data and records findings. - **The development team**, which fixes findings and prepares a new build for retesting. ISTQB stresses that designing acceptance tests from acceptance criteria should be a collaborative effort between business analysts and testers, so the acceptance testing phase delivers business value and reduces release risk ([ISTQB, PDF](https://istqb.org/wp-content/uploads/2024/11/ISTQB-CT-AcT_Syllabus_v1.0_2019.pdf)). ## Where UAT Fits in Software Testing TechTarget places UAT after unit testing, quality assurance, system testing, and integration testing ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)). In the software development life cycle, it sits in the testing stage before deployment. For the full set of stages, see [What Is SDLC?](https://www.ciptadusa.com/en/blog/sdlc-adalah). ### SIT vs UAT SIT (System Integration Testing) and UAT both happen close to release, but their goals and testers differ. According to TechTarget, SIT checks that all software and hardware components work as expected as one complete system, and it is run by QA teams, not users. The SIT phase comes before UAT ([TechTarget](https://www.techtarget.com/it-infrastructure/answer/What-is-the-difference-between-SIT-and-UAT)). | Aspect | SIT | UAT | | --- | --- | --- | | Main question | Do all components connect and work as one system? | Can the system be used for users' real work? | | Performed by | QA team or testers | End users and business representatives | | Focus | Data flow and interaction between components | Business processes and user needs | | Timing | Before UAT | After SIT, close to release | | Output | A list of technical defects | Findings and an accept or not-yet decision | Table source: summarized from [TechTarget](https://www.techtarget.com/it-infrastructure/answer/What-is-the-difference-between-SIT-and-UAT) and [TechTarget](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT). TechTarget also notes that there are no industry standards for UAT or SIT, so how they are run varies from project to project ([source](https://www.techtarget.com/it-infrastructure/answer/What-is-the-difference-between-SIT-and-UAT)). That is why the scope and criteria for UAT should be agreed at the start of a project. ## Types of UAT TechTarget groups several kinds of testing under UAT ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT), [source](https://www.techtarget.com/it-infrastructure/answer/What-is-the-difference-between-SIT-and-UAT)): ### 1. Alpha Testing and Beta Testing In alpha testing, users or user groups test the software early in the cycle to find bugs during development. Beta testing comes later, releasing the product into the customer's environment to gather wider feedback. ISTQB associates beta testing with commercial off-the-shelf (COTS) products and SaaS platforms. It is performed by potential or existing users at their own locations. ISTQB also cautions that acceptance testing should not rely on beta testing alone, because beta testing is not systematic or measurable and does not guarantee that all requirements are covered ([ISTQB, PDF](https://istqb.org/wp-content/uploads/2024/11/ISTQB-CT-AcT_Syllabus_v1.0_2019.pdf)). For more on the SaaS model, see [What Is SaaS?](https://www.ciptadusa.com/en/blog/saas-adalah). ### 2. Black Box Testing Users test specific functions without seeing the code inside. They judge the product only through their interaction with it. ### 3. Contract Acceptance Testing The software is tested against the criteria and specifications written into the contract between vendor and client. This type is relevant for [custom software development](https://www.ciptadusa.com/en/services/software) projects delivered by a third party. ### 4. Regulation Acceptance Testing Also called compliance acceptance testing, this checks that the software meets legal rules or the user's compliance needs. ### 5. Operational Acceptance Testing (OAT) The focus is operational readiness, such as compatibility, reliability, and stability. The client organization also assesses its own readiness to use the software, including employee training, software maintenance, and how failures are handled. Post-release maintenance is covered in [app maintenance cost per month](https://www.ciptadusa.com/en/blog/biaya-maintenance-aplikasi). ## UAT Process Steps The number of UAT steps varies with how granular a team wants to be. TechTarget summarizes the process in five steps ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)): 1. **Plan.** Define the business requirements to test, the timeline, and the UAT strategy. 2. **Create real-world test scenarios.** Scenarios should cover as many of the functional cases users will face as possible. 3. **Select the testing team.** Testers need to understand the business and know how to find and report issues. 4. **Test and document.** Users run the tests and log bugs in a bug tracker, with notes on how to reproduce them. 5. **Fix, retest, and sign off.** Developers fix the findings, tests are repeated, and testers sign off once the software meets their criteria. The software is then ready for production. On contract projects, the sign-off in step five can be recorded in a written document agreed by both parties, so it is clear which version was accepted and which findings move to a later phase. ## How to Write Acceptance Criteria Good UAT starts from clear acceptance criteria. ISTQB defines acceptance criteria as measurable statements that can be either true or false, used to check whether a requirement or user story has been implemented as expected. The criteria define what to test, while test cases describe how the testing is done ([ISTQB, PDF](https://istqb.org/wp-content/uploads/2024/11/ISTQB-CT-AcT_Syllabus_v1.0_2019.pdf)). According to ISTQB, good acceptance criteria are: - Precise, measurable, and concise, so a tester can judge pass or fail. - Free of technical solution details, focused on what must be achieved. - Inclusive of both functional and non-functional requirements. Atlassian adds that acceptance criteria should be defined before development begins, and written together with the product owner, the development team, and other stakeholders ([Atlassian](https://www.atlassian.com/work-management/project-management/acceptance-criteria)). ### The Given-When-Then Format ISTQB describes the Given-When-Then pattern for writing test cases in a structured language every party can understand ([ISTQB, PDF](https://istqb.org/wp-content/uploads/2024/11/ISTQB-CT-AcT_Syllabus_v1.0_2019.pdf)): - **Given:** the starting situation before the test. - **When:** the user's action on the system. - **Then:** the observable result of that action. Example (illustration): Given a salesperson is logged in and has one lead with the status "New", When they change the lead's status to "Negotiation", Then the new status appears in the lead list and is recorded in the activity history. ## UAT Example: Scenarios for a CRM Application Below is a sample set of UAT scenarios for the leads module of a CRM application. It is an illustration of the format, not the result of a real project. For what CRM is and its modules, see [What Is CRM?](https://www.ciptadusa.com/en/blog/crm-adalah). | ID | Scenario | Steps | Expected result | Status | | --- | --- | --- | --- | --- | | UAT-01 | Add a new lead | Open Leads, enter name, phone number, and source, then save | The lead is saved and appears in the list with the status "New" | Pass / Fail | | UAT-02 | Required field validation | Save a lead without a phone number | The system rejects it and shows a message that the phone number is required | Pass / Fail | | UAT-03 | Change lead stage | Move a lead from "New" to "Negotiation" | The stage changes and is recorded in the activity history | Pass / Fail | | UAT-04 | Access rights | Log in as salesperson A and search for a lead owned by salesperson B | Matches the agreed access rule, for example salesperson B's lead is not visible | Pass / Fail | | UAT-05 | Reporting | Open the pipeline report for the current month | Lead counts per stage match the data entered during testing | Pass / Fail | Scenarios like these work best in the language of business processes rather than technical terms, because users are the ones running them. For broader systems such as [ERP](https://www.ciptadusa.com/en/blog/erp-adalah), scenarios can be organized per process, for example from sales order to invoice. ## What a UAT Document Contains There is no single format for a UAT document. Based on the steps and practices TechTarget describes ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)), a UAT document can include the following (a sample structure; adapt it to your project): - **UAT plan:** goals, the processes in scope, schedule, participants, and test environment. - **Acceptance criteria:** the conditions the application must meet to be accepted. - **Scenarios and test cases:** steps, test data, conditions, and expected results. - **Findings log:** bugs or feedback with reproduction steps, priority, and fix status. - **Retest results:** a record that findings were fixed and tested again. - **Sign-off sheet:** a statement that the application meets business requirements, signed by the authorized party. ## UAT Challenges and How to Plan for Them TechTarget lists four challenges in UAT ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)): - **Poor test planning.** Because UAT comes at the end of the cycle, delays in earlier stages squeeze the time left for it. Allocate UAT time when you build the project schedule. - **The wrong testers.** Untrained testers may not know how to report bugs, which makes issues hard to reproduce. Train testers before UAT begins. - **Test environment.** Reusing the environment from functional and system testing can hide dependencies on that environment. Use a separate environment for UAT. - **Communication gaps.** Poor communication between UAT testers and the testing team delays bug reporting. Agree on a reporting channel and a schedule for reviewing findings. One more point to watch: a UAT finding can be a new feature request rather than a bug. Keep the two separate in the findings log so project scope and cost stay under control. Project cost components are covered in [how much a web app costs](https://www.ciptadusa.com/en/blog/biaya-pembuatan-aplikasi-berbasis-web). If you are building the first version of a product, read [What Is an MVP?](https://www.ciptadusa.com/en/blog/mvp-adalah) as well. ## FAQ ### What does UAT stand for? UAT stands for User Acceptance Testing: testing by end users to confirm the software meets real needs before release ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)). ### What is the difference between SIT and UAT? SIT is run by the QA team to confirm all components work as one system, while UAT is run by users to confirm the system fits business needs. SIT comes before UAT ([source](https://www.techtarget.com/it-infrastructure/answer/What-is-the-difference-between-SIT-and-UAT)). ### Who performs UAT? End users, supported by internal functional experts who shape the UAT cycles and interpret the results ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)). ### What are the types of UAT? The types TechTarget names include alpha and beta testing, black box testing, contract acceptance testing, regulation acceptance testing, and operational acceptance testing ([source](https://www.techtarget.com/it-infrastructure/answer/What-is-the-difference-between-SIT-and-UAT)). ### What goes into a UAT document? A UAT plan, acceptance criteria, scenarios and test cases, a findings log, retest results, and a sign-off sheet. The structure can be adapted to each project. ### What happens after UAT? Once the acceptance criteria are met and findings are fixed, testers sign off and the software is ready for production ([source](https://www.techtarget.com/it-infrastructure/definition/What-is-user-acceptance-testing-UAT)). After release, the application moves into maintenance. ## Run Your Software Project with Planned UAT, with CDS PT Cipta Dua Saudara helps businesses define requirements and acceptance criteria through [IT consulting](https://www.ciptadusa.com/en/services/consulting), then builds web and mobile applications through [custom software development](https://www.ciptadusa.com/en/services/software), with UAT as part of the handover process. We also build our own products such as [Zetta CRM](https://www.ciptadusa.com/en/incubating/zetta-crm). See [our work](https://www.ciptadusa.com/en/works), or read the [guide to choosing a software development partner in West Java](https://www.ciptadusa.com/en/blog/pilih-jasa-pembuatan-software-jawa-barat-20260907) and [when a business needs custom software](https://www.ciptadusa.com/en/blog/kapan-bisnis-butuh-software-custom-2026) before you start a project. --- *Markdown version of https://www.ciptadusa.com/blog/uat-adalah — generated for AI agents and LLM crawlers.*