Most first-time ISO 27001 budgets fail because they price the certification audit and forget the internal effort, the control remediation and the three-year cycle of audits that follows. The certificate is issued by an accredited certification body, but the bulk of the cost sits inside your organisation: staff time to build and run the information security management system (ISMS), fixes to controls that do not yet work, and evidence collection that has to continue every year. This guide explains what drives the cost, how certification bodies size the audit, how to build a three-year budget from your own quotes, and what a realistic timeline looks like from kick-off to certificate. It is written for CISOs, compliance leads, finance partners and founders preparing a first certification. It deliberately gives no price ranges: published "average cost" figures are mostly marketing estimates, and your quotes will depend on headcount, scope and complexity. For the standard itself and the certification steps, see the ISO 27001 Certification Guide.
Key takeaways
- Audit days drive the external fee. Certification bodies calculate audit time under ISO/IEC 27006-1:2024 from the number of people doing work under the organisation's control, adjusted for complexity and risk; the fee is broadly audit days multiplied by the day rate, plus travel and administrative charges.
- Budget for three years, not one audit. Certificates are valid for three years with surveillance audits each year; Schellman, an accredited certification body, describes each surveillance audit as about one third of the initial audit time and recertification as about two thirds.
- Internal effort is usually the largest line. Scoping, risk assessment, the Statement of Applicability, policies, internal audit and management review all consume named people's time before the auditor arrives.
- Preparation, not the audit, sets the timeline. Schellman puts full preparation at anywhere from three months to a year; its own process schedules stage 2 between one and nine months after stage 1 and issues the certification decision within four weeks of stage 2.
- Scope is the biggest lever you control. Headcount in scope, sites, outsourced services and technology diversity change both audit days and internal workload, so settle scope early and in writing.
What you are paying for
An ISO 27001 budget has two halves: getting ready and getting audited. Only the second half appears on a certification body's quotation.
| Cost component | What it covers | What drives it | Recurring? |
|---|---|---|---|
| Internal ISMS effort | ISMS lead, control owners, risk workshops, policy writing, evidence collection, internal audit and management review (clauses 9.2 and 9.3) | Scope size, existing maturity, number of control owners | Yes, every year |
| Control remediation | Fixing gaps found in the risk assessment: MFA, logging, backups, supplier reviews, access reviews, secure development | Gap assessment findings and risk treatment decisions | Mostly year one, then continuous improvement |
| External support (optional) | Gap assessment, implementation consultancy, outsourced internal audit, training | In-house expertise; independence needed for internal audit | Internal audit support often recurs |
| Tooling (optional) | GRC or compliance automation platforms, policy management, evidence collection integrations | Number of users and integrations; build vs buy | Yes, subscription |
| Certification audit fees | Stage 1 and stage 2 audit days, certification decision, certificate issue | Audit days from ISO/IEC 27006-1, day rate, travel, sites | Initial cycle, then recertification |
| Surveillance and recertification | Annual surveillance audits and a recertification audit before expiry | A fraction of initial audit time, plus scope changes | Yes |
| Staff time during audits | Interviews, evidence walkthroughs, follow-up on findings | Audit days and the number of people interviewed | Yes |
The certification body cannot help with the first half: under ISO/IEC 17021-1 impartiality rules an accredited certification body may not consult on the management system it certifies. If you use a consultant, it must be a separate organisation. See the ISO 27001 Certification Body Selection guide for how to compare certification body proposals.
How certification bodies size the audit
Accredited certification bodies follow ISO/IEC 27006-1:2024, published by ISO in March 2024 as the first edition replacing ISO/IEC 27006:2015, which builds on ISO/IEC 17021-1. Its normative Annex C sets audit time. The standard itself is a paid document, so ask each certification body to show its audit day calculation in the proposal rather than accept a single total.
- People in scope: the starting point is the number of persons doing work under the organisation's control. usd, a German certification body, notes that the 2024 revision counts people who work for the certified company whether or not they are employees, so freelancers inside the ISMS scope must be included.
- Multi-site organisations: usd also reports that audit time is now based on the total number of people, not the number of sites, with audit days then distributed across locations by each site's relevance, activities and risk.
- Complexity adjustments: Schellman lists factors that can raise or lower audit time: ISMS complexity, type of business, past ISMS performance, diversity of technology (IT platforms, segregated networks), outsourcing and third parties, system development, and the number of sites and disaster recovery sites.
- Scope extensions: the 2024 revision specifies how audit time is calculated when scope is extended, taking into account current activities, the controls relevant to certification and the information risks added.
- Version: UKAS set 31 October 2025 as the date by which certification bodies were to complete client transitions to ISO/IEC 27001:2022, so proposals now quote against the 2022 edition.
- Remote auditing: usd reports that the earlier 30 percent cap on remote audit activity, which needed separate approval when exceeded, was revised in 2024. Remote audit can reduce travel cost, but not audit days.
| Factor (per Schellman) | Tends to increase audit time | Tends to decrease audit time |
|---|---|---|
| Maturity | First certification, weak evidence | High preparedness, mature ISMS |
| Prior relationship | New certification body | Existing certification to another standard with the same body |
| Activities | Many applicable standards and regulations, system development | Single general activity, such as a service-only business |
| Logistics | Multiple buildings or locations, temporary sites, language barriers | Many people performing the same tasks |
| Risk | High-risk products or processes | Low-risk products or processes |
Building a three-year budget
The certificate runs for three years, so build the budget across the whole cycle. Use your own quotations and internal day rates; the structure below is the model, not the numbers.
| Year | External audit days | Internal effort | Other lines |
|---|---|---|---|
| Year 0 (preparation) | None, unless you buy a pre-assessment | Highest: build the ISMS, assess risks, remediate, operate controls, internal audit, management review | Gap assessment, consultancy, tooling set-up, training |
| Year 1 (initial certification) | Stage 1 plus stage 2 (initial audit time, A) | Audit support, nonconformity correction, continued operation | Travel, application and certificate fees if charged |
| Year 2 | Surveillance audit (about A divided by 3, per Schellman) | Run the ISMS: internal audit, management review, evidence | Tooling subscription, outsourced internal audit |
| Year 3 | Surveillance audit (about A divided by 3) | As year 2, plus preparation for recertification | As year 2 |
| Year 4 (start of next cycle) | Recertification audit (about two thirds of A) | As year 2 | As year 2 |
Worked example of audit days: Schellman's own illustration is a 12-day initial audit, giving surveillance audits of about 4 days and a recertification of about 8 days. Over a first certificate that is 12 plus 4 plus 4, so about 20 external audit days, and the recertification starts the next cycle. Multiply by each bidder's day rate and add travel to compare proposals on a like-for-like three-year basis.
The external fee formula: external cost = (audit days for stage 1, stage 2, two surveillance audits) multiplied by the day rate, plus travel and expenses, plus any application, certificate or annual management fees in the proposal. Ask each certification body to state every element separately; the ISO 27001 Certification Body Selection guide lists the contract terms to fix.
The internal effort estimate: list each workstream (scoping, risk assessment, Statement of Applicability, policies, each Annex A theme, internal audit, management review, audit support), name the owner, estimate days, and multiply by a loaded internal day cost agreed with finance. Add a contingency line for remediation, because the scale of control gaps is not known until the risk assessment is done.
A realistic timeline
The table separates what the standard and certification bodies fix from what you control. Figures marked with a source are that organisation's published position; certification bodies set their own rules within the accreditation requirements, so confirm them in your contract.
| Phase | What happens | Duration and source |
|---|---|---|
| Preparation | Scope, risk assessment and treatment, Statement of Applicability, policies, operating controls, internal audit, management review | Schellman: "anywhere from 3 months to a year" to fully prepare |
| Stage 1 audit | Documentation and readiness review; areas of concern to resolve before stage 2 | Set by audit days for your scope |
| Gap before stage 2 | Close stage 1 concerns, keep operating controls, gather records | Schellman process: stage 2 no less than one month and no more than nine months after stage 1 |
| Stage 2 audit | Implementation and effectiveness of the ISMS and controls | Set by audit days for your scope |
| Nonconformity closure | Correct minor findings and remediate major ones before certification | Schellman: weeks to months; if major findings cannot be verified within six months of stage 2, another stage 2 audit is needed |
| Certification decision | Independent review and decision by the certification body | Schellman process: no more than four weeks after stage 2 |
| First surveillance | Sample of the ISMS and controls | Schellman process: begins no more than 12 months after the certification decision; at least one surveillance audit per year |
| Recertification | Full audit of the ISMS before the certificate expires | Certificate valid three years; Schellman recommends starting within 32 months of initial certification |
The ISMS has to show records of operation at stage 2, including a completed internal audit and management review, so the preparation phase cannot be compressed by adding consultants alone: some activities need elapsed time to generate evidence. Our ISO 27001 Certification Guide gives indicative durations for a focused SaaS company and a multi-site enterprise; the ISO 27001 Certification Readiness Checklist lists what must be in place before stage 1.
Decision guidance: what makes it faster, slower, cheaper or dearer
- Scope: a tightly defined scope (one product, its people and its supporting services) reduces both audit days and internal workload. Carving out parts of a small company can add boundary controls that cost more than including them, so test scope options against both.
- In-house or consultant: an experienced in-house ISMS lead keeps knowledge in the organisation and lowers recurring cost; a consultant shortens the learning curve in year 0 but the organisation still has to operate the ISMS. Many small organisations buy a gap assessment and outsourced internal audit and build the rest themselves.
- Tooling: compliance automation reduces evidence collection effort in cloud-native estates but adds a subscription and does not replace risk decisions or control design. See the Compliance Automation Guide.
- Existing certifications: Schellman notes that existing certification to another standard with the same body can reduce audit time.
- Customer deadline: if a contract needs the certificate by a date, work backwards: certification decision, nonconformity closure, stage 2, gap after stage 1, stage 1, then at least one internal audit and management review cycle. If the dates do not fit, agree an interim position with the customer (a readiness letter or stage 1 report) rather than compress operation.
- Small and large organisations: small organisations usually have fewer audit days but relatively higher internal effort per person, because a few people own every control. Large organisations face more sites, more outsourced services and longer remediation, and often phase scope across certification cycles.
Implementation plan for a first certification
- Agree scope and budget owner: draft the scope statement (clause 4.3), name the ISMS lead and executive sponsor, and agree the budget model above with finance.
- Gap assessment: compare current practice to clauses 4 to 10 and Annex A to size remediation. The Gap Assessment vs Readiness Assessment vs Audit guide explains the difference between the three exercises.
- Request certification body proposals early: ask at least two accredited bodies for the audit day calculation, day rate, three-year schedule and fees. Booking early secures audit dates that fit the plan.
- Build and operate: run the risk assessment, approve the Statement of Applicability, remediate, and operate controls long enough to produce records.
- Internal audit and management review: complete both before stage 1, with an internal auditor independent of the work audited. See the ISMS Internal Audit and Management Review guide.
- Stage 1, close concerns, stage 2: track findings with owners and dates; hold contingency in the plan for the gap before stage 2.
- Close nonconformities and receive the decision: keep the correction evidence; it will be revisited at surveillance.
- Plan year 2 on day one: schedule internal audit, management review and the surveillance audit in the calendar; the ISO 27001 Surveillance Audit Checklist covers preparation.
Measuring cost and schedule
- Budget variance by component: actual against plan for internal effort, remediation, external support, tooling and audit fees.
- Internal days per workstream: recorded effort against estimate, to improve the next year's budget.
- Schedule adherence: planned against actual dates for internal audit, management review, stage 1, stage 2 and certificate.
- Nonconformities: number raised at each audit and days to close; repeat findings at surveillance signal rework cost.
- Audit days per cycle: initial, surveillance and recertification days against the proposal, flagging scope changes that added time.
- Commercial return: customer security questionnaires answered by the certificate alone, and deals that required it.
Common failure patterns
- Pricing only stage 2: comparing certification bodies on the initial audit price while surveillance days, travel and annual fees decide the three-year total.
- No owner for internal effort: the budget covers external fees, but control owners are not given time, so evidence is assembled at the last minute and stage 1 finds gaps.
- Underestimating remediation: setting the budget before the risk assessment, then discovering that access reviews, logging or supplier assessments do not exist.
- Undercounting people in scope: leaving contractors and freelancers out of the headcount given to the certification body, which then revises audit days upward.
- Compressing operation: booking stage 2 before controls have run long enough to produce records, leading to major nonconformities and a repeat audit.
- Treating the certificate as the finish line: no year 2 budget, so internal audit and management review slip and the first surveillance raises findings.
Framework mapping
| Activity | ISO/IEC 27001:2022 clause | NIST CSF 2.0 | Other reference |
|---|---|---|---|
| Defining scope, which drives audit days | 4.3 Determining the scope of the ISMS | GV.OC-03 | ISO/IEC 27006-1:2024 Annex C audit time |
| Funding and staffing the ISMS | 5.1 Leadership and commitment, 7.1 Resources | GV.RR-03 | |
| Internal audit before certification | 9.2 Internal audit | ID.IM-01 | |
| Management review | 9.3 Management review | ID.IM-01 | |
| Correcting nonconformities | 10.2 Nonconformity and corrective action | ID.IM-01 | Certification body nonconformity deadlines |
| Certification cycle and surveillance | ISO/IEC 17021-1 and ISO/IEC 27006-1:2024 |
Practitioner checklist
- Scope statement agreed, with headcount in scope including contractors and freelancers.
- Three-year budget covering internal effort, remediation, external support, tooling, audit fees, travel and surveillance.
- Internal effort estimated per workstream with named owners and protected time.
- At least two accredited certification body proposals showing audit day calculations and a three-year schedule.
- Remediation contingency held until the risk assessment is complete.
- Internal audit and management review completed before stage 1.
- Timeline worked back from any customer deadline, with the gap between stage 1 and stage 2 confirmed in the contract.
- Year 2 internal audit, management review and surveillance dates booked when the certificate is issued.
Standards and references
- ISO: ISO/IEC 27001 Information security management systems
- ISO: ISO/IEC 27006-1:2024 Requirements for bodies providing audit and certification of ISMS
- UKAS: Transition arrangements for ISO/IEC 27001:2022
- Schellman: ISO Certification Services Processes
- Schellman: 6 Factors That Can Affect Your ISO 27001 Timeline
- usd: New Requirements of ISO/IEC 27006-1:2024
Related NHI Mgmt Group resources: ISO 27001 Certification Guide, ISO 27001 Certification Readiness Checklist, ISO 27001 Certification Body Selection, ISO 27001 Statement of Applicability Template.