UAT evidence that reproduces, and sign-off that transfers risk.
Most UAT cycles produce opinions with attachments. This is the standard we hold ourselves to: five tests every piece of evidence must pass, a defect record shape that a developer can act on alone, and a sign-off packet that still means something when someone challenges the release.
Evidence is not the same as a result.
A test result is a claim: pass, fail, blocked. Evidence is what makes the claim checkable by someone who was not in the room. The distinction matters at exactly the moment UAT gets expensive - a disputed defect, a rejected release, a client who remembers the conversation differently.
Teams rarely fail UAT because they tested badly. They fail because the proof of what was tested lives in chat threads, local screenshots, and memory. By the time it is needed, the build has moved, the tester has moved on, and the only remaining artifact is an assertion.
Five tests every piece of evidence must pass.
If a record fails one of these, it will fail you later at the worst possible time.
- 01
Reproducible
A developer can reach the same failure from the record alone, without asking the tester what they did.
- 02
Attributable
The record names who observed it and who accepted or rejected it.
- 03
Timed
The moment is fixed to a second, so the state of the build and the data at that moment is knowable.
- 04
Verifiable
A reviewer can open the underlying source and see the same thing, not a paraphrase of it.
- 05
Durable
It survives past the sprint, the Slack retention window, and the tester leaving.
The defect record a developer can act on alone.
Seven fields. If any is missing, the ticket comes back with a question instead of a fix.
Build or release identifier, environment name, account or tenant used, browser or device.
The data state that mattered: which account, which plan, which feature flags.
Numbered actions, each one an action a stranger can perform.
The acceptance criterion this step was testing, quoted from the specification.
What happened, including the literal error text on screen.
The timestamp in the session, the frame showing the failure, and the tester sentence that reported it.
Assigned severity plus the person who triaged it, so the grade is attributable.
Five ways UAT evidence quietly stops existing.
Every one of these is normal practice somewhere, which is what makes it dangerous.
- Screenshots in chat
A pasted image has no timestamp, no build, and no link back to the session. Six weeks later nobody can tell which release it came from.
- Verbal approvals
"They said it was fine on the call" is not an approval record. Without the sentence and the second it was said, the decision cannot be defended.
- Summary-only notes
An AI summary of a UAT call compresses exactly the detail a developer needs: the literal error string, the sequence, the disagreement about severity.
- Evidence in three systems
Video in one tool, notes in another, tickets in a third. The join is manual, so it rots first.
- Sign-off without scope
A signature that does not name what was tested, on which build, with which known defects accepted, transfers no risk at all.
What a sign-off packet has to contain.
A signature transfers risk only when the thing being signed is unambiguous.
- 01
Scope statement
What was tested, on which build, against which acceptance criteria.
- 02
Cycle log
Sessions run, testers involved, dates, and duration.
- 03
Defect register
Every defect with severity, status, and its evidence reference.
- 04
Accepted exceptions
Known defects the business agreed to ship with, each with the approval quote.
- 05
Approval record
Who signed, when, and the exact statement they approved.
- 06
Evidence appendix
Numbered citations resolving to a moment, frame, or document page.
Note what is missing from that list: a summary. Summaries are useful for reading, useless for defending. The packet is built from citations, and the summary is generated from the packet rather than the other way round.
How this looks when the session is the source of record.
Record the UAT session however you already do, then upload it with the specification it was testing. Speech, screen frames, and document pages land in one index. Ask what failed and the answer arrives with the tester quote, the second it happened, and the frame showing the error text on screen.
Defects come out as typed artifacts with severity and supporting evidence, and push into Jira, Linear, Notion, or Slack with that evidence attached. The approval is captured the same way: the sentence that granted it, the speaker, and the moment. Deleting the session removes the derived evidence with it, so retention stays honest.
UAT evidence, answered.
- It is the record that proves a test happened and what it showed: the environment, the steps, the observed result, and a pointer to the source material that a reviewer can open, such as a timestamped moment in a session recording or a page in a specification. Evidence is not the same as a test result; a result asserts, evidence demonstrates.
- Rarely. A screenshot shows the end state without the sequence, the build, or the time. Pair it with a timestamped reference into the session so a developer can see what preceded the failure, or capture the frame from the recording itself so the two cannot drift apart.
- The business owner accountable for the acceptance criteria, not the test team. The signature is only meaningful when it names the build, the scope tested, and the defects being accepted, which is why the sign-off packet matters more than the signature.
- At minimum until the release is out of warranty and any contractual acceptance window has closed. Regulated programmes usually keep it for the life of the system. Practical rule: keep the evidence at least as long as anyone can still dispute the release.
- Record the UAT session, upload it with the specification document, and the platform indexes speech, screen frames, and document pages together. Defects come out as typed artifacts carrying quote, speaker, timestamp, and frame, and can be pushed into Jira or Linear with the evidence attached.
Your next recording could be
your most valuable asset.
Or it could sit in a Drive folder nobody opens again. The difference is whether it has citations attached.
- SetupOne drag-and-drop upload, or send the notetaker. No plugins.
- First insightCited Q&A on a 60-min recording in under 6 minutes.
- Cancel anytimeFull data export, full right to erasure.