# UAT sign-off template


Copy the tables below into a document or spreadsheet and replace everything in square brackets. Keep one UAT sign-off document per release, not per project, so each approval points at a specific build.

For smaller releases, the same UAT sign-off template works as a short release sign-off form or a website sign-off template: keep sections 1, 4, 5 and 8, and drop the rest.

**Section 1 · Project and release**

| Field | Details |
|---|---|
| Product owner | [Name, and the team or business unit that owns the product] |
| Project | [Project name] |
| Release | [Release name or version, for example Phase 1 launch or v1.4.0] |
| Delivery team and lead | [Team name, lead's name] |
| Ticket or contract reference | [Epic, ticket or change request number, or the contract reference where one applies] |
| UAT window | [Start date] to [end date] |

**Section 2 · Scope tested**

| Field | Details |
|---|---|
| Journeys and features | [For example: book a consultation, checkout, account area] |
| Pages or templates | [For example: home, service, product, basket, contact] |
| Requirements covered | [Links to requirements, specifications or tickets] |
| Changes since last sign-off | [List, or first release] |

**Section 3 · Environment and build**

| Field | Details |
|---|---|
| Environment and URL | [Staging or UAT URL] |
| Build tested | [Build number, commit or deployment ID] |
| Browsers and devices | [As agreed, for example current Chrome, Safari, Firefox and Edge; Safari on iPhone; Chrome on Android] |
| Test data and accounts | [Test accounts used; confirm no real customer data] |
| Integrations in test mode | [For example payments in sandbox, CRM test pipeline] |
| QA evidence | [Link to the QA or evidence report for this build] |

**Section 4 · Acceptance criteria and results**

| ID | Acceptance criterion | Result | Evidence | Tested by, date |
|---|---|---|---|---|
| AC1 | [Example: a visitor can book a consultation for any open slot and receives a confirmation email within five minutes] | [Pass / Fail / Needs input / Not tested] | [Link or screenshot] | [Name, date] |
| AC2 | [Example: product prices include VAT and match the approved price list] | [Result] | [Link] | [Name, date] |
| AC3 | [Example: checkout can be completed with a keyboard alone] | [Result] | [Link] | [Name, date] |
| AC4 | [Criterion] | [Result] | [Link] | [Name, date] |

**Section 5 · Open issues**

| Issue | Summary | Severity | Status | Agreed action and date |
|---|---|---|---|---|
| [ID] | [Short description, with a link to the ticket] | [Critical / Major / Minor / Cosmetic] | [Open / Fixed, awaiting retest] | [Fix before launch / Fix by date after launch / Accepted as is] |
| [ID] | [Summary] | [Severity] | [Status] | [Action, date] |

**Severity scale · agree it before UAT starts**

| Severity | Meaning | Suggested rule for sign-off |
|---|---|---|
| Critical | A key journey is blocked, data is lost or wrong, or there is a security or legal risk | Fix and retest before launch |
| Major | A feature fails or misbehaves, and the workaround is painful | Fix before launch unless the approver accepts it in writing |
| Minor | Works, with a small problem and an easy workaround | Launch with a dated fix plan |
| Cosmetic | A visual or copy detail that does not affect use | Batch into a later release |

**Section 6 · Not tested**

| Item | Reason | Risk and follow-up |
|---|---|---|
| [Example: load testing] | [Out of scope for this release] | [Plan before the spring campaign] |
| [Example: live payments] | [Test mode only during UAT] | [Smoke test on production after launch] |
| [Item] | [Reason] | [Follow-up] |

**Section 7 · Conditions of acceptance**

| Condition | Owner | Due |
|---|---|---|
| [Example: issues 3 and 7 fixed and retested before go-live] | [Delivery team] | [Date] |
| [Example: final privacy notice text supplied] | [Product owner] | [Date] |
| [Condition] | [Owner] | [Date] |

**Section 8 · Decision**

| Item | Details |
|---|---|
| Decision | ☐ Accepted ☐ Accepted with the conditions in section 7 ☐ Not accepted (reasons attached) |
| Statement | By signing, the approver confirms that the release and build described above have been tested against the criteria in section 4, and accepts it on the terms in sections 5 to 7. |

**Section 8 · Signatures**

| Role | Name | Organisation | Signature | Date |
|---|---|---|---|---|
| Approver: product owner (authorised to accept) | [Name] | [Team or business unit] | [Signature] | [Date] |
| Stakeholder (optional) | [Name] | [Team or business unit] | [Signature] | [Date] |
| Delivery lead | [Name] | [Delivery team] | [Signature] | [Date] |

---

## Join the waitlist

ShipperAG is recruiting tech and product teams building their own products for an invite-only pilot. [Join the waitlist](https://shipperag.com/?utm_source=release-kit&utm_medium=download&utm_campaign=oct26-pilot#join). Joining does not guarantee admission.

How to run UAT sign-off, write acceptance criteria an approver can sign, and avoid common pitfalls: [the full guide on shipperag.com](https://shipperag.com/uat-sign-off-template/?utm_source=release-kit&utm_medium=download&utm_campaign=oct26-pilot). Licensed CC BY 4.0.