An Infrastructure Engineering Project has been taken up by an Engineering Consultant Firm (AAA).

The Infrastructure Owner (OOO) who awarded the project to AAA requires that all engineering documents produced by AAA pass through the Review by another third party Engineering Consultant (RRR). The Engineering deliverables produced by AAA can only be considered finalized and concluded only if they have successfully satisfied all comments raised by RRR.

The Engineering Documents are typically documents produced by many disciplines. In this particular example we can assume that the following engineering disciplines are involved: Architectural, Structural, Geotechnical, Electrical, Mechanical, Piping. Both AAA and RRR need to mobilize engineers from all these disciplines. AAA needs to mobilize all these engineers to work & develop the Documents and also to support the responses to RRR's comments and the revision preparation that may be required due to these comments. On the other hand, RRR needs to mobilize all these engineers in order to Review and raise comments if any until the Document has been appropriately revised by AAA to allow its approval and closure for further actions by OOO. The above case can be typically found in many infrastructure projects around the world, either at a pure Design Stage or in Design & Build Projects (i.e. Engineering Procurement Construction (EPC)). In this particular example each of the above parties will be assigned the following roles in the context of contrat.io's workflow: AAA: The individual who acts as key focal point on behalf of AAA (e.g. the Project Manager or the Engineering Manager) will be taking up the role of Author. Each invovled Discipline Lead Engineers (e.g. Electrical, Structural etc) will be taking up the role of co-Author. RRR: The individual who acts as key focal point on behalf of RRR (e.g. the Project Manager or the Engineering Manager) will be taking up the role of Reviewer. Each invovled Discipline Lead Engineers (e.g. Electrical, Structural etc) will be taking up the role of co-Reviewer. The Document Controller will be the individual who initiates the process of Document Review. It can be any of the Document Controllers or Project Managers of AAA or RRR. The sole responsibility of the Document Controller is to assign the appropriate names and email addresses for all other roles, Author, co-Authors, Reviewers, co-Reviewers. It is noted that Authors can assign co-Authors themselves as well whereas Reviewers can do the same for co-Reviewers as well. The Review workflow is then followed through contrat.io. The use of contrat.io enables smooth iterations between parties and facilitates the resolution of Reviewer comments and conclusion of the Documentation for further actions by OOO.