ISO Compliance Insights & Best Practices
CART
ISO Compliance Insights & Best Practices
ITIL 5 is the first substantial revision of the framework since 2019, and it changes more than the version number on the cover. PeopleCert began the phased release in 2026, and the parts that matter to anyone maintaining service management documentation are structural: the value chain has a different shape, the practices sit in different categories, and artificial intelligence has moved from an absent topic to an examinable one.
This guide covers what actually changed, what carried over untouched, and what an organisation running ITIL 4 today should do about it. The short version: less than you fear, but not nothing.
Start with the reassurance, because it is the part most coverage buries. The seven guiding principles are the same seven. The four dimensions are the same four. There are still 34 management practices and they still have the same names. If you have written an incident management policy against ITIL 4, that policy describes a practice that exists identically in the current edition.
What changed sits in three places.
| Element | ITIL 4 | ITIL 5 |
|---|---|---|
| The value system | Service Value System (SVS) | ITIL Value System |
| The value chain | Service value chain, six activities | Product and service lifecycle, eight activities |
| Practice categories | Three: general (14), service (17), technical (3) | Two: product and service management (22), general management (12) |
| Framing | Services | Digital products and services |
| Artificial intelligence | Not addressed | AI capability model; dedicated AI governance publication |
| Value streams | Mentioned | Own chapter, with a mapping method |
Note what is absent from that table. No practice was withdrawn. No practice was renamed. No guiding principle changed. The framework also stopped expanding “ITIL” as an acronym — it is now simply the name, with “Version 5” used only where the edition needs distinguishing.
ITIL 4’s service value chain had six activities: plan, improve, engage, design and transition, obtain/build, and deliver and support. The current edition replaces them with an eight-stage product and service lifecycle:
Two things about this list are easy to get wrong, and most summaries do.
First, it is not a cycle. The word lifecycle invites a picture of eight steps performed in order, and the framework explicitly rejects that reading, describing the activities as stepping stones a given piece of work crosses in whatever order the work requires. A managed service provider that builds nothing still performs discover, transition, operate, deliver and support.
Second, these eight activities are the value chain. They did not arrive alongside it. The organisation’s value chain is the complete set of these activities, and a value stream is one path through them for one output. Getting that distinction wrong produces documentation that uses the two words interchangeably, which is the single most common defect in service management documentation written from secondary sources.
The current edition also adds value chain patterns — recurring shapes determined by whether the organisation builds the product, consumes it, or both. An internal IT function performs all eight with acquire dominant over build; a commercial product vendor may perform only the first five.
ITIL 4 sorted its 34 practices into general management, service management and technical management. The technical category no longer exists. ITIL 5 uses two: 22 product and service management practices and 12 general management practices.
Five practices actually changed category. The three former technical management practices — deployment management, infrastructure and platform management, and software development and management — moved into product and service management. So did information security management and service financial management, which had been general management practices.
The arithmetic reconciles exactly: 12 general is the old 14 minus those two, and 22 product and service is the old 17 service plus the three technical plus the same two. Every other practice sits where it did, under a category with a new name.
This matters less than it sounds. Categorisation affects how a practice is catalogued, not what it does, who owns it or what documentation it needs. In a documentation set the change touches one column of one table.
The most genuinely new material in ITIL 5 is artificial intelligence, and it is handled better than the marketing suggests. Rather than a chapter of exhortation, the framework provides a functional classification — six capabilities describing what an AI system actually does:
The value of this is governance, not taxonomy. Risk rises down that list as the distance between the AI and a human decision grows. Clarification helps someone decide; coordination decides and acts. Classifying a use case tells you how much oversight it needs, which is a far more useful question than whether the vendor calls it AI.
A dedicated AI governance publication and a separate qualification path sit alongside the core guidance. The four dimensions absorbed the topic too, with new material on how AI changes what people are accountable for.
The ITIL 5 continual improvement model keeps its seven steps. Two are reworded, and the rewording is more than cosmetic:
Both shift the model from a verdict delivered once to a question asked continuously. Improvement stops being an initiative that concludes and becomes a capability that persists. If your improvement register closes items on delivery rather than on measured benefit, that is the habit the change is aimed at.
PeopleCert has been clear that the release is phased and that existing ITIL 4 certifications remain valid. An organisation implementing against ITIL 4 documentation is not non-compliant; it is working to a previous edition of a framework, not a withdrawn standard. There is no deadline and no certification at stake for your management system.
That makes the transition a documentation exercise you schedule rather than an emergency. In practice:
Our earlier piece on whether ITIL 4 is still current covers the certification side of that decision, and ISO 20000 vs ITIL is worth reading if you are also carrying a certifiable standard — nothing in this edition changes that relationship.
For the full picture from the source, PeopleCert publishes the ITIL Foundation (Version 5) syllabus and scheme details directly.
No. PeopleCert states the release is gradual and that ITIL 4 certifications remain fully relevant. ITIL 4 is a previous edition, not a withdrawn one, and the practices are identical across both.
Thirty-four, the same number as ITIL 4, with the same names. They are grouped into two categories instead of three.
No. The same seven principles, with added emphasis on applying them together as a system rather than selecting whichever suits the decision.
The value chain. Six activities became eight, and they are no longer described as a cycle. Any document written around the old six needs rebuilding; most other documents need a vocabulary pass at most.
Not for the framework’s sake. A bridge route exists for individuals holding ITIL 4 Foundation who want the current credential, but an organisation’s documentation carries no certification that expires.
Rewriting a service management documentation set around an eight-activity lifecycle, two practice categories and a new AI governance layer is several weeks of work from a blank page. Our ITIL Toolkit provides 57 editable templates built against the current edition — a policy for each of the eight lifecycle activities, all 34 practices in their correct categories, the AI governance set, value stream mapping, experience management, and a matrix mapping every practice to every activity. It includes a transition guide recording exactly what moved from ITIL 4, so you can see what changed rather than take it on trust.
August 31, 2026
August 31, 2026
August 31, 2026
August 31, 2026
August 31, 2026