The Feedback functionality in COR allows us to exchange comments and suggestions in a centralized way on specific files such as images, videos, PDFs or GIFs. It is designed to optimize communication and the creative process within projects by linking each observation to an exact point in the file. In this way, we avoid the dispersion of emails or external messages and maintain a complete record of all versions and reviews.
Through the use of interactive markers, any of the task members can highlight an area of the file, leave their remark and generate an ordered thread of conversation. This functionality is integrated into the Files tab of each task and is key to streamlining the review and approval of deliverables, reducing time waste and misunderstandings.
- Adding comments on files
- Who can comment and approve in Feedback?
- Version management and approval of pieces
- Benefits of using Feedback
- Difference between Feedback and Reworks
Adding comments on files
To use the Feedback tool, we will first navigate to the task’s Files tab and select the speech‑bubble icon (identified as “View message on Feedback”) that appears next to the file. Clicking on that icon will open the viewer in Feedback mode.
In this page, if the file is an image, GIF, video or compatible PDF document, we will see a preview on which we can work; otherwise, COR will inform us that there is no preview available and will only allow us to download the file.
When there is a preview, the annotation tools will appear in the bottom bar. We will select the type of marker (pointer, arrow, rectangle, pencil, highlighter, among others) and click on the specific area of the file we wish to highlight. Doing so will display a text box where we will write our feedback and then save it by clicking on 'Confirm'. Each comment will be linked to the exact point in the file and will be visible as an interactive marker, allowing other task members to reply in the same thread and keep the conversation orderly.
On the side of the viewer we will find the Versions section. There we will be able to upload a New version of the file once we implement the requested changes. The system will preserve the history of comments and versions, thus facilitating the traceability of the work done.
Who can comment and approve in Feedback?
The Feedback functionality is available to all task members. This includes those with the Client role, provided they have project access and the necessary permissions. Everyone will be able to review the file preview and leave comments using markers.
However, there are differences depending on the role:
- File author: The person who uploaded the file will be the one who can send it for review. Once they consider the piece ready, they will use the button on the Feedback bar to submit the version to the corresponding Project Manager.
- Project Manager (PM): The PM of the task will be responsible for accepting or requesting changes to the piece. When they receive a review request, they will set the file status to Pending, Approved or Requires changes, and leave additional comments if adjustments are needed.
- Rest of the task members: The other members will be able to view and comment on all versions of the file. They can participate in discussions, clarify doubts and provide suggestions, but they will not have the option to approve or reject the piece.
Version management and approval of pieces
When working with Feedback, each file will have a version history. Once we have incorporated the changes requested by the Project Manager, we will be able to upload a new version from the “Versions” section in the viewer’s side panel. In doing so, the previous version will be stored and its comments preserved to maintain traceability.
The approval process will follow a defined workflow. When the author of the piece considers a version ready, they will send that version for review using the appropriate button on the Feedback bar. This will notify the assigned Project Manager, who will evaluate the piece and assign a status: Pending while the review is in progress, Approved if the piece meets the requirements, or Requires changes if adjustments are necessary. In the latter case, the PM will record their observations through markers and return the file so that the author can implement the corrections.
Once approval is received, the version status will be updated in the task’s Files tab, and members will be notified that the piece is ready for delivery. This cycle of versions and approvals will allow us to maintain a detailed record of each iteration and ensure that the final product reflects all observations made.
Benefits of using Feedback
Using Feedback in COR provides multiple benefits that improve communication and work efficiency:
- Centralization of comments: All comments on a file are registered in one place, avoiding scattering across emails or external chats.
- Greater clarity: Each comment is linked to a specific point in the file through a marker, preventing ambiguity and misunderstandings.
- History and traceability: All versions of the file and the comments associated with each are preserved, allowing us to review the evolution of the piece and ensuring no observation goes unanswered.
- Efficiency in review: By having an interface designed for feedback exchange, we speed up the review and approval process, reducing downtime and improving the quality of deliverables.
- Coordinated collaboration: Since all task members have access to the comments, a collaborative workflow is generated in which improvements are implemented in context, avoiding duplicate corrections and enhancing final coherence.
Difference between Feedback and Reworks
Although both functionalities are used to make adjustments to a task, Feedback and Reworks address different needs. The Feedback functionality is aimed at the detailed review of creative pieces; it allows us to place markers on a file (image, video, GIF or PDF) and leave specific comments to refine details during the normal production process. Each observation is associated with a version of the file, facilitating agile communication and avoiding misunderstandings.
For its part, the Rework functionality is designed to formally record changes that exceed the original scope of a task. If modifications requiring additional effort or a deviation from what was initially estimated are requested, we can generate a rework to document those changes. By doing so, we are able to measure the hours invested in that additional task and assess the impact on the project’s timelines and costs.
The main difference lies in the purpose and approach: while Feedback is used to adjust details and polish deliverables within the planned workflow, Reworks is used to control and justify significant modifications that generate deviations. In addition, Reworks automatically records the time devoted to those changes, whereas Feedback does not by itself account for extra hours.