Review a UAT session
A test run is only useful if the failure can be shown to someone who was not there. This walkthrough takes a narrated UAT session from upload to a defect with screen proof, and to a report you can sign off.
- Updated
- 8 October 2026
- Read
- 6 min
- For
- QA leads, testers, product owners
Seven steps from test run to sign-off.
Record the run, out loud
Share your screen and say what you do and what you see: "submitting now", "the error says we could not confirm this payment". Spoken steps become the transcript the findings quote.
Upload it as UAT
In New content, choose Upload a recording, set the recording type to UAT, and file it in the release project. A UAT recording yields its transcript findings first; screen states and on-screen text come later, when you ask for visual evidence.
A screen recording ready to upload, typed as UAT and filed in the release project. Read the findings
When transcript processing finishes, the defect is already a Bug finding with the tester's own words, the speaker, and the time. Recap, Transcript, Artifacts, and Ask are all ready at this point.
Add screen proof when it matters
Choose Analyze visual evidence. The dialog shows your monthly allowance, what this recording would use, and what remains, before anything starts. Your recording stays fully usable while it runs.
The allowance check before visual analysis starts: what this recording uses and what remains this month. Check what was on screen
Deep Dive shows what was on screen at any moment and a grid of scenes. The bug finding now carries the frame and the text read from it, so the error message is quoted exactly as it appeared.
Deep Dive on the UAT session: the screen, a description of the run, and every scene with its time, from the cart to the duplicate charge and its ticket. The bug with its proof: the frame, the quote, and the text read from the screen. Ask about the run
Use Ask on the recording: "Which acceptance criteria failed, and what is the fix?" The answer cites the moments it came from, and selecting a citation plays it.
A cited answer about the run. Each citation plays its moment. Hand it over
Approve the bug and push it to your tracker, or export a report as PDF or Word for the sign-off pack. Either way the evidence travels with the claim.
Exporting a report for sign-off: choose the sections, the format, and what to include.
A duplicate charge on a slow connection.
- The QA lead throttles the connection to slow 3G and pays for a $148 order once.
- The screen says "We could not confirm this payment", but the account shows two pending charges.
- Citesvue extracts a critical bug, with the quote, and the failed acceptance criterion AC-118, "exactly one charge per payment submission".
- Visual evidence adds the frame of the account activity with both charges, and the error text exactly as displayed.
- The release decision is quoted too: no rollout until the fix passes a retest on slow 3G.
Evidence that survives review.
For what a defect record and a sign-off pack should contain, see these two working standards.
UAT review, answered.
No. Transcript findings, Ask, and the recap are ready without it. Request visual evidence for the sessions where screen proof matters, such as a defect someone will dispute or a sign-off that needs the exact screen.
It uses your monthly visual-evidence allowance, in hours of video. The confirmation dialog shows the amount before you start, and transcription never uses this allowance.
Yes, and you still get the transcript, findings, recap, and Ask. Deep Dive, scene detection, and frame citations need video.
You choose: the timeline, the transcript, the findings, or all three, as PDF, Word, CSV, or JSON. Export settings let you include timestamps, speaker names, and screen images, or limit the export to a time range.