User Acceptance Testing (UAT): A Client Guide
User Acceptance Testing (UAT) is your formal opportunity to verify that what we have built meets your requirements before it goes live. This guide explains how to prepare and run UAT effectively.
The Purpose of UAT
UAT is not about finding code bugs (we do that internally). It is about validating that the system behaves correctly for your business — that workflows match your expectations, that data flows correctly, and that the system is fit for purpose from your users' perspective.
Preparing for UAT
- Appoint a UAT Lead from your team who will co-ordinate the testing effort
- Identify the right testers — ideally people who will actually use the system, not just technical reviewers
- Review the acceptance criteria in your SoW or sprint backlog — these are the items you are testing against
- Prepare test cases or test scenarios in advance if possible
- Ensure you have access to the staging environment (credentials from your Project Manager)
Running UAT
- Work through each feature systematically, following realistic user journeys
- Log every issue — even minor cosmetic ones — in the portal or the shared UAT tracker
- For each issue, describe: what you expected, what happened, and the steps to reproduce
- Attach screenshots or screen recordings where possible
- Mark items as Pass / Fail / Needs Clarification
UAT Timeframes
We typically allow 3–5 business days for UAT on a sprint delivery, and 5–10 business days for a major release. If you need more time, let your Project Manager know as early as possible. UAT cannot be indefinitely extended without timeline impact.
Sign-Off
UAT sign-off means you are confirming the system is ready for production deployment. Sign-off must be in writing (portal confirmation or email). Once production deployment occurs, any changes become change requests.