What is ITIL in simple terms?

ITIL is a widely used set of good practices for running IT as a service: how to handle faults and requests, approve changes, agree service levels and keep improving. It was created by the UK government and is now owned by PeopleCert. It is a framework rather than a law or a standard, so organisations adopt the parts that fit their size and risk.

What is the difference between ITIL and ITSM?

ITSM is the discipline of managing IT as services that meet agreed needs; ITIL is one framework describing how to do it well. You can practise IT service management without ITIL, using ISO/IEC 20000, COBIT or your own methods, but most ITSM tools, courses and job descriptions use ITIL's vocabulary, which makes it the common starting point.

What are the main ITSM processes?

The main ITSM processes are incident management, service request management, problem management, change enablement and service level management, supported by the service desk, asset and configuration management, knowledge management and monitoring. ITIL describes 34 practices in all, but most mid-sized organisations and schools gain most of the value from these core practices first.

Is ITIL still relevant?

Yes. ITIL remains the common vocabulary of IT service management, ITIL 4 was designed to work alongside Agile, DevOps and Lean, and PeopleCert released ITIL (Version 5) in 2026 with guidance on digital products and governing AI. What has changed is how it is applied: less paperwork, more automation and more focus on value. Treated as a rigid rulebook, it breeds bureaucracy; adapted, it improves service.

Can an organisation be ITIL certified?

No. ITIL certification is for individuals, from Foundation level upwards. An organisation that wants its service management certified uses ISO/IEC 20000-1, audited by an accredited certification body. Many organisations run ITIL-aligned practices without any certification, and a tender that asks for ITIL alignment is usually looking for evidence of documented, working processes and regular reporting.

ITIL and IT service management (ITSM) explained

Q: What is IT service continuity management?

IT service continuity management makes sure critical IT services can be recovered after a serious disruption, such as ransomware, fire or a long power outage. It ranks services by business impact, sets how much data and time each can afford to lose, and keeps tested recovery plans. It works alongside business continuity planning and your backup and disaster recovery arrangements.

ITIL is the best-known framework for IT service management (ITSM): the practices an organisation uses to plan, deliver, support and improve the IT services its people rely on. This guide covers ITIL 4 and Version 5, alternatives, tools, KPIs and costs for South African organisations, and how Arke Technologies in Johannesburg runs ITIL-aligned service management.

Request an IT assessment See our IT service desk

Insights

ITIL and IT service management (ITSM) explained

Last reviewed: September 2026, 21 min read

On this page

What is IT service management (ITSM)?

Last reviewed: September 2026.

A working definition of IT service management: the way an organisation designs, delivers, supports and improves the IT services its people use, managed as services rather than as boxes and software. Email, the finance system and the boardroom Wi-Fi are each a service, with users, an owner, an agreed level of quality and a cost. ITSM is the discipline that keeps each one working to that agreement.

That is the practical meaning of IT service management. Plain IT management asks "is the server up?"; service management asks "can the payroll team run payroll today, and who is accountable if they cannot?" That shift changes what gets measured, what is reported to the board and what is fixed first.

A fuller IT service management description has three parts: an IT service management system (the policies, processes, roles, tools and records), a framework describing good practice, of which ITIL is the best known, and the service itself, delivered against a service-level agreement (SLA). This guide, one of our insights and guides, covers all three.

A support agent in a headset points to a detail on her screen during a call.

Why it matters: the benefits of IT service management

The importance of IT service management shows in the questions boards, councils and governing bodies ask: what does IT cost, what does it deliver, and what happens when it fails?

One front door. Every fault and request is logged in one place, and every ticket has an owner.
Predictable service. Incidents are prioritised from P1 critical outage to P4 low-impact request, with targets agreed in the SLA.
Fewer repeat faults. Problem management removes root causes.
Safer change. Changes are assessed and approved before they are made.
Evidence for governance. Ticket, change and SLA records give audit committees facts, not anecdotes.

What is ITIL? The IT Infrastructure Library explained

ITIL, originally short for IT Infrastructure Library, is a body of good practice for IT service management. It began in the late 1980s at the UK government's Central Computer and Telecommunications Agency, which documented how well-run IT departments worked, and it is now owned by PeopleCert. Most ITSM tools, courses and job descriptions use its vocabulary.

ITIL is a framework, not a standard or a law. Nobody audits you against it, and you adopt the parts that fit: a school might start with incident and request management, a municipality with change and service continuity. People earn ITIL certification; organisations cannot.

ITIL has been revised several times. ITIL v3 described a five-stage service lifecycle of strategy, design, transition, operation and continual improvement, language many job descriptions still use. ITIL 4 (2019) reframed the guidance around value and collaboration. ITIL (Version 5), released by PeopleCert from February 2026, widens the scope to digital products and services and adds guidance on governing AI, while keeping ITIL 4's guiding principles, four dimensions and 34 practices; the two versions run in parallel for a transition period (PeopleCert, 2026). Because that core carries over, this guide uses ITIL 4's structure and notes where Version 5 differs. The ITIL Foundation book is the usual first IT service management book to read.

How ITIL works: principles, dimensions and the value chain

ITIL 4 describes a service value system: principles, governance, activities and practices that turn demand into value, with continual improvement running through all of them. Version 5 keeps the principles and dimensions and sets the activities out as an end-to-end lifecycle for digital products and services. These elements double as sound IT service management principles and best practices, whether or not you adopt ITIL by name.

ITIL element	What it says	What it means in practice
Seven guiding principles	Focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work across the whole system; keep it simple and practical; optimise and automate	Improve what exists before replacing it, in small steps, and automate a process only once it works
Four dimensions	Organisations and people; information and technology; partners and suppliers; value streams and processes	A service fails if any one is neglected: skills, tools, outside providers or workflow
Service value chain (ITIL 4)	Plan; improve; engage; design and transition; obtain or build; deliver and support	The activities every service passes through, from idea to daily support
Continual improvement	A repeating cycle from vision to measurement	Monthly reviews that change something, not just report it

This is modern IT service management: less weight on rigid process documents, more on value, flow and feedback, alongside Agile, DevOps and Lean. AI now sorts tickets and drafts summaries, and Version 5 adds guidance on governing it. Our view is that AI recommends, people decide, and every automated action is logged; see AI governance.

ITSM processes: the ITIL practices most organisations need

ITIL describes 34 management practices, a number Version 5 keeps; ITIL 4 groups them into 14 general management, 17 service management and 3 technical management practices. Few organisations need all of them. These IT service management functions, or ITSM processes, are the core most organisations, public bodies and schools implement first.

Practice	What it does	What good looks like
Service desk	The single point of contact for users	One number, one queue, every ticket owned
Incident management	Restores service after a fault	P1 to P4 priorities by business impact, with SLA clocks visible
Service request management	Fulfils routine requests: access, devices, software, joiners and leavers	Standard requests follow documented runbooks
Problem management	Finds and removes root causes	Repeat incidents fall month on month
Change enablement (formerly change management)	Assesses and authorises changes	Every change logged, risk-assessed and approved by the right authority
Service level management	Agrees, measures and reports service targets	SLA performance reviewed monthly with the business
IT asset and configuration management	Records what you own and how it connects	An accurate asset register and configuration records
Monitoring and event management	Detects faults before users report them	Alerts become tickets automatically
Knowledge management	Captures fixes and answers	Users and technicians find answers without escalating
Information security management	Protects the confidentiality, integrity and availability of information	Security incidents handled through the same disciplined process

These are the IT service management capabilities to expect from any serious provider or in-house team. For how a desk runs day to day, see IT service desk and helpdesk.

What is IT service continuity management?

IT service continuity management (ITSCM) makes sure critical IT services can be recovered after a serious disruption: ransomware, a fire, a failed server room or a long power outage. A business impact analysis ranks services by how much their loss would hurt, then sets how much data each can afford to lose (the recovery point objective) and how long it can be down (the recovery time objective).

In South Africa, load-shedding and cable theft make this routine rather than theoretical. The plan links to your backup and disaster recovery arrangements, names who invokes it and is tested, because an untested recovery plan is a hope. Boards should see the evidence; see King IV and technology governance.

IT services financial management: what each service costs

Financial management for IT services, which ITIL calls service financial management, answers the question finance directors and bursars ask most: what does each service cost, and is it worth it? It covers budgeting over a year or contract term, costing people, licences, hardware and support to each service, and, where useful, charging departments (chargeback) or simply showing them what they consume (showback). For public bodies, IT services financial management also supports PFMA and MFMA reporting; see PFMA, MFMA and ICT procurement.

IT service management frameworks and methodologies compared

ITIL is not the only option, and these IT service management frameworks and practices are often combined. The right IT service management framework depends on whether you need operating guidance, a certifiable standard, board-level governance or faster delivery.

Framework or methodology	What it is	Who is certified	Best used for
ITIL (4 and Version 5)	Good-practice framework for IT service management	Individuals	Designing and running service management day to day
ISO/IEC 20000-1	International standard for a service management system	Organisations, through accredited certification bodies	Proving service management to customers, auditors and tender panels
COBIT	ISACA's framework for the governance and management of enterprise IT	Individuals	Board-level IT governance and King IV Principle 12
ISO/IEC 27001	International standard for an information security management system	Organisations	Security controls; overlaps with ITSM on incidents, change and assets
Agile, DevOps and Lean	Ways of working that shorten delivery cycles and remove waste	Individuals, under various schemes	Software teams, and faster, safer change
SIAM	Service integration and management across several suppliers	Individuals	Organisations that buy IT services from several providers

A combination that suits many mid-sized organisations and public bodies: ITIL practices for operations, ISO/IEC 27001-aligned controls for security, and COBIT or King IV for board reporting. ISO/IEC 20000 certification is usually worth pursuing only when customers or a tender demand it. See our ISO 27001 certification guide and what is cyber security.

IT service management vs service delivery

IT service management and delivery are related but not the same. Service delivery is providing the service: answering the call, fixing the laptop, keeping the server running. Service management is the system around it: the agreements, measures and improvements that decide how delivery happens. IT service delivery management is the daily work of keeping delivery on the SLA. When you outsource, you keep the service management decisions (which services, at what level and cost), and your provider is accountable for delivery.

IT service management software, tools and platforms

IT service management software records every ticket, change and asset, runs the workflows and produces the reports. At its simplest, it is a ticketing system with SLA clocks, a self-service portal and a knowledge base. The IT service management tools on the market fall into five groups.

Type of toolset	Suits	Watch for
Enterprise ITSM suites	Large enterprises and public entities with many practices and integrations	Licence cost per agent, long implementations, specialist administration
Cloud service desk platforms	Mid-sized organisations and schools wanting a quick start	Thin change and asset features in lower tiers
Open source ITSM applications	Teams with in-house skills and a tight budget	You carry hosting, upgrades, security patching and support
Ticketing inside a managed service provider's platform	Organisations that outsource IT support	Whether you can see and export your own ticket history
Modules inside an ERP or business system	Organisations standardised on one platform	Narrow scope outside that platform

The best IT service management software is the one your team will keep current. Research from Gartner, such as its Magic Quadrant reports, gives large enterprises a long list, but most organisations should shortlist IT service management solutions on a few tests: ITIL-aligned workflows, SLA clocks matching your P1 to P4 priorities, self-service and knowledge, an asset register, a service dashboard managers will read, and an API.

Most ITSM tools are now sold as cloud services, so ask where the data is held and whether you can export all of it: tickets hold personal information, and POPIA applies. A connector or API should let an alert in Microsoft Azure or a failed backup open a ticket automatically. Faults in business systems such as SAP Business One or Microsoft Dynamics 365 Business Central should reach the same service desk, not a separate queue.

Our own platform, Hesper, is built for managed service providers and in-house IT teams: it raises monitoring faults as tickets, ties ticketing to SLA clocks and gates riskier automated repairs behind a recorded human approval. It launches in November 2026, with early access open until then; see Hesper monitoring and ticketing.

IT service management KPIs and metrics

These IT service management KPI examples cover speed, quality, stability and cost. They belong in a monthly service report and on a dashboard the business can read.

KPI	What it tells you	Watch out for
SLA attainment by priority	Whether P1 to P4 targets are met	A good average hiding missed P1s
First-contact resolution rate	How much the desk fixes without escalating	Tickets closed early to protect the figure
Mean time to restore service	How long users go without a service	Averages hiding a few very long outages
Repeat incidents	Whether problem management works	No problem records at all
Change success rate	Share of changes made without causing an incident	Changes made outside the process
Backlog age	Whether work is piling up	Old tickets closed in bulk before a review
User satisfaction	How the service feels to staff	Surveys with too few responses to mean anything

Keep IT service management metrics honest: report trends, not single months, and read the tickets behind any number that looks too good.

Roles, skills and organisational structure

ITIL defines roles, not job titles, and in most organisations one person holds several.

Role	Accountable for
Service owner	A service end to end, including its cost and performance
Practice owner	How a practice, such as change enablement, works across the organisation
Service desk team	Logging tickets and fixing what it can at first contact
Incident, problem and change managers	Major incidents, root causes and change approvals
Service level manager	Agreeing targets with the business and reporting against them

In a large enterprise these roles may sit under a head of IT service management or an IT service management director reporting to the CIO; in a school, the IT manager may hold most of them. The organisational structure matters less than clear accountability. The skills an IT service management professional needs are process discipline, clear writing, calm incident handling and the ability to explain risk to people who are not technical.

ITIL certification and IT service management training

ITIL certification is the best-known IT service management certification for individuals. Since February 2026 PeopleCert has offered the ITIL (Version 5) scheme alongside ITIL 4 for a transition period, and an ITIL 4 Foundation certificate remains a valid starting point for the new pathways (PeopleCert, 2026). The Version 5 scheme runs in levels:

Level	For	What it covers
ITIL Foundation	Anyone working in or with IT services	The vocabulary, guiding principles and core practices; the entry point to every pathway
Product, Service and Experience modules	Practitioners designing, running and improving services	Managing digital products and services end to end, and the experience of the people who use them
Practice modules	Practitioners running specific areas	Groups of related practices, such as monitoring, support and fulfilment
Strategy and Transformation modules	Managers and IT leaders	Direction, planning and leading change
Practice Manager, Managing Professional and Strategic Leader; ITIL Master	Experienced and senior practitioners	Designations for completing set combinations of modules, with ITIL Master the highest

Accredited training organisations deliver the courses and exams; fees vary with format and whether the exam voucher is included, so compare like with like and confirm which version a course teaches before booking. The IT Service Management Forum (itSMF), a not-for-profit professional association with national chapters in many countries, publishes guidance and runs events where peers compare tools and approaches.

How to build an IT service management plan in seven steps

An IT service management strategy does not start with a tool. This IT service management plan example suits a company, public body or school. Each step produces a document the steering committee can approve, and together they form the presentation you take to the board or council.

Write the vision statement
For example, an IT service management vision statement for a municipality: "Every member of staff gets IT help in one place, knows when it will be fixed, and sees the service improve every quarter."
Assess where you are
A maturity model review (ITIL publishes its own) scores each practice from ad hoc to optimised.
Define services and service levels
List services, owners and users; agree P1 to P4 priorities, with response and resolution targets matched to the business impact of downtime.
Write the policies and procedures
An IT service management policy template covers scope, roles, priorities, escalation, change approval, access to personal information under POPIA and review dates.
Choose and configure the tool
Fit it to your processes, import users and assets, and build the reports before go-live.
Train and launch
Short, role-based training, and clear guidance for staff on logging tickets.
Review and improve
A monthly service review, a quarterly report to the executive or council, and an annual refresh.

What IT service management costs, and what drives the price

Last reviewed: September 2026.

Most of the cost is people, tools and the scope of service, and most organisations buy it through a mix of three routes.

Route	What you pay for	What drives the cost
Run it in-house	Staff, a tool licensed per agent, training and certification	Team size, hours covered, tool tier, staff turnover
Outsource to an IT service management company	A monthly fee per user under an SLA	Users and devices, scope, service levels, on-site needs
Consulting and implementation	A defined project: assessment, process design, tool set-up	Number of practices, integrations, data to migrate, training

For market context, Johannesburg IT support technicians earn about R21,054 a month on average (Indeed, September 2026), before tools, training, leave cover and management. Published South African managed IT rates run from about R180 to R400 per user per month (matnet.co.za, September 2026), with some providers listing R450 (MiBOT, September 2026); what each fee includes varies, so compare scope as well as price. Published rates for IT project work run from about R550 to R750 an hour ex VAT (matnet.co.za, September 2026).

Arke Technologies prices managed IT per user per month, set after an assessment, and quotes consulting and implementation per project; see how our managed IT pricing works. Read managed IT services cost in South Africa and managed IT vs in-house IT.

Risks in IT service management, and how to prevent them

Risk	How to prevent it
Process for its own sake	Start where you are, and add process only where a KPI shows the need
Buying the tool first	Design the process, then configure the tool; an ITSM transformation that starts with software automates today's confusion
Everything is urgent	Write P1 to P4 definitions into the SLA and apply them consistently
No problem management	Review repeat incidents monthly and give each problem an owner
Change as bureaucracy, or no change control	Pre-approve low-risk standard changes; keep formal approval for the rest
Ticket data as a privacy and security risk	Design security in: role-based access, logging, and a written operator agreement under POPIA with any provider that processes the data
Lock-in	Confirm before signing that tickets, assets and knowledge articles can be exported

For the privacy side, see our POPIA compliance checklist.

Questions to ask an IT service management company

If you are comparing IT service management services from outside providers, ask:

Which ITIL practices do you run, and can we see a sample monthly service report?
Are P1 to P4 priorities and their targets written into the SLA?
Who reviews the service with us, and how do we escalate?
Where is our ticket data held, and can we export all of it?
At exit, do we receive our data, credentials, documentation and ticket history?

How Arke Technologies delivers ITIL-aligned service management

Arke Technologies (Pty) Ltd runs an ITIL-aligned service desk practice from Johannesburg for organisations, public bodies and schools across South Africa: incident, request, problem and change management, SLA reporting, escalation paths, change control and documented runbooks. Through IT consulting, we act as an IT service management consultant and design the practice for your own team to run; through IT outsourcing we run it for you; or we share the load through co-managed IT. Larger estates are covered under enterprise IT services.

Monitoring and automation. Our monitoring checks each managed computer every 15 minutes and logs faults as tickets automatically. Standard repairs run from our own tooling, and riskier ones need a recorded human approval.
Accountable access. Every remote session is approved and logged on our own platform, built on open-source RustDesk.
Governance and reporting. An SLA fixing scope, P1 to P4 priorities and the targets agreed with you; a named service lead; a monthly service review and report. Board-level IT service governance sits with our IT governance, risk and compliance service.
Compliance. POPIA built into how tickets and access are handled; ISO 27001-aligned controls; King IV Principle 12 reporting; PFMA and MFMA disciplines for public bodies.
Procurement fit. A Level 1 B-BBEE contributor, giving 135% procurement recognition (sworn affidavit available on request). Company documents, our CSD supplier number and SARS tax compliance status are available on request. Buy through a proposal and SLA, against a purchase order, or through a tender, for which we complete the standard bidding documents; see procuring from Arke.
Continuity. One contract and one accountable team, remote-first, with technicians hired for experience, education and certifications in step with the contracts we sign. You own your data, credentials and documentation, including ticket history and runbooks, and we hand everything over on exit.

Engagements run from discovery and assessment to a proposal, an SLA, onboarding and a monthly service review; see managed IT services.

Last reviewed: September 2026, 21 min read

Put your IT service management on a firmer footing

Tell us how support, change and reporting work today, and we will start with an assessment and a plan you can act on, whoever runs the service.

Request an IT assessment

Get our guides by email

Plain, sourced guides for the people who decide on and buy technology, sent to your inbox.

Frequently asked questions

How much does IT service management cost in South Africa?

Outsourced IT service management is usually bought as managed IT, at published South African rates of about R180 to R400 per user per month (matnet.co.za, September 2026). In-house, a Johannesburg IT support technician earns about R21,054 a month on average (Indeed, September 2026), before tools, training and management. Arke Technologies prices per user per month after an assessment, and quotes consulting per project.