> ## Documentation Index
> Fetch the complete documentation index at: https://docs.simpleuat.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Keep the client updated

> Use connection status, delivery review, comments, and notifications instead of a weekly status spreadsheet.

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](/account/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](/concepts/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](/troubleshooting/still-stuck) is `support@simpleuat.com` for product issues, not for the client's staging bugs.

<Columns cols={2}>
  <Card title="What they see" icon="eye" href="/delivery/what-client-sees">
    Inbox, review, findings, exports.
  </Card>

  <Card title="Deliver the packet" icon="send" href="/playbook/delivering">
    Snapshot, deliver, review statuses.
  </Card>
</Columns>