mariusene.dev

UAT summary and sign-off template

A UAT sign-off should say what was accepted, on which build, by whom, and what was left outside the signature. An email that says “looks good” records none of that.

Fill in the scope and the journeys before the session, the results during it, and send the pack the same day while people remember what they saw.

UAT summary and sign-off template
UAT SUMMARY

Build / environment:  <build> on <environment>, <date>
Attended:             <names and roles of business owners>
Facilitated by:       <name>

Result:               <n> journeys passed, <n> deferred, <n> blocking
Recommendation:       <accept / accept with deferrals / not accepted>

Scope
  Shown:              <journeys, by the names the business uses>
  Not shown:          <journeys left out, and who agreed>
  Differs from production: <stubs, data, configuration>

Journey results
  J1 <journey> — PASS — driver: <role> — evidence: <link>
  J2 <journey> — DEFER — <gap in one line> — see D1 — evidence: <link>
  J3 <journey> — FAIL, blocking — <gap in one line> — defect: <link>

Deferrals
  D1 <journey>: <gap>. Impact: <who, how often>. Workaround: <steps a user can take>.
     Accepted by: <name>. Fix target: <release>. Review: <date>.

Blockers
  <defect> — owner: <name> — to be shown again on: <build>

Improvements and open questions
  <request or question> — who responds: <name>

Sign-off
  Accepted:               <journeys> as shown on <build>, <date>
  Accepted with deferral: <journeys>, on the terms above
  Not accepted:           <journeys>
  Outside this signature: <anything not shown, any later build>
  Signed for the business: <name, role, date>

Free to use and adapt. No sign-up, no attribution needed.

How to use it

  • Name journeys the way the business names them, not by module or ticket.
  • Link one piece of evidence per journey: a screenshot showing the outcome, or a short recording.
  • The person who signs must be able to accept risk for the business. QA facilitates and records; QA does not sign.
  • A signature covers the build that was shown. Say so, or it will be read as covering every build after it.

Terms used here: User acceptance testing (UAT), Acceptance criteria, Deferred risk.

The thinking behind it