Using Landing Zone Assessment In Reviews And Reports

What this page is for

This page explains what changes when you turn Landing Zone assessment on and how that affects both the review page and the final report.

When to use it

Use this when:

• you are deciding whether to enable Landing Zone assessment for a review
• you want to know what additional value it adds to the output
• you need to explain why the report includes Landing Zone content

How it affects the workflow

When Landing Zone assessment is enabled:

• the review runs the additional Landing Zone checks
• the review page includes a Landing Zone Scores tab
• the Report tab can include a separate Enterprise-Scale Landing Zone Assessment download
• the report-ready email can include a separate Landing Zone download link
• the Landing Zone output can include architecture visuals that show the current platform shape

What it is for

Turn it on when the audience cares about platform maturity, governance alignment, or landing-zone design rather than only raw review findings.

What to expect

Landing Zone assessment should complement the normal review, not replace it. It gives you a second lens on the environment and can produce a separate report output alongside the normal resource assessment.

Common mistakes

• turning it on by default without considering whether the audience needs it
• expecting Landing Zone content to make sense without understanding the main review first
• expecting a Landing Zone report link when the assessment was not selected
• using it as a substitute for reading the core review output

Next step

• What the Landing Zone assessment covers
• Understanding Landing Zone results