--- title: Delivery slug: delivery docTags: createdAt: 2024-03-28T14:01:52.183Z --- # What is the Delivery Phase? Every workflow ends in a delivery phase. When an input enters this phase, it becomes a delivery-ready annotation and completes the request. 🎉 ![](https://api.archbee.com/api/optimize/wLEz_RbWP6nIMpY-prjlm/qvnKn1aU3J1SjZQtwB8xK_image.png "A general sketch of the workflow \"Annotation + Full review + Sampled review\"") # Available actions In the Delivery phase, there are multiple ways to iterate further on an annotation, if needed. These are presented below. ### Send for correction Managers inside a requests producer organization of a request you can send a delivery-ready input for correction. This will move the input to the workflow stage *Delivery: Correct* and create a Correction task. The action will remove the Input from *Delivery: Ready* state but keep it in the same Workflow phase (Delivery). If desired, you can assign the Correction task to a specific workforce member. However, this is an optional function and not selecting this means the task will be available for workforce members configured to work in the stage *Delivery: Correct*. ![](https://api.archbee.com/api/optimize/wLEz_RbWP6nIMpY-prjlm/hCY50z2Rv1A3812Wmbnny_send-for-correction.gif) ### Send for Review Managers of a request's producer or owner organizations can create review tasks for *Delivery: Ready* inputs. Just after sending a delivery-ready input for review and while the input is in its first review round it will be part of both the workflow stages *Delivery: Review* and Delivery: Ready. This is because the delivery-ready annotation isn't replaced until it has been accepted or rejected in review. If desired, you can assign the Review task to a specific workforce member. However, this is an optional function and not selecting this means the task will be available for workforce members configured to work in *Delivery: Review*. ![](https://api.archbee.com/api/optimize/wLEz_RbWP6nIMpY-prjlm/-N8r2MmhvhuW1JJY7pCCR_send-for-review.gif "Sending an delivery-ready input for review") ### Quick accept Accepts and moves inputs with unstarted review tasks to the stage *Delivery: Ready *without needing to be accepted by a reviewer inside a review task. Inputs with unstarted review tasks have the Task type "Review" and current task state "To Do". ::::WorkflowBlock :::WorkflowBlockItem Find the input/inputs you want to Quick Accept inside the **Phase inputs **table. You can use the search bar or the input ID filter if needed. ::: :::WorkflowBlockItem If you only want to quick accept one input, you can use the "Quick accept"-option in the inputs options menu. ::: :::WorkflowBlockItem If you want to quick accept multiple inputs, select them using the row checkboxes and then click the "Quick accept"-option inside the action bar that appears at the bottom of the page. ::: :::: ### Download Annotation For Delivery: Ready inputs, you can download the Annotation in the OpenLabel format. You do this by opening the inputs option menu and clicking the button "Download annotation". *** # Available monitoring ## Progress This section's content helps you understand how many inputs are delivery-ready and whether any additional iteration is being performed inside the delivery phase. ### Inputs in this phase The number of inputs inside the delivery phase that currently are in the stages Delivery: Review and Delivery: Correct. ### Inputs ready for delivery The percentage out of all inputs that are ready for delivery and download. ### General phase progress In this graph, you get insight into how the requests inputs are distributed in relation to this phase and its workflow stages. You can see how many inputs are in an earlier phase, how many are inside the phase, and in which workflow stage they are, as well as how many have are delivery-ready. *** ## Phase inputs In the phase input table, you can see all inputs that are currently inside the delivery phase. For each input, you can see when it changed workflow stage, how many tasks have been done on it in the current phase, and the state and type of any current task. The actions **Send for review**,** Send for correction**, and **Quick Accept **are available for specific inputs. You can read more about them in the section "Available actions" above. *** ## Error Summary With the Error summary you get insight into what issues reviewers have found and commented on during the delivery phase's review tasks. It helps you understand the most common and less frequent identified issues. :::hint{type="info"} The error summary insights are based on feedback items written by the phase's reviewers. Absolute numbers represent actual feedback items, not the edits made in response to the feedback. ::: ![](https://api.archbee.com/api/optimize/wLEz_RbWP6nIMpY-prjlm/q_CvVbpQe0I2hj4tfVzlF_error-summary.png "Example error summary") ### No of Correction Requests The number of feedback items of the type "Correction Requests". This is the sum of all errors shown in the "Error Type Distribution" to the right. ### No of Feedback Items The number of feedback items of the type "Advice". These are excluded from the chart "Error Type Distribution" and "Suggested properties". ### Error Type Distribution Shows the absolute count and relative share of all feedback items categorized as "Correction Requests", grouped by their error type. ### Suggested Properties For those items with the error type *Properties, *this shows the distribution of properties that we affected. Each error indicated as *Properties* has a single property connected to it. *** ## Individual Feedback Items This section helps you to get an overview of all given feedback, to answer questions such as: - How detailed and critical is the feedback of my colleague reviewers? - Are the reviewers giving valid feedback given the current guideline? - What is feedback where the reviewer and annotator are discussing in the comments? - How does feedback of type "MissingObject" look? - What type of feedback is marked as "invalid"? The items are split up by their feedback type. ### Correction Requests In this section, you see feedback items for the type Correction Request. These are things that the reviewer wants to get corrected before accepting the review. You can filter the feedback items by their Resolved status, the Error type, whether a discussion thread exists, or whether the overall Review of the input has been accepted yet. Below is a description of what information is available for each correction request. **Status** | Status | Comment | | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Unresolved | When created by the reviewer, and not yet approved | | Corrected | When the annotator has fixed the issue mentioned in the correction request. | | Resolved | When the reviewer has approved the annotators fix. | | Invalid | An item can be marked as "Invalid" by the user if they think it's not accurate with respect to the guidelines of the task, this can be due to mistakes in machine-generated feedback or from human reviewers. | An item can be "Unresolved" even if the overall Review was accepted, or the other way around. **Error Type** The type of error that was selected in the Correction Request. **Suggested property** If the Error type is "Properties", this column shows which property and value was suggested by the reviewer. **Comment** Shows the description that the reviewer might have given. **Thread exists** Will say "Yes", if there was any reply to the item, i.e. a discussion thread has been started in relation to the item. **External Scene ID** The scene ID of the reviewed annotation. **Current Round** The review round in which the input of this feedback item currently is. All inputs start in round 1. With each rejected review, they progress 1 round forward. **Accepted Review** Whether the overall Review was accepted or not. ![](https://api.archbee.com/api/optimize/wLEz_RbWP6nIMpY-prjlm/m__Duxa9yu_dSSesbTt6Q_screenshot-2024-04-09-at-105222.png) ### Feedback In this section you see feedback items of the type Advice. As the underlying data has less structure, the table has fewer columns and filtering options, but otherwise, it looks the same as the one above.