IT service management based on ITIL

A practical IT service man­age­ment model

ITIL provides service-management guidance and practices; it is not an end in itself. A practical company model defines a service catalogue, owners, response targets, escalation paths, communication rules and a measurable quality report. It must balance the four dimensions of service management: organisations and people, information and technology, partners and suppliers, and value streams and processes. In this model, network-development planning, web-application improvement, infrastructure optimisation, solution design, equipment expansion and technical support are linked to a service, owner, priority and measurable outcome.

What is ITIL?

ITIL is service-management guidance that organises value, guiding principles, governance, the service value chain, management practices and continual improvement. This guide applies ITIL 4 terminology in a practical model adapted to the organisation's size, capabilities and risks. Current training paths should always be confirmed in PeopleCert materials.

How does ITSM work in daily business support?

ITSM means IT service management. A user contacts the service desk, a technician classifies and prioritises the request, and the responsible team handles it. Monitoring and configuration records support impact assessment, user updates, cause analysis and service-quality reviews.

Why is an IT service catalogue important?

A service catalogue states what IT provides, who uses each service, when support is available, which dependencies matter, what limitations apply and who makes business decisions. Without it, every request looks like an exception and expectations cannot be compared fairly with capacity, cost or risk. A proportionate catalogue also links SLA commitments, operational SLO targets, escalation rules and the configuration items that support each service.

Which terms should decision-makers know?

A small set of consistent definitions helps management and technical teams discuss the operating model without relying on marketing generalities.

• ITIL 4: service management guidance organised around value, practices, governance and continual improvement; its terminology provides the main frame for this guide.
• ITIL (Version 5): the phased evolution of ITIL; check current PeopleCert information before choosing a training path.
• ITSM: the operating model used to deliver, support, measure and improve information technology services.
• SLA: the service commitment agreed with a customer, including calculation rules, service hours and exclusions.
• SLO: a measurable operational service target, often managed internally to help the operating team protect the customer-facing SLA.
• CMDB: a controlled source of configuration items and relationships; a smaller organisation may use a proportionate configuration register instead.
• Virtline: an IT outsourcing and helpdesk partner that helps companies define and operate service processes.

What does ITIL mean for IT service management?

ITIL helps teams design, deliver, support and improve services from the perspective of outcomes valued by users and the business. In practice, this means connecting the service catalogue, roles, priorities, Incident Management, Service Request Management, Problem Management, Change Enablement, Monitoring and Event Management, measurable service levels and a continual-improvement register. Governance determines who can approve risk, exceptions and investment, while records of completed work show whether agreed controls work.

• Define which services IT supports, for whom, during which hours and with which business priority.
• Separate incidents, service requests, problems, Change Enablement records and administrative tasks so each follows an appropriate workflow.
• Set SLA and SLO measures, escalation paths, service owners and a reporting method based on reliable data sources.
• Link alerts and tickets to systems, suppliers and configuration items in a CMDB or controlled configuration register.
• Keep control and audit evidence for approvals, access, backup, changes and completed improvement actions.
• Use continual-improvement reviews to prioritise automation, monitoring, documentation and resilience work.

How does ITIL structure helpdesk and IT outsourcing?

The service desk is a shared point of contact and coordination, but phone, portal and email can feed one case register. Provide a fallback independent of the failed service. The team knows each ticket’s priority and impact, while reports show missed targets, recurring incidents and decisions needing an owner.

Which ITIL practices should a company implement first?

Not every organisation needs a full ITSM transformation. The best starting set depends on service impact, recurring disruption, regulatory context and the team's capacity. Most companies first need a reliable contact channel, distinct ticket types, controlled production changes, service-level reporting and a cadence for selecting the next improvement.

• Incident Management: restore normal service operation quickly and limit adverse business impact after a disruption.
• Change Enablement: assess risk, authorise changes and manage the change schedule to increase successful service and product changes.
• Service Request Management: handle predefined, user-initiated requests effectively and in a user-friendly way.
• Problem Management: identify actual and potential causes of incidents, manage workarounds and known errors, and reduce the likelihood and impact of incidents.
• Monitoring and Event Management: systematically observe services and components, then record, report and respond to selected changes of state.

Which services belong in the first IT service catalogue?

The first catalogue does not need to be large, but it must tell users what they can request and show management where IT accepts responsibility. Each entry should identify users, an owner, support hours, priority rules, dependencies, SLA commitments, SLO thresholds and important exceptions.

• Accounts, onboarding, offboarding, permissions, MFA, privileged access and remote access.
• Workstations, laptops, printers, mobile devices and supported user applications.
• Microsoft 365, email, Teams, SharePoint, OneDrive and shared mailboxes.
• Servers, networks, VPN, backup, Monitoring and Event Management and business-critical systems.
• Standard changes, critical incidents, service requests, recurring problems and administrative tasks.
• Configuration relationships, external suppliers, support contracts and evidence required for service reviews.

How does Virtline implement a practical operating model?

Virtline helps adapt IT service management to the real size, systems and risk profile of the organisation. The work defines contact channels, priorities, decision rights, escalation, reporting and a review cadence. The goal is less operational ambiguity, more predictable service delivery and an agreed list of improvements with priorities rather than a theoretical process library.

What makes a monthly ITSM report useful to the business?

A useful report supports decisions instead of only counting tickets. It combines service quality, recurring disruption, changes, configuration and security exceptions with recommendations that can reduce future likelihood or impact. The report should explain calculation methods and business context so SLA or SLO percentages are not presented without meaning.

• Ticket volumes by service, type and priority, with response, restoration and fulfilment times.
• SLA and SLO results with service hours, exclusions, data sources, breached targets and required decisions.
• Recurring incidents, problems under analysis, active workarounds, known errors and improvement candidates.
• Status of backup, Monitoring and Event Management, updates, privileged access and relevant security risks.
• Changes assessed, authorised, implemented, unsuccessful or rolled back through Change Enablement.
• ISO 27001 control context and applicable NIS2 or DORA evidence needs where they affect incidents, suppliers, resilience or management reporting. Applicable laws depend on the organisation and its activities. ISO 27001 is a voluntary standard; technical records support assessment but do not by themselves establish compliance or certification.
• A prioritised improvement plan showing expected user impact, cost, risk, owner and acceptance evidence.

What are the acceptance criteria for an organised service desk?

Applying ITIL practices should produce working support procedures and documentation that allows the company to verify them. The organisation should be able to see which services are supported, how tickets are classified, where service targets are at risk, which problems remain open and which actions reduce disruption. Every deliverable needs an owner, review date and acceptance criterion.

• A service catalogue with owners, users, support hours, priorities, dependencies, targets and exceptions.
• Distinct Incident Management, Problem Management, Change Enablement, Service Request Management and administrative workflows, including escalation and communication rules.
• A service desk that operates as a single point of contact and routes exceptions to technical, supplier and business decision-makers.
• A CMDB or proportionate configuration register linked to services, systems, suppliers, access rules, monitoring sources and known risks.
• SLA and SLO reports covering backlogs, recurring incidents, change outcomes, workarounds, known errors and agreed improvement actions.
• Control and audit evidence for approvals, configuration decisions, backup checks, security exceptions and completed reviews, aligned where relevant with ISO 27001, NIS2 or DORA requirements.
• An automation backlog for safe ticket routing, standard requests, alert enrichment, evidence collection and repeatable configuration checks.
• Discovery: map services, owners and dependencies, separate ticket types, check urgent escalation and establish baseline SLA/SLO measures.
• Implementation: agree the catalogue, practices and monitoring; every automation has an owner, test, rollback plan and acceptance criterion.
• Improvement: regularly review outcomes, changes and evidence, resolve urgent gaps and select further actions with deadlines.

Related articles

These resources extend the discussion into service synchronisation, risk-aware request handling and the operating choices involved in IT outsourcing.

Primary sources and currency

We verify version names, modules and transition dates in current notices from the owner of ITIL.

Contact us about IT service management

Describe the supported systems, how faults are reported, recurring problems and the desired change timeline. Virtline will propose the scope of work, accountable people, improvement priorities and a way to verify results.