User Acceptance Testing (UAT) Sign-Off Template for Word
UAT sign-off is the moment the business says “we tested it and we accept it, including what is still broken”. The document has to show the numbers behind that decision, which defects are being accepted and why, and who authorized deployment. This template is a finished three-page example for a fictional payroll upgrade: an execution summary, the business-critical cases one by one, open defects with workarounds, exit criteria and a go-live decision with conditions.
- Pages:
- 3
- Works with:
- Word for Microsoft 365, Word 2016 or later, Word for Mac (Word for the web can fill in fields)
- Updated:
What you can do with it
- Release block with UAT start and end and planned go-live date pickers
- Execution summary by area (planned, passed, failed, blocked, not run) and key case results with a result dropdown per case
- Open defects table with a severity dropdown, workaround and an “accepted for go-live” checkbox
- Entry and exit criteria checklist, a Go / Go with conditions / No go dropdown, rollback note and four signatures

What's inside
The document has 3 pages. Each part below is a heading in the file, so you can jump to it from the Navigation Pane (View > Navigation Pane).
| Part | What it covers | What you write |
|---|---|---|
| Release block | What was tested, where and when | Project, release, owners, UAT dates, environment, go-live date |
| 1–2. Summary and results | How much was tested and what passed | Counts by area; business-critical cases with result and tester |
| 3. Open defects | What is still wrong and whether it is accepted | Severity, workaround, fix date, acceptance box |
| 4. Entry and exit criteria | Whether the agreed bar was met | Checkbox and evidence per criterion |
| 5–6. Decision and sign-off | The go-live call and who owns it | Go / conditions / no go, conditions, rollback; four signatures |
Before you start
- Agree exit criteria before UAT starts: minimum pass rate, which severities may stay open, and any parallel run required.
- Export the full test log and defect list from your test tool; this form summarizes them and should be attached to them.
- Check that every blocked or not-run case has a reason and a plan.
Step-by-step guide
Fill in the release block
Type the project, release, owners and environment, and pick the UAT and go-live dates.
Summarize execution
Enter planned, passed, failed, blocked and not-run counts per area and the total, then write the pass rate and explain anything blocked.
List the critical cases
One row per business-critical case. Pick the result from the dropdown and name the tester.
Decide on each open defect
Pick the severity, write the workaround and fix date, and tick Accepted only if the business owner agrees to go live with it.
Check the criteria
Tick each entry and exit criterion that is met and note the evidence. Leave a box empty if it is not met and turn it into a condition.
Make the call and sign
Pick Go, Go with conditions or No go, list the conditions and the rollback plan, and collect the four signatures.
Field and control map
Every content control and field in the document, in the order they appear. Gray-boxed fields in Word are the content controls.
| Name | Type | Where | Value in the sample |
|---|---|---|---|
| Release header | Text | Header | Payroll Platform Upgrade R4.2 |
| Project | Text | Body | Payroll Platform Upgrade |
| Release | Text | Body | R4.2 |
| Business owner | Text | Body | Dana Whitfield, Payroll Director |
| Test lead | Text | Body | Omar Feld, QA Lead |
| UAT start | Date picker | Body | October 19, 2026 |
| UAT end | Date picker | Body | October 30, 2026 |
| Environment | Text | Body | UAT-2 (production copy, masked) |
| Go-live date | Date picker | Body | November 14, 2026 |
| Result TC-001 | Dropdown | Body | Pass (Pass / Fail / Blocked / Not run) |
| Result TC-007 | Dropdown | Body | Pass (Pass / Fail / Blocked / Not run) |
| Result TC-014 | Dropdown | Body | Fail (Pass / Fail / Blocked / Not run) |
| Result TC-022 | Dropdown | Body | Pass (Pass / Fail / Blocked / Not run) |
| Result TC-061 | Dropdown | Body | Blocked (Pass / Fail / Blocked / Not run) |
| Result TC-088 | Dropdown | Body | Pass (Pass / Fail / Blocked / Not run) |
| Result TC-093 | Dropdown | Body | Fail (Pass / Fail / Blocked / Not run) |
| Result TC-104 | Dropdown | Body | Pass (Pass / Fail / Blocked / Not run) |
| Severity DEF-311 | Dropdown | Body | High (Critical / High / Medium / Low) |
| Accept DEF-311 | Checkbox | Body | checked |
| Severity DEF-318 | Dropdown | Body | Low (Critical / High / Medium / Low) |
| Accept DEF-318 | Checkbox | Body | checked |
| Severity DEF-320 | Dropdown | Body | Low (Critical / High / Medium / Low) |
| Accept DEF-320 | Checkbox | Body | checked |
| Entry env | Checkbox | Body | checked |
| Entry sit | Checkbox | Body | checked |
| Exit pass | Checkbox | Body | checked |
| Exit crit | Checkbox | Body | checked |
| Exit parallel | Checkbox | Body | checked |
| Exit training | Checkbox | Body | unchecked |
| Go decision | Dropdown | Body | Go with conditions (Go / Go with conditions / No go) |
| Conditions | Text | Body | Payroll team training completed by Nov 10; DEF-311 fix deployed by Nov 28; manual adjustment for 6 employees in the Nov 14 run. |
| Signer business | Text | Body | Dana Whitfield, Payroll Director |
| Signed date | Date picker | Body | 4 fields: Click or tap to enter a date. |
| Signer QA | Text | Body | Omar Feld, QA Lead |
| Signer IT | Text | Body | Sofia Brandt, HRIS Manager |
| Signer finance | Text | Body | Peter Lund, Controller |
{ PAGE } | Field | Footer | 1 |
{ NUMPAGES } | Field | Footer | 3 |
{ SEQ Table \* ARABIC } | Field | Body | 1 |
Every field, control and style, explained
The code in each card is read straight from the .docx file (the XML Word stores, or the field code you see with Alt+F9), so it is exactly what the template contains.
<w:lvl w:ilvl="0">
<w:start w:val="1"/>
<w:numFmt w:val="decimal"/>
<w:pStyle w:val="Heading1"/>
<w:lvlText w:val="%1."/>
<w:lvlJc w:val="left"/>
<w:pPr>
<w:ind w:left="440" w:hanging="440"/>
</w:pPr>
</w:lvl>
<w:lvl w:ilvl="1">
<w:start w:val="1"/>
<w:numFmt w:val="decimal"/>
<w:pStyle w:val="Heading2"/>
<w:lvlText w:val="%1.%2"/>
<w:lvlJc w:val="left"/>
<w:pPr>
<w:ind w:left="660" w:hanging="660"/>
</w:pPr>
</w:lvl>The section numbers (1., 2., 6.1 …) are not typed. A multilevel list is linked to the Heading 1 and Heading 2 styles, so any paragraph you set to Heading 1 gets the next number and the table of contents picks it up.
Piece by piece
<w:pStyle w:val="Heading1"/>- Links list level 1 to the Heading 1 style (level 2 to Heading 2).
<w:lvlText w:val="%1."/>- Level 1 shows its counter and a period: 1., 2., 3.
<w:lvlText w:val="%1.%2"/>- Level 2 shows the parent number, a period and its own counter: 6.1, 6.2.
<w:ind w:left="440" w:hanging="440"/>- Hanging indent so wrapped heading text lines up after the number.
In the sample: 1. Test summary, 2. Key test case results, 3. Open defects … (6 headings)
How it is used: To add a section, type the heading, then pick Heading 1 (Ctrl+Alt+1) or Heading 2 (Ctrl+Alt+2) on the Home tab. Numbers after it update by themselves.
How to change it: Home > Multilevel List > Define New Multilevel List to change the format (for example "Section 1"). Keep "Link level to style" set to Heading 1 and Heading 2.
Learn this: How to Plan and Structure Long Documents in Word: Outline View and Multilevel Numbering →Page { PAGE } of { NUMPAGES }The footer counts pages with two fields: PAGE is the current page and NUMPAGES is the total. Both recalculate when the document is printed, saved as PDF or scrolled in Print Layout.
Piece by piece
PAGE- The number of the page the field sits on.
NUMPAGES- The total number of pages in the document.
In the sample: Page 1 of 3 on the first page
How it is used: Nothing to do: add or delete pages and the numbers follow.
How to change it: Double-click the footer to edit the text around the fields. Insert > Page Number > Format Page Numbers sets the starting number.
Learn this: How to Set Up Pages in Word: Margins, Breaks, Headers, Footers, and Page Numbers →{ SEQ Table \* ARABIC }Each table caption uses a SEQ field that counts tables in order. Insert a new captioned table in the middle and every later caption renumbers.
Piece by piece
SEQ Table- A counter named "Table". Every SEQ Table field adds 1.
\* ARABIC- Show the counter as 1, 2, 3.
In the sample: 1 caption(s): Table 1
How it is used: Captions are what a "see Table 2" cross-reference points to (References > Cross-reference).
How to change it: References > Insert Caption adds a new one. If numbers look stale, press Ctrl+A then F9 to update all fields.
Learn this: How to Add a Table of Contents, Captions, and Cross-References in Word →<w:sdtPr>
<w:alias w:val="Project"/>
<w:tag w:val="project"/>
<w:text/>
</w:sdtPr>Names, numbers and other details people change every time are plain text content controls. Click one and type: the text replaces the sample, keeps the formatting, and the field still shows its name when selected.
Piece by piece
<w:alias w:val="…"/>- The title shown on the control’s tab when you click it.
<w:tag w:val="…"/>- A machine-readable name, useful for mail merge or code.
<w:text/>- Plain text: one line, one format, so pasted text cannot break the layout.
<w:showingPlcHdr/>- Present when the field shows gray placeholder text instead of a value.
In the sample: Project = Payroll Platform Upgrade
How it is used: 11 in this template: Release header, Project, Release, Business owner, Test lead, Environment, Conditions, Signer business, Signer QA, Signer IT, Signer finance. Use Developer > Design Mode to see every control at once, or the Selection Pane to jump between them.
How to change it: Developer > Properties changes the title, tag and placeholder. To show the Developer tab: File > Options > Customize Ribbon > Developer.
Learn this: How to Create Fillable Forms with Content Controls in Word →<w:sdtPr>
<w:alias w:val="UAT start"/>
<w:tag w:val="uat_start"/>
<w:date w:fullDate="2026-10-19T00:00:00Z">
<w:dateFormat w:val="MMMM d, yyyy"/>
<w:lid w:val="en-US"/>
<w:storeMappedDataAs w:val="dateTime"/>
<w:calendar w:val="gregorian"/>
</w:date>
</w:sdtPr>Dates are date picker content controls: click the arrow to pick from a calendar, or type a date in any format and Word shows it as "November 2, 2026".
Piece by piece
w:fullDate- The stored date, independent of how it is shown.
<w:dateFormat w:val="MMMM d, yyyy"/>- Display format: full month name, day, four-digit year.
<w:lid w:val="en-US"/>- Language used for month names.
<w:storeMappedDataAs w:val="dateTime"/>- Stores a real date value if the control is mapped to data.
In the sample: UAT start = October 19, 2026
How it is used: 7 in this template: UAT start, UAT end, Go-live date, Signed date. Pick the date from the calendar so every date in the document has the same format.
How to change it: Developer > Properties > Display the date like this, for example d MMMM yyyy or yyyy-MM-dd.
Learn this: How to Create Fillable Forms with Content Controls in Word →<w:sdtPr>
<w:alias w:val="Result TC-001"/>
<w:tag w:val="result_tc_001"/>
<w:dropDownList>
<w:listItem w:displayText="Pass" w:value="Pass"/>
<w:listItem w:displayText="Fail" w:value="Fail"/>
<w:listItem w:displayText="Blocked" w:value="Blocked"/>
<w:listItem w:displayText="Not run" w:value="Not run"/>
</w:dropDownList>
</w:sdtPr>Fields with a fixed set of answers are dropdown list content controls, so everyone uses the same words (useful when you search or count documents later).
Piece by piece
<w:dropDownList>- A list the reader must pick from (no free typing).
<w:listItem w:displayText="…" w:value="…"/>- One choice: the text shown and the value stored.
In the sample: Result TC-001 = Pass (Pass / Fail / Blocked / Not run)
How it is used: 12 in this template: Result TC-001, Result TC-007, Result TC-014, Result TC-022, Result TC-061, Result TC-088, Result TC-093, Result TC-104, Severity DEF-311, Severity DEF-318, Severity DEF-320, Go decision. Click the field and choose from the list.
How to change it: Developer > Properties > Add, Modify or Remove choices. Use a Combo Box instead if people need to type their own answer.
Learn this: How to Create Fillable Forms with Content Controls in Word →<w:sdtPr>
<w:alias w:val="Accept DEF-311"/>
<w:tag w:val="accept_def_311"/>
<w14:checkbox>
<w14:checked w14:val="1"/>
<w14:checkedState w14:val="2612" w14:font="MS Gothic"/>
<w14:uncheckedState w14:val="2610" w14:font="MS Gothic"/>
</w14:checkbox>
</w:sdtPr>Checklist boxes are checkbox content controls: click to tick or untick. They print as ☒ and ☐.
Piece by piece
<w14:checked w14:val="…"/>- 1 when ticked, 0 when not.
<w14:checkedState w14:val="2612"/>- Symbol for ticked: U+2612 ☒.
<w14:uncheckedState w14:val="2610"/>- Symbol for unticked: U+2610 ☐.
In the sample: 8 of 9 ticked in the sample
How it is used: 9 in this template: Accept DEF-311, Accept DEF-318, Accept DEF-320, Entry env, Entry sit, Exit pass, Exit crit, Exit parallel, Exit training. Click the box. Checkboxes need Word 2010 or later; very old versions show a static symbol.
How to change it: Developer > Properties > Checked symbol > Change, for example to ✓ (Wingdings 2).
Learn this: How to Create Fillable Forms with Content Controls in Word →<w:style w:type="paragraph" w:styleId="Callout">
<w:name w:val="Callout"/>
<w:basedOn w:val="Normal"/>
<w:pPr>
<w:pBdr>
<w:left w:val="single" w:color="F2A93B" w:sz="24" w:space="8"/>
</w:pBdr>
<w:shd w:fill="EEF2F8" w:color="auto" w:val="clear"/>
<w:spacing w:after="160" w:before="120"/>
<w:ind w:left="180" w:right="180"/>
</w:pPr>
<w:rPr>
<w:sz w:val="21"/>
</w:rPr>
</w:style>Notes and warnings use a paragraph style named Callout: tinted background, amber bar on the left, indented on both sides. Because it is a style, every callout matches and you can restyle them all at once.
Piece by piece
<w:shd w:fill="EEF2F8"/>- Light blue-gray background.
<w:left w:val="single" w:sz="24" w:color="F2A93B"/>- Amber bar, 3 pt wide, on the left edge.
<w:ind w:left="180" w:right="180"/>- Indented 1/8 inch on each side.
In the sample: Used for the notes, tips and warnings in the body.
How it is used: Put the cursor in a paragraph and pick Callout in the Styles gallery.
How to change it: Right-click Callout in the Styles gallery > Modify > Format > Border or Shading. All callouts change together.
Learn this: How to Use Styles and the Navigation Pane in Word →<w:trPr>
<w:cantSplit/>
<w:tblHeader/>
</w:trPr>Header rows are marked to repeat at the top of each page when a table breaks, and rows are set not to split across pages, so a long table stays readable when printed.
Piece by piece
<w:tblHeader/>- Repeat this row at the top of each page.
<w:cantSplit/>- Keep each row on one page.
In the sample: 4 of 7 tables repeat their header row
How it is used: Add rows with Tab in the last cell; the header keeps repeating.
How to change it: Click in the header row > Table Layout > Repeat Header Rows. Short tables are also set to keep with the next paragraph so they do not split.
Learn this: How to Build and Format Tables That Read Well in Word →<w:style w:type="paragraph" w:styleId="Guidance">
<w:name w:val="Guidance"/>
<w:basedOn w:val="Normal"/>
<w:pPr>
<w:spacing w:after="100"/>
</w:pPr>
<w:rPr>
<w:i/>
<w:iCs/>
<w:color w:val="6B7280"/>
<w:sz w:val="19"/>
</w:rPr>
</w:style>Instructions for whoever fills in the template use a Guidance style (gray italics). Delete them before you send the document; with a style, Find and Replace can remove them all at once.
Piece by piece
<w:i/>- Italic.
<w:color w:val="6B7280"/>- Gray text.
In the sample: One note under the title block.
How it is used: Home > Replace > More > Format > Style > Guidance finds every note.
How to change it: Right-click Guidance in the Styles gallery > Modify.
Learn this: How to Use Styles and the Navigation Pane in Word →Tips and limits
- Sign-off is a business decision, not a QA one. The business owner signs first.
- Never accept a Critical defect. If one is open, the answer is No go or a documented exception from the executive sponsor.
- Turn every unchecked exit criterion into a condition with an owner and a date.
- Keep the pass rate honest: count blocked and not-run cases as not passed.
- File the signed form with the change request so the change board can see it.
Learn the skills behind this template
Was this guide helpful? Spot a mistake? Send feedback · admin@arumsoft.com