ISO 27001 Implementation Roadmap: An Honest Phase Guide

A workable ISO 27001 implementation roadmap follows the standard’s own clause order, not a template shop’s task list: leadership mandate first, then context and scope (clause 4), leadership and policy (clause 5), risk assessment and treatment (clause 6), support and documented information (clause 7), operation and evidence (clause 8), internal audit and management review (clause 9), and only then the external certification audit. Published end-to-end figures from a named US audit firm run 3 to 12 months depending on size and starting point (IS Partners, https://www.ispartnersllc.com/blog/how-long-does-iso-27001-certification-take-a-realistic-timeline-and-what-to-expect/, checked 13-08-2026), and the practitioner consensus on certification forums sits at roughly 6 to 12 months for the whole effort, in the words of one consultant and lead auditor answering a founder, “be realistic about the timeline (around 6-12 months is typical)” (u/lexicalmatt on r/SaaS, ~2025, https://old.reddit.com/r/SaaS/comments/1h45waz/about_time_to_get_iso_27001_certificationneed/; practitioner forum language, not a verified figure).

The whole roadmap in one table

The phases below are anchored to the clause structure of ISO/IEC 27001:2022 as printed in the official contents page of EN ISO/IEC 27001:2023, the European adoption whose text is identical to ISO/IEC 27001:2022 (CEN-CENELEC adoption contents page via licensed reseller preview, https://standards.iteh.ai/catalog/standards/cen/fb88c620-1d4f-4fc7-b60c-eae6f5ba5732/en-iso-iec-27001-2023, checked 13-08-2026). The per-phase durations are indicative planning splits inside the sourced combined windows, which are quoted beneath the table.

PhaseWhat happensWho does the workRough duration
0. MandateSenior management commits, out loud, and names an internal ownerFounder or CEO, then the named ownerBefore the clock starts
1. Context and scope (clause 4)Understand the organisation and its interested parties, draw the ISMS scope tightly, record itThe internal owner, with leadership input2 to 4 weeks
2. Leadership, policy and roles (clause 5)Information security policy, roles, responsibilities and authorities assignedLeadership signs; the owner drafts1 to 3 weeks, overlapping phase 1
3. Risk assessment and treatment (clauses 6.1.2, 6.1.3)Risk methodology, risk register, risk treatment plan, Statement of ApplicabilityThe owner, with whoever knows the systems4 to 8 weeks
4. Support and documented information (clause 7)Resources, competence, awareness, communication, controlled documentsThe owner and team leads2 to 6 weeks, overlapping phase 3
5. Operation and evidence (clause 8)The controls run as designed and produce records an auditor can sampleThe whole team, business as usual4 to 12 weeks of operating records
6. Internal audit and management review (clauses 9.2, 9.3)A full internal audit by someone independent of the build, then a formal management review with minutesAn internal or bought-in auditor; top management in the room4 to 8 weeks (IS Partners, checked 13-08-2026)
7. Certification audit (Stage 1 and Stage 2)An accredited certification body reviews the documented system, then tests whether it operatesThe certification body, with your team answering4 to 8 weeks elapsed (IS Partners, checked 13-08-2026); audit days scale with in-scope headcount
8. After the certificateAnnual surveillance audits; recertification at the end of the cycleThe certification body, with your teamCertificate valid 3 years (Cybernion and databrackets, checked 13-08-2026)

The sourced combined windows behind the splits: IS Partners publishes implementation at 2 to 6 months, the internal audit phase at 4 to 8 weeks, the audit phase at 4 to 8 weeks, and an overall range of 3 to 12 months (IS Partners, checked 13-08-2026). A 2026-dated roadmap on an unbranded content site bands the total by size: small companies 3 to 6 months, medium 5 to 9, large 8 to 20 (Infosecurix, https://infosecurix.com/2026/07/13/the-definitive-iso-27001-implementation-steps-a-strategic-roadmap-for-2026/, checked 13-08-2026; publisher credentials opaque, treat as indicative only). What those durations depend on is covered in the durations section below.

Why listen to us

Atoro is an Irish AI governance and cyber compliance consultancy for software companies, and the first consultancy in Europe certified against ISO 42001. Our team has delivered more than 200 certifications across security and compliance (atoro.io, checked 08-08-2026), including ISO 27001 implementation work for software companies in Ireland and the UK. This roadmap is the sequence we work to, mapped to the clause structure the certification audit actually tests.

Do you need ISO 27001 yet?

Probably yes if enterprise customers or prospects keep asking for it, probably not yet if nobody in your pipeline has raised it. On buyer forums the reason given for starting is almost always customer demand, and the phrasing is consistent: “We’re a scrappy startup trying to get ISO 27001 certified (mostly because those enterprise clients keep asking for it)” (u/LevelFormal1459 on r/ISO27001, ~2025, https://old.reddit.com/r/ISO27001/comments/1kqf7k7/iso_27001_stage_1/; buyer forum language) and “Clients are starting to demand it, and patching together answers to their security questions just isn’t cutting it anymore” (u/EnoughContext022 on r/SaaS, ~2025, https://old.reddit.com/r/SaaS/comments/1h45waz/about_time_to_get_iso_27001_certificationneed/; buyer forum language).

The demand signal has a scale behind it: “As per the ISO Survey 2022, over 70 000 certificates were reported in 150 countries and from all economic sectors” (ISO, https://www.iso.org/standard/27001, checked 13-08-2026; figure date-stamped to the ISO Survey 2022, the most recent shown on that page as checked).

For UK and Irish buyers specifically, three practical markers tell you the timing is right:

  • A prospect’s procurement team asks for the certificate by name, or your security questionnaire answers keep losing you late-stage deals.
  • The buyer asks whether the certificate is accredited. In Ireland the standard is adopted unchanged as I.S. EN ISO/IEC 27001:2023, and certification to it is equivalent to certification to ISO/IEC 27001:2022 (NSAI, https://www.nsai.ie/certification/management-systems/iso-iec-27001-information-security-management-system/, checked 13-08-2026). An accredited certificate, issued by a certification body accredited by UKAS in the UK or INAB in Ireland (INAB directory of management systems certification bodies, https://www.inab.ie/inab-services/management-systems-certification/directory-of-management-systems-certification-bodies/, checked 06-08-2026), is, in our delivery work, what enterprise procurement teams mean when they ask.
  • You can name the revenue the certificate protects or unlocks. If you cannot, the honest answer is to keep answering questionnaires well and revisit in two quarters.

If the demand is not there yet, do not start the build. A roadmap started without commercial pull tends to die in phase 5, where the unglamorous evidence work lives.

Step zero: get senior management support out loud

Before scope, before policy, before any document: senior management commits, and says so to the company. Clause 5.1 of the standard is titled “Leadership and commitment” (EN ISO/IEC 27001:2023 contents page, checked 13-08-2026), and practitioners are blunt about why it comes first. The top-voted answer in an implementation thread on r/ISO27001 reads, in full: “Senior Management Support. Senior Management Support. Senior Management Support.” (u/InterestingMedium500, ~2025, https://old.reddit.com/r/ISO27001/comments/1rf1vn6/responsible_for_iso_27001_implementation/; practitioner forum language). Another implementer in the same thread adds the mechanism: “Make sure you get full support from your management and they say it out loud to the rest of the company. Because there’re times that you have to be annoying to other colleagues to get things done.” (u/chrans, same thread; account has a declared commercial interest in compliance software, phrasing used as language only).

The practical test: can the person running the implementation book time on other people’s calendars, change how other teams work, and get budget for the audit? If not, fix that first. It is cheaper than discovering the problem in phase 5.

Phase 1: context and scope (clause 4)

Answer first: decide what the ISMS covers, write it down tightly, and resist the urge to start with the tech stack. Clause 4 covers “Understanding the organization and its context” (4.1), “Understanding the needs and expectations of interested parties” (4.2), “Determining the scope of the information security management system” (4.3) and the ISMS itself (4.4) (EN ISO/IEC 27001:2023 contents page, checked 13-08-2026).

The sequencing correction practitioners repeat to technically minded implementers: “Put that aside (You will need that later) and first of all buy a standard read it. And then start with 4-7 otherwise your requirements can not be right. You can not do anything if you don’t have a scope or Management support or the proper ressources to do all of this.” (u/Legitimate_Dog4229 on r/ISO27001, ~Sep 2025, https://old.reddit.com/r/ISO27001/comments/1nf48gb/where_to_start_with_iso_27001_compliance_aws/; practitioner forum language). The same thread’s question is the archetypal roadmap ask, from a first security hire at a company running everything in AWS: “I’m looking for a practical approach or roadmap that I can propose to leadership, something like: Step 1: establish ISMS scope, Step 2: identify assets, Step 3: assess AWS controls, etc.” (u/Loud_Message1058, same thread; buyer forum language).

On scope, the forum consensus is repeatable advice, not a rule of the standard: “Scope. Scope. Scope. What are you protecting and for whom. Draw a circle around that and keep as tight as possible in year one. Minimal viable compliance.” (u/Finominal73 on r/ISO27001, ~2025, https://old.reddit.com/r/ISO27001/comments/1mowu3o/iso_27001_pros_whats_your_number_one_tip_for/; practitioner forum language). For a small provider the narrow version sounds like this: “start narrow. Your core managed services offering, the team delivering it, the systems supporting it. Don’t try to include everything you do. You can expand scope later.” (u/mlitwiniuk on r/ISO27001, ~Jun 2026, https://old.reddit.com/r/ISO27001/comments/1tnklcs/defining_the_scope_for_a_small_msp/; practitioner forum language). And keep the scoping statement general enough to survive change: “You don’t want to have to purchase a new certificate everytime you retire a subprocess or introduce a new one.” (u/Pure-Gas5424, same thread).

One 2024 addition now sits inside this phase. Amendment 1:2024 to ISO/IEC 27001:2022 adds climate-change considerations to the clause 4.1 and 4.2 context text; ISO lists the amendment as a free download at CHF 0 on the standard’s page (ISO, https://www.iso.org/standard/27001, checked 13-08-2026; tier 2 corroboration that Amd 1:2024 added a documented climate change assessment: SureCloud, checked 13-08-2026). Expect auditors to ask whether climate change was considered as a relevant issue in your context analysis, however briefly.

Phase 2: leadership, policy and roles (clause 5)

Answer first: turn the step-zero commitment into paper: an information security policy, and named roles, responsibilities and authorities. Clause 5 covers “Leadership and commitment” (5.1), “Policy” (5.2) and “Organizational roles, responsibilities and authorities” (5.3) (EN ISO/IEC 27001:2023 contents page, checked 13-08-2026).

Keep this phase short and real. A one-page policy that leadership has actually read beats a forty-page document nobody owns. What the auditor tests later is not the policy’s length but whether roles named in it match what people actually do.

Phase 3: risk assessment and treatment (clauses 6.1.2 and 6.1.3)

Answer first: assess your information security risks, decide how to treat them, and record both in the document chain the audit will test: risk methodology, risk register, risk treatment plan and Statement of Applicability. Clause 6.1.2 covers the information security risk assessment and 6.1.3 the risk treatment (EN ISO/IEC 27001:2023 contents page, checked 13-08-2026); the Statement of Applicability requirement sits at clause 6.1.3 d), with four required contents: the necessary controls, justification for inclusions, whether each is implemented, and justification for exclusions of Annex A controls (tier 2 corroboration across three independent pages: Cybernion, https://cybernion.com.au/insights/iso-27001-statement-of-applicability/, SecureSlate, https://getsecureslate.com/blog/iso-27001-statement-of-applicability-template, Security Compliance Guide, https://securitycomplianceguide.com/blog/iso-27001-statement-of-applicability/, all checked 13-08-2026; direct confirmation from ISO’s online browsing platform was blocked in our research session, flagged in the source list).

Two sequencing corrections buyers need here, both from practitioner forums. First, risk work does not come before scope: “It seems you started from the Risk Assessment part which is actually a rookie mistake. You start by creatign a project plan and defining the scope, and then you follow several steps before performing the Risk Assessment.” (u/pedercina7 on r/ISO27001, ~Jul 2026, https://old.reddit.com/r/ISO27001/comments/1umi2ap/need_guide_for_isms/; practitioner forum language, typo in original). Second, the register drives everything downstream: “If you are asking what controls you need, you never actually performed a risk assessment and created risk treatment plans. Those would tell you what to do.” (u/gomaterzu, same thread).

This is also where the 2022 edition’s structure matters. Annex A of the standard “contains 93 information security controls organised under four themes: Organisational controls, People controls, Physical controls, Technological controls” (NSAI, checked 13-08-2026), and your Statement of Applicability works through that set, not the withdrawn 2013 edition’s 114. And clause 6.3, “Planning of changes”, is new in the 2022 edition (EN ISO/IEC 27001:2023 contents page, checked 13-08-2026): changes to the ISMS itself now need to be planned, which in practice means your change log and your roadmap for expanding scope become audit evidence.

Phase 4: support and documented information (clause 7)

Answer first: resource the ISMS, make people competent and aware, and get your documented information under control. Clause 7 covers resources (7.1), competence (7.2), awareness (7.3), communication (7.4) and documented information (7.5) (EN ISO/IEC 27001:2023 contents page, checked 13-08-2026).

This phase is the paperwork people picture when they dread ISO 27001, and it is smaller than its reputation for a software company. Most of what clause 7.5 demands already exists in some form: onboarding material, access procedures, incident runbooks. The work is bringing them under version control with named owners and review dates, not writing a library from scratch. As one implementer put it: “most people don’t realize how much they actually already doing the controls according to ISO 27001 requirements; they just don’t know about it” (u/chrans on r/ISO27001, ~2025, https://old.reddit.com/r/ISO27001/comments/1rf1vn6/responsible_for_iso_27001_implementation/; practitioner forum language, account has a declared commercial interest in compliance software).

Phase 5: operation and evidence (clause 8)

Answer first: run the system you designed, for long enough that it produces records, because those records are what Stage 2 samples. Clause 8 covers operational planning and control (8.1), and the risk assessment and treatment repeated as operations (8.2, 8.3) (EN ISO/IEC 27001:2023 contents page, checked 13-08-2026).

One myth needs killing here, because it circulates on ranking pages. You will read that “the ISMS must have operated for at least three months before Stage 2” (Elevate Consult, https://elevateconsult.com/insights/iso-27001-audit-stage-1-vs-stage-2-differences-explained/, checked 13-08-2026, which presents this as fact). ISO 27001 sets no fixed minimum operating period before Stage 2, as Australian consultancy Cybernion states explicitly on the same topic (Cybernion, https://cybernion.com.au/insights/iso-27001-stage-1-vs-stage-2-audit/, checked 13-08-2026). What you need is operating evidence, not a calendar minimum: an auditor wants records that show the controls ran.

What that evidence looks like, from a lead auditor answering an implementer who had finished the documents: “An auditor wants records that show the controls ran, access reviews actually done, a backup restore tested, a couple of incidents logged and closed, management review minutes. With 8 to 10 people the real trap is over engineering it, so keep everything only as heavy as your risks genuinely justify.” (u/Head_Personality_431 on r/ISO27001, ~Jul 2026, https://old.reddit.com/r/ISO27001/comments/1umi2ap/need_guide_for_isms/; practitioner forum language).

The design principle for this phase: make evidence a by-product of doing the work, not a separate collection exercise. Access reviews scheduled in the calendar, restore tests ticketed, incidents logged in the tracker you already use. Teams that bolt evidence collection on at the end manufacture the scramble that forum posters describe as “audit prep turning into a last-minute scramble” (u/Mysterious_Step1657 on r/SaaS, ~Feb 2026, https://old.reddit.com/r/SaaS/comments/1r2v1mn/how_are_small_saas_teams_handling_soc_2_iso_27001/; buyer forum language).

Phase 6: internal audit and management review (clauses 9.2 and 9.3)

Answer first: before any certification body visits, a full internal audit and a formal management review must both be complete, and they are the two tasks first-timers leave too late. Clause 9.2 covers internal audit and 9.3 management review, with 9.3.2 and 9.3.3 setting the review’s required inputs and results (EN ISO/IEC 27001:2023 contents page, checked 13-08-2026).

The lead auditor quoted in phase 5 puts the sequencing plainly: “The two things left too late are almost always the internal audit and the management review, and you need both before a stage 2.” (u/Head_Personality_431, same thread). Schedule both inside your build window, not as audit preparation after it.

Two failure patterns to design out, both recurring practitioner forum observations rather than clauses of the standard. First, independence: an internal audit run by the people who built the system marks its own work and misses its own blind spots, which is why many first-timers buy this step in even when they did everything else themselves. Second, management review theatre: a meeting held to produce minutes, not decisions. The review has required inputs and results under 9.3.2 and 9.3.3, and an auditor reading minutes that record no decisions, no actions and no resource questions will treat them as what they are. The internal audit itself has its own depth (programme scope, competence, sampling, nonconformity handling), covered in our ISO 27001 internal audit requirements guide rather than repeated here.

Phase 7: the external certification audit

Answer first: an accredited certification body audits you in two stages, Stage 1 on the documented system and Stage 2 on the operating one, and the certificate then runs a three-year cycle with surveillance. The two-stage structure is set by ISO/IEC 17021-1, the certification-body requirements standard, not by ISO 27001 itself (Cybernion, checked 13-08-2026, which names ISO/IEC 17021-1 and ISO/IEC 27006-1 correctly; process detail also on certification body databrackets’ own FAQ page, https://databrackets.com/faqs/iso-27001-certification-process/, checked 13-08-2026).

Three mechanics worth knowing before you book:

  • Audit days scale with your scope headcount. The day count is calculated under ISO/IEC 27006-1 from the number of people in scope (Cybernion, checked 13-08-2026); day-count bands by headcount are published in IAF MD 5, referenced by Elevate Consult without a link (checked 13-08-2026). A tight phase-1 scope literally shrinks the audit bill.
  • Nonconformities have classes and a clock. Findings split into major and minor nonconformities, and corrective action follows clause 10.2 of the standard (databrackets FAQ, checked 13-08-2026). A major nonconformity can hold the certificate until it is fixed (Cybernion, checked 13-08-2026).
  • The certificate runs a three-year cycle. Annual surveillance audits keep it valid, with a recertification audit at the end of the cycle (Cybernion and databrackets, both checked 13-08-2026).

Choose the certification body on accreditation: UKAS-accredited in the UK, INAB-accredited in Ireland (INAB directory, checked 06-08-2026). And hold the role separation: a consultancy prepares you, and only an accredited certification body audits and certifies. Indian consultancy TCSA states it cleanly on its own methodology page: the consultant does not issue the certificate (TCSA, https://www.tcsa.in/frameworks/iso-27001/implementation, checked 13-08-2026). What the audit itself costs, and what drives that number, is covered in our ISO 27001 certification cost guide.

Two 2022-edition markers the old roadmaps miss

Most roadmap pages still ranking were written against the 2013 edition, and some have not caught up. Two cheap signals tell you whether advice you are reading is current.

Clause 6.3, Planning of changes. New in the 2022 edition; it simply did not exist in 2013 roadmaps (EN ISO/IEC 27001:2023 contents page, checked 13-08-2026). If a roadmap never mentions planning changes to the ISMS, it was not written against the current edition.

The control count. The 2022 edition has 93 Annex A controls in four themes (NSAI, checked 13-08-2026). The 2013 edition had 114 across 14 domains. Two duplicate 2026-dated roadmap pages from compliance platform dSalta still state, verbatim, “ISO 27001 requires extensive documentation across 114 controls in Annex A” (dSalta, https://www.dsalta.com/resources/iso-27001/iso-27001-implementation-roadmap-90-day-plan-ai-automation, checked 13-08-2026). If the number on the page is 114, the page is stale, whatever its date says.

How long it honestly takes, and what drives it

Answer first: months, not weeks. The sourced published windows are IS Partners’ 3 to 12 months overall, with implementation at 2 to 6 months, the internal audit phase at 4 to 8 weeks and the audit phase at 4 to 8 weeks (IS Partners, checked 13-08-2026), and the practitioner forum consensus of roughly 6 to 12 months (u/lexicalmatt, labelled forum language above). Anything dramatically shorter deserves a hard look at who benefits from the claim.

The short claims are compression marketing, and their own pages show it. dSalta sells a “90-day plan” wrapped around AI automation, on pages that still carry the 2013 edition’s control count (dSalta, checked 13-08-2026). Axipro publishes a week-by-week “6-week roadmap” whose own page concedes the problem, warning against what it calls “certification theatre” (Axipro, https://axipro.co/iso-27001-implementation-roadmap/, checked 13-08-2026). Six weeks of work can produce a documented system; it cannot produce the operating records that make a Stage 2 audit passable, unless the system already existed and the six weeks are documentation of a running reality.

What actually moves your duration:

  • Scope headcount. Audit days are calculated from the number of people in scope under ISO/IEC 27006-1 (Cybernion, checked 13-08-2026). Narrow scope, smaller audit, shorter Stage 2.
  • Evidence you already have. A company that already does access reviews, restore tests and incident logging starts phase 5 with months of records instead of weeks.
  • The internal owner’s protected time. Every duration above assumes someone owns this as a real part of their job, not as a side project between tickets.
  • What you cannot compress. The gap between writing a control and having records of it running. That is elapsed time, and no spend shortens it.

Where implementation projects actually go wrong

The same patterns recur across practitioner forums, and they are sequenced, not random.

Starting in the wrong place. Drafting policies or hardening AWS before scope and context exist. The corrections from u/Legitimate_Dog4229 and u/pedercina7 above are the two halves of the same mistake: start with clauses 4 to 7, in order.

Management review theatre. The review held to produce minutes rather than decisions. Clause 9.3.2 sets required inputs and 9.3.3 required results; minutes that show no decisions, actions or resource questions read as theatre to any auditor, and the pattern is a recurring practitioner forum complaint (recurring observation across the r/ISO27001 implementation threads cited above, labelled forum language).

An ISMS run just for the certification audit. The parallel universe version: documents that exist for the auditor while the real business runs elsewhere. Axipro’s “certification theatre” warning names the same thing from the vendor side (checked 13-08-2026), and the buyer who prompted the phase-5 lead auditor quote had the right instinct: “My goal is to build a complete and secure operational environment aligned with ISO 27001, not just prepare documentation” (u/JealousMap6488 on r/ISO27001, ~Jul 2026, buyer forum language). The test is brutal and simple: would this process still happen if the certificate disappeared?

Internal audit by the builders. The people who designed the system auditing their own design. Independence is what first-timers most often buy in, precisely because this blind spot is structural, not a skills gap (recurring practitioner forum pattern, labelled forum language).

Over-engineering a small company’s ISMS. Ten-person companies building enterprise-weight processes. The lead auditor’s advice from phase 5 bears repeating as the closing word of this section: “keep everything only as heavy as your risks genuinely justify” (u/Head_Personality_431, practitioner forum language).

What you can do yourself vs where help earns its fee

Answer first: a small team can genuinely self-implement, and practitioners say so; the places outside help earns its fee are the judgement calls and the independent checks.

The DIY case, from a lead auditor answering a small MSP owner who asked “how much of the preparation work I can realistically do myself”: “you can implement ISO27001 without spending a dime on any external software or consulting” (u/RepresentativeLow300 on r/ISO27001, ~May 2026, https://old.reddit.com/r/ISO27001/comments/1tbwo0l/practical_roadmap_to_iso_27001_certification_for/; practitioner forum language). The DIY roadmap itself, from a consultant in the first-security-hire thread: “Buy a copy of the standard … You would start fulfilling the requirements, clause by clause. First, you’d do a context analysis. Second, you’d draw up a policy. Third, you’d set up a plan. And so on. See and do, learn and do, from the above.” (u/Raf_Adel, ~Sep 2025, https://old.reddit.com/r/ISO27001/comments/1nf48gb/where_to_start_with_iso_27001_compliance_aws/; practitioner forum language). The standard itself costs CHF 155 from ISO (Swiss francs; ISO sells in CHF, not USD) and the climate amendment is a free download (ISO, https://www.iso.org/standard/27001, checked 13-08-2026).

The honest counterweights, same forums. On where to spend: “Then bring in a consultant mainly for gap analysis and audit readiness. (otherwise you risk to get precooked solution not easily fitting in your organisation).” (u/MimirLearning, ~May 2026, same MSP thread). On the hidden cost of DIY: “You will probably need 20-30x as long for – say – risk management as the consultant will. During those long hours you cannot bill any work you do to a customer. Is ‘doing it yourself’ really cheaper?” (u/Pure-Gas5424, same thread). And the resourcing pattern that works for small teams, from an r/SaaS founder thread: “The core play is: one owner, one system, maximum automation, and outside help only at key checkpoints.” and “Bring in a consultant just for the initial gap assessment plus pre-audit dry run; they’re overkill for day-to-day.” (u/gardenia856 on r/SaaS, ~Feb 2026, https://old.reddit.com/r/SaaS/comments/1r2v1mn/how_are_small_saas_teams_handling_soc_2_iso_27001/; practitioner forum language).

Our version of that pattern, stated plainly: you can do the context and scope work, the document control, the evidence habits and the management review logistics yourself, with one protected owner. Help earns its fee in four places: the gap analysis that calibrates the whole build, the risk methodology design that everything downstream depends on, the independent internal audit that cannot be independent if you built the system, and certification body selection and audit management. Note the MSP owner’s framing of the real question, which is the right one: “Which parts are worth doing yourself, and where is it better not to cut corners?” (u/BuffaloExternal6226 on r/ISO27001, ~May 2026; buyer forum language).

FAQs

Where do we start with ISO 27001 implementation?

With leadership commitment and scope, not with the tech stack or policy templates. Clause 4 context and scope work comes first because every later requirement depends on it: as one practitioner put it, “start with 4-7 otherwise your requirements can not be right” (u/Legitimate_Dog4229 on r/ISO27001, ~Sep 2025, practitioner forum language). Buy the standard itself (CHF 155 from ISO, Swiss francs, checked 13-08-2026) and read clauses 4 to 10 before writing anything.

How long does ISO 27001 implementation take before we are audit-ready?

Published figures from a named US audit firm put implementation at 2 to 6 months, inside a 3 to 12 month overall path to certification (IS Partners, checked 13-08-2026). Practitioner forum consensus sits at roughly 6 to 12 months for the whole effort (u/lexicalmatt on r/SaaS, labelled forum language). What moves you inside that range is scope headcount, existing evidence, and whether the internal owner has protected time.

Gap analysis first or policies first?

Neither, strictly: context and scope come first, then the gap analysis against the standard’s clauses, then policy work. Policies written before scope and risk assessment tend to be rewritten, which is why practitioners tell first-timers to read clauses 4 to 7 before drafting anything (u/Legitimate_Dog4229, practitioner forum language). The risk assessment then tells you which controls, and therefore which procedures, you actually need.

How narrow can our scope be in year one?

Narrower than most first-timers assume, and expandable later. The repeatable forum advice is “Scope. Scope. Scope. What are you protecting and for whom. Draw a circle around that and keep as tight as possible in year one” (u/Finominal73 on r/ISO27001, practitioner forum language). For a software company that typically means the core product, the team delivering it and the systems supporting it, not every activity the company touches. Keep the scoping statement general enough that retiring a subprocess does not force a certificate change.

Can we implement ISO 27001 ourselves, without a consultant?

Yes, and practitioners say so explicitly: “you can implement ISO27001 without spending a dime on any external software or consulting” (u/RepresentativeLow300, a lead auditor, on r/ISO27001, ~May 2026, practitioner forum language). The trade-off is time, with one counter-view estimating DIY takes 20 to 30 times longer than consultant-led work on tasks like risk management (u/Pure-Gas5424, same thread). The middle path most small teams land on: self-implement, and buy in the gap analysis, the independent internal audit and the pre-audit dry run.

Can a small team get audit-ready without a full-time compliance hire?

Yes, if one person owns it as a protected part of their job. The working pattern described by small-team founders is “one owner, one system, maximum automation, and outside help only at key checkpoints” (u/gardenia856 on r/SaaS, ~Feb 2026, practitioner forum language). What does not work is distributing ownership across a team where it is nobody’s actual job, which is how phase 5 evidence work turns into the last-minute scramble.

What do companies usually leave too late?

The internal audit and the management review, almost always. A lead auditor answering an implementer mid-build: “The two things left too late are almost always the internal audit and the management review, and you need both before a stage 2” (u/Head_Personality_431 on r/ISO27001, ~Jul 2026, practitioner forum language). Schedule both inside the build window, and keep the internal audit independent of the people who built the system.

Can we realistically get ISO 27001 certified in 90 days?

From a standing start, treat the claim as marketing. The 90-day plans on ranking pages come from platforms selling speed, and one of them still carries the withdrawn 2013 edition’s control count (dSalta, checked 13-08-2026). A 90-day build can document a system, but Stage 2 samples operating records, and those take elapsed time to accumulate; published end-to-end figures from a named US audit firm run 3 to 12 months (IS Partners, checked 13-08-2026). The exception is a company whose controls already run and whose 90 days are documentation of an existing reality.

The honest next step, if this roadmap has shown you the shape of the work, is a scoped plan rather than a generic quote. Atoro delivers ISO 27001 implementation for software companies in Ireland and the UK, working to exactly the sequence above, so the scope, the calendar and the split between your work and ours are settled before the build starts.

Sources

  1. ISO, ISO/IEC 27001:2022 standard page, https://www.iso.org/standard/27001, checked 13-08-2026 (tier 1, standards body: full title, edition 3, published 2022-10, 19 pages, list price CHF 155 (Swiss francs); Amendment ISO/IEC 27001:2022/Amd 1:2024 listed at CHF 0, free download, the climate-action amendment adding climate-change considerations to clause 4.1/4.2; ISO Survey 2022 figures “over 70 000 certificates … in 150 countries”, date-stamped to the 2022 survey as shown on the page).
  2. EN ISO/IEC 27001:2023 contents page via licensed reseller preview (iTeh Standards / SIST), https://standards.iteh.ai/catalog/standards/cen/fb88c620-1d4f-4fc7-b60c-eae6f5ba5732/en-iso-iec-27001-2023, checked 13-08-2026 (tier 1 adoption text, approved by CEN “without any modification” from ISO/IEC 27001:2022: clause 4-10 structure and subclause titles, including 6.3 Planning of changes new in the 2022 edition; 6.3 confirmed via the SIST Slovenian national-edition TOC on the same preview).
  3. NSAI (National Standards Authority of Ireland), ISO/IEC 27001 page, https://www.nsai.ie/certification/management-systems/iso-iec-27001-information-security-management-system/, checked 13-08-2026 (tier 1, national standards body and certification body: verbatim “Annex A of the standard contains 93 information security controls organised under four themes”; Irish adoption as I.S. EN ISO/IEC 27001:2023 and equivalence of certification).
  4. INAB, Directory of Management Systems Certification Bodies, https://www.inab.ie/inab-services/management-systems-certification/directory-of-management-systems-certification-bodies/, checked 06-08-2026 (tier 1, accreditation body: INAB accreditation context for Ireland).
  5. IS Partners, “How Long Does ISO 27001 Certification Take?”, https://www.ispartnersllc.com/blog/how-long-does-iso-27001-certification-take-a-realistic-timeline-and-what-to-expect/, checked 13-08-2026 (tier 2, named US audit firm, self-published: 3 to 12 month overall range; implementation 2 to 6 months; internal audit phase 4 to 8 weeks; audit phase 4 to 8 weeks).
  6. Cybernion, “ISO 27001 Stage 1 vs Stage 2 audit”, https://cybernion.com.au/insights/iso-27001-stage-1-vs-stage-2-audit/, checked 13-08-2026 (tier 2, named practitioner, strongest structural accuracy on the SERP: two-stage split set by ISO/IEC 17021-1; audit days scale with in-scope headcount under ISO/IEC 27006-1; ISO 27001 sets no fixed minimum operating period before Stage 2; three-year cycle; certificate withheld until a major nonconformity is corrected).
  7. Cybernion, Statement of Applicability guide, https://cybernion.com.au/insights/iso-27001-statement-of-applicability/, checked 13-08-2026 (tier 2: SoA requirement at clause 6.1.3 d) with the four required contents).
  8. SecureSlate, SoA template guide, https://getsecureslate.com/blog/iso-27001-statement-of-applicability-template, and Security Compliance Guide, SoA guide, https://securitycomplianceguide.com/blog/iso-27001-statement-of-applicability/, both checked 13-08-2026 (tier 2 corroboration of clause 6.1.3 d); note: direct tier 1 confirmation from ISO’s Online Browsing Platform was blocked (HTTP 403) in the research session).
  9. databrackets (US certification body), ISO 27001 certification process FAQ, https://databrackets.com/faqs/iso-27001-certification-process/, checked 13-08-2026 (certification body’s own page used for process mechanics only: Stage 1/Stage 2 detail, nonconformity classes, corrective action under clause 10.2, three-year cycle; its self-stated IAS/A2LA accreditation claim is unverified and is not relied on anywhere in this guide).
  10. Elevate Consult, Stage 1 vs Stage 2 comparison, https://elevateconsult.com/insights/iso-27001-audit-stage-1-vs-stage-2-differences-explained/, checked 13-08-2026 (tier 2: source of the “ISMS must have operated for at least three months before Stage 2” claim this guide refutes; also references IAF MD 5 day-count bands by headcount without a link).
  11. dSalta, “ISO 27001 implementation roadmap 90-day plan”, https://www.dsalta.com/resources/iso-27001/iso-27001-implementation-roadmap-90-day-plan-ai-automation (and its duplicate URL), checked 13-08-2026 (tier 2, platform marketing: the 90-day compression pitch; verbatim 2013-edition error “114 controls in Annex A” on 2026-dated pages).
  12. Axipro, ISO 27001 implementation roadmap, https://axipro.co/iso-27001-implementation-roadmap/, checked 13-08-2026 (tier 2: the week-by-week 6-week roadmap; its own “certification theatre” warning).
  13. TCSA Tranquility Cybersecurity, ISO 27001 implementation methodology, https://www.tcsa.in/frameworks/iso-27001/implementation, checked 13-08-2026 (tier 2, named Indian consultancy: consultant-versus-certification-body role separation; its “500+ implementations” and INR fee figures are self-asserted marketing and are not used in this guide).
  14. Infosecurix, 2026 roadmap, https://infosecurix.com/2026/07/13/the-definitive-iso-27001-implementation-steps-a-strategic-roadmap-for-2026/, checked 13-08-2026 (tier 2, unbranded content site, weak authority: size-banded timelines small 3-6, medium 5-9, large 8-20 months; used as indicative only).
  15. SureCloud, ISO 27001 pages, checked 13-08-2026 (tier 2 corroboration: “Amendment 1:2024 added a documented climate change assessment to ISO 27001:2022”).
  16. Practitioner and buyer forum language (LANGUAGE SOURCE ONLY, never evidence of fact): u/lexicalmatt on r/SaaS (~2025, https://old.reddit.com/r/SaaS/comments/1h45waz/about_time_to_get_iso_27001_certificationneed/, 6-12 month practitioner consensus); u/LevelFormal1459 on r/ISO27001 (~2025, https://old.reddit.com/r/ISO27001/comments/1kqf7k7/iso_27001_stage_1/, “enterprise clients keep asking for it”); u/EnoughContext022 on r/SaaS (~2025, same 1h45waz thread, “Clients are starting to demand it”); u/InterestingMedium500 and u/chrans on r/ISO27001 (~2025, https://old.reddit.com/r/ISO27001/comments/1rf1vn6/responsible_for_iso_27001_implementation/, senior management support; chrans account has a declared commercial interest in compliance software, flagged); u/Loud_Message1058, u/Legitimate_Dog4229, u/delvetechnologies, u/littlepeggysue and u/Raf_Adel on r/ISO27001 (~Sep 2025, https://old.reddit.com/r/ISO27001/comments/1nf48gb/where_to_start_with_iso_27001_compliance_aws/, roadmap ask, clauses 4-7 sequencing, DIY roadmap; delvetechnologies posts semi-commercial content, flagged); u/JealousMap6488, u/gomaterzu, u/pedercina7 and u/Head_Personality_431 on r/ISO27001 (~Jul 2026, https://old.reddit.com/r/ISO27001/comments/1umi2ap/need_guide_for_isms/, post-documents sequencing, risk-assessment-first correction, internal audit and management review left late, evidence expectations); u/Finominal73 on r/ISO27001 (~2025, https://old.reddit.com/r/ISO27001/comments/1mowu3o/iso_27001_pros_whats_your_number_one_tip_for/, “Scope. Scope. Scope.”); u/byxgm3rx, u/mlitwiniuk and u/Pure-Gas5424 on r/ISO27001 (~Jun 2026, https://old.reddit.com/r/ISO27001/comments/1tnklcs/defining_the_scope_for_a_small_msp/, small-MSP scoping); u/Mysterious_Step1657 and u/gardenia856 on r/SaaS (~Feb 2026, https://old.reddit.com/r/SaaS/comments/1r2v1mn/how_are_small_saas_teams_handling_soc_2_iso_27001/, resourcing pattern, last-minute scramble); u/RepresentativeLow300, u/MimirLearning, u/KeySubject4895, u/Pure-Gas5424 and u/BuffaloExternal6226 on r/ISO27001 (~May 2026, https://old.reddit.com/r/ISO27001/comments/1tbwo0l/practical_roadmap_to_iso_27001_certification_for/ and https://old.reddit.com/r/ISO27001/comments/1tbwjg0/iso27001_for_my_it_msp/, DIY feasibility and counterweights).
  17. Atoro supplied facts: Atoro is an Irish AI governance and cyber compliance consultancy for software companies; the first consultancy in Europe certified against ISO 42001; Atoro’s ISO 42001 certificate is AIMS-AT-120224, issued by A-LIGN under ANAB accreditation; atoro.io (checked 08-08-2026) states “more than 200 certifications delivered across security and compliance”.