View/Export Results
Manage Existing Surveys
Create/Copy Multiple Surveys
Collaborate with Team Members
OR
Sign inSign in with Facebook
Sign inSign in with Google

UAT questionnaire and feedback form for business testers

Sixteen questions for the testers who worked your scripts, ending in a go or no-go verdict.

  • 16questions
  • About 4 minto answer
Use this template Answer it first
UAT Feedback Survey · answer to move through it
Use this template
Question 1 of 16 Who tested, and what
Which of these best describes your part in this UAT test cycle?
I do this work every day
I approve or sign off this process
I know the rules behind it
I set up roles or configuration
I support people who do this work
Something else
Question 2 of 16 Who tested, and what
Which area or process did you test in this cycle?
Area one
Area two
Area three
Area four
More than one
I was not told
Question 3 of 16 Who tested, and what
Where did you do the testing?
The dedicated test environment
A staging or pre-production copy
A training or demonstration copy
The live system, using test records
I am not sure
Question 4 of 16 Who tested, and what
About how long did you spend testing in total?
Under an hour
One to three hours
Half a day
A full day
More than a day
I could not say
Question 5 of 16 Did it do the job
Did you complete the tasks you were given, from start to finish?
Yes, all of them
Most of them
About half
Hardly any
None of them
I had no tasks
Question 6 of 16 Did it do the job
What, if anything, stopped you finishing a task?
Question 7 of 16 Did it do the job
The system gave the right answers for all the cases I tried.
1
2
3
4
5
Strongly disagreeStrongly agree
Question 8 of 16 Did it do the job
The steps matched the way this work is actually done in my area.
1
2
3
4
5
Strongly disagreeStrongly agree
Question 9 of 16 Did it do the job
The test environment behaved closely enough to the real thing.
1
2
3
4
5
Strongly disagreeStrongly agree
Question 10 of 16 Did it do the job
I was given enough time to test all of this properly.
1
2
3
4
5
Strongly disagreeStrongly agree
Question 11 of 16 How bad, and where it went
How serious was the worst problem you ran into?
It stopped the work and there was no way round it
It stopped the work but there was a way round it
It slowed the work down or made mistakes likely
It was untidy but it did not change the outcome
I did not run into a problem
Question 12 of 16 How bad, and where it went
Is that problem logged where the project team will see it?
Yes, and I have the reference
Yes, but I have no reference
No, this is the first report of it
I do not know
I had nothing to report
Question 13 of 16 How bad, and where it went
Describe any problem you ran into: what you did, what you expected, what happened.
Question 14 of 16 The recommendation
If this went live next week as it is, what would happen in your own area of work, day to day?
Question 15 of 16 The recommendation
I am confident this is ready for my area to use for real work.
1
2
3
4
5
Strongly disagreeStrongly agree
Question 16 of 16 The recommendation
In your view, should this go live as it stands today?
Go
Go, once the problems I described are fixed
Go, if an agreed manual workaround is in place
Not yet
I cannot judge from what I tested

The 16 UAT questionnaire questions

A UAT questionnaire is the short form business testers fill in after working their assigned tasks in a test environment. It records what they finished, what stopped them, how serious the worst fault was and whether they would release. Rename the areas in question 2, or build a questionnaire of your own.

Plain text, one question per line, with the answer scale.

Who tested, and what (4 questions)

Four quick taps that make every rating below readable.

  1. Which of these best describes your part in this UAT test cycle?Choose one
  2. Which area or process did you test in this cycle?Choose oneReplace the four placeholders with your own areas.
  3. Where did you do the testing?Choose one
  4. About how long did you spend testing in total?Choose one

Did it do the job (6 questions)

Task completion, one open box, then four statements on one agree scale.

  1. Did you complete the tasks you were given, from start to finish?Choose one
  2. What, if anything, stopped you finishing a task?Open text, optional
  3. The system gave the right answers for all the cases I tried.Strongly disagree to Strongly agree
  4. The steps matched the way this work is actually done in my area.Strongly disagree to Strongly agree
  5. The test environment behaved closely enough to the real thing.Strongly disagree to Strongly agree
  6. I was given enough time to test all of this properly.Strongly disagree to Strongly agree

How bad it was (3 questions)

Severity with its definition inside each option, then where the fault was logged.

  1. How serious was the worst problem you ran into?Choose one, five worded levelsThe definitions sit in the options, so testers rate alike.
  2. Is that problem logged where the project team will see it?Choose oneA fault reported only here is not in your tracker yet.
  3. Describe any problem you ran into: what you did, what you expected, what happened.Open text, optional

The recommendation (3 questions)

The impact in their words, a confidence rating, then the verdict.

  1. If this went live next week as it is, what would happen in your own area of work, day to day?Open text, optional
  2. I am confident this is ready for my area to use for real work.Strongly disagree to Strongly agree
  3. In your view, should this go live as it stands today?Choose one, five worded optionsEach "Go, if" answer names a fix somebody owns.

How to use the UAT questionnaire

Once testing stops, send it to the people who did the work and the person who approves it. Collect answers without names: questions 1 and 2 already say who tested what.

Read question 14 first, then count the answers to question 16 as a share of people and split them by area. Agree your threshold before you send, such as no open fault in the top severity class.

Acceptance testing judges the service from a business perspective, not whether users understand it.[1] To rate whether people can work the interface, send the user experience survey.

Still choosing the tool? Run the software evaluation survey first. After release, the app feedback survey asks the public.

Staff who now work in the new system can answer the technology survey questions a month on.

Several desks each holding a checklist card, with lines running right into a single two-way decision gate above a release box
Many testers, one decision.

UAT questionnaire FAQ

What questions should a UAT questionnaire ask?

Who tested and where, whether the tasks finished, a few ratings on one agree scale, how serious the worst fault was, whether it reached the tracker, what would happen if it shipped as it is, and a go or no-go.

Who should fill in a UAT questionnaire?

The people who do the work, plus whoever approves it. The business defines the criteria and writes the test scripts,[1] so its people are the ones to ask, not the project team.

Is this a UAT sign-off form?

Question 16 collects each tester's recommendation, and the approver's answer to it is what your sign-off rests on. Attach the results to your own sign-off document.

Does it replace test cases and the defect tracker?

It sits beside them. The test cases record what was run and the tracker records every fault; this records what the people who ran them thought. Question 12 shows faults that never reached the tracker.

Related technology survey templates

More surveys for the technology team sit with the technology survey templates.

TechnologyIT Support SurveyWhen the subject is IT support over a year, not one release.12 questions, 3 min TechnologyDeveloper Experience SurveyWhen your own engineers rate the toolchain they build with.14 questions, 4 min TechnologyWebsite Feedback SurveyWhen visitors judge a public web page they found on their own.14 questions, 3 min

Michael Hodge, survey methodology · Updated 29 September 2026 · How templates are reviewed

Sources (1)
  1. U.S. Department of Homeland Security, Customer Experience Directorate. User Acceptance & Usability Testing. dhs.gov

Ask for the verdict while the test is fresh

Sixteen questions, about four minutes, no names asked.

Use this template