Start with the decision an IT architecture review must support. Define the business scenario, the users and the system boundary. The diagram is a view of the solution; it needs to help explain behaviour, dependencies and responsibility.
Follow one request from authentication through application services and data access. Ask what happens when a dependency fails, how the failure is observed and who owns recovery. Include the operational path alongside the successful path.
Close with design findings, evidence needed and accountable owners. Keep the review and decision records close to the delivery work so the next discussion starts from the latest understanding.

