ISO 42001 gap analysis how to do it is a common question, because it is the first real step of any project. A gap analysis shows the distance between your current AI governance and what ISO/IEC 42001:2023 asks for. It tells you what to fix, in what order, and roughly how big the job is.
ISO/IEC 42001:2023 is the international standard for an AI management system (AIMS). You do not need to be perfect to start. A good gap analysis is honest, and it is written down so the whole team can act on it.
What is an ISO 42001 gap analysis and why do it first?#
A gap analysis, also called a gap assessment, is a structured review. You compare your current policies, processes, records and responsibilities against each requirement of the standard. The result is a list of what already works, what is partly there and what is missing.
Doing it first saves effort. Without it, teams often write documents they do not need or miss areas that matter. It also gives leaders a clear picture, which helps when they decide on time, people and budget.
ISO 42001 gap analysis: how to do it step by step#
- Agree the scope. Decide which AI systems, teams and locations are in. A narrow first scope is easier to manage.
- List your AI systems. Note what each system does, who owns it, whether you build it or buy it, and what data it uses.
- Collect what you already have. Gather AI policies, risk registers, data protection records, security controls, supplier agreements and training records.
- Review each area of the standard. Go through leadership, planning, support, operation, performance evaluation and improvement. Also review the controls in the annexes and decide which apply to you.
- Record the evidence. For each requirement, write what you do today and where the proof is. If there is no proof, note that.
- Rate each gap. Use a simple scale such as met, partly met and not met. Add a note on how serious the gap is.
- Build the action plan. Group gaps into tasks with an owner, a priority and a target date.
- Share the results. Present them to leaders and agree resources before you start writing documents.
What should the gap report show?#
A useful report is short enough to read and detailed enough to act on. Include these items.
| Item | What to record |
|---|---|
| Scope | Systems, teams and locations reviewed, and what was left out |
| Requirement | The area of the standard in your own words |
| Current practice | What you actually do today |
| Evidence | Where a document, record or screenshot proves it |
| Gap rating | Met, partly met or not met |
| Action | The task, the owner and the target date |
Write the requirements in your own words and keep the report simple. The aim is a plan, not a perfect document. Do not copy text from the standard into your report, and keep the evidence column honest, because the auditor will ask to see it later.
Every organisation is different, but some gaps show up often. These are general examples of what a report might list, not findings from any client:
- No complete list of AI systems, or no named owner for each one.
- An AI policy that exists on paper but is not known by staff.
- No clear method for assessing AI risks and the effect of AI systems on people.
- Little oversight of suppliers who provide AI models or data.
- Training that covers security but not responsible AI use.
- No internal audit or management review of AI governance yet.
If you already run an information security or quality system, many routines carry over. Document control, internal audit and management review are good examples. Our ISO 27001 consulting page shows how these systems fit together.
What happens after the gap analysis?#
The report is only useful if you act on it. Turn it into a project plan within a few days, while the details are fresh. A simple order works well for most teams.
- Fix the foundations first: scope, roles, the AI system list and the AI policy.
- Run the AI risk assessment and the assessment of how AI systems affect people.
- Write or adapt the procedures and records the plan calls for. A ready-made toolkit can speed this up, but you must adapt it to your real processes.
- Train the people who own AI systems and the people who will audit them.
- Run the system, collect records and hold the first internal audit and management review.
- Repeat a short gap check, close what remains and then book the certification audit.
Review progress against the plan at regular meetings. Gaps that stay open for months usually have no clear owner, so name one person for each task.
Should you do it yourself or ask a consultant?#
You can run the first review yourself if you know the standard well. A fresh pair of eyes often finds blind spots, though. An experienced ISO 42001 consultant can run the assessment, rate the gaps and help you build a realistic plan. We work on-site across India and remotely abroad. How much help you need depends on the size and readiness of your organisation. A gap analysis helps you prepare, but it does not guarantee certification, because the decision belongs to the certification body.
Frequently asked questions#
How long does an ISO 42001 gap analysis take?#
It depends on the number of AI systems, teams and locations in scope, and on how well your records are organised. A small scope is quick. A large organisation needs more interviews and more evidence.
Do we need a gap analysis if we use ready-made templates?#
Yes. Templates give you documents, but they do not show where your real practice differs from the standard. A gap analysis tells you which templates to use first and what else to change.
When should we repeat the gap analysis?#
Repeat a shorter check before the certification audit, after you have written documents and run the system. It helps you close remaining gaps while there is still time.
Ready to start? Read our complete guide to ISO 42001, then contact AdWiser to talk about your gap assessment.

Leave a Comment