Structured Reviewing – Approval

After the product is reworked based on the review comments, an approval is required. In this approval phase the reviewers get the opportunity to accept or reject the rework which is performed. It shows the reviewers their comments are taken seriously, it provides insight in comments from other reviewers and it creates a final moment to make sure the product fits the reviewers’ needs.

The approval is not meant as:

• a formal acceptance of the product (which should be arranged in a formal RACI/stake holder list)
• a second review phase. New comments are not wished, unless they arise because of the recently performed rework.
• a new discussion phase to widely discuss the products.
  
  

The approval phase is meant to:

• check if the rework is done as intended
• check if rework based on comments of other reviewers does not conflict with your interests
• thank the author for the rework
  

Strategy

Approving rework can be done with various levels of detail. Depending on the risks and the importance of the comments, a reviewer can choose for a strategy.

1. Just check the statuses. If all are Accepted –> accept the rework. For Rejects, check the author’s response.
2. Check all statuses ánd all the author’s responses. See if you agree with the responses.
3. Check all statuses, responses and randomly check some performed rework. Preferably take a random check on some Major comments.
4. Check all reworked comments in the overview ánd check all rework in the document.
   
   

All of the above can be done checking all comments or only your own comments.

When disapproved, inform the moderator and clearly state why the rework is disapproved and what should change to get it approved.

Next step: Finalization