Within COR we have the “Rework” functionality, which allows us to keep track of tasks that require modifications for optimal delivery. With this function, we can count the amount of reworks and the time it takes to analyze the deviations and make the tasks more efficient.
COR recommended workflow
In the recommended workflow, collaborators deliver a task assigned by their project managers (PM), setting the task status as finished.
Note: If you have the “In Review” status active, you can also use this as a pre-stage for the collaborator's handover to the PM.
If the project manager approves the task, they will send it to the client, but if they consider that there are changes to be made, they will create an “Internal rework”.
Once sent to the client, the client will give feedback. If the client approves, the task will be considered completed and the project manager will archive the task. If the client wants modifications, they will ask the PM for a rework, and the PM to the collaborators.
We also have the possibility for our client to use COR with role 6, so that he can independently visualize the delivery, work simultaneously and if necessary mark the rework himself.
How do I mark a rework in a task?
Within the task panel we will find the rework symbol at the top right edge.
To mark a rework, we must click on the icon, which will open a new modal to add all the information.
At the top we will select if the rework was requested by the client or if it was internal.
Types and Reasons for Reworks
There are two types of reworks and they are used to indicate where the rework request comes from:
Internal: Used when the request comes from the PM.
Customer: Used when the request comes from the Client who owns the Project.
Then we can select the Reasons for the rework. In the dropdown we will find the following options:
- Adjustments: Small changes to improve or optimize something in the delivery.
- Redefinition: Bigger changes to the initial request.
- Additional: Extra orders over the initial request.
- Correction: Rectify errors or problems in the deliverables.
Below we have the “Deadline” box, which is an optional field and represents the new delivery date, which we can chose from a calendar.
Note: soon it will also be possible to change the original task's deadline.
Next we have the drop-down with the “Collaborators” who will be responsible for performing the rework. These are also chosen from a drop-down menu.
Note: if the Client marks the rework, the PM will be selected by default, and the PM will then select the collaborators.
Finally there is the “Description” with the details to be taken into account when performing the rework.
To create the rework, click on the “create rework” button below, which is enabled when all the fields are completed.
To confirm the rework, we will place “Confirm” in the next box:
NOTES: All the hours logged after the rework will be “rework” hours. It should be noted that for now the reworks are not editable and cannot be deleted.
We can select the option “Do not show this message again” so that the modal does not appear again the next time we create a rework.
Finally we can visualize the rework in the following way. We can also the number of reworks in the rework icon. We will be able to visualize the rework in detail within the task messages.
Visualization in reports:
We will be able to view the logged rework hours in the Hours Report from the Hours section, as well as in the hours-related reporting of the different Insights panels in the Metrics section.