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.

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.

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.
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:
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.
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:
| Role | What it means |
|---|---|
| AI provider | Offers products or services that use AI, including AI platforms |
| AI producer | Designs, develops, tests or deploys AI systems, such as a team building models or AI features |
| AI customer or user | Uses AI systems, including tools from other vendors |
| AI partner | Supports 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.
Take a 10-person company. Its starting audit days vary by AI role:
| AI role | Starting audit days |
|---|---|
| AI user only | 3.5 |
| AI developer or provider | 3.5 |
| AI producer | 5 |
| Multiple roles | 6.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.
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.
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:
Start from why you're certifying, then test the scope against it:
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.

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.
Beyond credentials, frameworks and pricing, ask who will do the work, how offshore teams operate, when auditors are available, whether controls fit your business and what happens when plans change.
Paul Wenham explains the proposed 2027 SOC 2 criteria, AI points of focus, governance and change management updates, transition effort and Throughline's approach to fees.
SOC 2 for startups, from planning to reporting: typical USD audit fees, timelines, internal team hours, AI-assisted readiness and keeping a first report on track.
SOC 2 for mid-sized companies: typical USD costs, timelines and team hours, plus existing controls, multiple products, regulatory drivers and auditor changes.
SOC 2 for enterprises: typical USD costs, timelines and team hours, plus ISO 27001 reuse, multi-entity scope, vendors, procurement and customer deadlines.
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.
Three worked SOC 2 examples: AI-written code, agent-led access reviews and agents changing customer data. Follow each risk through its control, audit test and evidence.
Build an AI management system around your real use cases: an agent register, risk and impact assessments, shared responsibilities, governance policy and Statement of Applicability.
ISO 42001 isn't yet an enterprise requirement. What it covers, how it compares with SOC 2 and AIUC-1, and when it's worth it for an AI company.
How to cover production AI agents in SOC 2: governance, access, change management and monitoring, with indicative criteria mappings, customer responsibilities and practical audit expectations.
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.
Experienced CTOs don't choose a SOC 2 audit firm on price or speed. They look for tech stack expertise, a tailored approach, flexible scheduling, responsiveness and year-round partnership, because those factors decide how much time the audit really costs.
What Security, Availability, Confidentiality, Processing Integrity and Privacy each cover, how often they're included, and how to decide which belong in your SOC 2 report.
Which SOC 2 report should come first? Six client cases, practical decision tables and an illustrative 18-month cost comparison explain when to start with Type 1 and when to go straight to Type 2.
How long a SOC 2 Type 2 observation period should be, how to work backwards from a customer deadline, when auditors test, why reports run late and how much buffer to build in.
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.
Five signals of real quality in assurance and security, with practical guidance on building a compliance program that supports customer TPRM, repeatable enterprise reviews and revenue growth.
The person leading your SOC 2 audit is the most underrated factor in choosing an audit firm. Companies compare price, timelines and platform integrations, then barely ask who will actually do the work.
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.
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.
CPA firm registration, signing licenses and peer review are the starting point, not proof of quality. A practical guide to checking credentials and asking the questions that matter before choosing your SOC 2 auditor.
Neither is better for everyone. The right choice depends on your customers, how you run security and where you are headed. For AI-native and AI-centric companies, SOC 2's flexible criteria usually make it the stronger starting point.
There's a basic psychology behind why most people don't like audits. Fix this, and people are surprisingly happy to do them again.
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.
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.
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.
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.