@@ -123,7 +123,7 @@ The Data Manager has several columns to display comment information:
 You can configure the project so that annotators and reviewers are required to leave comments after taking specific actions:
 
 * [**Annotation > Annotating Options > Annotators must leave a comment on skip**](project_settings_lse#Annotation)
-* [**Review > AReviewers must leave a comment on reject**](project_settings_lse#Review)
+* [**Review > Reject Options > Reviewers must leave a comment on reject**](project_settings_lse#reject-options)
 
 ## Comment notifications
 
 
@@ -512,7 +512,9 @@ Tasks are shown in randomized task order while preserving the stable order of an
 
 <dd>
 
-Configure what rejection options are available to reviewers. 
+Select which reject options are available to reviewers, and which one is the default. 
+
+Use the **Available** column to choose the options. At least one option must be available. Use the **Default** column to choose the option that is applied when a reviewer clicks **Reject** without opening the menu. 
 
 <table>
 <thead>
@@ -524,45 +526,60 @@ Configure what rejection options are available to reviewers.
 <tr>
 <td>
 
-**Requeue rejected annotations back to annotators**
+**Reject and do not require rework**
 </td>
 <td>
 
-When a reviewer clicks **Reject**, the annotation is reassigned back to the annotator. 
+The annotation is rejected and is not sent back to the annotator for rework. 
+
+This is the default for new projects.
 
 </td>
 </tr>
+<tr>
 <td>
 
-**Remove rejected annotations from labeling queue**
+**Reject and return to annotator**
 </td>
 <td>
 
-When a reviewer clicks **Reject**, the annotation is not reassigned back to the annotator. 
+The annotation is rejected and sent back to the original annotator for rework. The annotator sees the rejected annotation in their labeling stream and can update it. The updated annotation is then shown to reviewers again in the review stream. 
 
 </td>
 </tr>
 <tr>
 <td>
 
-**Allow reviewer to choose: Requeue or Remove**
+**Reject and pass to another annotator**
 </td>
 <td>
 
-Reviewers see the following options:
+The annotation is rejected and the task is sent to a different annotator for a new annotation. 
 
-* **Accept**
-* **Remove** -- When selected, the annotation is rejected and removed from the labeling queue. 
-* **Requeue** -- When selected, the annotation is rejected and then reassigned back to the annotator.  
+The rejected annotation no longer counts toward the project's [overlap](#overlap), which opens one slot on the task for another annotator. The original annotator can no longer update the rejected annotation. The annotation, its rejection, and the time spent on it remain in the Data Manager and in dashboards.
 
-For example, a reviewer might decide to requeue an annotation that is nearly correct but just needs a slight change. However, an annotation with numerous errors may be easier to simply reject entirely and remove from the queue. 
-
-Note that when you click **Remove**, the annotation is also marked as cancelled/skipped. This is reflected in various metrics (for example, Data Manager columns and dashboards), and differentiates between the two rejection actions in the API with `was_cancelled: true`. 
+This option is only available when [**Task Assignment**](#distribute-tasks) is set to **Automatic**.
 
 </td>
 </tr>
 </table>
 
+When only one option is available, reviewers see a single **Reject** button that applies it. When more than one option is available, reviewers can click **Reject** to apply the default option, or open the reject menu to choose another option:
+
+* **No Rework** -- Reject without sending for rework.
+* **Return to Annotator** -- Reject and send back to the original annotator for rework.
+* **Pass to Another Annotator** -- Reject and send to a different annotator.
+
+![Screenshot of the reject menu](/images/review/reject-menu.png)
+
+For example, a reviewer might return an annotation that is nearly correct and only needs a small change. For an annotation with numerous errors, they might pass the task to another annotator instead. 
+
+The same options are available when reviewers reject annotations in bulk from the Data Manager. 
+
+Changing the available options only affects future rejections. Annotations that were already rejected keep the outcome that the reviewer chose. For example, annotations that were returned to an annotator can still be updated by that annotator after you make **Reject and return to annotator** unavailable. 
+
+Separately, you can enable **Reviewers must leave a comment on reject** to require reviewers to add a comment before they can reject an annotation from the review stream. This does not apply to bulk rejections from the Data Manager.
+
 </dd>
 
 <dt id="data-manager">Data Manager</dt>
 
@@ -79,7 +79,7 @@ stateDiagram-v2
     ANNOTATION_IN_PROGRESS --> COMPLETED: Annotations complete -<br>review not required
     NEEDS_REVIEW --> REVIEW_IN_PROGRESS: First review started
     REVIEW_IN_PROGRESS --> COMPLETED: All reviews done
-    REVIEW_IN_PROGRESS --> ANNOTATION_IN_PROGRESS: Annotation rejected<br>(requeue mode)
+    REVIEW_IN_PROGRESS --> ANNOTATION_IN_PROGRESS: Annotation rejected<br>(returned or passed)
 
     class CREATED neutral
     class ANNOTATION_IN_PROGRESS grape
@@ -91,7 +91,7 @@ stateDiagram-v2
 | State | Description | 
 |----------|------------|
 | **Initial** | Task has been created but does not have any annotations yet. |
-| **Annotating** | First annotation has been submitted, or a rejected annotation has been requeued back to the annotator. <br/><br/>Whether the task lingers in this state long enough for it to be reflected in the Data Manager depends on your project settings. See [Additional notes](#Additional-notes) below.|
+| **Annotating** | First annotation has been submitted, or a rejected annotation has been [returned to the annotator or passed to another annotator](project_settings_lse#reject-options). <br/><br/>Whether the task lingers in this state long enough for it to be reflected in the Data Manager depends on your project settings. See [Additional notes](#Additional-notes) below.|
 | **Needs Review** | The required number of annotations have been completed and the task is ready for review. <br/><br/>Whether the task enters this state depends on your project settings. See [Additional notes](#Additional-notes) below. |
 | **In Review** | First review has been created for any annotation within the task.  <br/><br/>Whether the task enters this state depends on your project settings. See [Additional notes](#Additional-notes) below.|
 | **Done** | All required annotations and reviews have been completed. |
 
@@ -35,7 +35,15 @@ After you [assign reviewers to tasks](#Assign-reviewers-to-tasks), they can revi
     - If the annotation is correct, click **Accept**. 
 
     - If the annotation is mostly correct, you can correct it by selecting a different option, changing the selected region, moving the bounding box, or whichever makes sense for the type of label you're reviewing. After correcting the annotation, click **Fix & Accept**. 
-    - If the annotation is completely incorrect, or you don't want to attempt to correct it at all, click **Reject** to reject the annotation. To place a rejected task back in the Label Stream for annotation, you must delete the annotation. Rejecting an annotation does not return it to annotators to re-label.
+    - If the annotation is incorrect, or you don't want to attempt to correct it yourself, click **Reject** to reject the annotation. 
+    
+        Clicking **Reject** applies the project's default reject option. If the project has more than one reject option available, you can open the reject menu to choose how to handle the rejection: 
+        
+        - **No Rework** -- The annotation is rejected and is not sent back for rework. 
+        - **Return to Annotator** -- The annotation is sent back to the original annotator so that they can update it. 
+        - **Pass to Another Annotator** -- The task is sent to a different annotator for a new annotation. The original annotator can no longer update the rejected annotation. 
+        
+        Which options you see depends on the project's [**Reject Options**](project_settings_lse#reject-options) settings. 
 
 3. Continue reviewing annotated tasks until you've reviewed all annotated tasks. Click **Data Manager** to return to the list of tasks for the project.
 
@@ -141,7 +149,7 @@ How much access a paused user keeps depends on why they were paused:
 A pause only restricts the type of work that triggered it. Annotation limits and annotator evaluation both measure annotation work, so a flexible pause stops new annotation work only. If a paused user is also a reviewer, they can continue reviewing. Only a full pause stops a user from reviewing. 
 
 !!! note
-    A flexible pause acts as a full pause when the project's [**Reject Options**](project_settings_lse#reject-options) are set to **Remove rejected annotations from labeling queue**. In this case, rejected annotations are never returned to the annotator, so there is nothing for them to recover. 
+    A flexible pause acts as a full pause when the project's [**Reject Options**](project_settings_lse#reject-options) do not include **Reject and return to annotator**. In this case, rejected annotations are never returned to the annotator, so there is nothing for them to recover. 
 
 ### Manually pause an annotator