

ISO 27001 projects stall on logistics far more often than on security. Teams treat certification as a documentation exercise, write a stack of policies, then discover shortly before Stage 2 that nobody owns access reviews and no one has booked a certification body. It is a cross-functional project, and it needs a real plan: a phased timeline, named owners, a budget, and an evidence checklist tied to your Statement of Applicability.
Running certification as a sequenced project helps teams prepare for Stage 2. Here is how to build that plan.
Before you draw a single timeline, make sure these are in place. Skipping them is a frequent reason a plan has to be rewritten halfway through.
Management commitment: a named sponsor at leadership level who can approve budget, resolve conflicts between teams, and sign off the management review.
A rough scope decision: which legal entities, products, locations and systems you intend to certify.
A place to track work: a compliance automation platform, or at minimum a shared task tracker with owners and due dates.
Familiarity with ISO 27001:2022 Annex A: the four control themes (organizational, people, physical, technological) and what they ask of you.
A starting structure: our free ISO 27001 project plan in Excel gives you the five phases and task list to adapt rather than invent.
Scope determines everything downstream: audit duration, effort, cost, and how many controls you have to evidence. Decide which business units, offices, cloud environments and processes sit inside the ISMS boundary, and write down what sits outside and why. A 40-person SaaS company certifying one product and its AWS production environment has a very different workload from a manufacturer certifying three sites.
Then run a gap analysis against Annex A to size the actual work. Be honest here. Risk assessment maturity is weaker than most teams assume: in the UK's 2025/2026 cyber security survey, 41% of small businesses said they had undertaken a cyber security risk assessment, down from 48% in the previous survey (UK Department for Science, Innovation and Technology and Home Office).
The output of this step is a gap list with an owner and an effort estimate per item. That list becomes your project backlog.
You do not need a full-time CISO to certify. You do need unambiguous ownership. A mid-sized German company can run the program with a part-time project lead (often a CTO, head of IT or security champion) supported by engineering, HR, legal and the leadership sponsor.
Build a simple RACI across the main workstreams: ISMS documentation, risk management, technical controls, people controls (onboarding, offboarding, training), supplier management, and audit coordination. Name a person per Annex A control rather than a department. "Engineering" is not an owner.
Capacity is the real constraint. In ENISA's 2024 survey of organizations in EU sectors covered by NIS 2, 59% of surveyed SMEs reported difficulty filling cybersecurity roles (European Union Agency for Cybersecurity). Confidence is a constraint too: a UK cyber skills survey found 43% of businesses reported that their cyber lead lacked confidence in carrying out a cyber security risk assessment (UK Department for Science, Innovation and Technology, Ipsos and Perspective Economics). Plan around the people you have, and lean on guided workflows or expert support for the parts your team has never done before.
Split the budget into four buckets so leadership can see where money and time actually go:
Internal time: the largest and most frequently ignored cost. Count engineering hours for technical controls, plus the project lead's weekly commitment.
Tooling: a compliance platform, plus any security tooling the gap analysis exposed (MDM, logging, vulnerability scanning).
External support: optional consulting, policy writing, penetration testing or internal audit, scoped to specific deliverables.
Certification body fees: Stage 1 and Stage 2 audit days, quoted by an accredited body (in Germany, usually DAkkS-accredited), plus annual surveillance.
Resist fixing numbers too early. Audit effort depends on headcount, scope complexity and number of sites, so collect quotes from two or three accredited bodies before locking the figure. The business case is usually easier than teams expect: in ENISA's 2025 NIS Investments study, 70% of surveyed organizations identified regulatory compliance as a main driver of cybersecurity investment during the preceding year (European Union Agency for Cybersecurity).
The Statement of Applicability (SoA) is the spine of your audit. For every Annex A control, record whether it applies, the justification, and its implementation status. Then extend it into an evidence checklist by adding one column: what artifact proves this control operates?
Be specific. "Access control policy" is a document; a recurring access review with dated approvals is evidence. Auditors sample records across the period, so one screenshot from last week rarely survives Stage 2. Our guide to ISO 27001 audit evidence that passes breaks down what sampling looks like in practice, and the nonconformities auditors commonly write can involve evidence gaps rather than missing policies.
Automated collection is what keeps this current. Integrations with AWS, Google Cloud, Azure or Microsoft 365 can pull configuration states, user lists and device posture continuously, so the checklist stays populated instead of being rebuilt by hand. Technology adoption here is already mainstream: in PwC's 2025 global compliance survey, 76% of respondents said their companies used technology for risk assessment (PwC).
Lay the project out in five phases, each with an exit criterion:
Scope and gap analysis: boundary agreed, gap list signed off.
Implementation: policies approved, risk assessment and risk treatment plan complete, technical controls live.
Operation: controls running long enough to generate records. This is the phase teams cut short, and it is the one auditors test.
Internal audit and management review: real findings, documented corrective actions, leadership decisions recorded.
Certification audit: Stage 1 reviews your documentation and readiness; Stage 2 tests whether the ISMS actually operates.
Leave a gap between Stage 1 and Stage 2 to close findings. Book the certification body early, because lead times at accredited bodies are often the binding constraint, not your own readiness. Total duration depends on scope and starting maturity, though automation can shorten the implementation phase. Work through our pre-audit readiness checklist before you confirm the Stage 2 date.
Certification is a three-year cycle, not an event. Annual surveillance audits sample a subset of controls, and recertification revisits the whole ISMS. Put the recurring activities in your plan now: regular access reviews, risk assessment refreshes at planned intervals, supplier reviews, awareness training, internal audit, and management review.
Assign each a calendar date and an owner in the same system you used for the certification push. Continuous monitoring and automated evidence refresh mean surveillance preparation becomes a review exercise rather than a second project.
Scope creep mid-project: a new product or acquired entity appears in month four. Decide explicitly whether it enters this cycle or the next, and update the SoA and certification body quote accordingly.
Evidence gaps found weeks before Stage 2: run automated readiness checks regularly, not once. An ISO 27001 checklist surfaces missing artifacts while there is still time to generate records.
Budget overruns from unplanned consulting: scope external help to named deliverables with fixed outputs, and move repeatable work into platform-supported workflows.
A stalled handover: if a consultant-led project has gone quiet, migrate the existing policies, risk register and SoA into a single system before restarting, so you keep the work already paid for.
Start with scope and a RACI, then build everything else around the evidence checklist. If you want a structure to copy rather than design, our phased project plan worksheet gives you owners, phases and tasks in one place, and Secfix, the compliance automation platform built in Europe, can keep that plan populated with automated evidence collection as you move toward Stage 2.
Fix your ISMS boundary in writing before implementation starts, and treat any later addition as a formal scope change.
Name an individual owner for every applicable Annex A control, not a team.
Budget in four buckets and collect quotes from two or three accredited certification bodies before committing a number.
Extend your Statement of Applicability with an evidence column, and automate collection wherever an integration exists.
Schedule surveillance activities in the same plan on the day you book Stage 2.
A penetration test is not explicitly mandatory. Annex A requires technical vulnerability management, and a pentest is a common way to demonstrate it, so many auditors expect to see one or an equivalent justification in your risk treatment. For software companies selling to enterprise customers, we generally recommend one.
Contact accredited bodies directly and request a quote based on your scope, headcount and number of sites. Compare audit days and surveillance terms, not just the headline fee, then schedule Stage 1 and Stage 2 with enough space between them to close findings. Book early, as availability is often the longest lead time in the whole project.
An information security management system is the whole framework: scope, risk assessment, controls, documented procedures, internal audit, management review and continuous improvement. A security policy is one document inside it. Certification assesses the management system and whether it demonstrably operates, which is why evidence matters more than page count.
Yes. The requirement is a committed project lead with leadership backing and clear control ownership across engineering, HR and operations. Guided workflows, automated evidence collection and targeted expert input cover the specialist knowledge gaps that a dedicated security hire would otherwise fill.
Discover stories, tips, and resources to inspire your next big idea.

The Secfix Agent is lightweight program that runs daily in the background of your employee’s computers for security checks
Free SaaS webinar now open for all our visitors