> For the complete documentation index, see [llms.txt](https://docs.rubica.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rubica.au/workflow/client-requests/what-your-client-sees.md).
# What Your Client Sees
The client's request page: one list of everything you need, in your firm's colours, that saves as they go and works on any phone.
The client opens their request from the link in the email. They don't need a login. The page uses your firm's branding, or the template's own colours if it has them.
All names shown are examples.
At the top they see the request's name, the due date and how many days are left, the intro from the template, and a progress bar. Their adviser's name and email sit alongside, so they know who to ask.
## The list
Each step shows what it is and where it's up to:
| Label | Meaning |
| --------------------------- | -------------------------------------------------------------------------------- |
| **Not started** | Nothing done yet. |
| **In progress** | Started, such as a form part-way through. |
| **With {adviser} to check** | Sent, and waiting for you to review. |
| **Asked again** | You've asked for something different. Your reason is shown on the step. |
| **Done** | Accepted, or nothing more to do. |
| **Not applicable** | The client said this doesn't apply to them. |
| **Optional** | They can leave it out. |
| **Not needed** | You marked it as not needed (only shown if the template shows these greyed out). |
Steps marked **One per client** show the person's name, such as *Most recent payslip · Sam*, so each person in a couple can send their own.
## Each kind of step
Clicking a step opens it:
* **Form**: **Start form**, or **Continue form** if they've started. The form opens in its own page and their progress shows back on the list.
* **Document**: **Drop files here or choose files**. They can add several files, up to 3 MB each, and a note.
* **Link**: **Open** takes them to the link (to book a meeting, for example). They then click **I've done this**.
* **Choice**: they pick one of your options.
* **Text answer**: they type their answer and click **Save** (or **Update** to change it).
* **Agreement**: they read your statement, tick the box and confirm. If the step has full terms, they read them first: see below.
Every step has room for a note to the adviser. If something doesn't apply, they can press **Not applicable**, and **Actually, this applies to me** puts it back.
Everything saves as they go, so they can stop and come back to the same link at any time.
## Agreeing to terms
When an acknowledgement step has full terms, such as your whole privacy policy, the client sees a **Read and agree** button instead of a tick box.
All names shown are examples.
1. **Read and agree** opens the terms in a pop-up.
2. The tick box and **I agree** stay greyed out, with *Scroll to the end of the terms to agree ↓*, until the client reaches the end.
3. They tick the box and click **I agree**. **Not now** closes the pop-up without agreeing.
The terms shown are an example.
The step then shows *You agreed on…* with the exact words they ticked. **Read again** opens the terms at any time.
Every time the client opens the terms is recorded, with the time, their IP address and browser, even if they don't agree. See [Proving What the Client Agreed To](/workflow/client-requests/proving-what-the-client-agreed-to.md).
On a phone, the terms fill the screen.
## When you ask again
If you ask again, the step reopens with your reason at the top, so the client knows exactly what to change.
## I'm finished
When they've sent what they can, the client presses **I'm finished**. This tells you to take a look and runs the template's actions under **When it comes back**. They can still add things afterwards.
## On a phone
The page works the same on a phone. The adviser panel moves to the bottom.
