Software UAT checklist
Have business users accept agreed tasks, exceptions, permissions, integrations and handover with recorded evidence.
Author：WeTech technical team · Updated： (Hong Kong time (GMT+8))
UAT establishes whether users can complete work under agreed rules. Record requirement-linked scenarios, data, expected and actual results, issue severity and sign-off owner. Passing development tests does not replace business acceptance, and unresolved issues need an explicit release decision.
When to use this guide
For business and procurement teams preparing a custom-system launch, supplier change or acceptance pack.
UAT scenario checklist
| Scenario | Test | Evidence |
|---|---|---|
| Normal work | End-to-end creation to completion | Sample, result, version |
| Exceptions | Blank, boundary, cancel, duplicate | Expected message and state |
| Access | Different and revoked roles | Allowed and denied records |
| Operations | Integration failure, recovery, handover | Incident record and owner confirmation |
Define expected results before testing
Use suitable de-identified or synthetic data and have business owners approve calculations and states first. Do not rewrite expectations after seeing the output merely to make a test pass. Requirement changes need a revised baseline and affected tests with recorded reasons.
Separate defects from additions
Compare issues with the agreed brief to distinguish nonconformance, ambiguity and new requests. Record steps, affected roles, version and evidence. After a fix, retest the related task; a developer marking an issue resolved is not business acceptance.
Make sign-off explicit
Sign-off should list accepted scope, open issues, accepted limitations, owners and deadlines. Confirm migration, backup, operating documentation and production accounts separately so completed screens do not hide unready data. Assign the release decision to a named owner.
Illustrative scenario
Hypothetical UAT: test order creation, cancellation, duplicate submission, manager permissions and accounting outages. Duplicate posting can block release while minor wording changes receive a separate deadline. The severity rules must be agreed for the actual project.
Frequently asked questions
Can the supplier perform all acceptance?
Business users must still validate workflow rules and expected outcomes.
Does UAT require real payments?
Prefer isolated environments and test or intercepted interfaces to avoid real transactions.
Must everything be retested after a fix?
Retest affected workflows and critical controls, expanding by the change impact.
Brand and public case scope
WeTech Consulting, also called WeTech or WeTech AI HK, provides AI and IT consulting in Hong Kong. WeProperty HK and WeCredit HK are self-developed products. Their cases support the observable features listed: property, estate and transaction-reference entry points for WeProperty; submission, review and public-data masking for WeCredit. WeCredit is not a TU credit-rating service or a final determination of facts.
WeProperty HK · WeCredit HK (case studies in Traditional Chinese)
Reference sources
Official documents support the technical, risk and measurement concepts. Checklists, estimation methods and illustrative scenarios are WeTech planning recommendations, not official prices or client results. Check the supplier’s current plan and terms. Sources reviewed: (GMT+8)
Related guides
Discuss your project
Share your workflow, systems and goals. We will review scope before discussing deliverables, acceptance and a quotation.
Request an initial consultationExplore this service