> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/user/review/how-to-upload-a-document-for-review.md).

# How to Upload a Document for Review

This document explains how to upload a DOC or DOCX document and start a review process. It also explains how to configure the request and select reviewers.

### Upload a document for review

{% hint style="danger" %}
Your billing plan must include the Review feature. If your plan does not support Review, DocStudio shows the standard tariff limitation dialog.
{% endhint %}

<figure><img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2FqxfoCJSnyNCQdaOioDkZ%2Fimage.png?alt=media&amp;token=accf85da-1302-48ba-b0ef-31e2511eed62" alt=""><figcaption></figcaption></figure>

You can start a review process directly from the Dashboard. Follow these steps to upload a document, configure the request, and add reviewers:

1. Open the **Dashboard**.
2. Click **For review**.
3. Add **one** DOC or DOCX file.
4. Check the selected file and click **Next**.
   * Check the **Subject** and change it if needed.
   * Enter a message for the reviewers if needed.
5. In **Reviewers**, select a DocStudio mailbox or enter an email address.
   * Repeat this step to add more reviewers.

{% hint style="info" %}
Add at least one reviewer to enable **Send for review**.
{% endhint %}

6. Click **Send for review**.

DocStudio creates the review process and opens the document in the Review editor. You can also find the process on the **Review** page.

{% hint style="info" %}
Each review process can contain one file. You can upload files with the `.doc` and `.docx` extensions.
{% endhint %}

### Review request overview

{% columns %}
{% column width="50%" %}

* **Subject** — Check or edit the review subject.
* **Message** — Add an optional message for the reviewers.
* **Reviewers** — Select DocStudio mailboxes or enter email addresses to invite reviewers.
* **Send for review** — Start the review process and open the document in the Review editor.
* **Back** — Return to the document selection step.
* **Close** — Close the dialog without starting the review.
  {% endcolumn %}

{% column width="50%" %}

<figure><img src="https://2962383972-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoqUiFHjwtCCGSaEDqbXb%2Fuploads%2F5uU3UmMMj656SqezXHVx%2Fimage.png?alt=media&amp;token=73b06294-c62a-405c-ba1c-95016e8232a6" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
When you have the I**nitiator** role, you can invite additional reviewers after the process starts, as described in [Review Process Editor](https://support.docstudio.com/user/review/review-process-editor).
{% endhint %}

### Related topics

* [Review list page Overview](https://support.docstudio.com/user/review/review-list-page-overview)
* [Review Process Editor](https://support.docstudio.com/user/review/review-process-editor)
* [Dashboard Page Overview](https://support.docstudio.com/user/dashboard/dashboard-page-overview)


---

# 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.docstudio.com/user/review/how-to-upload-a-document-for-review.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.