Teams preparing for ISO/IEC 20000-1 often ask the same question first: how many documents do we actually need? The honest answer is that the standard does not give a fixed number. It requires documented information where it says so, plus whatever your organisation needs to run services consistently and to show that it does.
This article groups the documents into practical layers so you can plan the work, avoid padding, and be ready for a certification audit conversation.
How ISO 20000-1 treats documentation#
The current version of the standard uses the term "documented information". That covers both documents (policies, plans, procedures) and records (evidence that something happened). Auditors will look for both.
Two principles help when scoping the effort:
- Document what the standard explicitly requires. Read each requirement and note where it says information must be documented, retained or available.
- Add only what your organisation needs. Size, service complexity and staff competence all affect how much detail is sensible. A process three people follow daily may need a one-page workflow, not a 20-page procedure.
Documentation should describe how you really work. If an auditor follows a ticket through your tool and the procedure says something different, the document is the problem.
Core service management system documents#
These sit at the top of the system and set direction. Expect to produce most of them early in the project.
- Scope of the service management system (SMS). Which services, locations, teams and customers are covered, and any exclusions with the reasons.
- Service management policy. Approved by top management and communicated to the people who need to know it.
- Service management objectives. Measurable goals aligned with the policy and with customer requirements.
- Service management plan. How you will deliver the objectives: resources, responsibilities, timelines, tools and the approach to managing services.
- Context and interested parties. A record of internal and external issues, and the requirements of customers, users and suppliers.
- Risk and opportunity register. Risks to the SMS and to services, with planned actions.
- Roles and responsibilities. Who owns each process and who has authority to act.
Service and process documentation#
This layer is where most of the day-to-day effort goes. The standard covers service delivery, relationship management, supply, resolution, control and design and transition processes. You need to show each is defined, applied and effective.
| Area | Typical documents |
|---|---|
| Service catalogue and agreements | Service catalogue, service level agreements, service requirements, agreements with customers |
| Incident and service request management | Procedure, priority and categorisation rules, escalation paths, knowledge articles |
| Problem management | Procedure, problem records, known error records |
| Change management | Change policy, change categories, approval rules, change schedule, change records |
| Release and deployment | Release policy and plans, deployment records, test and acceptance evidence |
| Service design and transition | Requirements, design documents, transition plans for new or changed services |
| Configuration and asset management | Configuration management approach, configuration records, asset information |
| Capacity and availability | Capacity plan, availability plan, monitoring and review records |
| Service continuity | Continuity and availability plans, test results, review records |
| Information security | Information security policy, controls for service-related risks, incident handling links |
| Supplier and relationship management | Supplier list, contracts, documented agreements with internal groups or other parties that contribute to services, performance reviews |
| Budgeting and demand | Budgeting and accounting approach, demand management records where relevant |
Not every row needs a stand-alone document. Several processes can share one template or one page, provided the content is clear and an auditor can find it.
Records that prove the system works#
Documents describe intent. Records show operation. Many first-time audit findings come from missing or inconsistent records, not missing policies.
- Competence and awareness. Role descriptions, training records, and evidence that staff know the policy and their part in it.
- Service performance. Reports against SLAs and objectives, with evidence that someone reviews them and acts.
- Customer feedback. Satisfaction surveys, complaint records and how they were resolved.
- Operational records. Incident, request, problem and change records from your service management tool, plus review of major incidents.
- Monitoring and measurement. What you measure, how often, and what you did with the results.
- Internal audit. Audit programme, criteria, reports, and follow-up of findings.
- Management review. Agenda, inputs, minutes, decisions and actions.
- Nonconformities and improvements. Corrective actions, root causes and the improvement register.
Check the retention period for each record type and make sure your tool does not purge data sooner than you intend.
A practical way to build the document set#
- Map your services and processes first. List the services in scope, who delivers them and which tools they use. This shows which documents already exist informally.
- Run a gap review against the standard. For each requirement, note whether you have a document, a record, or neither.
- Draft top-level documents. Scope, policy, objectives and plan come first because other documents refer to them.
- Standardise templates. Use consistent headers, version control, owners and approval fields across all documents.
- Write process documents with the people who run them. Service desk, change and infrastructure staff should review drafts so the text matches practice.
- Operate before you audit. Give the system enough time to generate records. Run an internal audit and a management review before the certification audit.
If you also manage information security under ISO 27001, many policies and controls overlap. Our article on what an ISO 27001 toolkit should include shows how to structure that side of the document set.
Frequently asked questions#
Does ISO 20000-1 require documented procedures for every process?#
The standard asks for documented information in specific places and leaves the rest to the organisation. You still need to be able to show that processes are defined, understood and followed, but this can be done with short procedures, workflows or tool configurations as long as they are controlled and accurate.
Can we use our ITSM tool as documentation?#
Yes, in part. Ticket workflows, categories, approval rules and reports can serve as evidence and sometimes as the process definition itself. You should still control versions, assign owners and make sure people can find the guidance they need.
How do ISO 20000-1 documents differ from ISO 27001 documents?#
ISO 20000-1 focuses on how services are designed, delivered and improved, while ISO 27001 focuses on information security risk and controls. Both share management system elements such as policy, objectives, internal audit and management review, so organisations can often combine those parts in an integrated system.
If you would rather start from a structured set than a blank page, the ISO 20000 Toolkit is a ready-to-use documentation toolkit you can adapt to your own services and processes.
