The review of an IT architecture is done in two phases, the first focuses on the generated architecture, ensuring that it is complete and consistent, which is normally an IT architect peer review. Typically, once an architecture view is completed, this peer review is done prior to moving on to next steps; this is therefore the last step in finalizing a view within the Perspective (i.e. a set of models, the process models for example). See for example: Activity: Define Logical Perspective and the final step Task: Assess the Architecture.

The second step, the review described here, is a review of the content of the architecture in terms of how accurately it captures the business, which normally involves a number of stakeholders that have intimate knowledge of the area of the business in question and at the correct level, namely Business, Logical or Technical.

The purpose is to ensure that there is cohesion and agreement in the models, from the architecture perspective and agreement from stakeholders. This review may be done at any time, but after the completion of a perspective, and after the perspective has been analyzed and updated as needed (i.e. the Task: Analyze the Architecture has been completed). This review is focused on communicating the IT architecture and soliciting feedback.

Actions defined during the review are documented, assigned and tracked.