How long does ISO 27001 certification take? That depends mostly on your size, your scope and how much of the work you have already done. No honest consultant can give one number for every company. What we can give you is the order of the work, the things that slow it down and a way to build a realistic plan.
ISO/IEC 27001:2022 sets the requirements for an information security management system (ISMS). To certify, you build that system, run it long enough to produce records, and pass a two-stage audit by an accredited certification body. The calendar time comes from three things: your preparation, how quickly your people can act and the audit dates available.
What are the phases of an ISO 27001 project?#
Every project follows the same broad path. The length of each phase is what varies.
- Scope and gap analysis. Decide what is in scope and compare your current controls with the standard.
- Risk assessment and treatment. Identify information security risks, decide how to treat them and record the choices.
- Documents and controls. Write the policies and procedures, and put missing controls in place.
- Training and awareness. Explain the system to the people who use it.
- Running the system. Operate the controls and keep records, so the auditor sees evidence of use.
- Internal audit and management review. Check the system yourself and have top management review it.
- Stage 1 audit. The certification body reviews your documents and readiness.
- Stage 2 audit. The auditor checks that the system works in practice, and a certificate follows if the result is satisfactory.
Note that the phases overlap. You can draft documents while the risk assessment is still being reviewed, and you can train staff while controls are being put in place. A good project manager overlaps the work where safe, and keeps dependencies, such as risk treatment before the Statement of Applicability, in the right order.
How long does ISO 27001 certification take for different companies?#
Without quoting fixed durations, here is how the situation changes the plan.
| Situation | Effect on timeline |
|---|---|
| Small company, narrow scope, good basic security | Shortest path, because fewer people and processes are involved |
| Mid-size company, several teams, some policies in place | A middle path, with time spent on alignment and records |
| Large or multi-site organisation, complex systems | Longest path, because of more people, more risks and more evidence |
| Starting from no documented security | Longer, as controls must be built before they can be audited |
Treat these as patterns, not promises. Two companies of the same size can need very different time if one already controls access, backups and suppliers well and the other does not. The gap analysis is what turns a rough guess into a plan you can trust.
What slows an ISO 27001 project down?#
Delays usually come from people and decisions, not from the standard itself.
- Unclear scope that keeps changing during the project.
- No named owner, so tasks wait for someone to take them.
- Top management not available for approvals and the management review.
- Risk assessment done in a hurry, then redone when gaps appear.
- Controls that need purchases or vendor work, such as logging or backup changes.
- No time for the system to run, so there are no records to show an auditor.
- Waiting for certification body audit dates in a busy period.
The last two deserve attention. An ISMS needs a period of operation before Stage 2, because the auditor wants to see that you actually follow your procedures. Ask your certification body how much operating history they expect. Also book the audit dates early, so your plan has fixed targets.
How can you shorten the timeline safely?#
You cannot skip the standard, but you can remove avoidable delay.
- Fix a narrow, sensible scope and keep it stable.
- Name one project owner and one backup.
- Use ready-made templates to speed up drafting. Our ISO 27001 toolkit provides editable documents and a gap assessment checklist, with one year of e-mail support and a free upgrade within 6 months. You still need to adapt them to your business.
- Run the gap analysis first, so you start with facts.
- Schedule management review and internal audit dates at the start.
- Consider outside guidance for a first project. See our ISO 27001 consulting, which can help you avoid false starts.
Another practical help is to keep the first version simple. Short policies that people read are better than long ones that nobody follows. You can add detail later, during the yearly improvement cycle. Auditors check that the system fits your business and works, not that it is long.
Work backwards from the audit. Pick the Stage 1 and Stage 2 dates your certification body offers, then place each phase before them, with a few weeks of spare room. A plan with a margin survives the usual surprises, such as a key person on leave or a vendor delay.
Keep the team informed as you go. A short weekly status note, with what is done, what is blocked and what is next, keeps the project visible to management and makes problems easy to spot early. Teams that skip this often discover late that an approval or a purchase was never started.
Finally, remember that certification is not the end. After the certificate, you run the system, hold surveillance audits and improve it. A realistic timeline therefore covers the first certificate and the habits that keep it valid.
Frequently asked questions#
Can we get certified without any operating history?#
Not usually. The auditor needs records that show your controls work. Ask your certification body how much operating history it expects before Stage 2.
Does a consultant make the project faster?#
Often, because it avoids rework and false starts. But the speed still depends on how quickly your own people act. No one can promise an audit outcome.
Is the certificate valid forever?#
No. It is typically valid for three years, with yearly surveillance audits, and then you recertify.
For the full picture, read our complete guide to ISO 27001 or contact AdWiser to build your plan.

Leave a Comment