Skip to main content
You don’t need a second status tracker. The client already has (or will have) UAT Inbox, findings, and review actions. Keep the records accurate so they don’t need a paraphrase.

​
During the week

  • Mark runs as you go. A silent in-progress run with zero results looks like you haven’t started.
  • Comment on findings when you have new evidence. That’s the thread, attached to the bug.
  • Watch New pills in the sidebar for connection, delivery, retest, and comments. Notifications.

​
Don’t wait for the export

Exports are generated from recorded work (and plan-gated). They’re the polished packet, not the only communication. If checkout is blocked on payment sandbox, log blocked and a finding; don’t only say it on a call.

​
Connection is part of updates

If they’re still PENDING, they cannot receive a delivery. Nudge the invitation or Delivery ID approve step early. Connections. Founding/beta feedback flags in the product are often off. Don’t promise the client an in-app feedback widget. Email still works: support is support@simpleuat.com for product issues, not for the client’s staging bugs.

What they see

Inbox, review, findings, exports.

Deliver the packet

Snapshot, deliver, review statuses.