> 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/reviewing-what-comes-back.md).

# Reviewing What Comes Back

Check what the client sent: accept it, or ask again with a reason they'll see. Then finish your team's steps.

As the client works through the request, each step on your checklist updates on its own. You don't need to refresh or wait for an email.

## Statuses

| Status                  | Meaning                                                | What you can do                                  |
| ----------------------- | ------------------------------------------------------ | ------------------------------------------------ |
| **Waiting on client**   | Nothing in yet.                                        | **Skip** if you no longer need it.               |
| **To check**            | The client has sent something.                         | **Accept** or **Ask again**.                     |
| **To ask again**        | You've added it to the follow-up, but not sent it yet. | **Review & send**, or **Remove from follow-up**. |
| **Asked again**         | The follow-up has gone to the client.                  | Wait for the client.                             |
| **Accepted** / **Done** | Finished.                                              | **Undo** if you change your mind.                |
| **Not needed**          | You marked it as not needed, or skipped it.            | **Ask for it** to put it back.                   |
| **N/A**                 | The client said it doesn't apply.                      | Ask again if it does.                            |

Steps that are **To check** are highlighted, with **Accept** and **Ask again** right on the row.

<figure><img src="https://3555949013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqzoPnlIGiL5ejRdJEq5X%2Fuploads%2Fgit-blob-32db3be94d5a4d789aab80204242d2d2db366716%2Frequest-panel-follow-up.png?alt=media" alt="A sent request with one thing waiting to be asked again"><figcaption><p>All names shown are examples.</p></figcaption></figure>

## Check a step

Click the step to open it. You'll see the client's note, their files or answer, and the buttons.

<figure><img src="https://3555949013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqzoPnlIGiL5ejRdJEq5X%2Fuploads%2Fgit-blob-e5c70899bb8ed53b445a4e14951ffb1c1677598b%2Frequest-panel-to-check.png?alt=media" alt="A step opened for checking"><figcaption></figcaption></figure>

* Click a file to open it.
* **Accept** marks the step **Done**.
* **Ask again** opens a box for your reason.

Forms are a little different: a form step shows **Done** as soon as the client submits it, and you review the answers on the form request itself, on the **Form Requests** tab. See [Finding Form Results](/workflow/client-requests/finding-form-results.md).

## Ask again

When something isn't right, you can collect everything you need to send back and send it to the client in one email, instead of an email per item.

1. Click **Ask again** on the step, and type what the client should change or add. Write it as you'd say it to them, such as *"This statement is from last year. Could you send the latest one?"* They see it word for word.
2. Click **Add to follow-up**. Nothing is sent yet. The step shows **To ask again**.

<figure><img src="https://3555949013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqzoPnlIGiL5ejRdJEq5X%2Fuploads%2Fgit-blob-3769a5b17d38318aa9bf848905dbb7a76d5efc8f%2Frequest-panel-add-to-follow-up.png?alt=media" alt="Typing a reason and adding the step to the follow-up"><figcaption><p>All names shown are examples.</p></figcaption></figure>

3. Repeat for anything else. An orange **Follow-up** bar at the top of the request counts what you've collected, such as *2 things to ask again*.
4. When you're ready, click **Review & send** on that bar.

<figure><img src="https://3555949013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqzoPnlIGiL5ejRdJEq5X%2Fuploads%2Fgit-blob-604549f3e2c0e80d20fa6aaf0d8eac242a7c3d1a%2Fask-again-review-send.png?alt=media" alt="The Ask Again window listing what&#x27;s going back to the client"><figcaption><p>All names shown are examples.</p></figcaption></figure>

The **Ask Again** window lists what's going back and who to. Each person gets one email listing only what's needed from them, with the link to their page. Click **Next →** to check the email, then **Review →** and **Confirm & Send →**.

The steps change to **Asked again**, and reminders (if they're on) keep going until they're back. To take a step off the follow-up before sending, open it and click **Remove from follow-up**.

The email uses the template's **Ask again email** wording if it has one: see [Building a Client Request Template](/workflow/client-requests/building-a-client-request-template.md#ask-again-email).

## Changed your mind?

* On a step you've accepted or marked **Not needed**, click **Undo** to put it back to **To check**.
* On a step you marked **Not needed** before the client had sent anything, click **Ask for it** to put it back on the client's list.

## Your team's steps

Your team's steps sit under **Team**, with the role each one is for. Tick them off as you go, or use **Complete all**. The client never sees these.

## When it's all in

When the client presses **I'm finished**, the request bar shows **Client finished** and the template's actions run, such as creating a review task or notifying the adviser. See [When a Form Comes Back](/households/forms/when-a-form-comes-back.md).

When every client step is done, the request shows **Complete** and reminders stop.