Start hereIdentify AI systems, models and actor roles
~115 days leftOpen step
Guide library
Regulation Europe

EU AI Act

Artificial Intelligence Act · Regulation (EU) 2024/1689

Classify your AI systems and map obligations to your role and the current phase-in dates.

Who it applies to

Providers, deployers and other actors within the Act’s territorial and material scope, including certain actors outside the EU.

What you’ll produce

Role- and risk-specific governance, transparency, documentation and conformity evidence as applicable.

Separate duties for general-purpose AI models, specific transparency cases and high-risk systems. Check the current amended timetable and sector-specific routes.

Check official publications for this guide
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What systems are we building, selling or using?
Require teams to disclose AI in customer products and internal decisions. Assign responsibilities based on actual development and use, including changes to vendor systems that could shift the organization’s role.
Which uses need a stop or review decision?
Give Legal and the product risk owner authority to pause a potentially prohibited or high-risk use. Record classification, obligations, and applicable dates for each version and purpose.
Who will keep oversight and evidence current?
Reserve capacity for evaluation, documentation, staff training and response. Confirm vendor documentation access, logging and incident responsibilities in procurement decisions.

How to spend the first week

  1. Have Procurement, HR, Engineering and products list active and planned AI uses, including vendor tools and bundled features.
  2. Pick a consequential use. Trace the user, model and version, decision influenced, intervention available and role of each organization.
  3. Give Legal and the operator a clear classification question, preferred owner and date. Put unresolved uses on the next release review agenda.

What to review each week

Track unclassified AI uses, applicable deadlines, failed oversight tests, missing provider documentation and systems approved for one purpose but used for another.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

EU AI Act kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Identify AI systems, models and actor roles · AI governance lead + legal [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Have Procurement, HR, Engineering and products list active and planned AI uses, including vendor tools and bundled features.
2. Pick a consequential use. Trace the user, model and version, decision influenced, intervention available and role of each organization.
3. Give Legal and the operator a clear classification question, preferred owner and date. Put unresolved uses on the next release review agenda.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
DATES AND TRIGGERS

Official milestones

See the deadline calendar
The whole journeyabout 115 days across 4 steps
  1. 01Identify AI systems, models and actor rolesAI governance lead + legal · ~14 days
  2. 02Classify and assign obligationsProduct counsel + risk lead · ~21 days
  3. 03Implement controls and evidenceModel owners + data governance · ~45 days
  4. 04Complete required assessments and monitorConformity lead + operations · ~35 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 12 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Identify AI systems, models and actor rolesAI governance lead + legalAt initiationSet a start dateInventory; Actor-role analysis; Scope decisionOpen
Classify and assign obligationsProduct counsel + risk leadBefore development and market placementSet a start dateClassification memo; Obligation register; Phase-in scheduleOpen
Implement controls and evidenceModel owners + data governanceBefore applicable obligations take effectSet a start dateTraining evidence; Technical documentation; Evaluation and oversight recordsOpen
Complete required assessments and monitorConformity lead + operationsBefore market placement and ongoingSet a start dateAssessment file; Monitoring plan; Incident workflowOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Identify AI systems, models and actor roles

    Who AI governance lead + legal When At initiation

    Inventory uses and model dependencies, intended purposes, market jurisdictions and provider/deployer responsibilities.

    How to do this step

    Before you start

    Product specifications, vendors, deployment geography, intended purposes, version history and contracts.

    1. List each AI system and use separately. Record whether it is built, purchased, branded, integrated or modified and where its outputs are used.
    2. Separate the model from the system, and trace providers, deployers and other actors through the value chain. Flag substantial modifications and changed intended purposes for role review.
    3. Confirm facts with Product, Procurement and Legal. Assign the person who will keep each inventory row up to date.

    What a reviewer should see

    An applicant-screening entry identifies the end use, decision influenced, version, vendor, inputs, people affected and who may override the output.

    When to escalate

    Escalate shared or rebranded systems, unclear supplier responsibilities or a product change with no role review.

    What to produce

    InventorySpreadsheet

    Gather first

    • Asset exports or system discovery
    • Service owner interviews
    • Approved scope and architecture

    How to prepare it

    1. Export a dated baseline from the source system. Give each asset, service or record class a stable ID and remove duplicates without losing links to the source.
    2. Add ownership, purpose, sensitivity and any vendor or system it depends on. Mark unknowns explicitly and assign them to someone to resolve.
    3. Reconcile the register against an independent source such as cloud billing or the production deployment list. Set a refresh cadence and an owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID
    SYS-014
    Item
    Production billing database
    Owner
    Platform operations
    Location and purpose
    Production EU region, stores invoice and account data
    Impact and dependencies
    High. Identity provider and managed backups.
    Verified on
    2026-11-10, cloud inventory export

    Check before handing it over

    Each item has one accountable owner. The source and as-of date let a reviewer trace it back.

    Share the reviewed inventory with the people building the control, privacy or testing scope.

    Actor-role analysisSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

    Scope decisionMemo

    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.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    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.

    Check before handing it over

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

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

  2. 02

    Classify and assign obligations

    Who Product counsel + risk lead When Before development and market placement

    Screen prohibited practices, high-risk criteria, transparency triggers and any general-purpose model obligations. Map applicability and dates by system.

    How to do this step

    Before you start

    Approved inventory, factual use, affected groups, current rules and applicable sector legislation.

    1. Review possible prohibited uses first. Then assess high-risk criteria, transparency duties and any general-purpose model obligations relevant to the actor.
    2. Record the provision, reasoning, applicable date and reviewer for each obligation. Use the current amended timetable and capture which provisions the schedule relies on.
    3. Put restrictions and open questions into the deployment process. Make a new decision when the use, model, audience or material behavior changes.

    What a reviewer should see

    The classification memo shows what the system actually does, which provisions were checked, why they apply and the next review trigger.

    When to escalate

    Bring unresolved prohibited-use or high-risk questions to Legal before launch and escalate missing documentation for a role with obligations.

    What to produce

    Classification memoSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

    Obligation registerSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

    Phase-in scheduleSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

  3. 03

    Implement controls and evidence

    Who Model owners + data governance When Before applicable obligations take effect

    Build required risk and data governance, oversight, evaluations, logging and documentation. Implement literacy and user transparency where applicable.

    How to do this step

    Before you start

    Applicable obligations, technical documentation, evaluation data, oversight design, instructions and product release plan.

    1. Write what the system is allowed to do, who oversees it, what they can see, when they intervene and how they override or stop it.
    2. Test representative failures, foreseeable misuse and the ability of staff to intervene. Record the exact version, test inputs, thresholds, results and unresolved limitations.
    3. Map applicable logging, data governance, transparency and training requirements to actual operation. Assign evidence retention and access roles.

    What a reviewer should see

    An oversight test records a harmful or incorrect output, the reviewer’s intervention, what the downstream user saw and whether action completed before the decision.

    When to escalate

    Raise an untested override, a material performance gap or a system operating beyond its approved purpose.

    What to produce

    Training evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Technical documentationMemo

    Gather first

    • Current authority instructions or package list
    • Approved source records and evidence
    • Submission owner and intended review route

    How to prepare it

    1. Download the current instructions and confirm the required format and version. Create an index that maps every required document or answer to a file and owner.
    2. Cross-check names, version numbers and scope across the package. Check file size, required signatures, redactions and all attachment references against the actual portal requirements.
    3. Have a second person run a completeness check. Save a read-only copy of the submitted version, receipt, and follow-up owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Package section
    Evidence and supporting technical records
    Requirement and source
    Authority package checklist, current release
    Artifact and version
    Test report TR-017 v2, approved
    Responsible person
    Submission coordinator with technical reviewer
    Submission and receipt
    Record the official filing ID and date after upload

    Check before handing it over

    The submitted package can be recreated from the index and the receipt is linked to the exact files.

    Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.

    Evaluation and oversight recordsMemo

    Gather first

    • Approved scenario and participant roles
    • Goals and scoring criteria
    • Event timeline and expected records

    How to prepare it

    1. Prepare a scenario and timed new information that tests decisions, handoffs and evidence. Assign a facilitator and separate observer.
    2. During the exercise, note what participants actually did, the timestamps and where expected responses failed. Distinguish simulated actions from real ones.
    3. Write a short after-action summary with owners, deadlines and a retest plan. Attach the scenario, attendance and evidence references.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Scenario
    Simulated export leak found at 09:20 UTC
    Objective
    Reach operational and legal leads and classify the incident within the exercise target.
    Observed behavior
    Engineering preserved logs. Initial escalation went to an inactive mailbox.
    Action and owner
    Privacy operations updates the routing list before 2026-12-01.
    Retest
    Repeat the handoff in the next on-call drill.

    Check before handing it over

    An absent participant can see what was tested, what happened and why an action was assigned.

    Send approved findings to action owners and file the record for governance or assessment.

  4. 04

    Complete required assessments and monitor

    Who Conformity lead + operations When Before market placement and ongoing

    Select the relevant conformity route where required. Track declarations, registrations, incidents and substantial modifications.

    How to do this step

    Before you start

    Classification, evaluation results, provider materials, relevant standards and applicable release conditions.

    1. Confirm which conformity or impact assessments, declarations and registrations apply to the organization’s role and use. Record who reviews and files each applicable item.
    2. Tie approval to the version, purpose and operator instructions. Schedule production monitoring and document what events require Reporting, Legal or Product review.
    3. Test how the team detects and reports an incident, handles vendor updates and suspends use if needed. Review classification before material changes.

    What a reviewer should see

    A dated release record links the completed applicable assessment, version, evidence, monitoring thresholds and named incident contact.

    When to escalate

    Escalate failed release conditions, suspected serious incidents or a supplier change that breaks the evidence used for approval.

    What to produce

    Assessment fileMemo

    Gather first

    • Current authority instructions or package list
    • Approved source records and evidence
    • Submission owner and intended review route

    How to prepare it

    1. Download the current instructions and confirm the required format and version. Create an index that maps every required document or answer to a file and owner.
    2. Cross-check names, version numbers and scope across the package. Check file size, required signatures, redactions and all attachment references against the actual portal requirements.
    3. Have a second person run a completeness check. Save a read-only copy of the submitted version, receipt, and follow-up owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Package section
    Evidence and supporting technical records
    Requirement and source
    Authority package checklist, current release
    Artifact and version
    Test report TR-017 v2, approved
    Responsible person
    Submission coordinator with technical reviewer
    Submission and receipt
    Record the official filing ID and date after upload

    Check before handing it over

    The submitted package can be recreated from the index and the receipt is linked to the exact files.

    Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.

    Monitoring planMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

    Incident workflowMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    Every decision has one accountable person, a backup and a practical route to reach them.

    Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes