Document review process

[tidiane_diaclient]

Users have reported that the document review process involves too many configuration settings, making it time-consuming. There is a need to simplify the process to improve efficiency and make it easier for users to complete document reviews.

[atighe84]

Hi @tidiane_diaclient 

The review workflows are set up in a way that you have multiple options to configure how a user can respond or action how the review step is responded to. This ensures that you can get the right response to tailor and influence the outcome of the review in question on the project.

Is there a certain review workflow that you and your team are having configuration issues with?

Regards,

Andrew

[tidiane_diaclient]

Hi @atighe84 ,

Thank you for the reply.

The feedback we are receiving is not necessarily related to a specific workflow configuration issue, but rather to some limitations and usability challenges encountered when using the review workflows.

For example, when reviews are configured as a parallel review group, we do not see a way to assign different review due dates to each entity or reviewer within the same group. A single deadline applies to the entire review stage, whereas some teams would like certain reviewers to have shorter or longer review periods than others. From what we can see, this level of control is only achievable through sequential review workflows, where each reviewer has their own review step and due date.

In addition, some users have raised concerns about the number of clicks and configuration steps required to complete or manage reviews. They feel that the review process can become quite time-consuming, especially on projects with a high volume of documents and frequent review cycles. As a result, there is a recurring request to simplify the user experience and reduce the number of actions needed to perform common review tasks.

These are the types of pain points that we have.

Regards,

Tidiane

[atighe84]

Hi @tidiane_diaclient 

Unfortunately for users within a group step, there is only one due date that can be assigned to this step, although you can add the users as key reviewers and then select the option that each key reviewer has to review the information before the next step can commence. That way, you could initiate a 5 or 6 working day timeline to this review step and the users within the step can then delegate who takes more time to do their review within this step than the others within the 5 or 6 day timeline. Not ideal but could be a workaround.

For projects with high volumes of files that need to go through a review process, you could enable the roll back to initiator option within the review template settings at each step. This will encapsulate the review into one unique review ID with multiple rounds if a review step is rejected and reduce the number of separate reviews across on the project.

Regards,

Andrew