Integrated Assessment ServicesCertification and auditor training, USA

ISO 20000 Certification in USA

ISO/IEC 20000-1:2018 IT Service Management System Certification for Enterprise IT, MSPs, Cloud Providers and Digital Service Organizations

ISO/IEC 20000-1 sets requirements for a service management system (SMS) that helps an organization plan, design, transition, deliver, monitor and continually improve its services.

Independent certification checks a defined SMS against the standard for the services and locations named in the scope. It looks for consistent delivery, measurable service requirements, supplier governance and improvement. It does not guarantee uptime or SLA results.

  • Managed service providers
  • Cloud and SaaS
  • Data centers
  • Internal IT
  • Telecom
  • IT support

Standard status

Current ISO/IEC 20000-1 standard

Certification is to ISO/IEC 20000-1:2018, including Amendment 1:2024. The 2018 edition replaced the 2011 edition, which is withdrawn; it adopted the common management system structure and gave organizations more freedom in how they meet requirements. No newer edition has been published.

Certification standard
ISO/IEC 20000-1:2018Service management system requirements. Confirmed by ISO in 2023.
Amendment
Amd 1:2024Climate action changes: consider whether climate change is a relevant issue. No emission targets.
Certification body rules
ISO/IEC 20000-6:2017Requirements for bodies auditing and certifying SMS, used with ISO/IEC 17021-1:2015.
Guidance
ISO/IEC 20000-2:2019 and 20000-3:2019Applying an SMS; defining scope and applicability. Guidance only, not certified against.

Official records: ISO/IEC 20000-1:2018 (opens in a new tab) · Amd 1:2024 (opens in a new tab) · ISO/IEC 20000-6:2017 (opens in a new tab) · ISO/IEC 20000-2:2019 (opens in a new tab) · ISO/IEC 20000-3:2019 (opens in a new tab) · IEC webstore (opens in a new tab)

ISO/IEC 20000-1 is not ITIL and not a software product. ISO and IEC publish the standard; they do not issue certificates.

The basics

Understanding IT service management system certification

Your SMS is your work. Certification is an independent check of it, for the services in scope.

An SMS is the policy, plans, processes, roles and records you use to manage services: understanding service requirements, planning, delivering services, managing suppliers, monitoring performance, internal audit, management review and continual improvement.

Independent certification means a certification body audits the SMS and decides, through people not involved in the audit, whether it meets ISO/IEC 20000-1 for the scope on the certificate.

ISO 20000 certification does not automatically cover

  • Every IT service the company offers
  • Every software product
  • Every cloud platform
  • Every supplier
  • Every IT employee
  • Every data center or location
  • A specific service desk software tool

It is not a guarantee of uninterrupted service or of every SLA being met. It is not ITIL certification and not an information security certification.

Who it is for

IT service management certification for modern service organizations

ISO 20000 is voluntary. These are typical patterns, not rules; your own services decide your scope.

Scope builder

Define the IT services covered by ISO 20000 certification

Seven steps to a draft scope statement for technical review. It does not approve scope, exclude outsourced services automatically, or decide multi-site sampling.

  1. 1Organization
  2. 2Services
  3. 3Customers
  4. 4Delivery model
  5. 5Locations
  6. 6Tools
  7. 7Workforce
A. Organization

Requirements

Explore ISO/IEC 20000-1:2018 requirements

Clauses 4 to 10. Summaries are our own and do not reproduce the standard; check subclause titles against your copy. ITIL practice names are not ISO requirements.

Service lifecycle

From service planning to continual improvement

A way to see how service management fits together. Real processes run iteratively and in parallel, not as a fixed waterfall.

Service level management

Understanding service level management and SLAs

Explore a fictional SLA for a managed IT support service. Every target here is an example, not a requirement: ISO 20000 does not set uptime, response or resolution figures.

Fictional priority matrix (example targets, measured in the stated hours)
PriorityDefinitionResponse targetResolution target
P1 CriticalService unavailable for many users or a critical function15 minutes4 hours
P2 HighService degraded for many users, or unavailable for a key group30 minutes8 support hours
P3 MediumOne user or a non-critical function affected4 support hours3 business days
P4 LowMinor issue with a workaround1 business day10 business days

SLA, KPI and OLA

SLA, KPI and OLA compared
SLAKPIOLA
What it isA documented agreement between the service provider and the customer about the service and its targetsA measure used to track performanceAn internal agreement between parts of the provider that support an SLA, where used
Who it is withCustomerUsed internally, sometimes shared with the customerInternal teams or internal suppliers
ExampleP1 incidents resolved within 4 hoursPercentage of P1 incidents resolved within target this monthNetwork team restores connectivity within 2 hours to support the P1 target
Required by ISO 20000?Service level agreements are part of service level management (8.3.3); content is agreed with the customerMeasures are needed to monitor performance; the choice of KPIs is the provider’sISO 20000 refers to agreements with internal suppliers; the term OLA is common practice

Terms and arrangements differ between organizations. Certification does not mean every SLA will be met.

Service catalogue

What services are actually covered?

A fictional catalogue. Yours must describe your own services; one template does not fit every organization.

Incident management

Managing IT service incidents

Incident management restores service and manages the impact of disruption. Not every incident is a security incident, and certification does not guarantee resolution within a set time. Follow a fictional incident.

  • Major incidents A defined procedure for incidents with high business impact, with clear leadership and communication.
  • Business impact Drives priority and escalation.
  • Customer communication Regular updates until service is restored.
  • Evidence Timestamps, actions and closure in the ticket record.

Service requests

Service requests vs incidents

Classify six fictional tickets, then check your answers. Providers set their own approved fulfilment procedures; there is no single required workflow.

A user asks for access to the shared sales folder.

The email service is down for everyone.

A new employee needs a laptop and accounts set up.

The VPN is very slow for all remote users.

A user asks how to set an out-of-office reply.

A scheduled report failed to run overnight.

Problem management

Moving from repeated incidents to root cause management

An incident is an unplanned interruption or degradation. A problem is the cause, or potential cause, of one or more incidents. Not every incident needs its own problem record.

Change and release

Managing service changes without unnecessary disruption

Controls depend on risk and change type; not every change needs the same approver or a Change Advisory Board. Change control is an organizational decision process, separate from deployment tooling.

Controlling service releases and deployments

A fictional SaaS release. ISO 20000 certification does not approve a software product’s functions or security.

  1. Release planning Version 4.2 of a fictional SaaS app bundles three features and two fixes.
  2. Release contents Release notes list what changes, linked to change records.
  3. Testing and acceptance Testing in a staging environment; acceptance criteria agreed with the product owner.
  4. Deployment Phased rollout to 10% of tenants, then all tenants.
  5. Rollback or recovery A tested rollback plan exists if errors exceed agreed limits.
  6. Communication Customers notified of the release window and new features.
  7. Post-implementation evaluation Incidents after release are reviewed; lessons recorded.

Configuration

Understanding service configuration information

Configuration items (CIs) and their relationships. No particular CMDB product is required, and a tool is never certified because its customer is.

Availability

Managing service availability requirements

An educational calculation. ISO 20000 requires availability requirements and targets to be agreed and monitored; it does not require a percentage or 24/7 service.

Capacity and demand

Planning IT services for customer demand

Fictional weekly ticket volumes for a service desk. Change the expected growth to see the effect on demand. No staffing ratio applies to everyone; each provider sets its own capacity method.

Fictional weekly ticket volumesTwelve weeks of tickets as navy bars and a projected next twelve weeks as amber bars. Values are in the text beside the chart.

Last 12 weeks (fictional)Projected 12 weeks

For example a new customer being onboarded.

Service continuity

Service continuity within ISO 20000

Service continuity requirements, dependencies, disruption scenarios, recovery arrangements, plans, testing, communication and review.

Service continuity and ISO 22301
ISO/IEC 20000-1 service continuityISO 22301 BCMS
FocusContinuity of services in the SMS scopeContinuity of the whole organization’s prioritized activities
AnalysisService continuity requirements and risksBusiness impact analysis and risk assessment
CertificatePart of ISO 20000 certificationSeparate ISO 22301 certification

ISO 20000 certification does not show ISO 22301 conformity. ISO 22301 certification

Suppliers

Managing services delivered through third parties

A fictional MSP and four suppliers. Externally delivered parts are not excluded from scope automatically: what matters is your governance of the end-to-end service. Suppliers are not certified as part of your SMS.

Customer relationships

How service providers manage customer relationships

A fictional quarterly service review. Not an IAS customer, and not real data.

Fictional service review, Q3 (percentages of tickets or hours in the quarter)
MeasureAgreed targetActualStatus
P1 incidents resolved in target95%92%Below target
P2 incidents resolved in target90%94%Met
Requests fulfilled in target90%96%Met
Server availability (agreed hours)99.5%99.8%Met
Customer satisfaction responses (score of 4 or 5 out of 5)85%88%Met
Incident trends
P1 incidents concentrated on the finance application; a problem record is open.
Customer feedback
Positive on the service desk; concern about month-end outages.
Decisions
Prioritize the finance application problem; add monitoring before month-end.
Actions and owners
Application support lead: root cause by next review. Operations manager: monitoring change this month.

Evidence dashboard

What does strong ISO 20000 audit evidence look like?

Select a measure. Values are fictional and illustrative, not IAS customer results, and ISO 20000 sets no threshold for any of them.

Strong and weak evidence

Strong and weak evidence
AreaStronger evidenceWeaker evidence
Service levelsAgreed targets, actual results, reporting and documented reviewsA service target that is never measured
Incident managementConsistently classified tickets with complete lifecycle recordsUnclassified, unresolved tickets with no explanation
Problem managementRoot cause investigation and effective follow-upRecurring incidents with no problem evaluation
ChangesRecorded assessment, authorization and reviewUncontrolled changes and incomplete records
SuppliersAgreements, monitoring and reviewSupplier names without defined responsibilities or monitoring
Management reviewRecorded evaluation, decisions and actionsA meeting invitation with no evidence of decisions

Readiness check

Is your IT service management system ready for ISO 20000 certification?

Twenty-three questions, no contact details. Educational only: it does not evaluate security or uptime and does not predict Stage 1 results.

1Is the SMS scope defined?
2Is a service management policy established?
3Are service owners assigned?
4Are services clearly identified?
5Is a service catalogue available?
6Are customer requirements determined?
7Are service agreements established?
8Are service levels monitored?
9Are incidents managed?
10Are service requests managed?
11Are problems evaluated?
12Are changes controlled?
13Are releases managed?
14Is relevant configuration information maintained?
15Are suppliers governed?
16Are service availability and continuity addressed?
17Are capacity and demand reviewed?
18Are service performance results evaluated?
19Are improvement opportunities identified?
20Are personnel competent?
21Have internal audits been conducted?
22Has management review been completed?
23Are corrective actions managed?
0 of 23 answered

Certification process

How to get ISO 20000 certified in the USA

Steps 1 to 6 are your preparation; steps 7 to 14 are independent certification. IAS does not install ITSM software, write your processes or implement your SMS, and certification is not guaranteed.

What happens during ISO 20000 audits?

Stage 1 and Stage 2 compared
Audit stagePurposeActivitiesEvidenceRelevant personnelNext step
Stage 1Confirm readiness and plan Stage 2Review scope, catalogue, policy, documented information, services and suppliers, processes, internal audit and management reviewSMS scope, catalogue, policy, SMS plan, audit and review recordsTop management, SMS manager, service ownersAddress concerns; Stage 2
Stage 2Assess implementation and effectivenessSample incidents, requests, problems, changes, supplier control, SLA monitoring, availability, continuity, reporting, customer relationships and improvementTicket, change and release records; service reports; supplier reviewsService desk, operations, change and release, supplier and relationship managersClose findings; certification decision

Audits use sampling. Stage 1 is not always remote, and one good interview does not prove the whole SMS works.

Documents

What documents and records are needed for ISO 20000 certification?

Some documented information is required by the standard; other records are typical evidence. No particular form or ITSM platform is required.

ISO 20000 documents and records
Document or recordTypeRelated clause
SMS scopeDocumented information required4.3
Service management policyDocumented information required5.2
Service management objectivesDocumented information required6.2
Service management planDocumented information required6.3
Service catalogueDocumented information required8.2.4
Service level agreementsDocumented information required8.3.3
Contracts or agreements with suppliersDocumented information required8.3.4
Change management policyDocumented information required8.5.1
Capacity planDocumented information required8.4.3
Service availability requirements and targetsDocumented information required8.7.1
Service continuity plansDocumented information required8.7.2
Information security policyDocumented information required8.7.3
Evidence of competenceDocumented information required7.2
Internal audit program and resultsDocumented information required9.2
Management review resultsDocumented information required9.3
Nonconformities and corrective actionsDocumented information required10.1
Service reportsIllustrative or expected evidence9.4
Incident and service request recordsIllustrative or expected evidence8.6.1, 8.6.2
Problem and known error recordsIllustrative or expected evidence8.6.3
Change and release recordsIllustrative or expected evidence8.5.1, 8.5.3
Configuration informationIllustrative or expected evidence8.2.6
Customer feedback and complaintsIllustrative or expected evidence8.3.2
Demand informationIllustrative or expected evidence8.4.2

Clause references follow ISO/IEC 20000-1:2018; check them against the standard.

Compared

ISO 20000 certification vs ITIL — what is the difference?

ISO/IEC 20000-1 contains requirements an organization can be certified against. ITIL, owned by PeopleCert, is guidance for managing services, with qualifications for individuals. ITIL 4 is widely used, and PeopleCert introduced ITIL (Version 5) in 2026.

ISO 20000 and ITIL compared
ISO/IEC 20000-1ITIL
Standard or frameworkInternational standard with requirementsFramework of guidance and good practice
OwnerISO and IEC (joint technical committee)PeopleCert
Primary purposeRequirements for a service management systemGuidance for managing services and creating value
Requirements or guidanceRequirements (“shall”)Guidance; adapt to your organization
Organizational certificationYes, by a certification bodyNo organizational certification scheme
Individual qualificationsNot the purpose of the standardYes, professional qualifications for individuals
Process practicesDefined processes in clause 8Practices described as guidance
AssessmentIndependent auditExams for individuals
Intended usersOrganizations delivering servicesIndividuals and organizations
Ongoing improvementSurveillance and recertification auditsContinuing professional development for individuals
  • Not interchangeable An employee’s ITIL qualification does not make the employer ISO 20000 certified.
  • No maturity guarantee ISO 20000 certification does not prove ITIL maturity.
  • Not a prerequisite ITIL is not required for ISO 20000.
  • Not all mandatory ITIL practices are not ISO 20000 clauses.

PeopleCert: ITIL certifications (opens in a new tab)

Compared

Service management, information security and quality management

Integration can share internal audit, management review and corrective action. Each certificate stays separate: none shows conformity with another.

ISO 20000, ISO 27001 and ISO 9001 compared
ISO/IEC 20000-1ISO/IEC 27001ISO 9001
Main purposeService managementInformation security managementQuality management
ScopeServices and the SMSInformation security for defined scopeProducts and services broadly
Service deliveryCentral focusSupportingCovered generally
Information securityOne process within service assurance (8.7.3)Central focus, with Annex A controlsNot specific
Risk managementRisks to services and the SMSInformation security risk assessment and treatmentRisks and opportunities for quality
Customer requirementsAgreed service requirements and SLAsInterested-party security requirementsCustomer requirements and satisfaction
Audit focusService records, SLAs, suppliers, changeRisk treatment, controls, incidentsProcesses, customer focus, improvement
CertificationSeparate certificateSeparate certificateSeparate certificate

ISO 27001 certification · ISO 9001 certification

Cloud and SaaS

IT service management for modern digital service providers

Follow a fictional SaaS service journey and see where responsibility sits. Your certificate does not certify your cloud provider, does not cover every application automatically, and does not guarantee uptime.

Small and growing providers

ISO 20000 certification for IT startups and MSPs

There is no minimum employee count. Small providers still meet every applicable requirement, and a small company does not automatically get a shorter audit.

  • Small service desk teams Roles can be combined if responsibilities are clear.
  • Remote teams Processes work the same wherever people sit.
  • Outsourced infrastructure Governed through supplier management.
  • Ticketing and SLAs A simple tool is fine if records are complete.
  • Defined scope Start with the services you can evidence.
  • Internal audit and management review Still required.

ISO 20000 certification across multiple service locations

Service desks, distributed teams, follow-the-sun support, data centers, remote staff, vendors and several legal entities. Locations are not included because the parent company is certified, and multi-site sampling is not automatic: it needs technical review.

  • Shared SMS One system across locations, with clear site roles.
  • Site-specific processes Differences must be visible and controlled.
  • Scope boundaries Name each site on the certificate.
  • Legal entities Name the entities covered.

Benefits

How ISO 20000 can support service delivery

What a working SMS can help with. No outcome is guaranteed: not zero outages, 100% SLA compliance, fewer tickets, cost savings, customer satisfaction, contracts or universal recognition.

  • Consistency More consistent service management.
  • Ownership Clear service owners.
  • Requirements Defined customer requirements.
  • Monitoring Better visibility of performance.
  • Incidents and changes More structured handling.
  • Suppliers Stronger governance.
  • Procurement Can support customer and tender requirements.

Cost and audit duration

How much does ISO 20000 certification cost in the USA?

Cost follows audit time and travel. Audit time is set during technical review under ISO/IEC 20000-6 and ISO/IEC 17021-1, from people in scope, sites, services, complexity, outsourcing, shifts and the audit type. No prices, audit days or discounts are published.

How long does ISO 20000 certification take?

Preparation depends on your scope, how established your processes are and how much operating evidence you have. Documents alone are not enough, new ITSM software is not required, and no fixed timeline is promised. Tick what is in place.

Already in place

Certification cycle

Maintaining ISO 20000 certification

Report significant changes: new services, catalogue changes, new suppliers or sites, service desk changes, ITSM tool migrations, major incidents and scope changes. Certificates can be suspended or withdrawn if requirements are not met.

  1. 1

    Initial certification

    Stage 1, Stage 2 and an independent decision.

  2. 2

    Surveillance

    At least once a calendar year; the first within 12 months of the decision.

  3. 3

    Surveillance

    Checks changes and continued effectiveness.

  4. 4

    Recertification

    Audit and decision before expiry.

Accreditation

Understanding IAS ISO 20000 accreditation

Accreditation concerns the certification body; certification concerns your SMS. UQAS accreditation does not by itself mean IAF MLA recognition, IAS is not itself “IAF-accredited”, and no certificate is automatically accepted worldwide.

Verify an IAS certificate

IAS accreditation details

Who issues the certificate
Integrated Assessment Services LLC under its UQAS accreditation, subject to confirmation that ISO/IEC 20000-1 is in the accredited scope. Your proposal names the issuer. EAS’s JAS-ANZ accreditation is separate and does not belong to IAS.
Rules applied
ISO/IEC 17021-1 and ISO/IEC 20000-6:2017 for audit time, auditor competence and decisions.
Checking a certificate
Certified organization, scope, sites, standard edition, certificate number, issuer, accreditation, issue and expiry dates, and current status. IAS certificates: IAS certificate search.

Impartiality

Independent IT service management system certification

A certification body must stay independent of what it certifies.

  • No consultancy IAS does not implement SMS, write service catalogues, SLA frameworks, incident workflows or change processes, or run gap analyses for organizations it certifies.
  • Competence Auditors are assigned for the services in scope.
  • Confidentiality Service and customer data are protected.
  • Conflicts of interest Identified and managed.
  • Independent decisions Made by people not involved in the audit.
  • Complaints and appeals A documented process.
  • Training is separate Training does not make a successful audit more likely.

Training

Build internal IT service management auditing competence

Training is delivered through EAS and is separate from certification. Ask us about ISO/IEC 20000 courses; dates appear on the training schedule when courses are scheduled.

IAS USA

Why IT service providers consider IAS USA

Certification coordination for organizations across the US. Office: 1341 W Mockingbird Ln, Suite 600W, Dallas, TX 75247.

  • Coordination One contact from application to certificate.
  • Scope review Services, sites and suppliers reviewed before audit time is set.
  • Defined process Stage 1, Stage 2 and surveillance planned ahead.
  • Clear quotation Factors explained before you agree.
  • Communication Clear reports and timelines for findings.

Quotation

Request your ISO 20000 certification proposal

Nine short steps. Scope builder and readiness answers are included only if you choose.

  1. A certification coordinator and an ITSMS technical reviewer review your scope.
  2. Audit time and price are set after technical and pricing review.
  3. Nothing is agreed until you accept the proposal.

Do not include customer SLAs, ticket exports, infrastructure diagrams, passwords or other confidential details in this form.

  1. 1Company
  2. 2Requirement
  3. 3Services
  4. 4Delivery
  5. 5SMS status
  6. 6Workforce
  7. 7Locations
  8. 8Certification
  9. 9Project
A. Company information

FAQ

ISO 20000 certification questions

50 answers for US service providers.

What is ISO 20000 certification?

Independent confirmation by a certification body that an organization’s service management system (SMS) meets ISO/IEC 20000-1 for the services and locations named in the certificate scope.

What is ISO/IEC 20000-1?

The international standard that sets requirements for a service management system to plan, design, transition, deliver and improve services.

What is the latest published ISO 20000 edition?

ISO/IEC 20000-1:2018, including Amendment 1:2024. The 2011 edition is withdrawn.

Is ISO 20000:2026 published?

No. ISO/IEC 20000-1:2018 with Amendment 1:2024 is the current version.

What is ISO/IEC 20000-1:2018/Amd 1:2024?

An amendment on climate action. Organizations consider whether climate change is a relevant issue and whether interested parties have climate-related requirements. It does not set emission targets.

What is an IT Service Management System?

The policies, processes, roles and records an organization uses to manage the services it delivers, from requirements to improvement.

What types of companies can be certified?

Any organization that delivers services to internal or external customers and operates an SMS: MSPs, cloud and SaaS providers, data centers, telecom providers, internal IT departments and others.

Can MSPs obtain ISO 20000 certification?

Yes. The scope names the managed services covered and the locations that deliver them.

Can SaaS companies obtain certification?

Yes, for the services in scope. The certificate covers service management, not the software’s functionality or security.

Can internal IT departments be certified?

Yes. Internal customers and internal suppliers are covered by the standard.

Is ISO 20000 mandatory in the USA?

No. It is voluntary, though some customers or contracts may ask for it.

What are ISO 20000 requirements?

Clauses 4 to 10: context, leadership, planning, support, operation of service management processes, performance evaluation and improvement.

What services should be included in scope?

The services you want certified and can show evidence for. Name the services and the locations delivering them.

Can outsourced services be included?

Yes, where the organization governs the parties involved and controls the end-to-end service. Outsourced parts are not excluded automatically.

Can multiple delivery sites be covered?

Yes. Each site’s role must be clear. Multi-site sampling is only possible where certification rules allow it, after technical review.

What is a Service Catalog?

Information about the services you deliver: descriptions, owners, customers, dependencies and service levels. ISO 20000 uses the spelling “catalogue”.

What is Service Level Management?

Agreeing service requirements and targets with customers, monitoring results and reviewing them.

Are SLAs mandatory?

ISO 20000 requires service level agreements for services in scope, as part of service level management. Their content and targets are agreed with customers.

Is 24/7 support necessary?

No. Support hours are whatever you agree with customers.

What is Incident Management?

Restoring service as quickly as agreed after an unplanned interruption or degradation, and managing its impact.

How is an Incident different from a Service Request?

An incident is something going wrong with a service. A service request is a planned request, such as access or information.

What is Problem Management?

Finding and dealing with the underlying causes of incidents, to prevent recurrence or reduce impact.

What is Change Management?

Assessing, authorizing and reviewing changes to services and their components, with controls scaled to risk.

What is Release Management?

Planning, testing and deploying releases into the live environment, with acceptance and recovery arrangements.

What is Service Configuration Management?

Keeping accurate information about service components and how they relate. A specific CMDB product is not required.

How are suppliers managed?

Through agreements, defined responsibilities, performance monitoring and regular review, for both external and internal suppliers.

What is Service Availability Management?

Agreeing availability requirements, monitoring them and planning improvements.

What is Service Continuity Management?

Planning how services will continue or be restored after a major disruption, and testing those plans.

What is Capacity and Demand Management?

Understanding demand for services and planning the resources needed to meet it.

Is ITIL certification required?

No. ITIL qualifications are for individuals and are not a prerequisite for ISO 20000 certification.

What is the difference between ISO 20000 and ITIL?

ISO/IEC 20000-1 contains requirements an organization can be certified against. ITIL is guidance owned by PeopleCert, with qualifications for individuals.

What is the difference between ISO 20000 and ISO 27001?

ISO 20000 covers service management; ISO 27001 covers information security management. Each needs its own certificate.

Can ISO 20000 be integrated with ISO 9001?

Yes. Common elements such as internal audit and management review can be shared; each standard keeps its own requirements.

Can ISO 20000 be integrated with ISO 22301?

Yes. Service continuity work can support a business continuity system, but ISO 22301 is certified separately.

Does ISO 20000 certify software products?

No. It certifies a service management system, not a product or tool.

Does certification guarantee uptime?

No. It shows that a system for managing services is in place and working.

What documents are required?

Certain documented information, such as scope, policy, objectives, the SMS plan, the catalogue, SLAs, supplier agreements and audit and review records, plus process records.

What happens during Stage 1?

A readiness review of scope, catalogue, policy, documented information, processes, internal audit and management review.

What happens during Stage 2?

An audit of how the SMS works in practice, using samples of tickets, changes, supplier reviews and reports.

Can certification audits be remote?

Some activities may use remote techniques where accreditation rules allow. The audit plan sets this; it is not promised in advance.

How much does ISO 20000 certification cost?

It depends on audit time and travel, which depend on scope, people, sites and complexity. We quote after technical review.

How long does certification take?

It depends on how ready your SMS is and how much operating evidence you have. We do not promise a fixed timeline.

How long is a certificate valid?

Usually three years, subject to successful surveillance audits.

What is a surveillance audit?

An audit at least once a calendar year to check the SMS continues to work.

What happens if our IT services change?

Tell the certification body about significant changes. Scope changes may need review or an extra audit.

Can we transfer an existing certificate?

Transfers depend on the current certificate’s status, accreditation and audit history, and are reviewed case by case.

Who issues the certificate?

Integrated Assessment Services under its UQAS accreditation, subject to confirmation that ISO/IEC 20000-1 is in the accredited scope. Your proposal names the issuer.

How can IAS accreditation be verified?

Use the IAS certificate search for IAS certificates and ask for the accreditation certificate and scope.

Can a small IT company be certified?

Yes. There is no minimum size, but all applicable requirements still apply.

How do we request an ISO 20000 quotation?

Use the quotation form on this page. A certification coordinator and an ITSMS technical reviewer review your details first.