# 6.3.2 Defining the scope

The organization sets out the scope of each risk management activity (ISO 31000:2018, 6.3.2): its objectives and the outcomes expected, the period and places covered, what is in and out, the tools and techniques, the resources and who is responsible, and how it connects with other projects, processes and activities. The step before 6.3.2 supplies its input, so run both together.

- Framework: ISO/IEC 23894:2023
- Cited to: ISO/IEC 23894:2023, clause 6.3.2
- Source: https://www.iso.org/standard/77304.html
- Last updated: 2026-10-20

## What it asks

The organization sets out the scope of each risk management activity (ISO 31000:2018, 6.3.2): its objectives and the outcomes expected, the period and places covered, what is in and out, the tools and techniques, the resources and who is responsible, and how it connects with other projects, processes and activities. For AI the scope names the system, its intended use and users, and where it fits among the organization's other activities.

## Where generative AI changes the answer

The scope decision that causes most trouble is whether a bought copilot embedded in another product is in scope, because no one on the team owns it.

## Who it binds

The AI risk owner, the assessment team and the business owner of each generative AI use.

## Evidence an auditor samples

- Scope statement naming the AI system, intended use and exclusions

## The test you can run

Ask for one completed assessment for a live use, with its criteria, its analysis and its treatment decision.

## Common failures

- Scope silent on which uses of the system are covered

## Before the draft publishes

Run the step once, by hand, on one live generative AI use, and keep the working paper. A method that has never been run on a real use is a template.

## What this page does not say

It does not state the text of ISO/IEC DTS 25568, because ISO has not published the draft's clause text. It does not certify anything.

Not legal advice; does not certify.