EU AI Act
Classify your AI systems and map obligations to your role and the current phase-in dates.
ISO/IEC 42001:2023 · AI management systems
Put AI governance, impact assessment and lifecycle controls into a certifiable management system.
Organizations developing, providing or using AI that want an AI management system in a defined scope.
AI management system and optional third-party certification for that management system scope.
Map legal obligations independently. A management system certificate has a defined organizational scope.
Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.
Fill this in with your sponsor and send it to the people who own the work.
ISO 42001 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 Inventory AI and define governance scope · AI governance lead + leadership [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. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
Checklist, instructions and 12 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Inventory AI and define governance scope | AI governance lead + leadership | At initiation | Set a start date | AI inventory; Scope statement; AI policy | Open |
| Assess risks and impacts | AI risk lead + affected teams | Before deployment and after material change | Set a start date | AI risk register; Impact assessments; Control applicability | Open |
| Evidence lifecycle controls | Product + model owners | Across the lifecycle | Set a start date | Validation reports; Monitoring plan; Supplier controls | Open |
| Audit and improve the management system | Internal audit + leadership | Before external audit and on recurring cadence | Set a start date | Internal audit; Management review; Corrective actions | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify systems, lifecycle roles, dependencies and intended contexts. Approve AI policy and allocate decision rights.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
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.
Evaluate impacts on individuals, groups and society and select relevant controls. Document risk treatment and review thresholds.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Define acceptance criteria, data governance, evaluation, oversight, monitoring, incident response and supplier obligations. Save actual operation records.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Fictional details. Use the same fields with evidence from your work.
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.
Fictional details. Use the same fields with evidence from your work.
A different person can operate the control or test it using the matrix and its evidence links.
Give the baseline to control owners and the assessor before walkthroughs or sampling.
Conduct internal audit, complete management review and address findings. If needed, engage a qualified certification body.
Fictional details. Use the same fields with evidence from your work.
Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.
Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.
Fictional details. Use the same fields with evidence from your work.
The minutes identify the person who approved each action and the date the decision will be revisited.
Give owners the actions and add the approved record to the relevant audit or governance file.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.