ISO 27001 document control: a ready setup for spaces, tags, templates and workflows
A ready-to-use setup for ISO 27001 document control: three spaces, sections in clause order, tags for Annex A, nine templates and the review workflows.

ISO 27001 document control means every policy, procedure and record of your information security management system (ISMS) is identified, reviewed, approved, available to the right people, protected and kept with a version history, as clause 7.5 of ISO/IEC 27001 asks. The simplest way to get there is to decide the structure before writing the first document.
This page gives that structure, step by step, ready to copy: where each kind of document lives, how it is tagged, which template it follows, and who reviews and approves it. It is the setup we would use if we started our own certification today. We run our certified ISMS in Elium, so each step shows how it works there. The structure itself works in any knowledge platform or document system with owners, review dates, approval and access rights. If you are still deciding what to document, start with our guide to ISO 27001 documentation.

Why the structure comes first
Most documentation problems that auditors find are about upkeep: a policy nobody owns, a review that never happened, a record that someone "updated" afterwards, a Statement of Applicability that points to nothing. A structure decided on the first day prevents most of them, because the rules are part of it: every new document gets an owner, a review date and an approver automatically.
Two distinctions shape everything below.
- Documents and records need different rules. A policy changes and must be reviewed; an audit report is evidence of a moment and must never change. Since the 2022 edition, the clauses about records ask for information to be available as evidence, so an auditor will ask to see the records themselves.
- Readers and owners need different access. Everyone must read the security policy. Few people should read the risk register or the incident reports.
Step 1: separate rules, evidence and suppliers
Use three areas, each with its own readers and its own rules.
| Area | Who can read it | What it holds | Rules |
|---|---|---|---|
| Information Security | All staff. Owners and the security manager write | Overview, clause documents, policies, procedures, Statement of Applicability, awareness | Approval required; review every 12 months |
| Security Records | The security committee, and auditors during the audit | Management reviews, internal audits, risk assessments, incidents, tests, corrective actions | No review date: records are evidence and do not expire |
| Suppliers and Services | The security manager, IT, purchasing | One description per supplier or service | Review every 12 months, less often for low-risk suppliers |
In Elium: each area is a space. Information Security is a moderated space open to all staff; the other two are private spaces. Set the default review period of each space in its settings, so every new article gets a review date. See review dates and types of spaces.
Step 2: order the sections like the standard
Auditors read the standard from clause 4 to clause 10. Put the sections of your main area in the same order.
- Start here
- Context and scope (clause 4)
- Leadership and policies (clause 5)
- Planning: risk method, Statement of Applicability, objectives (clause 6)
- Support: competence, awareness, communication, document control (clause 7)
- Operation: procedures (clause 8)
- Performance: indicators, internal audit programme (clause 9)
- Improvement: nonconformities and corrective actions (clause 10)
- Annex A, in four sections: Organisational, People, Physical, Technological
"Start here" holds one document: an overview that explains each clause in a few lines and links to the document that governs it. It is what a newcomer reads first and the map an auditor follows. Its core is a short table:
| Clause | Governing document | Owner | Next review |
|---|---|---|---|
| 4 Context | Scope of the ISMS | Security manager | March |
| 5 Leadership | Information security policy | Management | January |
| 6 Planning | Risk assessment method; Statement of Applicability | Security manager | April |
| 7 Support | Document control procedure | Security manager | June |
| 8 Operation | Operational planning | IT lead | May |
| 9 Performance | Internal audit programme | Security manager | September |
| 10 Improvement | Corrective action procedure | Security manager | October |
In Elium: add a tab for each document type (Policies, Procedures, Guidelines). Then save a search on the space with the Expired and Verified statuses, sorted by expiration date. Expired documents come first, then the ones that expire soonest. This is your "due for review" list.
Step 3: tag every document the same way
Tags turn a list of documents into a register you can filter. Create these tag categories. Make the first three mandatory in all three areas: records and supplier descriptions need a document type and their Annex A controls too. Let only administrators change the values, so the lists stay clean.
| Category | Values | What it gives you |
|---|---|---|
| Document type | Policy, Procedure, Guideline, Plan, Register, Record | Tabs, filters and a clean document register |
| Annex A control | A5.1 to A8.34 (93 values) | Pick a control and see every document behind it |
| Classification | Public, Internal, Confidential, Restricted | How each document must be handled |
| ISO 27001 clause | 4 to 10 | A second way to follow the standard |
| Audience | All staff, Engineering, Operations, Management | Who to invite when a document changes |
The Annex A tag is the most useful at audit time. Filter on one control and you see its policy, its procedure and the records that prove it works, in one view. It is the closest thing to a live Statement of Applicability. See tag categories in Elium.

Step 4: use ISO 27001 policy templates, and one template per kind of document
Templates give every document of a kind the same fields and headings, so readers know where to look and filters work.
| Template | Structured fields | Headings in the body |
|---|---|---|
| Policy | Owner, Approver, Applies to, Effective date, Change summary | Purpose, Scope, Policy statements, Responsibilities, Exceptions, Related documents |
| Procedure | Owner, Related policy, Records produced | Purpose, Roles, Steps, Records, Related documents |
| Supplier or service | Provider, Service, Data processed, Hosting location, Certifications, Criticality, Contract link | What it does, Data and access, Security assurance, Exit plan |
| Risk assessment | Asset or process, Likelihood, Impact, Risk owner, Treatment, Linked controls | Context, Threats, Analysis, Treatment plan |
| Management review | Date, Participants | Actions from last time, Changes, Performance, Audit results, Objectives, Risks, Improvements, Decisions |
| Internal audit | Period, Auditor, Clauses and controls covered | Scope, Method, Findings, Nonconformities, Improvements |
| Incident | Date, Severity, Status | What happened, Impact, Root cause, Actions, Lessons |
| Test report | Date, Type (recovery, penetration, restore), Result | Scope, Results, Actions |
| Change report | Date, Change, Risk level | What changed, Risk assessment, Approval, Outcome |
The risk assessment template gives every assessment the same likelihood and impact fields. A risk method without defined scales is one of the problems certification bodies report most often.
Two fields on the policy template need a short explanation. The change summary says, in one line, what changed in this version and why. A version history shows what changed, not why, so the field records the reason. The approver names who must approve; the version history then shows who actually did.
In Elium: create the templates in the template builder and limit each one to its space. See templates.

Step 5: set the workflows
Writing and approving
- Every change to a published document starts as a draft. Readers keep the approved version until the new one is published.
- Policies need approval before they are published. For the top-level security policy, ask two approvers in order: the security manager, then management. For procedures, the security manager is enough.
- When you publish, decide who is told: nobody for a typo, everyone concerned for a rule that changes how people work.
In Elium: make approval mandatory in the Information Security space, and request approval with approvers in order for the top-level policy. See approval.

Keeping documents current
- Every document has one owner, who is reminded before the review date.
- Once a month, the security manager checks the "due for review" list: every document past its review date or close to it, the most overdue first.
- When someone leaves, their documents move to a named successor the same day.
In Elium: when the review date is close, the owner gets a task and an "Expiring Contents" notification; after the date, the document shows a red badge. Content transfer moves a leaver's articles to a successor.

Proving people know the rules
- When a policy is new or changes, ask its audience to read it.
- For rules everyone must follow, ask people to confirm they have read them, and keep the list of who confirmed. The European Union Agency for Cybersecurity (ENISA) lists staff acknowledgements among the evidence for the security policy under the NIS2 directive.
- New colleagues read the policy set in their first week.
In Elium: invite the audience to read the article. For confirmations, a platform administrator sends the article as an urgent notification, which stays on screen until each person clicks "Mark as read". Each article's analytics show who opened it.

Running the management system
- Write each management review in Security Records, using the management review template. Use the expired documents and the open approvals as inputs.
- Log each nonconformity and improvement as its own record, with an owner.
- Once a year, export the list of users and the members of each area, check who has access, and file the result as a record.
At audit time
- Give the auditor read access to the documents and the records they sample, only for the duration of the audit.
- Export your document register: titles, document types, owners and Annex A controls, plus the list of overdue documents.
- Before Stage 1 of a first certification, make sure an internal audit and a management review have already taken place and are on record. Certification bodies check both.
In Elium: give the auditor a guest account or access to specific articles, and export the results of a search on the document spaces (titles, tags and template fields). An assistant limited to the Information Security space can answer staff questions from the approved policies. See smart assistants.
Step 6: write the first documents
Start with what the standard requires, then the Annex A policies most organisations need. Documents the standard requires are marked with an asterisk.
| Section | Documents |
|---|---|
| Start here | ISMS overview |
| Context and scope | Scope of the ISMS*, context and interested parties |
| Leadership and policies | Information security policy*, roles and responsibilities |
| Planning | Risk assessment and treatment method*, Statement of Applicability*, security objectives*, planning of changes |
| Support | Competence, awareness programme, communication, document control |
| Performance | Indicators and how they are measured*, internal audit programme* |
| Improvement | Nonconformity and corrective action procedure |
| Annex A | Acceptable use, access control, supplier security, incident management, business continuity, backup, change management, secure development, asset inventory, cryptography, logging and monitoring, vulnerability management, remote working, legal and contractual requirements |
| Security Records | Risk assessment results*, risk treatment plan*, internal audit reports*, management review minutes*, nonconformities and corrective actions* |
ISO 27001 documentation explains what each required document must contain and how auditors check it.
Step 7: connect your AI assistant
If your staff use an AI assistant such as Claude, ChatGPT or Microsoft Copilot, connect it to your documentation once the structure is in place. Each group then gets something different from it.
| Who | What they ask the assistant | What stays with a person |
|---|---|---|
| The security manager | "Move these policies into the Policy template and suggest their Annex A tags." "Which controls in our Statement of Applicability have no document, or one past its review date?" | Checking each draft, and deciding which controls apply |
| Document owners | "Compare the remote working policy with the access control policy and prepare the changes as a draft." | The review, then the approval |
| All staff | "Can I use my own phone for work email?" | Reading the policies everyone must follow, and confirming it |
Keep five rules, whatever tools you use:
- Same access rights. The assistant works with the rights of the person asking. A record that someone cannot open must never appear in an answer to them.
- Drafts, then approval. What the assistant writes is a draft. It follows the same review and approval as any other change (step 5).
- The assistant is a supplier. Give it its own description in Suppliers and Services: provider, data processed, hosting, and whether your documents are used to train its models. The certification body DQS expects AI suppliers to be covered by supplier management.
- An answer is not an acknowledgement. Keep recording that people read the policy itself.
- One source for every assistant. If teams use different assistants, for example Claude in IT and Copilot everywhere else, connect each one to the same areas. Access rights and approval stay the same, whichever assistant is asked.

In Elium: assistants connect through the Model Context Protocol (MCP), an open standard that Claude, ChatGPT and Microsoft Copilot Studio support. The assistant acts with the permissions of the person who connected it. It reads each article with its owner, review date and approval status, so it can tell when a policy is overdue. Writing is off by default and is enabled for each platform. Once enabled, the assistant creates articles from Markdown with your templates, fields and tags, and saves its changes to existing articles as drafts: it never publishes them, and the approval rules of the space still apply. Administrators see every connected assistant in one list and can limit or remove it. See about MCP, create and update articles and manage MCP apps.
Two ways to write, one approval. IT teams often prefer plain text: they write Markdown, or let their assistant draft it. Quality, HR and operations staff prefer an editor. Both can work on the same documents. Whichever way a change is written, it becomes a draft and goes through the same approval, so the auditor sees one process. In Elium, Markdown comes in through import or an assistant, and everyone else uses the editor.
Let your assistant apply this setup
An administrator's assistant can do the repetitive parts of this page. First create by hand the three spaces and their sections (steps 1 and 2), the templates (step 4) and the review and approval rules (step 5): an assistant cannot create these. Then ask it for the rest:
Read https://elium.com/resources/iso-27001-document-control-setup
Then, in our Elium platform:
1. Create the five tag categories of step 3. Make Document type, Annex A
control and Classification mandatory in the three security spaces,
and let only administrators add tags.
2. Create the tags of each category, including one tag for each of the
93 Annex A controls of ISO/IEC 27001:2022 (number and title).
3. Create each document of step 6 as a draft in its section, with the
matching template. Leave the text for the owner to write.
Show me the full list before you create anything.
Move the documentation you already have
Many IT teams start their ISMS as Markdown files, often in a Git repository. To move it, give the assistant the files, map each one to a section and a template, create them as drafts, and send each one through approval. Then name one place as the reference and stop editing the other, so nobody updates a copy that is no longer read. Keep the Git history as the record of how the documents were first drafted. Word files and PDFs move the same way.
In Elium: Elium imports Markdown, including for migrations in bulk, and a connected assistant creates articles from Markdown with their template, fields and tags. See Markdown input format.
What we see in practice
ISMS documentation is usually kept in one of two places: shared folders, where nobody knows which policy is current and which is last year's copy, or a compliance tool that only the security team opens. The rules are only useful if people read them, and the evidence is only useful if an auditor can follow it.
Our own ISMS has run in Elium since our first certification in 2022. In our April 2026 surveillance audit, our certification body noted that view tracking, approval workflows and change history support the control of our documented information. We describe how we run it in a separate article, including what we would do differently: that is the setup on this page. If you want this setup on your Elium platform without building every part by hand, step 7 shows how an assistant applies the tags and the first documents.
Start with IT, then extend
Most organisations start where the deadline is: the information security team, in the Information Security area. Once owners, review dates and approval work there, extend the same rules to the quality and environmental systems. ISO 9001 and ISO 14001 share the structure of ISO/IEC 27001, including clause 7.5 on documented information, so one set of rules for owners, reviews, approval and retention serves all three. Our guide to ISO 9001:2026 and organisational knowledge covers the quality side.
Where to start
Take one afternoon. Create the three areas, set their default review periods, and create the Document type and Annex A tags. Then add your information security policy: give it an owner, an approver and a review date, and ask everyone to confirm they have read it. That one document already shows an auditor the whole cycle.
Common questions
An ISO 27001 document management system should give every document a named owner, a review date with a reminder, approval before publication, a version history, access rights per area, and a record of who read the policies everyone must follow. It should also let you tag each document with its Annex A controls, so you can show an auditor the evidence behind a control in one view. Records need different rules: no review date, but an access rule and a retention period.
A practical structure separates three areas: the documents everyone follows (policies and procedures, in clause order), the records only a few people need (reviews, audits, incidents, tests), and supplier descriptions. Each area gets its own readers and review rule, and every document carries a document type and its Annex A controls as tags.
Setting up ISO 27001 document control takes an afternoon to a day for the structure: the three areas, their review periods, the tags and the templates. Writing and approving the documents takes longer, from weeks to months depending on what already exists. Plan backwards from the certification audit: the internal audit and the first management review must already have taken place before it starts, so their records need a home from the beginning.
An ISO 27001 policy template should contain structured fields for the owner, the approver, who the policy applies to, the effective date and a summary of the last change, followed by fixed headings: purpose, scope, policy statements, responsibilities, exceptions and related documents. Step 4 above gives this template and eight others, one for each kind of document.
To move ISO 27001 documentation from SharePoint or a Git repository, set up the new structure first, then map each existing file to its area, section and template, and bring it in as a draft that goes through approval. When everything has moved, name the new system as the reference and stop editing the old copies, so nobody updates a version that is no longer read. Keep the old version history as a record of the earlier drafts. An AI assistant connected to both sides can do most of the mapping.
You prove employees have read the security policy by asking them to confirm they have read it and keeping the list of who did, for example through a read confirmation in your knowledge platform or a signed acknowledgement. ENISA lists staff acknowledgements as evidence for the security policy under NIS2.
You can use Claude or Copilot to manage ISO 27001 documentation if you connect them to the system that holds it: they can move policies into templates, prepare changes on review day, find controls with no document behind them, and answer staff questions from the approved policies. A person still reviews and approves every change, and each assistant must only see what the person asking may see. Step 7 above gives the rules.
Sources
Show the 7 sources
- International Accreditation Forum, IAF MD 26:2023, Transition requirements for ISO/IEC 27001:2022, 2023. Checked 22 October 2026.
- ENISA, Technical implementation guidance on Implementing Regulation (EU) 2024/2690, 2025. Checked 22 October 2026.
- TÜV NORD CERT, Description of the certification procedure, ISO 27001, 2022. Checked 22 October 2026.
- DNV, Insights from auditing information security management systems. Checked 22 October 2026.
- ISO Joint Technical Coordination Group, Exploring management system standards. Checked 17 November 2026.
- ISO/TC 46/SC 11, Explanatory document on "documented information", 2015. Checked 17 November 2026.
- DQS, AI and ISO 27001: what businesses should know and what auditors will look for, 2026. Checked 17 November 2026.
Data and sources
This setup comes from how we run our own certified ISMS, plus the changes we would make, checked against public guidance from the International Accreditation Forum (IAF), ENISA and certification bodies. Clause numbers are given so you can check each point against your own copy of the standard. The example screens are invented content.