ISO/IEC 27001:2022 Clause 7.5 outlines the documented information practices organisations may adopt to create, update, control, protect, and retain ISMS documentation. Documented information typically falls into two categories:
- Documents to Maintain – such as policies, procedures, and standards
- Records to Retain – including evidence like logs, reviews, and meeting minutes
Documented information includes all policies, procedures, and evidence that support the operation of an ISMS. For SMEs, applying Clause 7.5 practices can help keep documentation accurate, up to date, accessible to authorised staff, protected against loss or misuse, and retained for defined periods. These practices provide a framework for managing documented information consistent with ISO 27001 guidance.
Why Clause 7.5 Matters for SMEs
Small and growing organisations often manage their ISMS with limited staff and resources. Clause 7.5 outlines documentation and control practices that organisations may adopt to support ISO 27001 requirements. Clear document control can help reduce inconsistencies, assist staff in using the most current information, and support SMEs in reflecting ISO 27001 guidance and document control practices.
Applying these practices thoughtfully may provide a framework for organising documentation. For example, organising policies, procedures, and records and maintaining version control may provide clearer organisation of documents and records for SME teams.
What ISO 27001 Clause 7.5 Covers
ISO/IEC 27001:2022 Clause 7.5 is divided into three sub-clauses that describe how organisations may manage documented information. These practices apply to all ISMSs, including SMEs with lean teams.
Sub-clause 7.5.1 – General Requirements

Sub-clause 7.5.1 outlines practices for maintaining the documented information specified by ISO 27001 and retaining information that supports the effective operation of the ISMS. This can include:
- Policies (e.g. Access Control Policy)
- Procedures / SOPs (e.g. Incident Management Procedure)
- Records showing the activity occurred (e.g. access review evidence)
This sub-clause highlights the distinction between documents to maintain and records to retain, which can help SMEs manage documentation efficiently and support collection of relevant evidence.
Sub-clause 7.5.2 – Creating and Updating Documentation
Sub-clause 7.5.2 describes how organisations may create and update documented information. Documents can benefit from being:
- Identifiable (title, document ID)
- Assigned an owner
- Version-controlled
- Reviewed and approved
- Accessible to authorised staff
- Kept current
For SMEs, using templates and consistent metadata may reduce drafting time and support consistent document structures.
Sub-clause 7.5.3 – Controlling Documented Information
Sub-clause 7.5.3 outlines practices for controlling and protecting documented information throughout its lifecycle. Controls may include:
- Access – limiting viewing or editing to authorised roles
- Availability – making documents accessible when needed
- Protection – reducing the risk of loss, corruption, or unauthorised use
- Distribution – promoting use of the most current version
-
Retention and disposal – applying defined lifecycle rule
These practices may be used to apply ISO 27001 document control guidance within the ISMS.
What Counts as Documented Information in an ISMS?
Under ISO/IEC 27001:2022 Clause 7.5, all documented information in an ISMS generally falls into two categories:
- Documents to Maintain – controlled, versioned, and kept up to date.
-
Records to Retain – evidence retained to support ISMS processes and compliance activities.
|
Type of Documented Information |
Typical Action (per ISO 27001 Clause 7.5) |
Relevant Examples |
|
Documents to Maintain |
May be controlled, versioned, and updated regularly |
Information Security Policy, Access Control Policy, ISMS Manual, Statement of Applicability |
|
Records to Retain |
May be collected, stored, and retained to support ISMS activities |
Access review logs, incident logs, training records, risk assessment results, management review minutes |
Why Document Control Is Important for Audits
Certification auditors reviewing ISO 27001 Clause 7.5 often look for evidence that:
- Policies and procedures are current, approved, and version-controlled
- Staff are using the most up-to-date published versions
- Records and evidence logs are complete and traceable
- Retention and disposal practices align with the organisation’s policies
- Key ISMS records (e.g. risk assessments, SoA updates) correspond with reported ISMS activities
In practice, insufficient document control can contribute to audit non-conformities, while consistent management of documented information may help limit the likelihood of findings. Maintaining clear document control can also support smoother ISMS operations and improve transparency for SME teams.
Practical Guide for SMEs: Applying Clause 7.5

SMEs can apply ISO 27001 Clause 7.5 by standardising metadata, centralising a Document Register, using templates, and applying clear retention rules. Following these practices may describe a structured approach to organising documents, applying consistent processes, and managing documented information across systems.
1. Standardise Document Metadata
Use consistent fields across all ISMS documents:
- Document ID
- Version number
- Owner and approver
- Review date
- Classification
2. Maintain a Central Document Register
A central Document Register can help SMEs maintain control over ISMS documentation by:
- Tracking all ISMS documents, including external records
- Showing ownership, approval dates, and version history
- Linking back to the "Source of Truth" document
3. Use Simple Naming Conventions
Consistent naming improves clarity and searchability:
- Example: POL-AC-001 Access Control Policy
- Include prefixes for type (POL = policy, PROC = procedure, REC = record)
4. Apply a Clean, Logical Folder Structure

Organise documents in a clear structure:
ISMS/
00 – Framework & Scope
01 – Policies
02 – Procedures
03 – Records
04 – Risk Management
05 – Audits and Reviews
06 – Annex A Controls
5. Managing Documented Information Across Platforms
SMEs often store documents across multiple platforms (e.g. Google Drive, Jira, HR software). Sub-clause 7.5.3 focuses on control rather than central storage.
Practical Control Strategy:
|
Challenge |
Possible Solution |
|
Documents in multiple platforms |
Designate a "Source of Truth" location (e.g. SharePoint ISMS folder) |
|
Tracking external documents |
Use Document Register with direct links, owner, and approval date |
|
Preventing unapproved edits |
Apply "Read Only" rules for approved documents |
|
Draft version management |
Keep drafts separate until formally approved |
6. Apply Retention Periods
Define clear rules for how long ISMS records are retained and when they may be disposed of, taking into account audit cycles, contractual requirements, and internal policies. For example, some organisations may choose to retain key ISMS records for 2 – 3 years to support audit and review activities. Retention periods are typically documented and applied consistently as part of sub-clause 7.5.3 document control practices.
7. Use Templates to Support Consistency
Templates may help SMEs maintain consistent metadata, version control, and document structures, while reducing drafting and review effort.
Summary
By standardising metadata, centralising a Document Register, using consistent naming and folder structures, managing distributed documents, applying retention rules, and leveraging templates, SMEs can apply Clause 7.5 practices while keeping documentation organised and aligned with ISO 27001 requirements.
How Templates Can Support SMEs with ISO 27001 Clause 7.5
Using templates for documented information management may provide a structured approach to drafting and organising documents. Well-designed templates can:
- Help apply consistent metadata and version control
- Reduce the risk of missing fields or policy gaps
- Support more efficient drafting and review
- Assist in maintaining ISO 27001-aligned formatting
- Can be used to track retention in line with a central Records Retention Schedule
Clause 7.5 provides guidance to help maintain ISMS documentation that is organised, accessible, and controlled. For SMEs, understanding the distinction between documents to maintain (policies, procedures) and records to retain (logs, reviews, evidence) is important for efficient ISMS management and documentation practices.
Templates may provide a consistent approach to organising documents across teams, making it easier for SMEs to manage documents across multiple platforms, maintain traceability of ISMS activities, and track updates and approvals effectively.
Key Takeaways for SMEs on ISO 27001 Clause 7.5
ISO/IEC 27001:2022 Clause 7.5 provides guidance on managing documented information within an ISMS. For SMEs, understanding and applying this guidance may help maintain organised, accessible, and controlled documentation while supporting overall information security practices.
Key points to consider:
- Distinguish documents and records: Identify items as “documents to maintain” (policies, procedures) and “records to retain” (logs, reviews, evidence), which may provide a framework for organising documents and records.
- Standardise and centralise: Consistent metadata, naming conventions, and a central Document Register may help SMEs manage documents more efficiently.
- Apply control measures thoughtfully: Implement access, retention, and versioning practices suited to your team size and operational context, helping reduce confusion and maintain consistency.
- Leverage templates: Templates may support a consistent structure, reduce drafting effort, and help track document changes across multiple platforms.
By applying these practices thoughtfully, SMEs may maintain clearer documentation, support operational consistency, and may offer a framework for managing ISMS documentation. For additional guidance, SMEs may explore ISO 27001 template libraries or related resources to adapt these practices to their organisation’s needs.
Next Step: Using templates helps SMEs maintain well-organised, aligned documentation, enforce consistent metadata, and streamline document management across different platforms. To simplify your compliance journey and save time, explore our ISO 27001 template library and explore how these tools may provide guidance for organising ISMS documentation.
Next Article: Learn how to build a complete ISMS Manual with practical examples to simplify ISO 27001 implementation for SMEs: How to Build a Complete ISO 27001 ISMS Manual for SMEs.
Related Guides
Explore these ISO 27001 resources to help your SME build a practical, lean ISMS:
Start Here: Complete Guide
- ISO 27001 for SMEs and Startups: The Chill Implementation Guide (2026 Edition) – Full roadmap covering all clauses and Annex A controls, with practical steps, examples, and guidance.
B. Documentation and ISMS Templates – Detailed Guides by Topic
- ISO 27001 Mandatory Documents Checklist for SMEs – A practical guide to the essential ISMS documents small businesses typically prepare for ISO 27001 and streamlined audit preparation.
-
The 12 ISO 27001 Policies Commonly Adopted by SMEs and Startups – A concise guide to the core ISO 27001 policies small businesses often prepare to help organise and structure their ISMS.
- How to Build a Complete ISO 27001 ISMS Manual for SMEs – Step-by-step guide to assembling your main ISMS Manual, using templates and practical examples.
- ISO 27001 Templates vs Consultants vs Platforms – A practical guide to help SMEs choose between templates, consultants, and platforms for efficient ISO 27001 implementation.
Please Note: This article provides general information only and does not constitute legal, regulatory, or compliance advice. Using our products or following this guidance cannot guarantee certification, improved business outcomes, or regulatory compliance. Organisations remain responsible for ensuring all actions meet certification and compliance requirements.
This article also mentions examples of commonly used tools. Chill Compliance does not endorse any vendor and has no commercial or affiliate relationship with the providers listed. These examples are for general information only, and readers may wish to evaluate each tool independently, as features and pricing can vary.