To achieve ISO 27001 certification, you need a defined set of mandatory documents that prove your information security management system (ISMS) is structured, risk-aware, and consistently applied. These documents fall into three categories: policies, risk assessment records, and operational procedures. The exact volume depends on your organisation’s size and scope, but for small businesses, the list is more manageable than most people expect. Below, we answer the most common questions about ISO 27001 documentation so you know exactly what to prepare.
Which documents are mandatory under ISO 27001?
ISO 27001 specifies a core set of required documents that every certified organisation must maintain. These include the ISMS scope document, an information security policy, a risk assessment and risk treatment report, a Statement of Applicability (SoA), a risk treatment plan, and records of monitoring, internal audit results, and management reviews.
Beyond these, the standard requires documented evidence of competence for relevant staff, results of any corrective actions, and records showing that controls are operating effectively. While the standard does not dictate a specific format or file structure, every document must be version-controlled, accessible to the right people, and kept up to date. For small businesses, this rarely means hundreds of pages – a lean, well-organised set of documents covering the required areas is entirely sufficient.
What is a Statement of Applicability and why does it matter?
The Statement of Applicability (SoA) is a document that lists all the controls from ISO 27001 Annex A, states which ones you have implemented, and explains why any controls have been excluded. It is one of the most important documents in your ISMS because it directly connects your risk treatment decisions to your actual security controls.
Auditors pay close attention to the SoA because it shows whether your organisation has thought through its risks systematically. If you exclude a control, you need a justified reason – for example, a small software company with no physical products may reasonably exclude controls related to physical goods delivery. The SoA is also a living document: it should be updated whenever your risk landscape or business context changes. Think of it as the map that shows where your security controls are and why they are placed there.
How detailed does an ISO 27001 risk assessment document need to be?
Your ISO 27001 risk assessment document needs to be detailed enough to demonstrate a systematic, repeatable process – but it does not need to be exhaustive. It must identify information assets, describe the threats and vulnerabilities associated with each, assess the likelihood and impact of potential incidents, and record the resulting risk levels.
For small businesses, a focused risk assessment covering your most relevant assets – such as customer data, cloud systems, email infrastructure, and access credentials – is far more useful than a sprawling document that tries to cover every theoretical scenario. What matters most is consistency: use the same methodology throughout, document your reasoning, and show how your chosen controls respond to the risks you identified. Auditors want to see that your risk assessment drives your decisions, not that it fills a quota of pages.
What’s the difference between policies, procedures, and records in ISO 27001?
In ISO 27001, policies, procedures, and records serve three distinct purposes. Policies state your organisation’s intentions and commitments – for example, an acceptable use policy explains what employees may and may not do with company systems. Procedures describe how those intentions are carried out in practice. Records provide evidence that the procedures were actually followed.
Policies
Policies are high-level documents that set direction. Your information security policy, for instance, commits the organisation to protecting data and outlines who is responsible. Policies are typically approved by management and reviewed at regular intervals.
Procedures and records
Procedures translate policy into action – they describe step-by-step how tasks like access provisioning, incident response, or backup verification are performed. Records are the proof: logs, audit trails, signed forms, and review minutes that show the procedures were followed. All three layers are necessary for ISO 27001 certification, and auditors will look for alignment across them.
Can small businesses use templates for ISO 27001 documentation?
Yes, small businesses can absolutely use templates for ISO 27001 documentation, and doing so is a practical way to reduce preparation time significantly. Templates provide a compliant structure so you are not starting from a blank page, and they help ensure you do not accidentally omit a required element.
The important caveat is that templates must be customised to reflect your actual business. A generic policy document that does not mention your specific systems, roles, or processes will not satisfy an auditor. Templates work best as a starting framework – you fill in the specifics, remove sections that do not apply, and add detail that reflects how your organisation actually operates. Many digital tools and platforms now offer ISO 27001 certification support with pre-built, adaptable documentation, which makes this process considerably faster for small teams.
How long does it take to prepare ISO 27001 documentation?
For a small business, preparing ISO 27001 documentation traditionally takes between three and twelve months, depending on how complex your systems are and how much internal resource you can dedicate to the process. The risk assessment and Statement of Applicability tend to take the most time because they require genuine analysis rather than simply filling in a form.
That said, the timeline has shortened considerably with modern digital approaches. AI-assisted platforms can guide you through the documentation process step by step, automatically generating drafts based on your inputs and flagging gaps before your audit. What once required months of consultant-led workshops can now be completed in days when the right tools are in place. The bottleneck is usually not the writing itself – it is the internal decisions about scope, risk appetite, and control ownership that take time to align across your team.
How DICIS AG helps with ISO 27001 documentation
We built our platform specifically for small businesses that want ISO 27001 certification without the complexity and cost of traditional consulting engagements. Here is what working with us looks like in practice:
- AI-assisted documentation: Our platform generates the mandatory documents – including your risk assessment, SoA, and policies – based on your inputs, so you are not starting from scratch.
- Guided process: We walk you through each required step in a logical order, so nothing gets missed and you always know what comes next.
- Fully online audits: No travel, no on-site visits. Audits are conducted entirely online, which is particularly well suited to digital businesses and remote teams.
- Fast turnaround: What traditionally takes months can be completed in days on our platform, from documentation preparation through to certification.
- Transparent pricing: No hidden consultant fees. You know the cost upfront, which matters when you are running a small team with a defined budget.
If you are ready to get your ISMS in order and move toward certification, start your ISO 27001 certification with us today and see how straightforward the process can be.

