> 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.md).

# Client Requests

Ask a client for everything you need on one page: forms to fill in, documents to upload, questions to answer and links to open, with reminders and a clear view of what's back and what's still open.

A **client request** is a list of things you need from a client, on one page they open from an email. Instead of a chase email with attachments going back and forth, the client works through the list in their own time, and you can see exactly what's done, what's waiting and what needs another look.

<figure><img src="https://3555949013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqzoPnlIGiL5ejRdJEq5X%2Fuploads%2Fgit-blob-389c17de9400362cca6b2e760ce96112879d6c28%2Fclient-request-page.png?alt=media" alt="A client&#x27;s request page"><figcaption><p>What the client sees. All names shown are examples.</p></figcaption></figure>

A client request can include:

| Step                | The client…                                                                  |
| ------------------- | ---------------------------------------------------------------------------- |
| **Form**            | Fills in one of your forms. Their progress shows on the request.             |
| **Document**        | Uploads one or more files, with an optional note.                            |
| **Text answer**     | Types a short answer.                                                        |
| **Choice**          | Picks one of the options you give.                                           |
| **Link**            | Opens a link (to book a meeting, for example) and confirms it's done.        |
| **Acknowledgement** | Reads a statement, or your full terms in a pop-up, and ticks a box to agree. |

## How it works

1. **Build a template once.** A client request template is a [checklist template](/workflow/checklist-templates.md) with some steps marked for the **Client**. It holds the client's steps, any steps for your team, the email, reminders and what should happen when the client finishes. See [Building a Client Request Template](/workflow/client-requests/building-a-client-request-template.md).
2. **Send it.** From a household, job, opportunity or lead, choose the template, mark anything you already hold, and send. Each person gets their own link. See [Sending a Client Request](/workflow/client-requests/sending-a-client-request.md).
3. **The client works through it.** They upload, answer and fill in forms. Everything saves as they go, and they press **I'm finished** when they've sent what they can. See [What Your Client Sees](/workflow/client-requests/what-your-client-sees.md).
4. **You review what comes back.** Accept each item, or ask again with a reason the client will see. Reminders go out automatically until everything required is in. See [Reviewing What Comes Back](/workflow/client-requests/reviewing-what-comes-back.md). Forms in the pack are on the **Form Requests** tab: see [Finding Form Results](/workflow/client-requests/finding-form-results.md).
5. **When it comes back**, the template's actions run: create a review task, notify the adviser, start a job, and so on. These are the same actions forms use. See [When a Form Comes Back](/households/forms/when-a-form-comes-back.md).
6. **Keep the evidence.** Every agreement, every time the client opened your terms, and every email sent is recorded, and the whole request can be saved as a PDF. See [Proving What the Client Agreed To](/workflow/client-requests/proving-what-the-client-agreed-to.md).

{% hint style="info" %}
**Working towards a date?** Turn the request into a pack: a banner with the key date and status from the job, and steps that open and fall due as the job moves. See [Packs: a Key Date and Steps That Follow the Job](/workflow/client-requests/packs-a-key-date-and-steps-that-follow-the-job.md).
{% endhint %}

## Who can do what

* Building templates needs the **Rubica Checklist – Manager** permission set.
* Sending and reviewing requests needs **Rubica Checklist – User** (or Manager).

Ask your admin if you can't see the buttons described in these pages.