6. How To Good UAT Feedback

Think of raising feedback as telling a story: where were you, what did you try, and what went wrong?

Good feedback should always include screenshots and callouts of each element.

Steps	What to Include	Why It's Important
1. Where You Started	The Specific Location: What page or section were you on? (e.g., "The checkout page," "The CRM Contact record for Jane Doe," "The Sign-Up Form").	Helps the team quickly find the exact environment and feature you are referencing.
2. Steps to Reproduce	The Action Taken: List the clear, numbered steps you took right before the issue occurred. (e.g., 1. Clicked the 'Add to Cart' button. 2. Changed quantity to 3. 3. Clicked 'Update Cart').	Allows anyone to follow your path and see the issue happen for themselves.
3. The Expected vs. Actual Result	The Problem: Clearly state what you thought would happen. (Expected Result) versus what actually happened (Actual Result).	This defines the issue. (e.g., Expected: The cart total should update to $150. Actual: The cart total remained $50, and I got an error message).

Always include these details to make your feedback actionable:

Screenshot/Video Evidence: Always capture evidence, especially a screenshot. Use tools to call out the specific element on the screen that is not working.
A link to the page or email subject line of the item you are providing feedback on.
Environment Used: Specify which environment you were testing in (Staging or Production).
Your Setup: Note the Browser (Chrome, Safari, etc.) and if you were using Desktop or Mobile.

Note if providing feedback via Marker.io or similar, most of the above will be captured by default.

Feedback can be raised during testing to address bugs, missing scope, questions/clarifications and changes and edge cases.