In COR we can indicate the number of deliverables agreed with our clients for each project and in each task we can detail the quantity required in that work order.
For the same task, we can have multiple deliverables attached as they are made; this way, the PM or our client can validate the different deliveries.
We can use different methods to validate and approve the deliverables depending on what we consider more optimal based on our work dynamics.
Task Status
When a team member starts working on a task, he/she should change the status from "New" to "In Progress" to indicate to all members that the task is being executed. When working with deliverables in tasks, it is advisable to turn on the "Under Review" and "Adjustments" statuses so that we know more precisely at what stage the execution is.
When a task has only one deliverable, we can simply indicate that it has been delivered for validation, and the task will go to "Under Review" after attaching the file. The PM or the client can validate the delivery by finalizing the task, request changes by marking a rework, or through a message, changing the status to "Adjustments".
Checklist
In case we have multiple deliverables for the same work order, if we want to know the status of each one, we can do it simply through the task checklist.
With this functionality, each of our deliverables will be an item on the checklist. When attaching the deliverable and after validating it, the PM or the client can mark the item as solved, to indicate that it is approved.
The resolution of the item will then be the approval date of the deliverable, which can be viewed in the task history.
If we want a higher level of precision, in the same checklist instead of indicating the name of the deliverable, we can add two items, one to indicate that it is delivered and another to mark it as resolved.
It should be noted that the checklist items are dynamic and can be edited, new ones can be created later (for example, if we wish to add an extra item for a correction) and reordered as we see fit. This is also useful when there are multiple deliverables that do not depend on each other and may take more time to be approved.
Also, we can use the checklist functionality having only one item per deliverable, but adding the logic of changing the status to "In Process" or "Adjustments".
Subtasks
When working with multiple deliverables in a work order, in the same way that we can track the status with a checklist, we can do it through subtasks.
The mother task will then have the detail with the general description of the order and each subtask will be each of the deliverables, with its individual detecting deliverables by subtask, in the mother task we have the option to automatically count them, according to the number of deliverables of its subtasks.
This option can be very useful when it comes to larger or longer deliverables, which have different managers, or when there are multiple versions within the same deliverable (for example, banners with various sizes or different versions depending on the social network).
It is also a more dynamic way of working if the number of deliverables may vary during the execution of the task, or if there are dependencies between them, since we can concatenate the subtasks so that we cannot continue with a request until the previous one is finished.
Finally, this option also allows each deliverable to have its own checklist. We can detail the different formats of deliverables, apply a step-by-step of a single deliverable and even give more precision of the status of the delivery.
COR has the necessary flexibility to be able to apply different workflows in the different functionalities. Therefore, we can combine any of these options, as we consider convenient for our team.