ITIL 4
Definition
ITIL 4
ITIL 4 is the edition of the ITIL service management framework built around a service value system rather than a linear process lifecycle. It is no longer the newest edition, because the scheme’s owner has since begun marketing a further version.
The change from its predecessor was substantial. Earlier editions described a lifecycle of sequential stages; this one describes a value system with a flexible chain of activities that can be entered at different points.
That shift was a response to how software actually gets delivered now. Teams releasing continuously could not map their work onto a staged lifecycle without distorting it.
For outsourcing buyers the practical consequence is looser coupling — a provider can claim alignment with the framework while organising its own work quite differently, which makes “ITIL aligned” a weaker contractual phrase than it used to be.
Key takeaways
- The edition replaced a staged lifecycle with a service value system.
- Its structure suits continuous delivery better than the previous model did.
- A newer version is now being marketed, so this is no longer the current edition.
- “ITIL aligned” is a vaguer claim under this model and needs specifics in a contract.
How it works
The model describes a service value system that turns demand into value, with a service value chain of activities, a set of guiding principles, and a body of management practices spanning general management, service management and technical work.
The framework is positioned as broad rather than prescriptive. Its owner describes the scheme as the global best practice framework for digital product and service management, and now markets a newer version alongside it.
Adoption is wide by the owner’s own account. The same source reports more than 3 million certifications achieved worldwide, and says 90 percent of organisations report using ITIL practices.
| Element | What it describes | Contract relevance |
|---|---|---|
| Service value system | How demand becomes delivered value | Sets the shared model, not any obligation |
| Service value chain | Activities that can run in varying order | Explains why two providers differ in practice |
| Guiding principles | Advisory statements on how to work | Cultural rather than contractual |
| Management practices | Named capabilities such as incident and change | The part worth naming explicitly in an SLA |
Governance frameworks sit above this one rather than beside it. ISACA’s COBIT works at the governance layer with 40 governance and management objectives, answering who decides and who is accountable rather than how work flows.
The candid point is that flexibility cuts both ways. A framework that adapts to any delivery model also fails to guarantee any particular one, so a contract should name the specific practices required rather than cite the framework generically.
Examples
Buyers encounter the framework mostly through provider claims of alignment, which is precisely where the detail matters. These examples are all real, and none was selected for how well it reads.
A buyer writes “ITIL 4 aligned” into a contract and later finds the provider’s change process bears little resemblance to its own. The clause was too generic to enforce.
A better-drafted contract names incident, problem and change management explicitly, with defined interfaces. The framework supplies the vocabulary and the contract supplies the obligation.
A provider running continuous deployment maps its work to the value chain without adopting a staged lifecycle, which is exactly what the model was redesigned to permit.
A buyer moving from an older edition finds its existing IT support outsourcing process documentation still usable, since the practices survived the restructuring.
Related terms
Service management overlaps with governance, security and delivery methods, and the entries below draw the lines. Every definition below is one sentence, and every one names what it leaves out.
- service desk outsourcing: the contracted function where these practices are applied most visibly.
- IT support outsourcing: the wider support category the framework’s practices cover.
- service level agreement (SLA): the contractual instrument that turns framework language into obligations.
- agile outsourcing: the delivery approach this edition was reshaped to accommodate.
- digital transformation outsourcing: change programmes where service management is redesigned.
- infrastructure outsourcing: the platform layer these practices are most often applied to.
- ISO 27001: the security management standard, which is audited rather than adopted.
FAQ
What changed in ITIL 4?
It replaced the staged service lifecycle with a service value system and a flexible value chain, and reframed processes as management practices.
Is ITIL 4 still the current version?
No. The scheme’s owner now markets a newer version alongside it, so check which edition a provider or certificate refers to.
Does the framework certify an organisation?
No. Certification applies to individuals. There is no organisational certificate equivalent to an audited management system standard.
How does it relate to COBIT?
COBIT governs — who decides and who is accountable. This framework describes how services are designed, delivered and improved day to day.
Is “ITIL aligned” meaningful in a contract?
Weakly. Name the specific practices and interfaces you require, because the framework itself imposes no particular way of working.
Should buyers require the latest edition?
Not automatically. What matters is whether the provider’s actual processes meet your requirements, not which edition its staff studied.
Browse verified partners in the Outsource Accelerator directory and name the specific practices you need in the contract.
Independent
