Appearance
Scope Phase
Scope is where you define what is being governed and what “in scope” means. A good scope makes every later step faster: Requirements map cleanly, risks are comparable, and reviews become auditable instead of interpretive.
Scope is the first of the lifecycle phases:
Outcome
You leave this phase with:
- a registered AI System for the deployed system (or governance initiative), sent for approval
- clear ownership and AI System roles
- frameworks attached so Requirements and Controls are in scope
- initial risks and Evidence planning so implementation can start immediately
Time to first value: 30–60 minutes
Prerequisites: you can create or edit the AI System, or you can work with an AI System Owner
Path at a glance
- Define the system Register the AI System and describe the deployed system.
- Assign roles Ensure Owners and Editors are in place.
- Attach frameworks Scope governance work to standards and regimes.
- Capture risk context Identify initial risks and what Evidence exists.
Step 1: Register the AI System
Goal: establish the unit of governance.
Where in Modulos
AI Registry → AI Systems → New AI Systemto start the registration. The create dialog saves a Draft and opens the registration wizard.AI System → Settings → General Settingsto change the description and lifecycle stage after registration
Do this
- Give the AI System a specific, recognizable name, and select its Owners.
- In the wizard, describe what the system does, who it affects, and where it is deployed.
- Set the lifecycle stage to reflect reality.
You’re done when
- a reviewer can understand what is being governed without additional context
Step 2: Assign owners and AI System roles
Goal: make accountability explicit from day one.
Where in Modulos
AI System → Settings → User Access
Do this
- Assign at least one Owner. Add Editors for the people implementing Controls and attaching Evidence, and Viewers for oversight: Viewers read the AI System and add comments.
You’re done when
- the AI System has clear ownership and review responsibility
Step 3: Attach the right frameworks
Goal: define what “compliance” and “readiness” mean for this system.
Where in Modulos
- the Frameworks step of the registration wizard, and
AI System → Settings → Frameworksafter registration - the EU AI Act question of the wizard, and
AI System → Settings → EU AI Actafter registration, when relevant for classification and scoping
Do this
- Attach the frameworks and standards that apply to this system.
- Record key scoping decisions and classifications where required.
- On the last wizard step, select Create AI System. The status changes from Draft to Pending until an Organization Admin or an Organization Registration Manager approves it. See Registration approval.
You’re done when
- Requirements and Controls are scoped to the frameworks you care about
Step 4: Capture initial risks and Evidence context
Goal: enable fast implementation by starting from what matters most.
Where in Modulos
AI System → Risksto add initial AI System risks and threat selectionAI System → Evidenceto understand what artifacts already exist
Do this
- Identify the top risks for this system and select the most relevant threat vectors.
- Identify what Evidence already exists (policies, logs, design docs) that can support Control execution.
You’re done when
- there is a first-pass risk and Evidence plan to drive implementation