Skip to content
Implementation
15 min read

Phased ISO 27001 Implementation: A Practical Plan

support@ismscalculator.com|

Compliance lead mapping project milestones

A phased ISO 27001 implementation splits the project into stages that each end with a clear deliverable: scope and budget, gap assessment, risk work and documentation, operation with evidence, internal audit, and the certification audits. Each phase gets an owner, a milestone and a budget line, so leadership can see progress and you can catch slippage early. Most teams then run the phases in short sprints, so the work stays measurable.

This guide walks through each phase, what belongs in it, how to turn it into sprints, and how to estimate effort and cost before you commit.

Ismscalculator
ismscalculator.com
Plan ISO 27001 With Realistic Estimates
Estimate implementation cost and effort using company size, industry, and security maturity, then compare your plan with the model reference.
Estimate your ISO 27001 project

TL;DR

  • Split the project into six phases: scope and budget, gap assessment, risk treatment and documentation, operation, internal audit, certification audits.
  • Run the gap assessment early and rank gaps by effort, impact and cost. That ranking drives your sprint backlog.
  • Clauses 4 to 10 are mandatory. Teams that skip them and accept every control without a risk assessment put the whole project at risk.
  • Two-week sprints work: one published case reports delivering ISO 27001 in nine months this way.
  • Estimate before you commit. Company size, scope, number of sites and security maturity move the timeline and the budget more than anything else.

Table of Contents

Why phase the project at all

ISO 27001 is a management system standard, not a checklist of tools. You are building a system that has to run, produce records and be reviewed. Trying to do everything at once usually means documents get written before anyone has decided what the risks are, and controls get bought before anyone knows which ones the risk assessment requires.

Phasing fixes that by giving the work an order. ISACA recommends a phased approach for the ISO/IEC 27001:2022 transition, with clearly outlined milestones for tracking progress. That guidance was written for organizations moving from the 2013 edition, but the logic holds for a first-time project too: milestones make progress visible, and visible progress keeps management committed.

A phased plan also helps with money. Each phase has a bounded scope, so you can attach effort and cost to it, and you can show the finance team what the next quarter needs instead of presenting one large number.

The six phases at a glance

Phase Main output Typical owner
1. Scope and budget Defined ISMS scope, sponsor, budget, timeline Executive sponsor, ISMS manager
2. Gap assessment Ranked list of gaps against the standard ISMS manager, control owners
3. Risk treatment and documentation Risk register, Statement of Applicability, policies ISMS manager, security and IT leads
4. Operation Controls running, records being produced Control owners across teams
5. Internal audit and management review Audit report, corrective actions, review minutes Independent internal auditor, leadership
6. Certification audits Stage 1 and Stage 2 results, certificate Certification body, ISMS manager

The sections below take them in order.

Phase 1: Scope, ownership and budget

The first phase is about decisions, not documents. You define the ISMS scope, appoint an ISMS manager, identify stakeholders, secure budget approval and draft a project timeline. Those are the same pre-implementation tasks that most introductory guides list first, and for good reason: every later phase depends on them.

Scope deserves the most care. A narrow scope, such as one product, one business unit or one set of offices, is cheaper and faster, but it has to make sense to your customers. If your buyers expect the certificate to cover the platform they use, a scope that leaves it out will not satisfy them. Write down the boundaries: locations, systems, teams, data, and the suppliers you rely on.

At the end of this phase you should have:

  • a written scope statement approved by leadership;
  • a named executive sponsor and ISMS manager;
  • a budget range covering people time, tooling, consulting if you want it, and audit fees;
  • a draft calendar working back from the date you need the certificate.

A useful habit: choose your certification body early and ask when they can book your Stage 2 audit. Audit slots, not your own readiness, are sometimes what sets the date. Our project milestones guide explains why booking Stage 2 first can anchor the whole plan.

Phase 2: Gap assessment

A gap assessment compares what you do today with what the standard requires. ISACA’s guidance is to involve key personnel, categorize gaps by effort, impact and cost, then prioritize them by severity and risk, taking dependencies into account. Its 90-day transition plan places the gap assessment in weeks 3 and 4, which tells you it should be quick, not a project of its own.

In practice, walk through the management system clauses first, then the Annex A controls. For each item record:

  1. what exists today (policy, process, tool, nothing);
  2. who owns it;
  3. what evidence you could show an auditor right now;
  4. the effort to close the gap, and whether it depends on another item.

Keep the output as a simple register. Every row becomes a backlog item. Dependencies matter more than people expect: you cannot finalize your Statement of Applicability before the risk assessment, and you cannot test access reviews before you have decided who reviews what.

If you want a structured method, our step-by-step gap analysis guide covers the walkthrough in detail. For a faster read on where you stand, the free 2-minute readiness check gives you an indication before you schedule workshops.

Phase 3: Risk treatment and documentation

This is where the ISMS takes shape. You identify assets, assess risks, decide how to treat each one, and select controls. The outputs are a scored risk register with treatment decisions, a Statement of Applicability linked to that risk assessment, and the policies and procedures that describe how you operate.

The ISC2 warns about a common startup mistake: clauses 4 through 10 are mandatory, yet startups tend to accept all controls without a risk assessment instead of working through them, and failing those clauses can end the implementation. The fix is to treat the clause requirements as a work stream in their own right: context of the organization, leadership commitment, planning, support, operation, performance evaluation and improvement.

A few practical points for this phase:

  • Keep the risk method simple enough that people will actually use it. A five-by-five matrix applied consistently beats an elaborate model nobody updates.
  • Write the Statement of Applicability after the risk assessment, and justify every exclusion.
  • Fewer, shorter documents that people follow are better than a large library nobody reads.
  • If your scope includes AI workloads, an AI security governance framework can help you structure the governance questions that feed your risk assessment.

Finance firms should bring regulatory obligations into the risk assessment at this point, so the ISMS reflects the rules the business already works under. Our guide to audit preparation for finance companies goes into that. SaaS teams will find a parallel walkthrough in ISO 27001 for SaaS and tech companies.

Phase 4: Operate the system and collect evidence

A certification body does not certify documents. It certifies a system that has been running. That is why this phase exists: controls are switched on, people are trained, access reviews happen, incidents are logged, suppliers are assessed, and every one of those activities leaves a record.

Plan for a real operating period. Practitioners generally expect the ISMS to show a few months of operating evidence before the Stage 2 audit, and your certification body can tell you what it expects for your scope. Build this into the calendar, because it is the phase most often squeezed.

Typical evidence an auditor will want to see by the end of this phase:

  • a signed information security policy with a recent review date;
  • management review minutes showing senior leadership involvement;
  • the scored risk register and Statement of Applicability;
  • access review records and multi-factor authentication settings;
  • supplier records with security obligations;
  • training completion records and incident logs;
  • an asset register, backup logs and patching reports.

Assign each item to an owner and set a recurring reminder. The cheapest way to fail an audit is to do the work and forget to record it.

Phase 5: Internal audit and management review

Before Stage 2, complete an internal audit. The person performing it should be independent of the area being audited, so a small team often brings in someone from another department or an outside party. The audit tests whether the ISMS meets both your own rules and the standard, and produces findings you can fix before the certification body sees them.

Follow it with a management review. Leadership looks at audit results, risk status, incidents, objectives and resources, and records decisions. Those minutes are one of the first things an auditor asks for.

Treat internal audit findings as a short sprint backlog: fix, record, verify. Closing them with documented corrective actions shows the improvement cycle works. Our audit stages overview explains what each external stage examines, so your internal audit can mirror it.

Phase 6: Stage 1, Stage 2 and the certificate

The external audit is itself phased. Stage 1 reviews your documentation and readiness. Stage 2 examines whether the system operates effectively, with the main focus on clauses 8 to 10. After certification, you face annual surveillance audits, and a recertification audit at the end of the three-year cycle. Your certification body sets the exact audit days and schedule for your scope, so ask for them in writing early on.

ISO 27001 audit and recertification timeline

If you are moving from an older certificate, note that ISO/IEC 27001:2022 was published on 25 October 2022 and certificates based on the 2013 edition were set to expire or be withdrawn when the three-year transition period ended on 31 October 2025. New projects should work to the 2022 edition.

For a longer walkthrough of every step from kickoff to certificate, see our 80-step certification checklist.

Turning phases into sprints

Phases give the project its shape. Sprints give it a rhythm. Instead of waiting for a phase to finish, you break each into two-week increments with a goal you can demo.

Flo Health published an account of this approach: using two-week Scrum sprints, with daily stand-ups, sprint planning and sprint demos, they completed ISO 27001 implementation in nine months. The value they describe is transparency and stakeholder engagement, plus the ability to make changes quickly as the work unfolded. Your own timeline will depend on your scope and starting point, so treat nine months as an example, not a promise.

A workable sprint setup looks like this:

  1. Backlog. Load the gap assessment register. Each gap or clause requirement is an item with an owner and an estimate.
  2. Sprint goal. Pick a deliverable, for example “risk register scored for all in-scope assets” or “access reviews completed for production systems”.
  3. Short stand-ups. Fifteen minutes, focused on blockers, especially those waiting on leadership decisions.
  4. Demo. Show finished work to the sponsor: the policy approved, the control running, the record produced.
  5. Retrospective. Adjust the next sprint based on what slowed you down.

Some sample sprint themes across the phases:

Sprint theme Example deliverable
Scope and governance Approved scope statement, ISMS roles defined
Risk foundations Asset inventory, risk method agreed
Risk treatment Risk register scored, treatment plan drafted
Policies and awareness Core policies approved, training launched
Technical controls MFA, logging, backup and patching evidence in place
Supplier and access Supplier register, first access review completed
Audit readiness Internal audit done, management review minuted

Do not sprint on everything equally. Start with high-risk areas, because early wins there reduce actual exposure and give the sponsor something concrete to point to.

How long does a phased implementation take?

There is no single number. ISACA notes that duration varies with management commitment, scope, organizational size, number of locations and budget. A startup with one office and cloud-based systems moves differently from a firm with several sites and legacy infrastructure.

A better approach is to estimate each phase separately and add them up, then compare the result with a benchmark for companies like yours. Our implementation timeline guide and certification timeline guide show how those phases typically line up.

The factors that most often stretch a plan:

  • Leadership attention. Decisions that wait weeks for sign-off stall every sprint behind them.
  • Scope creep. Adding a business unit midway restarts parts of the risk work.
  • Evidence gaps. Controls that exist but produce no records have to run longer before an audit.
  • Audit availability. Certification body calendars can push the final date.

Budgeting each phase

Costs fall into a few groups: internal staff time, tooling, optional consulting for the gap assessment and documentation, internal audit, and the external audit fees. Figures published by vendors and consultancies vary widely by company size and scope, so use them as context rather than a quote. Our certification cost breakdown explains each cost group.

Two budgeting habits help. First, map each line to a phase, so the sponsor approves money against milestones. Second, include the recurring costs from the start: surveillance audits in the following years, and recertification at the end of the cycle. If you are also weighing the cost of a broader security assessment, this guide to budgeting for a cybersecurity assessment is a useful comparison point for the scoping work.

After certification: the cycle continues

Certification is a checkpoint, not the end of the phased plan. The certificate runs for three years, with annual surveillance audits in the two years that follow and a recertification audit before it expires. Between audits you keep running the cycle: risk reviews, internal audits, management reviews, corrective actions and awareness training.

The simplest way to stay ready is to turn the implementation sprints into a yearly calendar. One quarter for the internal audit, one for risk review and supplier checks, one for management review and objectives, one for audit preparation. Nothing then piles up the month before the auditor arrives.

Our perspective

Most teams we see start from the wrong question. They ask how much ISO 27001 costs, when the useful question is how much each phase costs for a company like theirs, and what changes if scope, size or maturity changes.

That is why we built our calculator around phases and assumptions you can edit. Company size, industry and security maturity feed a real-time estimate. Model reference comparisons let you check your plan against that reference, and the maturity assessment across the four Annex A control themes shows where your effort will actually go.

A phased plan should be something you can defend in front of your executives and your auditor. That means traceable numbers, a timeline you can adjust, and the ability to save and compare scenarios: a nine-month plan against a twelve-month plan, a narrow scope against a broad one. Estimates you can challenge are estimates people trust.

Start with the numbers, then sprint against them.

Martin

Plan your phases with real numbers

If you are ready to size the project, our ISO 27001 cost calculator turns your company size, industry and security maturity into a real-time estimate, and you do not need to sign up for the first calculation. You can save and compare scenarios, export a PDF report, share a link with your sponsor, and lay out phases in a customizable Gantt-style timeline. Our methodology page shows how the figures are built.

Ismscalculator

Not sure where you stand? Start with the free 2-minute check, or take the full readiness assessment for a domain-by-domain view. If you want an independent consultant to take on the gap assessment, you can also request an introduction through the platform.

FAQ

How many phases does an ISO 27001 implementation have?

There is no official number, because the standard requires a management system, not a project plan. Most teams use five or six phases: scope and budget, gap assessment, risk treatment and documentation, operation, internal audit, and certification audits. Pick the split that gives each phase a clear deliverable and owner.

Can we run ISO 27001 implementation in sprints?

Yes. Two-week sprints with a backlog drawn from your gap assessment suit the work well, and Flo Health has published its experience delivering ISO 27001 this way. Give each sprint a deliverable you can demo, such as an approved policy or a completed access review.

What should come first: the gap assessment or the risk assessment?

The gap assessment comes first. It shows where you stand against the standard and what is missing, and it sets your priorities. The risk assessment then determines which controls you need, and the Statement of Applicability records those decisions.

What do auditors want to see before Stage 2?

They expect a working system with records: a signed policy, management review minutes, a scored risk register, a Statement of Applicability, access reviews, training and incident records, and an asset register. An internal audit, performed by someone independent of the area audited, should be complete before Stage 2.

What happens after we get the certificate?

The certificate lasts three years. Annual surveillance audits follow in the next two years, and you recertify before it expires. Keep the management system running in between with regular risk reviews, internal audits and management reviews.

Sources

Ready to Estimate Your ISO 27001 Costs?

Use our free calculator to get a tailored cost, effort, and timeline estimate based on your company profile.

Calculate your estimate — free
Back to all articles