Mark a requirement as in scope or out of scope
Open the requirement detail page and choose Mark Out of Scope or Mark In Scope to change whether a requirement applies to your site. Only users with the Manager or Admin role for the Standards module can update a requirement’s scope.
Mark a requirement out of scope
Open the standard and select the requirement you want to change.
On the requirement detail page, click Mark Out of Scope.
In the Mark Out of Scope dialog, enter a Justification. The justification is required.
Click Mark Out of Scope to save the change.
After the requirement is marked out of scope, the requirement detail page shows an Out of Scope card with the justification, the date and time of the change, and who made it.
Out-of-scope requirements are visually de-emphasised in the requirement tree and do not affect the compliance score. Only in-scope requirements must be Ready before the standard can be activated.
Return a requirement to scope
Open the requirement detail page for the out-of-scope requirement.
Click Mark In Scope.
Read the confirmation. The requirement will count toward configuration and compliance again, and the previous out-of-scope justification will be cleared.
Click Mark In Scope to save the change.
Adoption parameter exclusions
Some requirements are excluded automatically by adoption parameters set during the standard adoption wizard. These exclusions are shown differently on the requirement detail page and cannot be changed manually. If a requirement is excluded by an adoption parameter, the page shows an Adoption Parameter label instead of the Mark Out of Scope or Mark In Scope controls.