> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/reviewing-and-exporting/understanding-reviews.md).

# Understanding reviews

Review what recipients send with checklist item reviews, which notify them, and file reviews, which don't. Then mark the request complete.

Pipefile gives you two ways to review what recipients send: **checklist item reviews** and **file reviews**. A checklist item review tells the recipient your decision and what to do next. A file review is a quiet marker for your own tracking and notifies no one.

When a recipient uploads, Pipefile emails you a summary of the checklist items they responded to, with a link to the request. Open the request from that email or from your dashboard to start reviewing.

## Checklist item reviews

A checklist item review is a formal decision on one checklist item. Use it when the recipient needs to know where they stand.

Open the item and select **Review item**. You can do this from the request page or from the file preview. In the dialog, choose a **Decision**:

| Decision            | Meaning                                                           | Message  |
| ------------------- | ----------------------------------------------------------------- | -------- |
| **Approve**         | The item is complete.                                             | Optional |
| **Mark incomplete** | Keep what they sent and ask for what's missing.                   | Optional |
| **Reject**          | What they sent doesn't satisfy the item, so they need to redo it. | Required |

The **Message to the recipient** is sent to them by email with a link to the request. Write it so the recipient knows exactly what to send next.

An item review also sets the files on that item:

* **Approve** and **Mark incomplete** accept the item's files that haven't been reviewed yet.
* **Reject** rejects them.
* Files that already have a file review keep it. If every file on the item has one, your decision applies to the item only.

### What happens after a checklist item review

* **The recipient is notified.** They get your decision and message by email, and by text if they receive the request by SMS.
* **Their checklist updates.** The next time they open the request, they can see which items are approved and which still need something.
* **Rejected and incomplete items reopen.** The recipient can upload to the item again. If they had already responded to everything, the request goes back to **Sent** and automated reminders start again.

{% hint style="info" %}
Review emails are batched. Pipefile waits 30 minutes after your last review on a request before sending, so reviews you give close together arrive as one email.
{% endhint %}

Made a mistake? Select **Undo item review** on the item. Undoing also restores any signatures that the review voided.

## File reviews

A file review is a quick accept or reject on a single file. Use it to track which files you've checked without bothering the recipient.

You can review files in two places:

* **The file preview.** Open a file and select **Accept file** or **Reject file**. You can also press **A** to accept or **X** to reject. Select **Undo review** to clear the review.
* **The request page.** Select one or more files on a checklist item, then select **Accept selected files** or **Reject selected files** in the toolbar.

### What happens after a file review

* **No notification is sent.** The recipient isn't told.
* **The checklist doesn't change.** A file review doesn't reopen the item, so it doesn't restart reminders.
* **The recipient sees it only in their request overview.** If they open it, they can see which files you accepted or rejected.
* **Rejected files are hidden.** On the request page, select **Show *****N***** rejected files** below the file list to see them again. Rejected files are left out of downloads and exports.

{% hint style="warning" %}
Rejecting a signed form voids its signatures. The form has to be signed again.
{% endhint %}

{% hint style="success" %}
If you need the recipient to fix or resend something, use a checklist item review. A rejected file on its own won't prompt them to act.
{% endhint %}

## Which review should I use?

|                                             | Checklist item review                   | File review      |
| ------------------------------------------- | --------------------------------------- | ---------------- |
| **What you review**                         | A checklist item (one or more files)    | One file         |
| **Options**                                 | Approve, Mark incomplete, Reject        | Accept or Reject |
| **Notifies the recipient**                  | Yes, after a 30-minute delay            | No               |
| **Reopens the item and restarts reminders** | Yes, when you reject or mark incomplete | No               |

Use a **checklist item review** when:

* A document is missing pages, expired, or the wrong version.
* You want to confirm to the recipient that an item is done.
* You need to explain what to send next.

Use a **file review** when:

* You're working through a large upload and marking what you've checked.
* You want to flag files for your team before deciding on the checklist item.

## Mark the request complete

When you have everything you need, select **Mark completed** at the top of the request. Confirm with **Mark Complete**.

* Your recipients are told the request is complete and no further action is needed.
* You can no longer review items on a completed request. To make changes, reopen it first. See [Expiration, completion and reopening](/requests/expiration-and-reopening.md).
* The confirmation dialog also lets you pick an export destination, so the files go to your cloud storage as the request closes. See [Cloud storage integrations and auto-export](/reviewing-and-exporting/cloud-storage-and-auto-export.md).

## Related

* [Download and export to PDF](/reviewing-and-exporting/download-and-pdf-export.md)
* [Reminders and notification sequences](/reminders-and-notifications/reminder-sequences.md)
* [E-signature](/forms-and-esignature/e-signature.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.pipefile.com/reviewing-and-exporting/understanding-reviews.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.