UAT Sign-off Form


Phase: Monitoring and controlling | Audience: Shared | Project: WEB-2026-01 Corporate Website Development


Understand it first

In simple words: The UAT Sign-off Form is the client's formal acceptance after testing. It confirms the website meets the criteria and can go live, and triggers the third payment (M3).

Think of it like: After the test drive and inspection, you sign the delivery note saying the car is accepted.


When is it created?

End of UAT (4 Dec 2026)

Who prepares it?

Project Manager prepares

Who approves or uses it?

Client Head of Marketing signs

What happens next?

Go-live; M3 invoice raised


How it connects to other documents

  1. Summarises results of the UAT Test Cases.
  2. Exit rules come from the Quality and Test Plan.
  3. Triggers M3 in the Invoice Tracker.


The sample document

Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.

Issued by: [Your Company] Technologies Pvt. Ltd.

Purpose: Client acceptance of the website after user acceptance testing. Signing completes deliverable D4 and triggers the M3 invoice. To be completed on 4 Dec 2026.


Item


Detail


Document no.

WEB-2026-01/UAS

Version

1.0

Date

4 Dec 2026

Owner

Project Manager

Audience

Shared with client

Phase

Monitoring and controlling

Status

Pending


1. Test summary

Measure


Value


Test period

1–4 Dec 2026

Test cases executed

__ of 15

Passed

__

Failed and fixed

__

Failed and open

__


2. Open defects at sign-off

Severity


Count


Allowed at sign-off


Critical

__

0

High

__

0

Medium

__

Up to 3, with fix dates

Low

__

Any, listed below


3. Known issues accepted

ID


Description


Severity


Fix by











4. Declaration

I confirm that user acceptance testing has been completed, the website meets the agreed acceptance criteria, and it may be deployed to production. Any known issues listed above will be fixed by the dates shown.

Signed for


Signature


Date


Head of Marketing, [Client Name]

Name and signature: ____________

Date: ________

Project Manager

Name and signature: ____________

Date: ________


WEB-2026-01/UAS · v1.0 · Shared with client. Bracketed items such as [Client Name] are placeholders.


Key takeaways

  1. No critical or high defects allowed at sign-off.
  2. Known minor issues can be accepted with fix dates.
  3. It is a key payment trigger.


Common mistakes to avoid

  1. Going live without signed UAT.
  2. Not listing accepted known issues.
  3. Leaving blanks unfilled.


Next lesson: 35. Go-Live Checklist