# Scope decision

EU AI Act | Worked example with fictional data

Step: Identify AI systems, models and actor roles
Owner: AI governance lead + legal
When: At initiation

## Gather first
- Service inventory and architecture
- Customer commitments and contracts
- Applicable criteria or legal text

## How to prepare it
1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

## Example

### Decision
Cover the hosted billing service for the April to June review.

### In scope
Production billing API, hosting, releases and production access.

### Excluded and why
Internal HR tool. It has no access to billing systems or data.

### Dependencies
Cloud hosting and corporate identity provider.

### Approval
Service owner approves after checking the architecture and contract.

## Review
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

## Handoff
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

Use the current rules and any prescribed forms for your engagement.
