UAT Test Script Template, With a Filled-In Example

User acceptance testing (UAT) is where the business checks that the software does what they need, before it goes live. The test script is the record of it: what was tested, what should have happened, what did happen, and who signed it off. Here is a template you can copy, a filled-in example, and a faster way to produce one.

Process improvement · 2026-11-16 · 6 min read

What a UAT test script must contain

FieldWhat to write
Test case IDA unique reference, like UAT-ORD-014, so defects and sign-offs can point to it
TitleThe business task being tested, in plain words: "Refund a paid order"
ObjectiveWhy the test exists: the requirement or user story it proves
PreconditionsWhat must be true before starting: test account, role, data that must exist
Environment and buildWhere and on what version it ran: "Staging, v2.4.0, Chrome 131"
StepsOne action per step, naming the exact button or field
Expected resultWhat should happen after each step, specific enough to judge pass or fail
Actual resultWhat did happen; "As expected" when it matched
StatusPass, Fail, Blocked or Not run, for each step and overall
EvidenceA screenshot of each step, especially failures
Tester, date and sign-offWho ran it, when, and who reviewed and approved it

The template

Copy this into a spreadsheet or document. One row per step; the header fields go once at the top.

Test case ID:      UAT-___
Title:
Objective:
Preconditions:
Environment/build:
Tester:            Date:

#  | Action | Expected result | Actual result | Status | Evidence
1  |        |                 |               |        |
2  |        |                 |               |        |
3  |        |                 |               |        |

Overall result:  Passed / Failed / Blocked
Tested by:       ______________   Date: ______
Approved by:     ______________   Date: ______

A filled-in example: refund a paid order

UAT-ORD-014 · Refund a paid order · Objective: an order manager can refund a paid order to the original card (story SHOP-231). Preconditions: an order manager account; order #5521 exists with status Paid. Environment: Staging, v2.4.0, Chrome.

#ActionExpected resultActual resultStatus
1Open order #5521 from OrdersOrder details open; status shows PaidAs expectedPass
2Click RefundRefund dialog opens with the amount $84.00As expectedPass
3Click Confirm refund"Refund issued" message appearsAs expectedPass
4Check the order statusStatus shows RefundedStatus still shows Paid after reloadFail

Overall: Failed (step 4). The tester logs a defect that points to UAT-ORD-014, step 4, with the screenshot attached. After the fix, the test is run again and signed off.

How to write expected results that are easy to judge

  • Name what you will see, not what the system does inside: "Status shows Refunded", not "Refund is processed".
  • Use the exact UI text: the message, the button, the status label.
  • One check per step. If a step has two expectations, split it, so a failure points at one thing.
  • Include values where they matter: amounts, counts, dates.
  • Write the expected result before you look, so the test cannot quietly "pass" whatever happened.

Evidence and sign-off

Screenshots are what turn a test script into evidence. Auditors and regulated teams (finance, healthcare, life sciences) usually ask for a screenshot of each step, or at least of every failure, plus a named sign-off. Keep the signed PDF with the release, and link the test case ID from your defects.

The faster way: record the test once

Filling this in by hand means pausing after every click to take and paste a screenshot. Instead, record your screen while you run the test. AI Flowchart keeps a screenshot each time the screen changes, writes each step's action and expected result from what happened, and gives you the test case with Pass/Fail per step, the overall result and the sign-off block. Export it as a PDF for sign-off, or as a CSV for TestRail or Jira.

Record a test run, free →

Frequently asked questions

What is the difference between a UAT test script and a test case?

They are often used for the same thing. A test case is one scenario with its steps and expected results; a UAT test script is the test case as run by a business user, with actual results, status, evidence and sign-off.

Who signs off UAT?

Usually the business owner or product owner for the feature, sometimes with a QA lead. The tester signs as the person who ran it, and the approver signs that the results are accepted.

Do I need a screenshot for every step?

It depends on your team or auditor. Many regulated teams require one per step; others only for failures and the final result. Recording the test captures every step anyway, so you can keep what you need.

Can I import the test case into TestRail or Jira?

Yes. AI Flowchart exports a CSV with one row per step (test case ID, title, preconditions, action, expected result, actual result, status, screenshot link) that TestRail and Jira test tools such as Xray and Zephyr can map on import.

Keep reading

← All guides

Try AI Flowchart free →