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

# Client Hand-off & Sign-off

> Hand a finished, live AIWA project to your client, get their sign-off, and give them Traffic and Accounts pages for their site.

A hand-off tells your client their live site is finished and theirs.

The client receives a clear summary of what they're getting, and signs it off when they're happy. Optionally, they also get a **Traffic** page and an **Accounts** page for their site.

**Finish projects cleanly, with a record that the client agreed.**

> [!NOTE]
>
> Hand-offs are part of the [agency console](/agency/console-overview.md), available on the Agency and Enterprise plans.

## Before You Start

To send a hand-off:

* The project must be **live** (published).
* At least one **client** must be on the project. If there isn't one, the dialog opens the invite dialog first.
* You need permission to **publish** the project.

## Send a Hand-off

**1. Open the Projects tab**

In the agency console, open **Projects** and find the live project.

**2. Select Hand off**

Select **Hand off** on the project's row or card.

**3. Check who will hear**

The dialog names the clients who will receive the hand-off.

**4. Add a note (optional)**

Write a short note to the client, up to 2,000 characters.

**5. Choose what to share**

Switch **Site traffic** and **Manage accounts** on or off. See below.

**6. Preview and send**

The dialog shows the hand-off document exactly as the client will read it. Send it when it looks right.

## What the Hand-off Document Contains

The document summarises the finished site:

* Its address
* Its pages
* What the site keeps (its data)
* The connected services
* How to get help

It also lists what the client can do in their portal, such as leaving comments on the site, viewing traffic and managing accounts.

The client can select **Download PDF** to save a copy using their browser's Save as PDF.

## Traffic and Accounts

Two switches decide which extra pages the client gets.

### Site traffic

On by default. The client gets a **Traffic** page showing:

* Page views
* Visitors (counted per day, so someone who visits on two days counts twice)
* Top pages
* Where visitors come from

They can look at the last 7, 30 or 90 days.

### Manage accounts

On by default when the site has sign-in. The client gets an **Accounts** page listing the people with an account on their site. From it, they can:

* Invite someone (they get an e-mail to choose their own password)
* Deactivate or reactivate an account
* Send a password reset
* Sign an account out

Only the workspace Owner can switch **Manage accounts** on. Anyone who can send the hand-off can switch it off.

Each change a client makes on the Accounts page appears in your console's **Activity** log, for your team only. Your team manages accounts through **App users** in the builder.

You can change both switches later from the same dialog. Changing them doesn't e-mail anyone.

## Sign-off

The clients receive one e-mail linking to the hand-off page in their portal.

The first client to select **Sign off** completes it. They can add an optional note. Signing off tells your agency the project is finished as handed over; the client can still leave comments afterwards.

When the client signs off, the Owner, the Admins and the person who sent the hand-off are told.

In the console's **Projects** tab, each project shows where its hand-off stands:

* **Waiting for sign-off**
* **Signed off**

Use the two filters of the same names to see them together.

## Withdraw or Send Again

* A hand-off waiting for sign-off can be **withdrawn**. Nobody is e-mailed.
* You can replace a waiting hand-off with a new one and a new note.
* A signed hand-off stays on record. **Hand off again** asks the client for a new sign-off.

## A Hand-off Changes Nothing on the Site

Sending, changing, withdrawing or signing a hand-off never touches the site or its deployment. Publishing doesn't depend on a hand-off either.

It is a record between you and your client, not a release step.

## Next: Building From Telegram

Agency owners can also check on projects and request work from their phone. Next, we'll look at the Telegram assistant.

> **[Build From Telegram](/agency/telegram.md)**
>
> Connect Telegram and check on projects, get links and request builds from a chat.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.