Most ISO 27001 projects slow down at the same point: the team understands the standard but is staring at a blank page. Policies, procedures, registers and records all need to exist, and nobody wants to write them from scratch.
An ISMS documentation toolkit exists to solve that problem. This article explains what a good one contains, which documents ISO/IEC 27001:2022 expects, and how to use templates so they reflect how your organisation actually works.
What an ISMS documentation toolkit is (and is not)#
A toolkit is a set of editable templates, checklists and worked examples that give you a starting framework for your information security management system. You adapt the content to your scope, risks, people and technology.
It is not a certification shortcut. Auditors do not assess whether you own templates. They assess whether your ISMS is defined, implemented and maintained. A template that has only had the company name changed will show up quickly in interviews and sample checks.
Used well, a toolkit saves drafting time, keeps document structure consistent, and reduces the risk of missing a required item. Used badly, it produces a thick manual that nobody follows.
The documents ISO 27001:2022 expects#
The main body of the standard requires certain information to be documented and retained. Annex A then adds supporting documentation through its controls. At the management-system level, expect to need the following.
| Document or record | What it does |
|---|---|
| ISMS scope statement | Defines the boundaries: locations, business units, systems and interfaces covered |
| Information security policy | Top-level direction from management, including commitment to objectives and improvement |
| Risk assessment and treatment methodology | Explains how you identify, analyse, evaluate and treat risks, and what criteria you use |
| Risk assessment and treatment results | The risk register and the treatment plan that follows from it |
| Statement of Applicability (SoA) | Lists the Annex A controls you have considered, whether each is applicable, and why |
| Information security objectives | Measurable targets, with plans for how they will be met |
| Competence records | Evidence that people doing security-relevant work are competent |
| Monitoring and measurement results | Evidence that you evaluate ISMS performance |
| Internal audit programme and reports | Planned audits, findings and follow-up |
| Management review outputs | Minutes and decisions from top-level review |
| Nonconformity and corrective action records | What went wrong, the cause, the fix and whether it worked |
Some of these are documents you write once and review. Others are records generated over time. A toolkit can give you the template, but the records only become real when you operate the ISMS.
Documents that support the Annex A controls#
The 2022 edition lists 93 Annex A controls grouped into four themes: organizational, people, physical and technological. You are not obliged to write a separate document for every control. Which documents you need depends on your risk treatment and your SoA decisions.
In practice, most organisations end up with policies and procedures such as:
- Organizational: access control, supplier security, incident management, business continuity for information security, legal and regulatory requirements, asset management and classification.
- People: screening, terms of employment, awareness and training, disciplinary process, remote working, confidentiality commitments.
- Physical: physical security perimeters, secure areas, clear desk and screen, equipment siting and disposal.
- Technological: secure configuration, malware protection, backup, logging and monitoring, cryptography, vulnerability management, change management, secure development, network security.
Keep these short and usable. A two-page procedure that staff follow is worth more than a twenty-page policy that sits on a shared drive.
What to look for in a toolkit#
Not every toolkit is equal. Before you commit, check it against this list:
- Aligned to the 2022 edition. Controls, theme structure and terminology should reflect ISO/IEC 27001:2022, not the older 2013 layout.
- Fully editable formats. You need to change wording, add your own controls, and keep version history.
- Coverage beyond policies. Look for procedures, registers, checklists, audit tools, training material and records templates, not only policy text.
- Worked examples. Filled-in examples show what "good enough" looks like, especially for a risk register and SoA.
- A gap assessment tool. It helps you see what already exists before you create anything new.
- Clear structure. Documents should map to the standard so you and your auditor can trace requirements easily.
The AdWiser ISO 27001:2022 Toolkit is one option along these lines. It provides 180+ editable template documents, including policies, procedures, controls, checklists, tools, presentations, posters and worked examples, plus a gap assessment checklist. It is delivered by e-mail, usually within 2 to 3 business days of payment confirmation.
How to use a toolkit without creating shelfware#
1. Run a gap assessment first#
Before editing any template, list what you already have: policies, runbooks, HR processes, vendor contracts, incident logs. Many organisations already do a lot of what ISO 27001 asks for, just informally.
2. Define scope early#
Scope drives everything else. Decide which business units, sites, systems and data are in, and document any dependencies on suppliers or other teams. A vague scope leads to vague documents.
3. Do the risk assessment before the controls#
Risk assessment results should decide which controls you apply. Writing policies first and justifying them afterwards is a common mistake, and the SoA will reveal it.
4. Tailor, then delete#
Replace generic wording with your real roles, tools and approval paths. Remove sections that do not apply. If a template says a quarterly access review happens and your team cannot realistically do it, change the template or change the practice. Do not leave a promise you will not keep.
5. Assign owners and review dates#
Each document needs a named owner, a version, an approval and a review cycle. Documented information must be controlled so people use the current version.
6. Run the ISMS, then audit it#
Operate the processes for long enough to generate records. Then carry out an internal audit and a management review, and fix what you find before any external assessment.
Frequently asked questions#
Do we need a document for all 93 Annex A controls?#
No. You need to consider every control and record your decision in the Statement of Applicability. Some controls are met through a dedicated policy or procedure, some through technical configuration, and some may be excluded with a justification. Document what is needed to operate the control consistently.
Can a toolkit alone get us certified?#
No. A toolkit helps you build documentation faster, but certification depends on a certification body finding that your ISMS is implemented and effective. Templates support that work but cannot replace risk assessment, management involvement, training, internal audit and real operation of the controls.
Can we use the same toolkit approach for other standards?#
Yes, the principle is similar for most management systems: start from structured templates, adapt them and operate the system. If you are also looking at AI governance, see ISO 42001:2023 Toolkit: What It Should Include and How to Use It. For payment environments, see What Documents You Need for PCI DSS 4 Implementation.
If you want to see how a structured template set could fit your ISMS project, review the ISO 27001:2022 Toolkit, or talk to the AdWiser team about your scope and next steps.
