What is ITIL 4 Measurement and Reporting? Metrics, KPIs and practice guide
ITIL 4 Measurement and Reporting is the service management practice that supports good decision-making and continual improvement by collecting relevant data across operational, tactical, strategic, and customer-experience measurements. Defined by AXELOS, it turns service data into insights via Critical Success Factors (CSFs), KPIs, and metrics, feeding Continual Improvement and Service Level Management so IT decisions stay evidence-based and aligned with stakeholder outcomes.
Why does ITIL 4 Measurement and Reporting matter today?
Only 28% of AI use cases in I&O (Infrastructure and Operations) fully meet ROI expectations, per a Gartner survey of 782 I&O leaders (Gartner, 2026). The reason is rarely technology. It is the absence of disciplined performance analytics: KPIs missing, baselines unclear, cadence too slow for the CIO. The Measurement and Reporting practice closes that performance analytics gap.
Many ITSM teams still treat measurement as a technical exercise: counting tickets, charting MTTR. Too narrow. The AXELOS practice guide defines the practice as "supporting good decision-making and continual improvement by decreasing levels of uncertainty" (AXELOS, 2020). If a report does not change behavior, it is overhead. For regulated sectors, disciplined reporting also underpins obligations under frameworks such as DORA and NIS2.
A balanced practice produces four flows of evidence (operational, tactical, strategic, customer experience), routing each to the audience that can act. It is the connective tissue between your broader ITIL practices and the wider ITSM framework that holds them together.
What does the ITIL 4 Measurement and Reporting practice actually do?
AXELOS describes the practice as a discipline for collecting valid data, analyzing it, and reporting findings, so stakeholders decide better. It stops opinion from masquerading as evidence. The ITIL 4 foundation materials place it in general management, serving every value stream.
The practice carries three responsibilities. First, define what good looks like: the CSFs (Critical Success Factors), KPIs (Key Performance Indicators), and metrics. Second, secure data quality: Gartner estimates poor data quality costs enterprises USD 12.9 million per year (Gartner, 2024). Third, deliver insight at the right cadence to the right audience.
The team owns the framework; numbers come from the practices being measured: change, incident, problem, service desk, capacity. Discipline lives in governance, not the data layer. Without it, dashboards sprawl into charts no one trusts.
How do the four measurement types differ in audience and cadence?
A mature practice distinguishes four measurement types that together form a complete performance analytics view. Each targets a different decision horizon, audience, and (for DACH compliance) cadence.
The four types of measurement in the ITIL framework
| Measurement type | What it measures | Primary audience | Example KPIs |
|---|---|---|---|
| Operational |
Technical performance of components and services |
Service Operations, SREs (Site Reliability Engineers), NOC (Network Operations Center) | Availability %, MTTR (Mean Time To Resolve), capacity utilization |
| Tactical |
Effectiveness of practices and value streams |
Practice Owners, Service Owners | Change success rate, first-contact resolution, SLA achievement |
| Strategic | Achievement of organizational and IT objectives | CIO, Executive Leadership | IT cost as % of revenue, time-to-market, OKR attainment |
| Customer Experience | Perceived quality and outcome value | Business stakeholders, end users | CSAT, NPS, Digital Experience Score, effort score |
The point most teams miss is routing each flow to the audience that can act on it, at a cadence that audience can use. A mature practice, like Matrix42 Service Management, traces every reported figure back to a system of record.
How do CSFs, KPIs and metrics fit together in ITIL Measurement and Reporting?
The biggest cause of dashboard sprawl is conflating these three layers. The AXELOS practice guide is precise about the hierarchy.
Critical Success Factor (CSF)
A condition that must be met for an objective to be achieved. Example: "Changes are deployed without disrupting business services."
Key Performance Indicator (KPI)
A small, quantifiable indicator showing whether a CSF is on track. Example: "Change success rate ≥ 98% for high-impact changes."
Metric
A lower-level measurement that feeds a KPI. Example: "Number of failed changes per release window."
A well-structured service typically carries three to five CSFs, each with two or three KPIs, and ten to twenty metrics. Anything beyond is noise. Ownership sits with a Service Measurement Manager or IT Performance Lead reporting to the CIO. In leaner organizations the role merges with Service Level Management: SLM defines what matters; Measurement and Reporting proves whether it happened.
The question of which KPIs actually earn their place in an ITSM program is settled here: a KPI is useful only when it rolls up to a stated CSF. Otherwise you report volume, not value.
Why do most ITIL measurement programs fail, and how do you avoid the trap?
Only 12% of I&O leaders exceed CIO expectations, often because they cannot translate operational metrics into business-relevant reporting (Gartner via Idevnews, 2024). Four pitfalls cause most damage: measuring what is easy, vanity reporting, neglecting customer experience, and treating reports as compliance theatre.
The antidote is governance. Every KPI needs a named owner, a stated CSF, a cadence, a decision it informs, and a retirement date. The ITSM reporting metrics lifecycle matters as much as the metric: add deliberately, review quarterly, retire ruthlessly. A clean Configuration Management Database (CMDB) is the foundation, since every KPI eventually traces back to a configuration item. Gartner reports 54% of I&O leaders cite cost optimization as their top AI goal (Gartner, 2025); without governance, that stays a slogan.
The forward-looking layer is AIOps. Gartner predicts 40% of organizations deploying AI will adopt dedicated AI observability by 2028 (Gartner, 2026). That extends the practice into model drift and bias, leading indicators that should feed the practice directly.
How does Measurement and Reporting relate to other ITIL practices?
Measurement and Reporting rarely operates alone within the wider set of ITIL 4 practices. It draws its raw numbers from the practices it measures and hands its insight to the practices that act on the results, so the value of the practice depends on those links being deliberate rather than accidental.
Service Level Management
Service Level Management negotiates the targets in SLAs and OLAs; Measurement and Reporting supplies the evidence that proves whether those targets were met. The two practices share a continuous feedback loop.
Continual Improvement
Continual Improvement depends on this practice for its data. Measurement and Reporting establishes the baselines, surfaces improvement opportunities, and validates whether a change delivered the benefit it promised.
Incident, Problem, and Change Enablement
These operational practices generate most of the source data. Resolution times, change success rates, and recurring problems feed directly into the operational and tactical measurement flows.
Service Configuration Management
Service Configuration Management is the ITIL 4 practice that maintains accurate information about configuration items and their relationships. Measurement and Reporting relies on the configuration data it produces, because every KPI eventually traces back to a configuration item and the service model it sits within.
Key takeaways
Evidence, not activity
The Measurement and Reporting practice turns service data into evidence-based decisions and decision-ready performance analytics.
Four flows, four audiences
The four measurement types each serve a different audience, decision horizon, and reporting cadence - balance all four rather than over-investing in operational telemetry.
Every KPI ladders to a CSF
Every KPI must roll up to a CSF; AXELOS recommends 3 to 5 CSFs, 2 to 3 KPIs each, 10 to 20 metrics.
Avoid the common traps
Vanity metrics, weak data quality, and ignored customer experience stall most programs.
Watch the leading indicators
AIOps and AI observability are leading indicators, governed inside the ITIL best practices framework.
Reporting that drives decisions, not just dashboards
Matrix42 Service Management ties every KPI to a single system of record, so each figure on a dashboard traces back to a real configuration item, ticket, or change rather than a spreadsheet. Role-based dashboards route operational, tactical, strategic, and customer-experience views to the people who can act on them. Built-in analytics and AI flag anomalies and trends early, so reporting shifts from describing activity to driving the next decision.
FAQs
ITIL 4 Measurement and Reporting is the practice that supports good decision-making and continual improvement by decreasing levels of uncertainty. Per AXELOS, it collects relevant data across operational, tactical, strategic, and customer-experience measurements, then analyzes, evaluates, and reports it to stakeholders. The practice underpins evidence-based IT management and feeds insights into Continual Improvement, Service Level Management, and Portfolio Management.
ITIL 4 defines four measurement types: operational (technical performance such as availability and capacity), tactical (effectiveness of practices and value streams), strategic (achievement of organizational objectives and OKRs), and customer-experience (perceived quality, satisfaction, and outcomes). Each type targets different audiences and decision horizons. Mature organizations balance all four rather than over-investing in operational telemetry alone, which can hide business-impact blind spots.
Critical Success Factors (CSFs) are the conditions that must be met for an objective to be achieved. KPIs are the few quantifiable indicators that show whether a CSF is on track. Metrics are the lower-level measurements that feed KPIs. Per AXELOS, a service may have 3-5 CSFs, each with 2-3 KPIs, supported by 10-20 metrics - a structured hierarchy that prevents dashboard sprawl.
Ownership usually sits with a Service Measurement Manager, IT Performance Manager, or Continual Improvement Manager reporting to the CIO or Head of Service Management. In smaller organizations the role is merged with Service Level or Continual Improvement ownership. The owner is accountable for the measurement framework, reporting cadence, data quality, and ensuring reports drive decisions rather than sitting unread in dashboards.
Common KPIs include percentage of SLAs achieved, mean time to resolve (MTTR), first-contact resolution rate, customer satisfaction (CSAT) and Net Promoter Score, percentage of changes successful, cost per ticket, and improvement initiatives completed on schedule. Mature organizations add business-outcome KPIs such as revenue protected by IT, time-to-market for new services, and employee digital-experience scores rather than infrastructure metrics alone.
Continual Improvement depends on Measurement and Reporting for evidence. Steps 3 ('Gather the data') and 4 ('Process the data') of the seven-step improvement model are executed by this practice. Reports surface improvement opportunities, baselines for change, and post-implementation validation. Without disciplined measurement, Continual Improvement becomes opinion-driven; with it, every improvement decision is grounded in observable service performance.
Service Level Management negotiates the targets in SLAs and OLAs, while Measurement and Reporting captures the data that proves whether those targets are met. The two practices share a feedback loop: SLM defines what matters to customers, Measurement and Reporting quantifies it, and the resulting reports drive both contractual conversations and improvement plans. Together they make service performance transparent to business stakeholders.
Frequent pitfalls include measuring what is easy rather than what matters, reporting volume over value (vanity metrics), focusing on operational data while ignoring customer experience, building dashboards no one acts on, and treating reports as compliance theatre. Per AXELOS, organizations also fail when they don't define CSFs first, leaving performance analytics disconnected from end-to-end service value.
Related Articles
What is IT Service Management (ITSM)?
IT Service Management (ITSM) is a structured approach that organizations use to design, deliver, manage, and continually improve IT services to align closely with business goals.
The ITSM Buyer's Guide: How to choose IT Service Management software for your business
Your ITSM vendor choice shapes your IT operations for years. It affects how cost-effectively you manage daily service delivery, so compare your options carefully.
NIS2 and DORA compliance guide: Securing European businesses through automated IT governance
European businesses must balance technological innovation with strict regulatory compliance. The EU has introduced NIS2 (Network and Information Systems Directive) and DORA (Digital Operational Resilience Act) to enhance cybersecurity and operational resilience across sectors critical to the economy.
How AI transforms Service Management: A European guide to responsible implementation
AI in service management refers to artificial intelligence technologies that automate, augment, and predict IT service management operations. These technologies range from AI assistants that help agents find information faster, to autonomous AI agents that resolve issues without human intervention, to proactive AI that prevents incidents before they occur.
Sources
- AXELOS / PeopleCert (2020). Measurement and reporting management: ITIL 4 Practice Guide. https://www.axelos.com/resource-hub/practice/measurement-and-reporting-management-itil-4-practice-guide
- Gartner (2025). Survey: 54% of Infrastructure & Operations Leaders Are Adopting AI to Cut Costs. https://www.gartner.com/en/newsroom/press-releases/2025-10-29-gartner-survey-54-percent-of-infrastructure-and-operations-leaders-are-adopting-artificial-intelligence-to-cut-costs
- Gartner (2026). AI Projects in Infrastructure and Operations Stall Ahead of Meaningful ROI Returns. https://www.gartner.com/en/newsroom/press-releases/2026-04-07-gartner-says-artificial-intelligence-projects-in-infrastructure-and-operations-stall-ahead-of-meaningful-roi-returns
- Gartner (2026). 40% of Organizations Deploying AI Will Use AI Observability to Monitor Model Performance by 2028. https://www.gartner.com/en/newsroom/press-releases/2026-05-12-gartner-predicts-40-percent-of-organizations-deploying-ai-will-use-ai-observability-to-monitor-model-performance-by-2028
- Gartner (2024). Data Quality. https://www.gartner.com/en/data-analytics/topics/data-quality
- Gartner via Idevnews (2024). Only 12% of Infrastructure & Operations Leaders Exceed CIO Expectations. https://www.idevnews.com/stories/7565/Gartner-Says-Only-12-of-Infrastructure-Operations-Leaders-Exceed-CIO-Expectations
- European Banking Authority (2024). Joint Technical Standards on major incident reporting (DORA). https://www.eba.europa.eu/activities/single-rulebook/regulatory-activities/operational-resilience/joint-technical-standards-major-incident-reporting
- Heise / BSI (2026). The clock is ticking: NIS2 registration deadline at BSI expires on March 6, 2026. https://www.heise.de/en/news/The-clock-is-ticking-NIS2-registration-deadline-at-BSI-expires-on-March-6-2026-11182664.html