Framework · IT service management · Certifiable

ISO/IEC 20000-1 IT service management: processes and certification

ISO/IEC 20000-1 is the international standard for a service management system (SMS). The 2018 edition, with Amendment 1:2024 on climate change, sets requirements for planning, delivering and improving services, including incident, change, service level and supplier management. Accredited certification bodies audit it in two stages.

Key takeaways

What you need to know about ISO 20000-1

Certifiable ITSMThe certifiable standard behind IT service management practice.
Process-basedClause 8 sets requirements for each service management process.
Works with ITILITIL practices help you meet the requirements.
Evidence from ticketsIncidents, changes and requests in your ITSM tool are the evidence.
OverlapStrong links to ISO 27001, 22301 and 9001.

Who needs ISO 20000-1?

It is voluntary, but common for service providers.

Managed service providersClients want proof services are run consistently.
IT outsourcing and BPOContracts and tenders often require it.
Internal IT departmentsA recognised benchmark for service quality.
Data centre and cloud operatorsService management alongside ISO 27001.
Public-sector IT suppliersTenders score ITSM certification.

QULDEX helps here first: the readiness check shows where you stand before you commit budget.

Clauses 4–10

What does ISO 20000-1 require?

ISO 20000-1 requires a service management system: plan services, manage relationships and agreements, supply and demand, design and transition, resolution and fulfilment, and service assurance, then measure and improve.

8.2 Portfolio

Service portfolio

Delivery, planning, catalogue, assets, configuration.

In QULDEX: Catalogue and CMDB linked
8.3 Agreements

Relationship and agreement

Business relationships, service levels, suppliers.

In QULDEX: SLA reports each period
8.4 Supply

Supply and demand

Budgeting, demand and capacity.

In QULDEX: Capacity plans tracked
8.5 Change

Design, build and transition

Change, design and transition, release and deployment.

In QULDEX: Change tickets sampled
8.6 Resolve

Resolution and fulfilment

Incidents, service requests, problems.

In QULDEX: Incident and problem evidence
8.7 Assure

Service assurance

Availability, continuity, information security.

In QULDEX: Reused from ISO 27001 and 22301
4–7, 9–10 SMS

Management system

Context, leadership, planning, support, evaluation, improvement.

In QULDEX: Shared with other ISO systems
Process explorer

What are the ISO 20000-1 service management processes?

Clause 8 of ISO/IEC 20000-1 sets requirements for each service management process, grouped into six areas; clauses 4 to 10 cover the management system itself. Select any process to see what it asks for and typical evidence.

2018current edition
6clause 8 process areas
22processes in clause 8
Amd 1:2024climate change added

Showing up to 6 per group. Search, filter, or open a group to see all 28.

Management system 6

  1. 4Context of the organisation

    Understand context, interested parties and the scope of the SMS.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Scope statement

  2. 5Leadership

    Top management commits to the SMS, sets the service management policy and assigns roles.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Service management policy

  3. 6Planning

    Address risks and opportunities, set objectives and plan the SMS.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Risk register, SMS plan

  4. 7Support of the SMS

    Resources, competence, awareness, communication, documented information and knowledge.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Training records, document control

  5. 9Performance evaluation

    Monitoring, internal audit, management review and service reporting.

    In QULDEXService reports generated from live data.

    Typical evidence
    Service reports, audit reports

  6. 10Improvement

    Nonconformity, corrective action and continual improvement.

    In QULDEXFindings flow into CAPA.

    Typical evidence
    CAPA records

Service portfolio 7

  1. 8.1Operational planning and control

    Plan and control the processes needed to deliver services.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

  2. 8.2.1Service delivery

    Deliver services in line with the SMS.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

  3. 8.2.2Plan the services

    Plan services against requirements and capability.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

  4. 8.2.3Control of parties involved in the service lifecycle

    Keep accountability when other parties run parts of the service lifecycle.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Party responsibilities

  5. 8.2.4Service catalogue management

    Maintain a service catalogue.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Service catalogue

  6. 8.2.5Asset management

    Manage assets used to deliver services.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Asset register
    Maps to
    ISO 27001 A.5.9

  7. 8.2.6Configuration management

    Record and control configuration items.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    CMDB extracts

Relationship and agreement 3

  1. 8.3.2Business relationship management

    Build relationships with customers and measure satisfaction.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Customer reviews, satisfaction results

  2. 8.3.3Service level management

    Agree, monitor and report service levels.

    In QULDEXSLA reports collected each period.

    Typical evidence
    SLAs, SLA reports

  3. 8.3.4Supplier management

    Manage external suppliers and internal suppliers acting as suppliers.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Supplier contracts and reviews
    Maps to
    ISO 27001 A.5.19

Supply and demand 3

  1. 8.4.1Budgeting and accounting for services

    Budget and account for service costs.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

  2. 8.4.2Demand management

    Understand and forecast demand for services.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

  3. 8.4.3Capacity management

    Plan and provide enough capacity to meet agreed requirements.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Capacity plans
    Maps to
    ISO 27001 A.8.6

Design, build and transition 3

  1. 8.5.1Change management

    Assess, approve and implement changes in a controlled way.

    In QULDEXChange tickets are sampled directly from your ITSM tool.

    Typical evidence
    Change records
    Maps to
    ISO 27001 A.8.32

  2. 8.5.2Service design and transition

    Design new or changed services and move them into operation.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Design and transition plans

  3. 8.5.3Release and deployment management

    Plan, build, test and deploy releases.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Release records

Resolution and fulfilment 3

  1. 8.6.1Incident management

    Restore normal service as quickly as possible.

    In QULDEXIncident tickets and resolution times linked as evidence.

    Typical evidence
    Incident records
    Maps to
    ISO 27001 A.5.26

  2. 8.6.2Service request management

    Fulfil service requests to agreed timescales.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Request records

  3. 8.6.3Problem management

    Find and remove root causes of incidents.

    In QULDEXProblems with root cause tracked to closure.

    Typical evidence
    Problem records

Service assurance 3

  1. 8.7.1Service availability management

    Meet agreed availability requirements.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Availability reports

  2. 8.7.2Service continuity management

    Keep services running during disruption.

    In QULDEXQULDEX gives this process an owner, KPIs and an evidence request, and links ITSM tickets as evidence.

    Typical evidence
    Continuity plans and tests
    Maps to
    ISO 22301

  3. 8.7.3Information security management

    Manage information security risks to services.

    In QULDEXSecurity controls reused from ISO 27001 when you run one.

    Typical evidence
    Security policy and controls
    Maps to
    ISO 27001

Clause numbers and titles follow ISO/IEC 20000-1:2018. Summaries are QULDEX paraphrases; the standard's text is the authority.

Certification path

How do you get ISO 20000-1 certified?

Build and run the management system, then an accredited certification body audits it in two stages. Most organisations take 6 to 12 months; less with an existing ISO management system.

  1. Define scope and services

    Decide which services, locations and parties the SMS covers.

  2. Assess risks and plan the SMS

    Assess risks to services, set objectives and plan the SMS.

  3. Implement controls and keep records

    Run each clause 8 process with records from your ITSM tool, and report on service levels.

  4. Run an internal audit and management review

    Clause 9 must operate at least once before certification.

  5. Stage 1 audit: design and documents

    The certification body checks scope, planning and documented information.

    1–3 days
  6. Stage 2 audit: system in operation

    Auditors sample records across processes and sites to confirm the system works.

    Audit days set by headcountMulti-auditor workspace →
  7. Keep it running for three years

    Year 1Surveillance audit
    Year 2Surveillance audit
    Year 3Recertification audit

Durations are typical planning ranges from QULDEX audit delivery, not requirements of the standard.

Documented information

Which documents does ISO 20000-1 require?

Auditors ask for these first. Process records from your ITSM tool supply most of the evidence.

Document or recordClauseWhere it lives in QULDEX
SMS scope4.4Program setup
Service management policy and objectives5.2 · 6.2Evidence vault
Service management plan6.3Evidence vault
Service catalogue8.2.4Evidence vault
Configuration information8.2.6Evidence vault
Service level agreements and reports8.3.3Evidence vault
Supplier contracts and reviews8.3.4Vendor register
Capacity plan8.4.3Evidence vault
Change, release, incident, request and problem records8.5–8.6Control workflows
Availability and continuity plans8.7.1–8.7.2Evidence vault
Information security policy8.7.3Evidence vault
Internal audit, management review and service reports9Audit workspace

Clause references follow ISO/IEC 20000-1:2018.

Time and cost

How long does ISO 20000-1 take and what drives the cost?

First certification usually takes 6 to 12 months. The number of services and how mature your ITSM tooling is drive effort most.

Where the time goes

Scope and services2–4 wk
Risks and planning3–6 wk
Run processes2–5 mo
Internal audit, review3–6 wk
Stage 1 + Stage 24–6 wk

Bars show the upper end of each range on one scale (8 months = full width).

What changes the effort

  • Services in scope: each needs SLAs, catalogue entries and reports
  • ITSM maturity: good tooling supplies most evidence
  • Suppliers: external parties in the lifecycle need control
  • Existing ISO 27001 or 22301: 8.7.2 and 8.7.3 evidence carries over
  • Locations: multi-site delivery adds sampling
Readiness check · 2 minutes

Are you ready for an ISO 20000-1 Stage 1 audit?

Auditors check these eight things first. Nothing you enter leaves this page.

4.4Is the SMS scope defined, with services listed?
8.2.4Is there a current service catalogue?
8.3.3Do you have SLAs and report against them?
8.3.4Are suppliers managed with contracts and reviews?
8.5.1Are changes assessed and approved?
8.6.1Are incidents recorded and resolved to targets?
8.6.3Do you find and fix root causes of problems?
9.2Have you completed an internal audit of the SMS?
Crosswalk

How ISO 20000-1 maps to ITIL, ISO 27001 and ISO 22301

ISO 20000-1 sets certifiable requirements; ITIL provides practice guidance that meets many of them. Its assurance processes overlap with ISO 27001 and ISO 22301.

ISO 20000-1 vs ITIL

ISO/IEC 20000-1ITIL 4
TypeCertifiable requirements standardBest-practice guidance
Who certifiesAccredited certification bodiesIndividuals, not organisations
ContentWhat a service management system must doHow to run service management practices
Use togetherYesYes; ITIL helps meet 20000-1
In QULDEXQULDEX maps ITIL practice records to 20000-1 clauses so ITSM tickets become audit evidence.

Process crosswalk

ISO 20000-1ITIL 4 practiceISO 27001:2022ISO 22301Shared evidence
8.2.6 ConfigurationService configuration managementA.5.9—CMDB
8.3.3 Service levelsService level management——SLA reports
8.3.4 SuppliersSupplier managementA.5.19–A.5.228.4Supplier reviews
8.4.3 CapacityCapacity and performance managementA.8.6—Capacity plans
8.5.1 ChangeChange enablementA.8.32—Change records
8.6.1 IncidentsIncident managementA.5.26—Incident records
8.6.3 ProblemsProblem managementA.5.27—Problem records
8.7.2 ContinuityService continuity managementA.5.308.4Continuity tests
8.7.3 SecurityInformation security managementAnnex A—Security controls

Indicative mapping. The full crosswalk is in the QULDEX control library.

Where QULDEX fits

How QULDEX runs ISO 20000-1 from processes to certificate

QULDEX is ISO 20000-1 service management compliance and audit software built from EGV Group's audit delivery, used by service providers and the auditors who test them. Pick your role to see who does what.

For service providers building or renewing a service management system.

  1. ScopeSet scope and contextScope and context recorded once per programme
  2. PlanningAssess risks and set objectivesRisk register and objectives tracked on the dashboard
  3. OperationRun the controlsRecords collected on schedule with owners
  4. Internal auditTest the systemAudit workspace, sampling and findings into CAPA
  5. CertificationHost the auditorControlled, logged evidence sharing
  6. SurveillanceKeep it runningLive readiness view for each year's audit
Without one systemWith QULDEX
SLA reports assembled by handReports linked as evidence each period
ITSM tickets outside the audit trailTickets sampled directly as evidence
Separate audits for 20000-1 and 27001Shared assurance evidence
Problem records never closedProblems tracked to closure in CAPA
10+years of audit delivery500+audits deliveredBoth sidesof the audit on one platformRBACand a full audit trail on every action
FAQ

ISO 20000-1 questions people ask

What is ISO/IEC 20000-1?

The international standard for a service management system, setting requirements for planning, delivering and improving services.

What is the difference between ISO 20000-1 and ITIL?

ISO 20000-1 is a certifiable requirements standard. ITIL is practice guidance that helps meet those requirements; organisations can't be ITIL certified.

What processes does ISO 20000-1 cover?

Service portfolio, relationship and agreement, supply and demand, design and transition, resolution and fulfilment, and service assurance, in clause 8.

What changed in ISO 20000-1 Amendment 1:2024?

It adds climate change to clause 4: you decide whether climate change is a relevant issue for the SMS.

How long is an ISO 20000-1 certificate valid?

Three years, with surveillance audits in years one and two and recertification in year three.

Can ISO 20000-1 be combined with ISO 27001?

Yes. Clause 8.7.3 requires information security management, which ISO 27001 controls can meet, and the management-system clauses align.

Can QULDEX run ISO 20000-1 alongside ISO 27001?

Yes. Shared clauses and evidence are mapped once, and each standard keeps its own report.

Sources

References

  1. ISO/IEC 20000-1:2018, Service management system requirements. iso.org
  2. ISO/IEC 20000-1:2018/Amd 1:2024, Climate action changes. iso.org
  3. ISO/IEC 20000-2:2019, Guidance on the application of service management systems. iso.org
  4. AXELOS / PeopleCert, ITIL 4. peoplecert.org
  5. ISO/IEC 27001:2022. iso.org

Reviewed by

Swati Chaturvedi

Framework reviewer · QULDEX

Reviewed this page against ISO/IEC 20000-1:2018 and Amendment 1:2024: processes, documents, certification path and crosswalk.

Page history
  • : Rebuilt with process explorer, ISO 20000-1 vs ITIL, crosswalk and readiness check
  • : Page first published

Find your ISO 20000-1 gaps in 15 minutes

Answer a short readiness check and get a gap summary by process. No sales call needed to see the result.

Schedule
Book a Demo