Short answer: user acceptance testing (UAT) is where you check that delivered software works for your business, using your real workflows, before you accept it. The agency tests that the code works. You test that it does the job. Plan a short list of real scenarios, test them on the test environment, report anything that doesn't match, and sign off when the agreed criteria are met.
How UAT differs from the agency's testing
| Agency testing | User acceptance testing |
|---|
| Who tests | Developers and testers | You and the people who'll use it |
| What it checks | The software works as built | The software works for your business |
| Based on | Technical requirements | Your real workflows and acceptance criteria |
| Ends with | A release ready for review | Your sign-off |
Both are needed. Our guide to
outsourcing QA and testing covers the agency's side.
Who should test
The people who'll use the software every day, not only the owner. A warehouse manager will find problems in a stock screen that a director never would. Two or three testers who know the work are usually enough.
Write scenarios, not features
Test the way your business works, from start to finish. A scenario has four parts:
| Scenario | Steps | Expected result | Pass / fail |
|---|
| A customer places an order for two items | Log in as a customer, add two items, check out | Order appears in the admin panel as "New", customer gets a confirmation | |
| A manager approves a discount | Create an order with a discount above the limit, log in as manager, approve | Order moves to "Approved", the approval is recorded with the manager's name | |
Ten to twenty scenarios usually cover a milestone. Include the awkward cases: a wrong entry, a cancelled order, a slow connection, someone without permission trying something they shouldn't.
Data entry safeguards lists mistakes worth testing for.
Test in the right place
- Use the test (staging) environment the agency provides, not the live system.
- Use realistic data: real product names, typical order sizes, long customer names.
- Test on the devices your users actually have, including an older phone.
How to report a problem clearly
A good report gets fixed fast. Include:
- What you were trying to do (the scenario)
- The steps you took
- What you expected to happen
- What actually happened
- A screenshot or short screen recording
- The device and browser or app version
"It doesn't work" can take a day to understand. A report like the one above can often be fixed the same day.
Bug or change?
A
bug is something that doesn't meet what was agreed. It's fixed as part of the milestone. A
change is something you've realised you want differently now that you can see it. Changes are normal and often valuable, but they're planned and agreed separately, so they don't hold up acceptance of work done as agreed. When in doubt, check the acceptance criteria. Our guide to
milestone payments explains how this ties to payment.
Not every problem is equal
- Blocking: a key workflow can't be completed. Must be fixed before sign-off.
- Major: it works, but wrongly or with a painful workaround. Usually fixed before sign-off.
- Minor: wording, alignment, small visual issues. Can be listed and fixed in the next release.
When to sign off
Sign off when every scenario passes or only minor issues remain, and those are written down with an agreed fix date. Signing off doesn't end the agency's responsibility: defects found later are normally covered by the warranty in your contract.
How we handle acceptance
Every milestone comes with a demo, access to a test environment, and the acceptance criteria agreed in the scope. On the scoping call we agree who on your side will test, so UAT is planned from the start rather than squeezed in at the end. Your part in the rest of the project is covered in
your role as the client.
FAQ
What is user acceptance testing?
The final check, by the business and its users, that delivered software works for their real workflows before it's accepted.How long should UAT take?
Agree a review window for each milestone in the contract, often a few working days. Larger releases need longer.Can I skip UAT if the agency has tested everything?
You shouldn't. The agency can check the software works as built, but only your team can confirm it works the way your business does.
Want acceptance built into your project plan from day one?
Book a free scoping call.