Review an output and record the decision

Workroomly Editorial
Begin the lesson ↓

Share this resource

Copy the link to share this page with your team.

Review the exact output, save a useful comment and update the task to match the result.

Part of Deliver and close a customer project

Review an output and record the decision

A useful review explains what was checked and what happens next. “Looks good” is less helpful than a decision tied to the task’s completion criteria.

Review and record

1. Open the task and read its description and acceptance criteria. 2. Open the exact output versions under Related Documents or the agreed delivery location. Read the full material, not only its filename or preview title. 3. Compare each criterion with the output. Record specific changes needed, or explain why the output passes. Recheck any corrections against the same criteria. 4. Open Comments → Write a comment. Include the output/version, checks performed, decision, unresolved points and next action. For example: “Welcome article v2 reviewed: the first three actions and support link are correct. Approved for publication.” Use wording that reflects your actual review. 5. Check the comment and task audience, then select the send arrow once. Posting a comment is separate from Update Task. 6. Reopen the task and read the complete saved comment. If posting was uncertain, look for it before sending again. 7. Choose the task status that matches its agreed purpose, then select Update Task. Reopen it to check the result.

Expected result: the decision is readable on the task and the status matches the work.

Important: a review task can be finished with a “changes needed” decision if its purpose was to complete the review. The production or correction task remains open until its own criteria are met. Content review is also different from the recipient accepting a delivery.

Continue learning

In this series: Plan and deliver work — guide 12 of 17.

Turn what you learned into the way the team works.

Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.