ITIL: IT Service Management Framework Explained

ITIL is the most widely adopted body of best practice for IT service management. Managed service providers, IT outsourcers and internal IT teams use it to run service desks, handle incidents, control changes and agree service levels. Clients often ask for ITIL-aligned processes in contracts, and many job descriptions list ITIL certification. 2026 brings a new generation, ITIL Version 5, rolling out in phases alongside ITIL 4. This guide explains what ITIL is, its core concepts and practices, how to adopt it in an IT services company, and what Version 5 changes.

What is ITIL?

ITIL provides guidance on how to create, deliver, support and improve technology-enabled services so they deliver value to customers. It covers operational practices such as incident and change management and strategic topics such as service design, relationship management and continual improvement.

Full form and definition

ITIL originally stood for Information Technology Infrastructure Library, after the series of books first published by the UK government. Today ITIL is used as a brand name. IT service management (ITSM) is the discipline of managing IT as a set of services delivered to users and customers.

Law, standard or certification?

ITIL is a voluntary best-practice framework. People earn ITIL certifications; organisations claim ITIL alignment. For a certifiable management system for service management, organisations use ISO/IEC 20000-1, which is compatible with ITIL.

History and background of ITIL

The UK government's Central Computer and Telecommunications Agency (CCTA) published the first ITIL books from 1989 to standardise IT practices across government. ITIL V2 (around 2000) focused on service support and delivery, ITIL V3 (2007, updated in 2011) introduced the service lifecycle, and ITIL 4 (February 2019) reframed ITIL around value co-creation, agile and DevOps ways of working, with 34 practices. Ownership moved to AXELOS in 2014 and PeopleCert acquired AXELOS in 2021.

ITIL Version 5

PeopleCert launched ITIL Version 5 in phases during 2026, starting with ITIL Foundation (Version 5), with advanced modules released progressively. PeopleCert positions it as an evolution rather than a reset, with a stronger focus on digital products and services, experience, and governance of AI, including an AI governance extension module. ITIL 4 remains available in parallel, and ITIL 4 certificates remain valid. Because modules are still being released, check PeopleCert's official materials for current details.

Why was ITIL introduced?

In the 1980s government IT quality varied widely between departments. ITIL documented proven practices so organisations could deliver reliable IT services at reasonable cost, independent of vendor or technology.

Main objectives and purpose

• Co-create value with customers through services.
• Deliver reliable, predictable services with agreed levels.
• Balance speed of change with stability.
• Provide a common vocabulary for IT teams, suppliers and customers.
• Continually improve services and practices.

Who needs ITIL?

• Managed service providers and IT outsourcers, where clients expect ITIL-aligned incident, problem, change and SLA management
• Internal IT departments in enterprises and government
• SaaS and cloud operations teams running customer-facing services
• Service desk and support centres
• IT professionals seeking career credentials

ITIL is used worldwide and is particularly strong in the UK, Europe, India, Australia and the Middle East. Indian IT services companies widely use ITIL as the operating model for global delivery.

Key concepts and practices

ITIL 4 service value system

• Guiding principles: focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; optimise and automate.
• Governance to direct and control the organisation.
• Service value chain activities: plan, improve, engage, design and transition, obtain/build, deliver and support.
• Practices: 34 sets of organisational resources for performing work.
• Continual improvement at every level.

Four dimensions of service management

Organisations and people; information and technology; partners and suppliers; and value streams and processes.

Practices most relevant to IT service companies

Core ITIL practices for managed services

Practice	Purpose
Service desk	Single point of contact for users and requests
Incident management	Restore normal service as quickly as possible
Problem management	Find and remove root causes of incidents
Change enablement	Maximise successful changes through risk assessment and authorisation
Service request management	Handle standard user requests efficiently
Service level management	Set and monitor business-based service levels
Monitoring and event management	Observe services and respond to events
Information security management	Protect information needed by the organisation
Service continuity management	Keep availability and performance at sufficient levels during disasters
Supplier management	Manage suppliers and their performance
Knowledge management	Make information and knowledge available and useful
Continual improvement	Align practices and services with changing needs

How to adopt ITIL: step by step

1. Start where you are: assess current processes, tools and pain points, for example slow incident resolution or failed changes.
2. Define the services you provide in a service catalogue, with owners.
3. Prioritise practices, usually service desk, incident, request, change and service level management first.
4. Design lightweight workflows in your ITSM tool, with categories, priorities and escalation rules.
5. Agree SLAs and internal operational level agreements that support them.
6. Train staff, including ITIL Foundation for team leads.
7. Measure: resolution times, change success rate, repeat incidents, customer satisfaction.
8. Add practices iteratively: problem, knowledge, monitoring, continuity and supplier management.
9. Review and improve through a continual improvement register.

Documentation typically maintained

• Service catalogue and service descriptions
• SLAs, OLAs and underpinning contracts
• Incident, problem, change and request procedures
• Priority and escalation matrices
• Change advisory or approval records and change calendar
• Knowledge base articles
• Service reports and continual improvement register
• Configuration management database (CMDB) or asset records

Audit and assessment requirements

ITIL has no organisational audit. Organisations can commission maturity assessments, and PeopleCert offers ITIL maturity assessment services. If clients need an audited certificate, ISO/IEC 20000-1 certification by an accredited body is the route. Service management controls also feature in SOC 2 and ISO 27001 audits, especially change and incident management.

Estimated implementation timeline

• Core practices (service desk, incident, request, change) in an MSP: 3 to 6 months
• Adding problem, knowledge, SLM and continuity: a further 3 to 6 months
• Mature, measured improvement: ongoing

Cost considerations

• ITSM platform licences
• Training and certification exams for staff
• Consultancy for process design or maturity assessment
• Staff time for process ownership and reporting

Benefits of ITIL

• Faster incident resolution and fewer repeat incidents.
• Fewer failed changes and outages.
• Clear SLAs and reporting that support client retention.
• Common language with enterprise clients and their auditors.
• Evidence for ISO 20000-1, ISO 27001 and SOC 2 controls.

Risks of poor service management

There are no penalties for ignoring ITIL, but contracts often impose SLA service credits and termination rights tied to incident handling and availability. Poor change control is a leading cause of outages.

Common implementation mistakes

• Implementing every practice at once.
• Copying heavyweight processes that slow down agile and DevOps teams.
• Making change approval a bureaucratic bottleneck instead of risk-based.
• Measuring ticket counts rather than outcomes.
• Buying an ITSM tool and calling it ITIL adoption.

Challenges for IT companies

• Different clients require different SLAs, tools and reporting.
• Integrating with clients' own ITSM tools.
• Combining ITIL change enablement with continuous delivery pipelines.
• Planning training as ITIL 4 and Version 5 run in parallel.

Best practices and recommendations

• Follow the guiding principle "start where you are".
• Use standard, pre-approved changes for low-risk automated deployments.
• Link incident and problem data to engineering backlogs.
• Align ITIL with COBIT for governance and ISO 22301 for continuity.
• Keep ITIL 4 processes running; adopt Version 5 concepts as training and materials become available.

Tools and technologies that help

• ITSM platforms with incident, request, change and problem workflows
• Monitoring, observability and on-call tools integrated with ITSM
• CMDB and asset discovery
• Knowledge base and self-service portals
• Reporting dashboards for SLAs

Relationship with other compliance frameworks

ITIL and related frameworks

Framework	Relationship
COBIT	Governance framework; ITIL practices implement many COBIT management objectives
ISO 9001	Quality management; ITIL provides service delivery evidence
ISO 27001	Change, incident and supplier controls overlap with ITIL practices
ISO 22301	Business continuity management that ITIL service continuity supports

Real-world implementation examples

The following are illustrative composites based on common patterns, not named clients.

Managed service provider

An MSP supporting 120 clients standardised priority definitions, introduced problem management for top recurring incidents and moved low-risk patching to standard changes, reducing repeat incidents and emergency changes within two quarters.

SaaS operations team

A SaaS company adopted lightweight incident management with severity levels, on-call rotation and blameless post-incident reviews, mapping them to ITIL practices for its SOC 2 audit.

Frequently asked questions

What is the latest version of ITIL?

ITIL Version 5, released in phases during 2026, starting with Foundation. ITIL 4 remains available in parallel.

Can a company be ITIL certified?

No. Only individuals are certified. Companies seeking an audited certificate use ISO/IEC 20000-1.

Are ITIL 4 certificates still valid?

Yes. ITIL 4 certifications remain valid, and ITIL 4 Foundation is accepted as a prerequisite for higher Version 5 qualifications.

How many practices does ITIL 4 have?

34 practices: general management, service management and technical management practices.

What are the ITIL guiding principles?

Focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; optimise and automate.

Is ITIL compatible with agile and DevOps?

Yes. ITIL 4 explicitly integrates agile, lean and DevOps concepts.

What is the difference between ITIL and ISO 20000?

ITIL is best-practice guidance; ISO/IEC 20000-1 is a certifiable standard for a service management system.

Who owns ITIL?

PeopleCert, which acquired AXELOS, the previous owner, in 2021.

Which ITIL practices should we start with?

Most service providers start with service desk, incident, service request, change enablement and service level management.

Conclusion and next steps

ITIL helps IT companies deliver services clients can rely on. Adopt it iteratively, focus on outcomes and keep processes as light as your risk allows.

1. Assess current practices and pain points.
2. Define services and SLAs.
3. Implement core practices in your ITSM tool.
4. Measure and improve continuously.
5. Plan training across ITIL 4 and Version 5.

How we keep this guide up to date

We review this guide every six months and as PeopleCert releases further ITIL Version 5 modules and transition guidance.