A procedure may be written correctly; if an old version is used in practice, that means nothing. If there’s no approval record, or three different copies of the same document are circulating, the auditor writes it up as a lack of control. Document control is one of the least conspicuous topics in an ISMS but one of those that produce the most findings. Below we turn the requirements of ISO/IEC 27001:2022 Clause 7.5 into rules for numbering, versions, approval, distribution and archiving. To keep approval, version and publication records digitally, you can set up the document flow through SharePoint document and revision management.
Why is document control a source of findings?
Clause 7.5.2 requires that, when documented information is created and updated, appropriate identification (such as title, date, author or reference number), format and media are ensured, and that it is reviewed and approved for suitability and adequacy. Clause 7.5.3 expects documented information to be available and suitable for use where and when needed and adequately protected, and requires distribution, access, retrieval, storage, change control, retention and disposal activities to be addressed. The standard doesn’t say how to do these things. The method is the organization’s.
Pictures you may come across in audits:
- Several versions on the file server with names like “Backup_Procedure_final_v3_current.docx”.
- The approver’s name written on the document, but no trace of when and how approval was given.
- The policy’s effective date being older than the procedure it refers to.
- Employees using an old PDF that arrived by email instead of the version on the intranet.
- Not knowing which version of the external documents the organization relies on (standards, customer requirements, manufacturer manuals) is current.
They all share the same root: documents aren’t managed from a single source of truth. The rules below define that source.
Numbering and version scheme
The purpose of numbering is to give every document a unique and permanent identity. The document name can change. The number doesn’t. A simple, common structure consists of the system abbreviation, document type and sequence number:
Format: <SYSTEM>-<TYPE>-<SEQ>
Types : POL (policy), PRC (procedure), WI (work instruction),
FRM (form/template), LST (list), PLN (plan)
Examples:
ISMS-POL-001 Information Security Policy
ISMS-PRC-007 User Account Lifecycle Procedure
ISMS-WI-007-02 Entra ID Account Disabling Work Instruction
ISMS-FRM-012 Restore Test Form
Link work instructions to the number of the procedure they belong to (like WI-007-02); impact analysis gets easier, and when a procedure changes, which instructions need review can be read from the number. Don’t put a department code in the number. The day the organization changes, the numbers lose their meaning, and either everyone carries on living with old codes or a chaotic mass renumbering begins.
A two-level structure is enough for the version scheme:
| Version | Meaning | Approval needed? |
|---|---|---|
| 0.1, 0.2 … | Draft, not in effect | No |
| 1.0 | First approved publication | Yes |
| 1.1, 1.2 … | Correction that doesn’t change the meaning (spelling, link, role name) | Process owner approval |
| 2.0, 3.0 … | Revision that changes scope, responsibilities or rules | Full approval flow |
Define the distinction between minor and major revisions in writing in the document. Without a definition, every change is marked “minor” and the approval flow is effectively switched off. We see this a lot in the field.
Preparation, review and approval flow
The approval flow has three roles: the author (who writes the content, usually a process specialist), the reviewer (who checks accuracy and consistency with other documents, usually the ISMS owner) and the approver (the process owner or top management depending on the document’s authority level). In small organizations, the same person writing and approving may be unavoidable; in that case at least give the review step to a different person.
- The author opens the draft in the document repository with a 0.x version and writes a change summary.
- The reviewer checks for conflicting documents, role names, record references and classification, and leaves comments on the draft.
- The approver approves the document; the approval date and identity leave a trace in the system (workflow record, electronic signature or archive of the approval email).
- The ISMS owner publishes the version, enters the effective date, updates the master list and moves the previous version to the archive.
- The affected roles are notified of the change; if needed, a short briefing or training record is created.
An electronic document management system runs these steps while leaving an automatic trail. For example, in SharePoint document libraries, major and minor version tracking can be used together with content approval; by showing minor versions only to those with edit rights, you prevent drafts being used by mistake. For the setup on the evidence side, see the article evidence management with SharePoint.
Distribution, access and managing obsolete documents
The basic rule of distribution fits in one sentence: the current version is published in only one place, and everywhere else links to that source. Distributing a document as an email attachment is the fastest way to produce uncontrolled copies. Every attached file is a copy.
- Separate read and edit permissions. “Access” in Clause 7.5.3 can mean permission to view only, or to view and change. Only the ISMS owner and the document owner should be able to change a published document.
- Reflect classification in distribution. An “internal” procedure can be open to everyone on the intranet; a “confidential” network topology instruction is opened only to the relevant team.
- Mark printed copies. For printed instructions used in the field, the wording “Printed copy is uncontrolled; verify the current version in the repository” is added to the template; if a controlled printed copy is needed, a distribution list is kept.
- Separate obsolete versions. A version that goes out of force isn’t deleted; it’s kept readable but in an archive separate from the publication area, marked “Obsolete”. A past incident is assessed against the rule valid at that date; you need to have that rule.
How long archived documents are kept is set together with the record retention rules; details are in the article records list and retention periods.
Controlling documents of external origin
Clause 7.5.3 requires documented information of external origin that is deemed necessary for planning and operating the ISMS to also be identified and controlled. A document of external origin is one the organization didn’t write but must comply with or use: standards, legal texts, customer information security requirements, contract annexes, manufacturer security guides.
You can’t change the content of these documents. But you can define which version is current, who tracks it and how often its currency is checked. A practical method is to open extra fields in the master list for the “external” type: source organization, publication date or version, where it’s accessed, the role responsible for tracking and the last check date. Copyright-restricted standard texts aren’t placed in general sharing areas; under the license terms they’re opened only to authorized people.
Sample master document list fields
ISO/IEC 27001 doesn’t require anything called a “master list”. Still, it’s the most practical tool for identifying documents and tracking their version and approval status. Nor does the list have to be kept by hand; it can be produced from the electronic document system’s metadata.
| Field | Explanation | Example |
|---|---|---|
| Document no. | Permanent, unique identity | ISMS-PRC-007 |
| Item | Current document name | User Account Lifecycle |
| Type / origin | Internal or external, document type | Internal / Procedure |
| Version | Version in force | 2.1 |
| Effective date | Start of validity of the approved version | Day.Month.Year |
| Owner | Role responsible for the content | IT Infrastructure Manager |
| Approver | Role with approval authority | IT Director |
| Classification | Access level | Internal |
| Next review | Planned date | Day.Month.Year |
| Related control | Annex A or other framework mapping | 5.16, 5.18 |
The “related control” field builds traceability between the SoA and the document set. When the auditor asks which document meets a control, the answer comes straight from the list; there’s no searching folder by folder.
Periodic review schedule
Annex A 5.1 requires information security policies to be reviewed at planned intervals and when significant changes occur. In practice this rule is applied to the whole document set. But trying to review all documents in the same month creates a pile-up, and the review turns into signing. Spread the schedule across the year and define two types of trigger:
- Calendar trigger: usually yearly for policies and procedures; more often for fast-changing instructions. The frequency is the organization’s own decision and is written in the document control procedure.
- Event trigger: an organizational change, a new system or system change, a post-incident review, an audit finding, a risk assessment result, a new version of an external document.
Even if a review requires no change, the decision is recorded; a “reviewed, no change” note and date are entered in the revision history or master list. Without the note, the auditor can’t verify whether a document unchanged for years was reviewed.
Setup checklist
- The document control procedure is written; numbering, version and approval rules are defined.
- A single document repository is designated; publication and draft areas are separated.
- Read and edit permissions are assigned by role.
- The master list is created; documents of external origin are on it too.
- An archive area and retention period are set for obsolete versions.
- The review schedule is spread across the year and owners are assigned.
The step that takes the most effort is usually moving existing files into this structure. Before moving them, decide which documents are really needed; for that you can use the ISO 27001 document set article, and for writing rules the guide to writing procedures and work instructions. Preparing and structuring the document set as a whole is part of our ISO 27001 documentation preparation work. For the official text of Clause 7.5, the ISO/IEC 27001 page should be the reference.
Frequently asked questions
Does ISO 27001 make keeping a master document list mandatory?
No, the standard doesn’t require a document called a “master list”. However, Clause 7.5 requires documents to be identified and their versions and changes to be controlled; a master list, or an equivalent report produced from the document management system, is the most practical way to show this.
Should old versions that become obsolete be deleted?
No. The old version is removed from the publication area and kept in a separate archive marked “Obsolete”. Since a past incident or decision is assessed against the rule valid at that date, these versions must be accessible for a certain period.
Should the approval flow be run even for a small typo fix?
A shortened flow can be defined for corrections that don’t change the meaning; for example approval by the process owner only and an intermediate version number. The criterion for this distinction must be written in the document control procedure.
How is a review evidenced when no change is needed?
The review date, the reviewing role and the “no change needed” decision are recorded in the revision history or the master list. Without this record, it can’t be verified that a document unchanged for a long time was reviewed.