ITIL 4 SLM cheat sheet

Service level management (SLM) is the practice of setting clear business-based targets for service levels and ensuring delivery, support, and products are delivered against those targets; it is not a reporting-only function.

Core SLM vocabulary: service level = one or more metrics defining expected or achieved service quality; service level target = a committed value for a metric; service level agreement (SLA) = documented agreement between provider and customer on required services and expected service levels.

Utility (fit for purpose) and warranty (fit for use) are the two components of service value; SLAs must cover warranty dimensions - availability, capacity, continuity, security - not just functional features.

SLM sits at the boundary between demand and supply: it converts customer outcomes and business needs into measurable targets, then feeds those targets into the service value chain and supplier contracts.

A service level is not the same as an operational metric: CPU utilisation is a component measure; 'order fulfilment available 99.9% of agreed hours' is a service level because it is stated from the consumer's perspective.

Customers and users are distinct groups: customers agree SLAs and fund services; users consume them. SLM must satisfy both, and user experience can diverge from contractual performance.

SLAs must be measurable, achievable, and mutually agreed; targets set without data on current performance create unachievable commitments and erode trust.

SLM supports the 'engage' and 'deliver and support' value chain activities by ensuring service levels are agreed, monitored, and reported against business-relevant outcomes.

The ITIL 4 service value system (SVS) has five components: guiding principles, governance, service value chain, practices, and continual improvement; SLM is one of the 34 management practices within the practices component.

The four dimensions of service management - organisations and people, information and technology, partners and suppliers, value streams and processes - must each be considered when defining service levels.

The service value chain has six activities: plan, improve, engage, design and transition, obtain/build, deliver and support; SLM is most active in engage and deliver and support, and informs plan and design and transition.

Guiding principles relevant to SLM include 'focus on value' (targets must reflect customer outcomes), 'collaborate and promote visibility' (shared data with customers), and 'keep it simple and practical' (few meaningful metrics).

Governance in the SVS is provided by the governing body; SLM supplies the performance evidence that governance uses to evaluate, direct, and monitor service delivery.

The 'obtain/build' activity requires SLM to align supplier and partner agreements with customer-facing SLAs so that underpinning commitments are not weaker than what is promised to the business.

Continual improvement in the SVS applies to SLM itself: the practice should periodically review whether targets remain relevant, achievable, and aligned to changing business needs.

SLM links to other practices: service catalogue management (what is offered), service desk (user-facing performance), capacity and availability management (feasibility of targets), and supplier management (underpinning contracts).

SLM workflow: engage stakeholders, agree requirements, define and document service levels, monitor and measure, report, review, and improve; each cycle feeds the next.

Service level requirements (SLRs) are the customer's stated needs before negotiation; they are translated into SLAs after feasibility assessment against capability, capacity, and cost.

Underpinning contracts (UCs) are agreements with external suppliers, and operational level agreements (OLAs) are internal agreements between teams; both must support the customer SLA.

Service reviews are structured meetings with customers to review performance against SLA, discuss issues, and agree improvements; they are distinct from day-to-day incident handling.

The service catalogue is the single source of truth for what is offered; SLAs should reference catalogue service entries so targets are traceable to defined services.

Negotiation technique: present measured baseline performance, model the cost of higher targets, and propose target tiers (for example, bronze/silver/gold) rather than accepting arbitrary figures.

SLM should define escalation paths and service credits or remedies for missed targets, and clarify exclusions (planned maintenance windows, force majeure, customer-caused failures).

Customer satisfaction surveys and user experience measures complement SLA metrics; SLM uses both contractual and experiential data to judge service quality.

SLA types: customer-based (one customer), service-based (one service for all customers), multi-level (corporate, customer, and service levels nested), and internal SLAs between internal provider units.

An SLO is a target value or range for a service level metric; SLAs commit to SLOs, and SLIs (indicators) are the measurements used to evaluate whether SLOs are met.

SLAs should state scope, service hours, responsibilities of both parties, service levels and targets, exclusions, reporting frequency, review cycle, and remedies for breach.

Service hours define when the SLA applies (for example, 08:00–18:00 business days); availability percentages must be calculated against agreed service hours, not 24x7 unless contracted.

Availability formula: availability % = (agreed service time − downtime) / agreed service time × 100; downtime excludes agreed exclusions such as planned maintenance.

Multi-level SLAs require alignment: the corporate SLA sets overall commitments, customer SLAs tailor them to specific customers, and service SLAs define delivery for each service.

SLAs should avoid over-specification: too many metrics dilute focus and increase measurement cost; prefer a small set of business-relevant measures with clear owners.

SLAs are living documents: they are reviewed at agreed intervals, updated when services or business needs change, and version-controlled with change records.

Measurement hierarchy: SLIs are raw measurements, SLOs are target thresholds, and SLA compliance is the aggregate judgment of whether SLOs were met over the reporting period.

Error budget concept: if an SLO allows 99.9% availability over a period, the permitted downtime is the budget; consuming it faster than planned signals a need to slow change or invest in reliability.

Reporting should be audience-appropriate: executives need outcome and trend summaries, service owners need metric detail, and operational teams need real-time dashboards.

Dashboards should show current value, target, trend, and breach status; colour coding without context is insufficient - include the measurement window and data source.

Continual improvement model: what is the vision, where are we now, where do we want to be, how do we get there, take action, did we get there, keep momentum.

SLM improvement actions should be prioritised by business impact and recorded in a continual improvement register with owners, dates, and success measures.

Trend analysis over multiple periods distinguishes systemic underperformance from isolated incidents; a single month's breach may not justify renegotiating an SLA.

Regular service reviews close the loop: performance data, root causes of misses, agreed actions, and updated targets feed back into the SLM cycle and the service value chain.