Some requirements genuinely do not apply: a control for a technology you do not run, an outcome for a service you do not provide. Marking them not relevant takes them out of scope honestly.
How to mark it
- On the item, choose Not relevant (in Detailed mode, mark individual statements N/A).
- Enter the reason when prompted. The item will not save as out of scope without one.
Example
Why a reason is required
An unexplained exclusion is indistinguishable from an avoided question. The recorded reason lets a reviewer, a colleague or a regulator see why the item was excluded and decide whether they agree, and it protects you when the assessment is revisited months later and nobody remembers the context.
What exclusion changes
- Excluded items leave the scoring basis: dashboard and report percentages are computed over in-scope items only, and the not-applicable count is shown separately.
- In Detailed mode, N/A statements are excluded from the completeness checks that drive derivation.
- Under a target profile, a targeted outcome marked not applicable still fails its target: a profile expectation cannot be satisfied by exclusion.
- The report lists out-of-scope items with their reasons, so the exclusions are visible rather than buried.