| Scope and covered activity | ISO/IEC 42001 is a certifiable AI management system standard for responsible AI governance, risk, controls, monitoring, and improvement. | The EU AI Act is binding EU AI regulation with role, risk, transparency, governance, conformity, and post-market duties. | Write the scope memo so teams can see when ISO/IEC 42001 is the implementation structure, when EU AI Act controls the obligation or assurance question, and where evidence can be reused without changing the source test. |
|---|
| Who must act | ISO/IEC 42001 ownership should sit with the team that can operate the relevant management system, control process, risk method, supplier relationship, incident process, privacy process, or AI governance scope. | EU AI Act ownership should follow that source's role model, such as regulator-facing accountable body, service organization, framework owner, provider, customer, processor, deployer, supplier, or risk owner. | Do not copy owners from one side to the other; map accountable owners, reviewers, and approvers separately. |
|---|
| Trigger or threshold | ISO/IEC 42001 work is triggered by scope definition, implementation, certification readiness, customer assurance, control gaps, incidents, supplier changes, or management review. | EU AI Act work is triggered when an AI system is placed on the market, put into service, or used in the Union and the Act's role-, risk-, transparency-, or high-risk obligations apply. | Use the trigger to route intake: standards implementation, regulatory response, assurance report, framework mapping, customer request, or operational remediation. |
|---|
| Core obligations | ISO/IEC 42001 requires practical governance: scope, roles, risk or impact decisions, evidence, operating cadence, monitoring, review, and improvement. | The EU AI Act requires legal compliance work tied to the specific role and risk class of the system: prohibited-practice checks, high-risk requirements, transparency duties, conformity assessment, registration, and post-market monitoring. | Translate both sides into a single task register only after labeling which requirement or guidance source each task satisfies. |
|---|
| Evidence and records | ISO/IEC 42001 evidence should show the process operating: owners, decisions, registers, control records, test results, review minutes, audit samples, or corrective actions. | EU AI Act evidence should match its own proof model, such as regulatory records, attestation evidence, framework profiles, risk analysis, or contractual assurance. | Build an evidence matrix with one row per claim and columns for source, owner, artifact, date, review trigger, and reuse permission. |
|---|
| Timing and cadence | ISO/IEC 42001 timing follows implementation, audit, certification, review, supplier, incident, or change cycles rather than a single universal deadline. | EU AI Act timing follows the legal application dates, transitional periods, conformity-assessment milestones, and post-market obligations that apply to the relevant AI system and role. | Track dates separately so an ISO review cycle does not get mistaken for a statutory deadline or assurance reporting period. |
|---|
| Enforcement or assurance route | ISO/IEC 42001 is usually tested through certification audits, internal audits, customer assurance, management review, or governance review, depending on how the organization adopts it. | EU AI Act is enforced as binding EU law through market-surveillance authorities, notified-body and conformity-assessment routes where applicable, post-market monitoring, and penalty exposure. | Separate audit readiness from legal compliance and from voluntary framework maturity so executives see the actual consequence of gaps. |
|---|
| Overlap and reuse | ISO/IEC 42001 can supply reusable management-system evidence, control operation records, risk decisions, and review outputs. | EU AI Act can reuse some of that evidence when the control, process, risk, or duty is genuinely the same. | Reuse evidence only after checking scope, actor, date, data type, service, supplier, and acceptance criteria; otherwise keep separate records. |
|---|
| Practical decision rule | Use ISO/IEC 42001 when the main work is building, operating, reviewing, or proving a management-system or standards-based control process. | Use EU AI Act when the main work is satisfying that side's law, assurance route, framework outcome, risk method, or external reporting expectation. | If both apply, keep the primary obligation visible and use the other side as supporting structure, not as a substitute source. |
|---|