In this lesson
After this lesson you can:
- Explain why two ISO 27001 quotes differ, in terms of days rather than margin.
- Work out which facts about your organisation drive your own audit duration up or down.
- Ask a certification body for its audit-time calculation, and read what comes back.
Read first: Choosing a certification body and the certification process
Audit days are the price.
Certification pricing confuses people because it does not behave like consulting pricing. There is no brand premium to speak of, no negotiation worth having over the headline figure, and two reputable bodies looking at the same company will usually land within a short distance of each other. That is because the thing being priced is a number of auditor days, and the number of auditor days is substantially determined before anyone writes a proposal.
Understanding this changes how you buy. The question is not whether a quote is competitive. It is whether the days are right, because if the days are wrong in either direction something has gone wrong. Too few days, and the audit will be shallow or revised upward once an auditor sees your actual organisation. Too many, and the inputs have been read too pessimistically, which is also fixable by asking.
This page is about the mechanism. If what you want is a budget figure for an ISO 27001 programme in India, including the work before the audit, that is on the cost page instead.
Where the rule lives.
Audit duration for an ISMS is set by ISO/IEC 27006-1:2024, the standard that specifies what a certification body must be in order to certify ISO 27001, read together with ISO/IEC 17021-1. The duration table sits in Annex C of the 2024 edition, with the calculation methods in Annex D.
One historical detail matters here, because it is the reason so much of what you will read online is wrong. In the previous edition, ISO/IEC 27006:2015, the audit-time material was in Annex B. The 2024 edition moved it to Annex C and changed parts of the method. So a blog post citing Annex B, or reproducing a duration table it describes as current, is quoting a superseded standard. The transition to the 2024 edition was mandated by IAF MD 29:2024 and had to be complete by 31 March 2026, which has passed. Every accredited body should now be calculating under the 2024 rules.
This is not a guideline the certification body may take or leave. Its accreditation depends on applying it, and it has to be able to justify its audit-time decisions to its accreditation body. That is useful to you, because it means the calculation exists in a form someone can show you.
It starts with headcount, and headcount is wider than you think.
The basis of the calculation is the number of people doing work under your organisation’s control within the ISMS scope, wherever in the world they are located. Read that twice, because two words in it cost companies money.
Under your control rather than on your payroll. Long-term contractors, freelancers and outsourced staff who work inside the scope are counted. A company with thirty employees and twenty contractors building and running the product is not a thirty-person organisation for this purpose.
Wherever located rather than at the audited site. Remote staff and people at other offices inside the scope count, even if nobody visits them.
The practical failure here is almost always the same, and it is not deliberate. Someone answers the certification body’s headcount question from the HR system, because that is where headcount lives. The quote comes back lower than it should be, and the correction arrives after Stage 1, when the auditor has seen the organisation chart and the contractor list. Supplying the right number at the start costs nothing and removes the single most common cause of a revised quote.
The effective number of persons.
The 2024 edition added a concept that matters a great deal to large, uniform organisations and very little to small technical teams. Where a group of people all perform identical activities, the square root of that group’s headcount may be used to determine the effective number of people for audit-time purposes, rounded up to the next whole number.
The logic is sound. If nine hundred people in a support centre all do the same work under the same procedure, an auditor does not learn nine hundred times as much by sampling nine hundred of them. What is being audited is the process, and a sample establishes whether it operates.
Two limits to hold on to. First, it applies per group of identical activity, not to the organisation as a whole, so the calculation is done group by group and then combined. Applying a square root to your total headcount is simply wrong and an accreditation body will say so. Second, identical means identical. A development team of forty people working across different services, stacks and data is not performing one activity, however similar the job titles look.
What moves the number.
Once the starting duration is established, adjustments apply. These are the factors that explain why two companies of the same size get different durations, and most of them are things you either know or can decide.
| Factor | Effect on duration | Why, and the nuance |
|---|---|---|
| More sites genuinely in scope | Up | Sampling may limit it where sites are near-identical. |
| Many people doing the same job | Down, relatively | The effective-persons rule applies to that group. |
| Regulated activity on top of the standard | Up | More control areas, and more evidence per area. |
| Developing your own software in scope | Up | Secure development controls are examined on top of operations. |
| Infrastructure wholly on a certified cloud platform | Down, sometimes | Fewer physical controls of yours to examine. |
| An integrated management system already audited | Down | Shared clause 4 to 10 machinery is not audited twice. |
| Remote auditing available for part of the work | Neutral to down | Changes travel and sometimes method, not the duty. |
| A previous cycle with findings against you | Up | Problem areas get audited harder and more often. |
The row worth dwelling on is the last one. Audit programmes are supposed to weight attention by importance and by what previous audits found, so an organisation carrying unresolved history gets audited harder. This is not punitive. It is the same logic you are required to apply to your own internal audit programme, where riskier and previously problematic areas come up more often.
How the days are split.
The total is divided across two stages that answer different questions, which is why the split is uneven.
Stage 1 asks whether your ISMS is auditable. The auditor reads your documented information, checks the scope, looks at your risk assessment and Statement of Applicability, and looks for evidence that an internal audit and a management review have genuinely happened. It is shorter, and its real output is a list of what will sink you at Stage 2 if you do not deal with it first.
Stage 2 asks whether the system operates. The auditor samples evidence, walks processes, and interviews the people who run them. It carries most of the duration because testing operation takes longer than reading design. What the auditor actually asks covers that conversation in detail.
A proposal that gives you one combined figure for both stages is not giving you enough to work with. Ask for them separately.
The rest of the cycle.
Initial certification is one of four engagements, and this is where cost surprises live. The certificate runs for three years, with surveillance audits in the first and second years and a recertification audit before it expires. Surveillance audits are shorter than the initial audit and their durations are derived from the same annex rather than set commercially.
So ask for all four priced together, before you appoint anyone. A low Stage 2 with the cost recovered across surveillance is a recognised shape and it is perfectly legal, and it is also invisible unless you ask for the whole cycle. How long a certificate lasts sets out what each visit in the cycle covers.
The question that gets your number.
You cannot calculate this yourself, and you do not need to. What you need is the certification body’s calculation in a form you can read and compare.
Step 1
Give them a real headcount, not an employee count
The basis is everyone doing work under your organisation’s control inside the ISMS scope, wherever they are located. Contractors and freelancers who sit inside the scope count. Understating this is the most common reason a quote is revised upward after Stage 1, which is the worst moment to discover it.
ISO/IEC 27006-1:2024, audit-time basis
Step 2
Describe the scope in the words you want on the certificate
Duration follows the scope, so a loose description produces a loose number. Name the entity, the services, the sites and whether you develop your own software. If you are still deciding the boundary, say so, because scope is the single biggest lever you control.
ISO/IEC 17021-1, scope of certification
Step 3
Ask for the calculation, in writing, by annex
The sentence that works: please send the audit-time calculation for our organisation, showing the starting duration from Annex C of ISO/IEC 27006-1:2024, every adjustment applied under Annex D, and the resulting days for Stage 1, Stage 2, each surveillance audit and recertification.
ISO/IEC 27006-1:2024, Annexes C and D
Step 4
Compare two bodies on inputs, not on totals
Two accredited bodies applying the same annex to the same organisation should land close together. If they do not, the difference is in the inputs: a different headcount basis, a different reading of your scope, or a different view on sampling. That is a conversation worth having before you appoint anyone.
ISO/IEC 27006-1:2024
An accredited body will send this, because it has to produce it anyway. A body that will not, or that treats the request as unusual, has told you something useful about which edition of which standard it is working from.
Why this page has no table.
You may have noticed that nowhere above does this page tell you how many days a company of your size needs. That is deliberate, and we would rather explain it than let you assume we did not know.
The duration table is in Annex C of ISO/IEC 27006-1:2024, and that standard is sold by ISO rather than published freely. The tables you will find reproduced on consultancy blogs and cost guides are overwhelmingly from Annex B of the superseded 2015 edition, usually without saying so. We could copy those figures. They would get this page more traffic than it will otherwise get, and some of them might even still be right.
We are not going to, because a number on this page becomes a number in somebody’s budget and then a number in an argument with a certification body. If you need the figure for your organisation, the certification body you are talking to has it, is obliged to be able to justify it, and will send it if you ask in the words above. If you need the table itself, buy the standard from ISO.
Want a sanity check on a quote you already have?
Send us the proposal and your real headcount and scope. We will tell you whether the days look consistent with the standard’s method, what the proposal has left out, and which questions to put back to the certification body.
Key takeaways.
- Audit duration is calculated under Annexes C and D of ISO/IEC 27006-1:2024, not quoted. A certification body has to be able to justify its calculation to its accreditation body.
- The 2015 edition held this material in Annex B. Any source citing Annex B, or a duration table it calls current, is quoting a superseded standard.
- The basis is everyone doing work under your organisation’s control inside the scope, wherever located, including contractors. Answering from the HR system is the usual cause of a revised quote.
- The effective number of persons rule lets the square root of a group performing identical activities be used, rounded up. It applies group by group, never to total headcount.
- Scope is the lever you actually control, because duration follows scope. Narrowing it for the right reasons lowers audit time and maintenance.
- Stage 1 reads design and Stage 2 tests operation, so the split is uneven and should be quoted separately.
- Price all four engagements in the three-year cycle together. A cheap initial audit with cost recovered across surveillance is invisible otherwise.
- This page publishes no day figures on purpose. The table is paywalled, the circulating versions are from 2015, and your certification body can give you yours.
Quick check.
What is the starting point for an ISO 27001 audit-duration calculation?
- Your annual revenue
- The number of Annex A controls in your SoA
- The number of people doing work under your organisation’s control in scope
- The number of sites
Check the answer
C. Duration starts from headcount inside the ISMS scope, wherever those people are located, including contractors. Sites and control counts are adjustments applied afterwards rather than the basis. ISO/IEC 27006-1:2024
A 900-person operations centre where everyone performs the same role sits inside your scope. How does the 2024 edition treat it?
- All 900 count in full
- The square root of that group’s headcount may be used, rounded up
- Groups over 500 are excluded
- It is capped at 100
Check the answer
B. The effective number of persons concept lets the square root of a group performing identical activities be used, rounded up to the next whole number. It is applied per group and cannot be applied to the organisation’s total headcount. ISO/IEC 27006-1:2024
Spot the mistake. A company gives its certification body an employee count of 30, omitting 20 long-term contractors who build and run the product, and accepts the resulting quote.
Check the answer
The headcount basis was wrong, so the quote was wrong.. People doing work under the organisation’s control inside the scope count regardless of contract type. The duration will be recalculated once the auditor sees the real picture, usually at or after Stage 1, which is the most expensive moment to find out. ISO/IEC 27006-1:2024
Sources.
- ISO/IEC 27006-1:2024, requirements for bodies auditing and certifying an ISMSISO catalogue entry 82908, published March 2024, replacing ISO/IEC 27006:2015 and Amd 1:2020Used here: That audit duration is governed by the standard, with the duration table in Annex C and the calculation methods in Annex D, and the effective number of persons concept added in this edition
- ISO/IEC 17021-1, requirements for bodies providing audit and certification of management systemsISO catalogue entry 61651Used here: The two-stage initial audit, the scope of certification, and the three-year cycle
- IAF MD 29:2024, transition to ISO/IEC 27006-1:2024International Accreditation ForumUsed here: That the 2024 edition is the one in force, with the transition complete by 31 March 2026
- NABCB BCB 125, accreditation criteria for ISMS certification bodiesNational Accreditation Board for Certification Bodies, Quality Council of India, January 2026Used here: That a certification body must justify its audit-time decisions to its accreditation body
Changes since publication
No audit-day figures are published on this page. The duration table sits in Annex C of ISO/IEC 27006-1:2024, which is sold rather than published freely, and the tables circulating online are from Annex B of the superseded 2015 edition. Ask your certification body for the calculation, or buy the standard.
Last checked against the ISO catalogue entries and the IAF’s published mandatory documents on 9 November 2026.