What is ITIL? The framework explained simply

ITIL comes up in most IT job postings, calls for tender and support tool presentations. But what is ITIL, exactly? The term refers to a set of best practices for IT service management (ITSM), used by IT departments to organize their support, their processes and their relationship with users and service customers. This guide covers the essentials: its definition, its versions, its fundamentals, the most widely used ITIL processes and how to apply them day to day.

What is ITIL? A definition

ITIL stands for Information Technology Infrastructure Library. It is a framework that describes how to design, deliver, operate and improve IT services for users, business units and every customer of the organization.

ITIL is neither a standard nor a piece of software. Unlike standards, it cannot be used to certify an organization, and it does not tell you which tool to use. Instead, it offers a common vocabulary, principles and practices that each organization adapts to its size and its challenges. That explains how widely it has spread: a technician, a support manager and a supplier speak the same language when they talk about an incident, a problem or a change.

ITIL vs ITSM: what's the difference?

The two terms are often confused. ITSM (IT Service Management) is the discipline: managing IT services in the broad sense, in other words the way an organization designs and delivers IT services to its users. ITIL is a framework that describes how to put it into practice. In short, ITSM is the “what”, and ITIL is one way of handling the “how”.

This is why people often talk about an ITIL-based ITSM approach: IT service management organized according to the framework's practices.

ITIL is not the only framework. COBIT, published by ISACA, focuses on IT governance, and the ISO/IEC 20000 standard is used to certify a service management system. These frameworks often complement each other: an organization can rely on ITIL for its practices and aim for ISO/IEC 20000 certification.

Where does ITIL come from? The main versions

ITIL was created in the late 1980s in the United Kingdom by the CCTA, a government agency tasked with improving the quality of IT services across public administration. It has since evolved through several versions:

• ITIL v2 (early 2000s): built around service support and service delivery, it popularized processes such as incident management and change management.
• ITIL v3 (2007), then ITIL 2011: published as a set of five books, it organizes service management around the service lifecycle, in five stages: strategy, design, transition, operation and continual improvement.
• ITIL 4 (2019): it replaces processes with “practices”, introduces the service value system and incorporates Agile, DevOps and Lean methods.
• ITIL (Version 5), early 2026: published by PeopleCert, which has owned ITIL since acquiring AXELOS in 2021, it builds on ITIL 4 and extends the scope to digital product and service management, as well as the role of AI and automation.

ITIL 4 remains widely used during the transition. Most of the concepts below come from ITIL 4, on which ITIL (Version 5) is built. The shift from a service lifecycle approach to a value-based approach is one of the major changes between ITIL v3 and ITIL 4.

ITIL fundamentals

Three concepts form the fundamentals of ITIL 4: the service value system, the four dimensions and the seven guiding principles.

The service value system

Since ITIL 4, the framework starts from a simple idea: an IT service is only worthwhile if it creates value for the people who use it. ITIL talks about value co-creation between the service provider and its customers, whether internal (a business unit, employees) or external. The service value system (SVS) describes how the components of an organization (guiding principles, governance, service value chain, practices, continual improvement) work together to turn demand into value.

At the heart of this system, the service value chain brings together six activities: plan, improve, engage (involve stakeholders), design and transition, obtain/build, and deliver and support.

The four dimensions

ITIL encourages you to look at every service from four angles:

• Organizations and people: the team's roles, skills and culture.
• Information and technology: the data, tools and knowledge the service needs.
• Partners and suppliers: the providers and contracts the service relies on.
• Value streams and processes: the sequence of activities that produce the service.

Neglecting one dimension weakens the service: a good tool won't make up for poorly defined roles, and a skilled team will still be held back by a poorly managed supplier.

The seven guiding principles

ITIL 4 sets out seven principles that guide decision-making in a wide range of contexts:

1. Focus on value: every action should serve the user, the customer or the business.
2. Start where you are: build on what already exists instead of rebuilding everything.
3. Progress iteratively with feedback: move forward in small steps and adjust.
4. Collaborate and promote visibility: share information across teams.
5. Think and work holistically: consider the service as a whole, beyond your own team.
6. Keep it simple and practical: remove steps that add nothing.
7. Optimize and automate: automate what can be automated, once the way of working has been optimized.

The most widely used ITIL processes

ITIL 4 describes 34 practices, split between general management, service management and technical management. In everyday language, people still often talk about ITIL processes. Not all of these practices are needed from day one. For an IT department, a handful of them form the foundation:

• Incident management: restore the service as quickly as possible after an interruption or degradation (a computer that won't start, an application that can't be reached), to reduce the impact on users.
• Service request management: handle routine user requests, such as granting access, installing software or providing equipment.
• Problem management: identify and address the root cause of recurring incidents, to keep them from happening again.
• Change management (“change enablement” in ITIL 4): assess the risks and impacts of changes to the information system, then organize their approval before implementation. ITIL distinguishes between standard, normal and emergency changes.
• Service level management: define service commitments (SLAs) with the service customer, then monitor compliance. A service level reflects the expected quality, measured by indicators such as response time or resolution time.
• Configuration management: keep the components of the information system and their relationships up to date, usually in a CMDB.
• IT asset management: track the lifecycle of hardware and software, from purchase to retirement.
• Knowledge management: capture solutions so that similar requests can be resolved faster.
• Service desk: the single point of contact between users and the IT department. It broadens the role of the helpdesk, which focuses on resolving incidents.

The distinction between an incident and a problem is one of the most important in ITIL. The incident is the effect, which you want to fix quickly. The problem is the cause, which you want to resolve for good. Ten “printer jammed” tickets are ten incidents, but they may point to a single problem: a faulty driver.

Why apply ITIL?

• Clearer support: every request follows a defined path, which reduces lost or duplicated tickets.
• Measurable commitments: service levels set clear deadlines and make it possible to track the quality perceived by the service customer.
• Fewer recurring incidents: problem management addresses root causes instead of repeating the same fixes, which reduces ticket volume.
• Better risk control: assessing impacts and organizing approval before taking action limits service interruptions.
• A shared vocabulary: internal teams, service providers and software vendors understand each other more easily.

ITIL also has its limits. Applied to the letter, it can weigh down a small team and create a risk of bureaucracy. ITIL itself recommends adapting it: start with the practices that address your current pain points, often incident and request management, then expand gradually.

How to implement ITIL successfully

Implementing ITIL is an organizational project before it is a tool project. Here are the most common steps:

1. Assess the current situation: how do requests come in today, who handles them, and what are the actual turnaround times?
2. Choose your first ITIL processes: usually incident and request management, followed by the service catalog.
3. Define roles: technicians, group leads, change manager.
4. Set realistic service commitments and share them with users.
5. Get the right tool: a spreadsheet or a shared mailbox quickly reaches its limits for tracking tickets, SLAs and IT assets, and increases the risk of things slipping through the cracks.
6. Train your teams: the ITIL Foundation certification, which is aimed at individuals rather than organizations, provides a common grounding. ITIL Foundation (Version 5) has been available since February 2026, and ITIL 4 Foundation certificates remain valid.
7. Measure and improve: monitor indicators and adjust practices, in the spirit of continual improvement.

Applying ITIL beyond IT

ITIL practices aren't limited to the IT department. HR, facilities and accounting teams also receive requests, have deadlines to meet and incidents to deal with: onboarding a new employee, creating a badge, repairing an office. Applying the same principles to these teams (service catalog, request management, service levels, knowledge base) is known as enterprise service management (ESM). ITIL 4 moves in this direction by presenting its practices as service management practices in the broad sense, not just IT practices. For users, the benefit is a single portal for all their requests. For the organization, it's a way to share the same methods and indicators across departments.

Putting ITIL into practice with GLPI

Once your organization is defined, a tool that structures day-to-day work helps you apply these practices over time. GLPI is built on ITIL practices and brings service management and IT asset inventory together in a single solution, for the IT department as well as the rest of the company.

• Incidents and requests: in GLPI's helpdesk software, every ticket is typed as an incident or a request and follows a defined lifecycle, from creation to closure. Business rules can automatically assign tickets to the right group.
• Service catalog: users submit their requests from a portal, with forms tailored to each type of need.
• Problems and changes: GLPI has dedicated objects that can be linked to the relevant tickets. A problem can group together the incidents it causes, and a change documents its impact analysis, approval and implementation plan.
• Service levels: SLAs and OLAs set response and resolution times, with escalation levels triggered before or after the deadline.
• Configuration and assets: GLPI's CMDB software references equipment, software and their relationships. Fed by GLPI Agent, the CMDB stays up to date, and each ticket can be linked to the relevant item.
• Knowledge: the knowledge base captures solutions, for technicians and users alike.

GLPI is free and open source software: using it requires no paid license. A GLPI Network subscription, in the Cloud or on your own servers, is offered through an integrator partner and also provides a contractual guarantee from the publisher. The partner's support on your project is not included in the subscription.

To explore these practices in the tool, you can try GLPI Network Cloud with a free 45-day trial.