Skip to main content
Delivery replaces the zip of screenshots plus a status email. You still did the testing. The platform freezes it and hands it to their inbox.
1

ACTIVE connection

Delivery ID SUA-XXXX-XXXX, connection code, or invitation. They must approve. States: PENDING | ACTIVE | REVOKED | DECLINED | BLOCKED. Connect.
2

Build delivery snapshot

Immutable copy of the work at that moment. Later runs don’t rewrite what you sent. Snapshots.
3

Deliver UAT

Needs a title, a project, a plan that allows delivery, and an approved connection. If the button fails: can’t deliver.
4

They review

Statuses: awaiting_review | in_review | retest_requested | accepted | accepted_with_issues | not_ready. Actions: accept, accept with known issues, not ready, request retest.
5

Export if needed

Plan-gated: Executive PDF, HTML, Word, PowerPoint, Markdown, Email, Excel, CSV, XML, JSON, Jira Importer CSV, GitHub Issues JSON/CSV, Azure DevOps CSV, Evidence ZIP. Generated from recorded work, not a blank template you fill. Exports.
There is no public status page for SimpleUAT itself. Admin System Health is staff-only. Client “are we done?” lives in review status.

How delivery works

Provider vs recipient, inbox, archive.

Client has no account yet

Invitation and pending resume.