Project Management

User Acceptance Tests (documentation)

From the Project Confusion in Transition Management Blog
Projects are about transition from one state to a desirably better state. Management is often viewed as a source of confusion. So lets break down the confusion and build up the means for transition to meaningful deliveries.

About this Blog


Recent Posts

Notes on Reporting Progress (ii)

User Acceptance Tests (documentation)

Start Right

Documents Supplied for Post-HOTO

Notes on Documenting Acceptance Tests


Agile, Agile Communications, App design, Communications Management, Give-back | Outreach, information communication technology, New Year, PMIef, Project Management, Quality, Risk, Risk Management, System design, Volunteering


Categories: Risk Management

This article continues from my notes on acceptance testing in my region. The acceptance report or UAT Report as is typically known, is outlined here

A UAT Report may be progressive such that it presents the summary of acceptance tests that are in progress at any time a report is needed, or a summary of concluded acceptance tests. It records the aggregation and or finality of test results, observations, discrepancies/deviations from the RTM, and resolutions if any that were made during the course of testing. 💯

The report may include out of scope testing such as tests or retests brought forward from a previous UAT regime. Or mention of (significant) outcomes from testing beyond formal test cases.

The final report is usually signed-off by the parties involved. The document may serve as a binding document that the planned tests are conducted, and present plans i.e agreement for completing whatever else that may be outstanding after the tests.

A UAT Report may comprise contents e.g.

(Suggested) Contents of UAT Report

  1. Background of UAT
  2. UAT Scope
  3. UAT Process
  4. UAT Details e.g. dates, duration, resources, etc.
  5. Quality Assurance
  6. Resources, Users & Roles
  7. Criteria for Completion of UAT
  8. UAT Outcomes, Issues & Analysis
  9. Residual Risks
  10. Additional Requirements Arising from UAT
  11. Post UAT i.e. work to complete after UAT such as further enhancements
  12. Post UAT Stress & Reliability Test period - followed by Warranty period
  13. Lessons Learned
  14. UAT Sign-off
  15. Appendices, Attachments, References such as links to test plan, test procedures, test cases, test results, security, assessments, analytics, etc.


A UAT Report in essence-

  • Presents a consolidated view of what has transpired. A historical record on the build (where possible); especially when things were made on the fly and lacking as-built documentation.
  • Is applicable to everyone- and produced by anyone- with vested interest in the testing or project. Anyone authorized can contribute to the construction of the report. 
  • Emphasizes the terms to close a project phase (stage or work component) and move on to the next. The terms may include newly negotiated terms to deal with doubly unknowns uncovered during testing.
  • Plan it as the end goal in testing. Exploit it as preparation, but to publicize structures and processes leading to the conclusion of testing. 

How do we create an acceptable UAT Report?

  • Gather evidence of work outcomes as project progresses e.g. to ease documentation.
  • Build upon a template that everyone is agreeable with. An approach visible to everyone is to evolve the report, editable by authorized users on a shared repository.
  • Involve stakeholders that matters in crafting and reviewing the report, both formally and informally. As the saying goes, engage stakeholders early on in testing ('the project'), and bring onboard influencers in completing the testing.


References & past notes on the same topic:


Posted on: September 20, 2022 07:09 AM | Permalink

Comments (1)

Please login or join to subscribe to this item
Latha Thamma reddi Sr Product and Portfolio Management (Automation Innovation)| DXC Technology Mckinney, Tx, USA
User Acceptance Testing (UAT) is in essence a process that verifies if a solution (new or improved) works for the user. Even though it’s done in the last stages of software implementation, that doesn’t mean it’s not important or can be skipped as a whole

Please Login/Register to leave a comment.


"Critics can't even make music by rubbing their back legs together."

- Mel Brooks