Throughline.
    Insights
    Compliance Planning

    ISO 42001 Audit Days and Cost: How AI Roles and Scope Set the Price

    How certification bodies set ISO 42001 audit days under ISO/IEC 42006, how AI roles and in-scope headcount drive the price, and when scoping to engineering and product makes sense.

    Paul Wenham
    2026-11-11

    ISO 42001 certification audits can be longer, and pricier, than companies expect. Cost comes down to audit days, and audit days come down to how many people are in scope and how many AI roles the company holds.

    A 10-person company can start anywhere from 3.5 to 6.5 audit days, depending on its AI roles. A growing number of companies are narrowing their scope to engineering and product to bring the days down. This guide explains how audit days are set, what AI roles are, and when a narrower scope makes sense.

    If you're still deciding whether to certify at all, start with ISO 42001 for AI companies.

    How are ISO 42001 audit days calculated?

    Certification bodies follow ISO/IEC 42006, the standard that sets requirements for bodies certifying AI management systems. To be accredited, they have to calculate audit time its way, rather than estimating from company size alone.

    The starting figure comes from two inputs:

    • In-scope headcount. The people whose work affects the AI management system, not the whole company. Someone who spends part of their time on AI-related work counts as a fraction of a full-time equivalent.
    • AI roles. Whether the organisation acts as an AI producer, an AI developer or provider, an AI user, or multiple of these at once. Each category has its own audit-time table, and multiple roles carry the most days.

    The certification body then adjusts that figure for complexity, such as how many AI systems are in scope, how critical or high-risk they are, how much is built in-house, and how many sites are involved. The calculated time is treated as a minimum: going below it needs a documented reason.

    The days cover the initial certification audit, which runs in two stages: a review of the management system's design, then a test of whether it operates. Surveillance audits in the following years are shorter.

    What are AI roles in ISO 42001?

    AI roles describe how an organisation relates to AI systems. ISO 42001 requires every organisation to determine its roles in clause 4.1, drawing on the definitions in ISO/IEC 22989. They have nothing to do with user accounts or access permissions. The main ones are:

    RoleWhat it means
    AI providerOffers products or services that use AI, including AI platforms
    AI producerDesigns, develops, tests or deploys AI systems, such as a team building models or AI features
    AI customer or userUses AI systems, including tools from other vendors
    AI partnerSupports others' AI, such as system integrators or data suppliers

    Most tech companies hold multiple roles at once. A SaaS company that builds AI features into its product is a provider and a producer. The same company is also a customer when its staff use AI tools for support, sales or engineering. Holding multiple roles puts it in the highest audit-time category, because the auditor has to cover the obligations of each role.

    For how these roles shape the management system itself, see ISO 42001 for AI-native startups: where to start.

    How do AI roles change audit days?

    Take a 10-person company. Its starting audit days vary by AI role:

    AI roleStarting audit days
    AI user only3.5
    AI developer or provider3.5
    AI producer5
    Multiple roles6.5

    Holding multiple roles nearly doubles the starting point compared with a single provider or user role, and that's where most tech companies land. Those are starting points, before any adjustment for complexity.

    Every day matters, because audit days typically cost anywhere from $1,500 to $3,000 each. The three extra days for multiple roles cost almost as much as an entire single-role audit. For comparable SOC 2 budgets, see SOC 2 cost and timeline benchmarks by company size.

    Can you limit ISO 42001 scope to engineering and product?

    Yes. You set the scope of your AI management system, as long as its boundaries are clear and justified. Scoping it to the engineering and product teams that build and run your AI features means fewer people count toward the in-scope headcount.

    How much that saves depends on size. For a 10-person company, it won't change much: the smallest headcount band already covers one to ten people, so narrowing the team keeps you in the same band. At that size, your AI roles matter more than your headcount.

    The saving grows with the company. A 20-person company with multiple roles might start at around 9.5 days; scoping it to its 10 or so engineering and product staff could bring that to about 6.5. Either way, the certificate then covers the AI in your product, rather than every way the company uses AI.

    Is a narrower ISO 42001 scope a smart move?

    Often, yes. Most companies seek ISO 42001 to show customers that the right systems sit around the AI in their product. A scope covering engineering and product does exactly that, for less time and money.

    It's worth checking a few things before you narrow it:

    • Where internal AI touches customers. For an AI-native company, AI used in support, operations or compliance may handle customer data or affect the service. Leaving that out can exclude risks your customers care about.
    • What the certificate says. Enterprise reviewers read the scope statement. A narrow scope is fine when it clearly matches what they rely on, but it can raise questions if it looks like it avoids something. See AI vendor risk questions for third-party due diligence for what reviewers ask.
    • The boundaries. In-scope teams still depend on out-of-scope ones, such as people, IT and vendor management. Those dependencies need managing, and the auditor will ask how.
    • Where you're heading. If customers will soon expect coverage of internal AI use, extending the scope later means extra audit work. Starting broader can cost less overall.

    How should you decide your ISO 42001 scope?

    Start from why you're certifying, then test the scope against it:

    • Which customers are asking, and what do they need assurance over?
    • Which AI systems do those customers actually rely on?
    • Does any internal AI use touch customer data or affect the service?
    • What AI roles does the company hold, within the scope and outside it?
    • Would the scope statement read well to an enterprise reviewer?
    • Will you need to extend the scope within the next year or two?

    An AI use case register makes this much easier, because it shows every AI use, its owner and what it touches. See ISO 42001 for AI-native startups for where to start, or ISO 42001 with Throughline for certification support.

    Related reading

    Paul Wenham
    Written by
    Paul Wenham

    Former PwC manager, founder of AssuranceLab and former Sensiba partner and Chief Innovation Officer. Now founder of Throughline, focused on compliance and assurance for AI-native companies.

    More from Paul
    Compliance Planning · Audit & Assurance
    SOC 2 Cost and Timeline Benchmarks by Company Size

    Typical SOC 2 costs and timelines for startups, mid-sized companies and enterprises, by report type. Compare planning, readiness, observation, fieldwork and reporting, plus related costs in USD.

    Audit & Assurance
    How Australian Companies Should Choose a SOC 2 Audit Firm

    Australian companies need a SOC 2 report issued under the AICPA standards by a US-licensed CPA firm, delivered by a strong local team in Australian time zones. Here's how the provider options compare, and what to check.

    Compliance Planning · Audit & Assurance
    How Much Does SOC 2 Cost? The True All-In Cost, Category by Category

    A category-by-category SOC 2 budget in USD, covering audit fees, readiness, platforms, penetration testing, consultants, internal assessments and operational costs. Learn what is required, what is optional, and what a quote can leave out.

    Audit & Assurance
    SOC 2 Isn't Pass/Fail: What It's Really For

    SOC 2 is a risk report, not a certificate. Understand how enterprise customers use it, why having a report is only base camp, and how to turn your audit into a trust asset for growing revenue.

    Compliance Planning
    SOC 2 Readiness Assessments: Your Questions Answered

    What readiness should cover, when to involve your auditor, which gaps matter most, and how readiness, Type 1 and Type 2 can work as one continuous engagement. A practical guide to preparing for a report your customers can rely on.

    SOC 2
    What makes a SOC 2 report quality?

    Enterprise buyers use SOC 2 as an initial qualifier, then look deeper. A quality report is what carries you through that assessment and turns your compliance investment into real trust.

    SOC 2
    What makes a SOC 2 audit high quality

    Audit quality isn't service quality, and it isn't only professional standards. The real test is whether a reader of your report thinks: this tells me what I need to know.

    Audit & Assurance
    Getting Through Enterprise Security Reviews

    Enterprise security teams review you in the background and rarely give feedback. What they look at beyond SOC 2, what counts as a genuine pen test, and how a quality report does the heavy lifting.

    Agentic Compliance
    Agentic Compliance: AI-Native, Human-Led

    Compliance from first principles, the 95% problem, the compliance metadata AI needs, rethinking screenshots, spreadsheets and policies, and why audits should meet clients where they are.

    Last updated