Why this matters

Information Technology Infrastructure Library (ITIL) is the best-known framework for IT service management (ITSM). When its owner publishes a new version, teams ask the same questions: what changed, what must we relearn, and what can we keep? The risk is answering from marketing copy. Many training and consultancy pages describe ITIL 5 in detail, but they are not the owner, and they disagree with each other on dates and naming.

This topic separates what can be verified from the owner's own pages from what is still unconfirmed, and then shows how to prepare without waiting. The preparation is mostly work you should do anyway: name an owner for every product and service, bring AI under governance, and tie service work to outcomes people can measure.

Core concepts

What is verified (as of 20 October 2026). PeopleCert's certification page for the ITIL Foundation Bridge (Version 5) says the bridge is for ITIL 4 certification holders and covers only the updates in ITIL Foundation (Version 5). It lists digital product and service management across the lifecycle, including how ITIL reflects "modern digital and AI-enabled environments", updated language and core concepts, an "enhanced value creation approach" linking strategy, delivery, and measurable outcomes across the stakeholder ecosystem, and managing digital and AI complexity. The page does not give a release date for ITIL 5 itself.

What is not verified. Practice names and structure, how much of ITIL 4 carried over, formal release dates, and any separate AI governance publication. Third-party sources report figures for these. Treat them as leads to check on peoplecert.org, and do not repeat them as facts.

Three themes to plan around. The owner's wording supports three themes: a product orientation (digital products and services together), AI as part of the environment that service management must govern, and value expressed as measurable outcomes. Each connects to topics in this guide: product ownership (see Topic 2.8 — Product and Service Ownership), AI governance (see Topic 5.6 — AI Governance, Risk, and Compliance), and measurement (see Topic 7.3 — Measurement and Reporting).

What stays. ITIL 4 concepts remain the widely documented foundation: the service value system, guiding principles, four dimensions, and the service value chain (see Topic 1.4 — The Service Value System). Label statements "in ITIL 4" or "in ITIL 5" so readers know which they are reading.

Certification. ITIL 5 does not make ITIL a certifiable standard for organisations. People take certifications; organisations that want a certifiable standard look at ISO/IEC 20000 (see Topic 1.8 — Service Management Frameworks and Standards).

Best practices

  1. Read the owner first. Start from peoplecert.org and the ITIL publications you are licensed to use. Record what you read and the date in your own notes, and mark everything else as unconfirmed.
  2. Keep ITIL 4 working. Do not stop practices that work because a new version exists. Change a practice when the owner's guidance and your own evidence both say it needs changing.
  3. Make an estate map. List your services, digital products, platforms, and AI systems, each with a named owner. Gaps in ownership are the first finding, whatever version you use.
  4. Give products a lifecycle owner. A product owner is accountable from idea to retirement, and a service owner for the service that delivers it. Relabelling services as products without changing ownership changes nothing.
  5. Put AI under governance early. Identify AI systems in use, assign an accountable owner, define oversight and review, and connect them to your risk register. Check the law that applies to you; this guide gives no legal advice.
  6. Ask for evidence of value. For each service, say which outcome it supports and how you would know. Measures belong to the team that owns the service; see the companion Service Management Metrics book.
  7. Use the continual improvement habit. Treat adoption as a backlog of small changes with feedback, not a programme with a big-bang date.
  8. Plan capability, not only certificates. Choose training paths from the published scheme, but judge readiness by whether teams can run the practice. A certificate is not organisational compliance.
  9. Phase the transition. Compare current practices with the owner's guidance, decide what to keep, change, or add, and sequence the changes against your release calendar.
  10. Re-check before each decision. The publication is phased. Set a recurring reminder to re-read the owner's pages before you commit budget or change policy.

Questions to discuss with your team

Which of our services, products, platforms, and AI systems have no named owner today? Ownership is the hinge of the product and AI themes. Start by listing what exists; people often discover systems nobody remembers adopting. Expect surprise at shadow tools and embedded AI features. Follow up by asking who would be called at 3 a.m.

What do we believe about ITIL 5 that we read on a blog rather than from the owner? Naming second-hand beliefs makes the verification task concrete. Teams tend to repeat percentages, dates, and practice names with great confidence. Sort each belief into verified, plausible, and unknown. Follow up by assigning someone to check each against the owner's page.

Where do we use AI in our services today, and who oversees each use? This tests whether governance exists in practice. Answers range from "nowhere" to a long list including vendor features switched on by default. Listen for oversight that is a policy document only. Follow up by asking what would tell us an AI system was wrong.

Which service could we describe to a customer in terms of an outcome rather than an uptime target? Value-focused practice starts with outcomes. Teams often default to availability percentages. Push for the customer's sentence: what is better for them when the service works. Follow up by asking how we would notice if the outcome got worse while the target stayed green.

What in our current ITIL 4 practice is working so well that we should refuse to change it without evidence? This guards against change for its own sake. Expect pride in a mature incident or change process. Ask for the evidence that it works, which also prepares the baseline for later comparison. Follow up by asking what evidence would change our minds.

What is the smallest first step we can take this quarter that helps whichever version we end up following? Small steps beat a transition programme built on unverified details. Typical answers are the estate map, an AI inventory, or one outcome-based measure. Choose one with an owner and a date. Follow up by agreeing when we will re-read the owner's publications.

In practice: a service management example

A regional logistics company's IT department runs a customer portal, a warehouse system, and a recently added AI assistant that drafts replies for the service desk. The service manager hears that ITIL 5 stresses products and AI governance and is asked for a transition plan within a month.

The team resists drafting a plan from slide decks. Instead it spends a week building an estate map: eleven services, three digital products, two platforms, and four AI-enabled features, one of which was switched on by default in a vendor tool and had no owner. It then reads the owner's certification pages, records what they say in a one-page note, and lists everything else as unconfirmed. Each AI feature gets an owner, a review date, and a line in the risk register. The service desk lead decides that every AI-drafted reply is read by an agent before it is sent, and that agents record when they change a draft materially.

What changes: the unowned feature is either adopted by a named owner or switched off, and the leadership team gets a short estate map rather than a framework tour. What remains hard: the department cannot yet say which outcomes each service supports, and the estimate of how many AI drafts were edited depends on agents recording edits consistently. The plan for next quarter is to pick two services and write their outcomes down with the customers who use them.

Four perspectives

Product and delivery teams

Expect to be asked who owns the product after it ships. Treat the live service as part of the product, and keep the AI features you build in the same estate map as everything else.

Service and operations teams

Your practices are the working foundation. Keep them running, record the evidence that they work, and be ready to show how AI assistance is overseen when it touches tickets, alerts, or changes.

Leadership and governance

Fund ownership and verification before funding a transition programme. Ask for the estate map, the AI inventory, and a list of ITIL 5 statements the team has verified from the owner.

Customers and users

You should be able to see what a service is for in your own terms, and to learn when AI is part of how you are served. Ask for both.

Agile, AI, automation, and analytics

Agile

Treat adoption as continuous improvement: a small backlog of changes, reviewed with stakeholders, adjusted as the owner publishes more. Caution: a "transition programme" with one go-live date is the opposite of this and hides the verification work.

AI

ITIL 5, as the owner describes it, covers AI-enabled environments. In practice, give every AI use an owner, a human review point, and a way to detect errors. Caution: do not ask an AI assistant to summarise ITIL 5 from memory; it may produce confident, wrong details. Give it text you have read from the owner and ask it to quote that text.

Automation

Automate the estate map where you can: pull service and product lists from your catalogue and configuration data, and flag entries with no owner. Caution: automation exposes data quality problems, so keep a person responsible for resolving each flag.

Analytics

Track a handful of adoption signals, such as the share of services and AI systems with a named owner, and the number of ITIL 5 statements marked verified. Caution: counts of "owners named" can be gamed by naming anyone; pair them with a check that the owner knows. See the Service Management Metrics book (topic 1.8, ITIL 5 measurement and value outcomes).

Common failure modes

  • Repeating blog claims as fact. Mark each claim verified or unconfirmed, and link only the owner's pages for the verified ones.
  • Relabelling services as products. Change ownership and lifecycle accountability, or the label is decoration.
  • AI governance as a document. Name owners, controls, and review dates, and test that people follow them.
  • Assuming ITIL 4 practices carry over unchanged, or are all obsolete. Compare practice by practice against the owner's guidance and your own evidence.
  • Treating certificates as compliance. Measure whether teams can run the practice, not who passed an exam.
  • Big-bang transition. Phase changes and re-check the owner's publications between phases.

Maturity model

Dimension Initiate Develop Standardise Manage Orchestrate
Source discipline ITIL 5 knowledge comes from blogs and hearsay Some owner pages read, not recorded Verified and unconfirmed claims recorded with dates Claims re-checked before each decision Teams share a living, dated verification log
Ownership Services, products, and AI systems have unclear owners Owners named for main services Estate map with an owner for every item Ownership gaps reviewed and closed on a cadence Owners coordinate across teams and suppliers
AI governance AI use unknown or ungoverned Main AI uses listed Oversight, risk, and review defined per system Errors and overrides measured and reviewed Governance adapts as AI and rules change

Checklist

  • We read the owner's ITIL 5 pages and recorded what they say, with the date.
  • Every ITIL 5 claim we use is marked verified or unconfirmed.
  • We have an estate map of services, products, platforms, and AI systems.
  • Every item on the map has a named owner.
  • Every AI system has an oversight point, a review date, and a risk register entry.
  • We identified which ITIL 4 practices work and kept the evidence.
  • We chose one small first step with an owner and a date.
  • We scheduled a recurring re-check of the owner's publications.

AI prompts

Build an estate map from material you paste in.

I will paste a list of our services, digital products, platforms, and AI-enabled features: [paste list].
Build a table with columns: item, type (service, product, platform, AI system), owner (use only what I provided; write "unknown" otherwise), and one question I should ask about it.
Ask me clarifying questions first if the list is ambiguous. Mark every assumption. At the end, list what you are unsure of.

Sort ITIL 5 statements into verified and unconfirmed.

Below are statements we have heard about ITIL 5: [paste statements].
Below is text I copied from the owner's published pages: [paste owner text].
For each statement, say whether the owner text supports it, contradicts it, or says nothing. Quote the supporting words exactly. Do not use outside knowledge. List what you are unsure of.

Draft an AI oversight table for review.

Our AI-enabled features are: [list features and what each does].
Draft a table with columns: system, risk if wrong, human review point, owner [leave blank if not given], review date [leave blank]. Do not invent legal obligations; list the questions we must ask our legal adviser instead.
Ask clarifying questions first, mark assumptions, and list what you are unsure of.

AI skills

  • itil-5: use to build an estate map, a gap analysis, and a phased adoption plan, with ITIL 5 claims flagged unconfirmed.
  • maturity-models: use to turn the maturity table into a team self-assessment.
  • risk-register: use to record AI risks and owners.

Key sources

  • PeopleCert, ITIL Foundation Bridge (Version 5) certification page: the owner's own description of the update topics; the main verified source here.
  • Wikipedia, "ITIL": a neutral overview of ITIL's history and versions; check its ITIL 5 statements against the owner.
  • Wikipedia, "IT service management": the wider field ITIL sits in.

References

  1. ITIL Foundation Bridge (Version 5) — PeopleCert — https://www.peoplecert.org/browse-certifications/it-governance-and-service-management/ITIL-1/itil-foundation-bridge-version-5-4158
  2. ITIL — Wikipedia — https://en.wikipedia.org/wiki/ITIL
  3. IT service management — Wikipedia — https://en.wikipedia.org/wiki/IT_service_management
  4. Artificial intelligence — Wikipedia — https://en.wikipedia.org/wiki/Artificial_intelligence
  5. AIOps — Wikipedia — https://en.wikipedia.org/wiki/AIOps
  6. Product management — Wikipedia — https://en.wikipedia.org/wiki/Product_management
  7. DevOps — Wikipedia — https://en.wikipedia.org/wiki/DevOps
  8. Goodhart's law — Wikipedia — https://en.wikipedia.org/wiki/Goodhart%27s_law