UAT Email Templates: 7 Emails From Invitation to Sign-Off

Last updated: November 6, 2026

A UAT round usually needs seven emails: an invitation, test instructions, a reminder, a retest request, a sign-off request, a conditional sign-off, and a confirmation. Each template below is ready to copy. Most of the work is filling in four things: the link, the deadline, who decides, and what happens next.

UAT (user acceptance testing) is where the intended users decide whether to accept the result. It often runs on email, because the clients and business users doing it are rarely in your tracker. The templates we found online mostly stop at the sign-off request, so this set covers the whole round, in the order you send them, with wording that works for a client website project. For the wider process, see what user acceptance testing means.

Which UAT Email to Send When

Email	Send it	Who gets it	What it must say
1. Invitation	As soon as the dates are set	Testers and the decider	Dates, time needed, and who decides
2. Instructions	The day testing opens	Testers	Link, login, tasks, how to report, deadline
3. Reminder	Before the deadline	Anyone who has not replied	What is left, and a one-line way to finish
4. Retest request	When fixes are on staging	Whoever reported each issue	What changed and what to recheck
5. Request sign-off	When blockers are fixed and retested	The decider	Results, open items, and a date to answer by
6. Conditional sign-off	When they accept with caveats	The decider	Each condition, its owner, and its date
7. Confirmation	When the decision is in	Everyone involved	Who approved, when, and what happens next

The 7 UAT Email Templates

Replace everything in brackets. Send emails 3 and 4 as replies, so the whole round stays in one thread.

1. UAT Invitation Email

Send this as soon as you know the dates, so people can keep the time free. Naming the decider now stops a late argument about whose answer counts.

Note: Subject: Can you test [project] from [start date] to [end date]?

Hi [Name],

[Project] is nearly ready, and we need you to check that it does what you need before it goes live on [launch date].

Testing runs from [start date] to [end date] and should take about [time]. You do not need to install anything or write a test plan. We will send a link and a short list of tasks on [start date].

Can you do it? If not, please tell me who should. [Decider] will make the final call on whether it is ready.

Thanks,
[Your name]

2. UAT Instructions Email

Send this the day testing opens. Saying what is not ready yet saves you a list of comments about placeholder pages.

Note: Subject: UAT is open for [project]: please finish by [deadline]

Hi [Name],

Testing is open. Here is what you need:

Link: [staging link]
Login: [test account, or none needed]
Please try: [task 1], [task 2], [task 3]
Not ready yet: [what to ignore]

Tell us about anything that stops a task or looks wrong by [how to report]. For each one, say which page you were on and what you expected. Screenshots help.

Please finish by [deadline], so we have time to fix what you find before [launch date].

Thanks,
[Your name]

3. UAT Reminder Email

Send this as a reply a day or two before the deadline. A short answer and a different reviewer give them two easy ways out of the silence.

Note: Hi [Name],

Testing closes on [deadline], and I have not seen anything from you on [task or page] yet.

A short reply is enough. "All good" counts. If you cannot get to it, tell me who can and I will send it to them.

Thanks,
[Your name]

If the date passes, say what happens next before it happens: who you will ask instead, and what moves if nobody answers. BesTest's advice is to escalate to the project sponsor once the deadline has gone. Do not treat silence as approval unless your contract says so.

4. UAT Retest Request Email

Send this when fixes reach staging, as a reply to the person who reported each issue. Saying what you decided not to change, and why, heads off the same comment coming back.

Note: Subject: Re: UAT is open for [project]: [number] fixes to recheck

Hi [Name],

We have fixed what you reported. Please recheck these on [staging link] by [date]:

1. [Issue]: [what changed]
2. [Issue]: [what changed]

We left [item] as it is because [reason]. Tell me if that is a problem.

Reply "fixed", or tell me what still looks wrong.

Thanks,
[Your name]

5. UAT Sign-Off Request Email

Send this to the decider once blockers are fixed and retested. Three named answers make it easy to reply, and open items stated here cannot come back as a surprise.

Note: Subject: Sign-off needed by [date]: UAT for [project]

Hi [Name],

Testing for [project] is finished, and we need your decision by [date] to go live on [launch date].

Tested: [what was tested], by [who], from [start date] to [end date]
Result: [number] issues found, [number] fixed and retested, [number] still open
Still open: [issue, why it can wait, when it will be fixed]

Please reply with one of these:

1. Approved: go ahead.
2. Approved with conditions: go ahead once [you name them].
3. Not approved: [what has to change first].

Thanks,
[Your name]

6. Conditional Sign-Off Email

Send this when they approve with caveats. Writing the conditions back gives each one an owner and a date, and gives them the chance to correct you.

Note: Subject: Re: Sign-off needed by [date]: your conditions

Hi [Name],

Thanks for reviewing [project]. You approved it on these conditions:

1. [Condition], owned by [name], done by [date]
2. [Condition], owned by [name], done by [date]

Accepted as it is for now: [item], to be fixed in [release].

Please reply to confirm this is right. We will go ahead on [launch date] once you do.

Thanks,
[Your name]

7. UAT Sign-Off Confirmation Email

Send this to everyone involved when the decision is in. It closes the round and leaves one message that says who approved what.

Note: Subject: UAT signed off: [project] goes live on [date]

Hi everyone,

[Name] approved [project] on [date], [with no conditions / with the conditions below].

Next: [launch step] on [date], owned by [name]
Still open: [items and dates]
Sign-off record: [where it is kept]

Thanks to [testers] for testing.

[Your name]

A Filled-In Sign-Off Request

Here is email 5 for a website rebuild. This is an illustration, not a real project.

Note: Subject: Sign-off needed by Thursday: UAT for the new booking site

Hi Sam,

Testing for the new booking site is finished, and we need your decision by Thursday to go live on Monday.

Tested: booking, the contact form, and the pricing page, on phone and desktop, by Ana and Lee, from May 4 to May 8
Result: 11 issues found, 10 fixed and retested, 1 still open
Still open: the map loads slowly on phones. It does not stop a booking, and the fix is planned for the week after launch.

Please reply with one of these:

1. Approved: go ahead.
2. Approved with conditions: go ahead once you name them.
3. Not approved: tell us what has to change first.

Thanks,
Jo

Is an Email Reply Valid UAT Sign-Off?

Guides disagree. BesTest's request template says "a reply to this email with your decision is sufficient". QAPractices lists accepting email approval as a mistake: "not a record; disputes arrive later".

Both have a point. A reply is a dated, written answer from a named person, but it can sit in one inbox, and it proves little if the email did not say what was tested. If your contract or a regulator asks for a signature, use that. Otherwise, a reply works best when the request lists what was tested and what is still open, and when you file the reply where the rest of the team can find it. Email 7 does that second part.

How to Collect the Feedback These Emails Ask For

Email suits the decision. It suits the feedback less, because a comment about a page arrives without the page. Agree on where comments go before email 2 goes out, and if you are asking a client, these client feedback templates cover the earlier review rounds.

In OverlayQA, you create a client link for the page, and we can email it to each client for you. They comment on the page in any browser with no account, each comment becomes an issue in your project with the screenshot attached, and they can press Done reviewing when they have finished. There is no approval step on each issue, so email 5 still handles the sign-off. For other options, see the best UAT testing tools.

Frequently Asked Questions

How do you write a UAT email?

Say what you need, from whom, and by when, then say what happens next. Put the deadline in the subject line. Keep links and logins on their own lines, so a tester can find them again without rereading the whole email.

How do you ask for UAT sign-off by email?

Say that testing is finished, summarize what was tested and what is still open, and ask for one of three answers by a date: approved, approved with conditions, or not approved. Email 5 above has the wording.

When should you send a UAT invitation?

As soon as the dates are set, so people can keep the time free and you find out early if someone cannot do it. Send the instructions separately on the day testing opens, so the link and login are at the top of their inbox when they need them.

What should a UAT sign-off email include?

The project and release, the test dates, who tested, the number of issues found, fixed, and still open, a reason each open issue can wait, the date you need an answer by, and the answers you will accept. Clear acceptance criteria make that summary much easier to write.

Who should send UAT emails?

Whoever runs the round, usually the UAT lead or project manager, so replies reach one person. On a client project, that is often the account lead. The sign-off request goes to the person named as the decider in the invitation, not to every tester.

What if a stakeholder does not reply to a UAT email?

Send the reminder, and offer a one-line answer or a different reviewer. If the deadline passes, tell them what happens next, then ask the project sponsor. Do not count silence as approval unless your contract says it counts.

Can UAT be signed off with open issues?

Yes, if the decider accepts them knowingly. That is what email 6 is for: it records each open item, who owns it, and when it will be fixed. A blocker stays a blocker until it is fixed and retested.

Do you still need a UAT sign-off document?

It depends on the project. For a small website, the request and its reply may be enough if both of you agree. Regulated work, or a contract that ties payment to acceptance, usually needs a formal document, and the email then goes with it rather than replacing it.

Collect UAT comments on the page itself. With OverlayQA, clients comment with no account, each comment becomes a tracked issue with the screenshot attached, and they can tell you when they have finished reviewing.