Glossary
UAT (User Acceptance Testing)
UAT (User Acceptance Testing) is the final testing stage, where the people who will use new software test it on real tasks and real data before it goes live. It confirms the software supports the business, not just that the code works, and it is the point where the business formally signs off.
Key Facts
| Who tests | The staff who will use it daily, plus a decision-maker |
|---|---|
| Typical duration | 1–3 weeks depending on scope |
| Test with | Real scenarios, realistic data, edge cases and month-end processes |
| Exit criteria | No critical issues open, agreed fixes scheduled, written sign-off |
How to run UAT well
- Write scenarios from real work: "create a quote with a 12% discount for a new dealer".
- Use realistic data, including awkward cases.
- Record issues with steps, screenshots and expected results.
- Classify issues as critical, major or minor, and agree what must be fixed before launch.
See user acceptance testing: how business owners should sign off software.
Frequently Asked Questions
Can the developer do UAT?
No. Developers test that it works as built; UAT tests that it works for the business, so users must do it.
What if UAT finds many issues?
That is UAT doing its job. Prioritise, fix the critical ones, and delay launch rather than go live with broken core flows.
Related Glossary
Take the next step
Need help implementing this in your business?
Turbo Bytes Consulting helps businesses streamline operations and build custom software architectures that scale without chaos.