Someone has told you an ITIL audit is coming. Your first question is probably: what will they actually check?
That is a fair question, because ITIL (a set of good practices for IT service management, or ITSM) is a framework, not a rulebook with a pass mark. This guide explains what an "ITIL audit" usually means and how to prepare, step by step.
First, find out what kind of audit it is#
ITIL 4 is published by PeopleCert (formerly AXELOS). It describes a service value system, four dimensions of service management and 34 management practices, such as incident, change and service request management. At the time of writing, ITIL certifications are awarded to people, not to companies. So an "ITIL audit" is rarely a certificate audit of ITIL itself.
In practice, the phrase usually means one of these:
- An internal audit. Your own team or internal auditors check that IT follows the processes you have written down.
- A customer or client audit. A client checks how you run the services they buy from you.
- An ISO/IEC 20000-1 audit. This is the international standard for a service management system, and companies can be certified against it. ISO publishes a technical specification, ISO/IEC TS 20000-11, dated 1 September 2021, on how ISO/IEC 20000-1 relates to ITIL (ISO/IEC JTC 1/SC 40/WG 2, 2021).
- A maturity or gap assessment. A consultant or manager rates your practices against ITIL 4 and lists improvements.
Ask the audit sponsor three things: who is auditing, what is in scope, and what criteria they will use. The answers shape everything below.
Step 1: Agree the scope and the criteria#
Write a one-page scope note. For instance, a 50-person software company might scope the audit to its hosted product support: the service desk, the on-call team and the change process for production.
Then list the practices in scope. Most audits focus on a core group:
- Incident management
- Problem management
- Change enablement
- Service request management
- Service level management
- Service configuration management
- Continual improvement
Do not try to cover all 34 practices unless the auditor asks. A smaller scope done well beats a wide scope done thinly.
Step 2: Check that your documentation exists and matches reality#
Auditors usually start with documents. They want to see what you say you do. Then they check whether you do it.
For each in-scope practice, confirm you have:
- A short policy that states the intent and who owns it.
- A procedure with clear steps, roles and hand-offs.
- Defined records, such as a ticket template or change form.
- Targets, such as response and resolution times, where they apply.
- A review date and a version number on each document.
The most common problem is a procedure that nobody follows. If your change procedure says every change needs approval, but half your changes skip it, fix one or the other before the audit. Do not hand the auditor a document that your team ignores.
Step 3: Gather evidence, not just documents#
Evidence is proof that a process actually ran. A good habit is to pick a sample for each practice and make sure the full trail is there.
| Practice | Example evidence to have ready |
|---|---|
| Incident management | A sample of closed tickets showing logging, priority, assignment, resolution and closure |
| Problem management | Records of recurring incidents, root cause notes and follow-up actions |
| Change enablement | Change records with risk assessment, approval and a post-change review |
| Service request management | Request records with approvals and fulfilment dates |
| Service level management | Agreed targets and regular performance reports |
| Continual improvement | An improvement register with owners, status and outcomes |
Pick your samples before the auditor does. Open each one and ask: could a stranger follow what happened? If a ticket says only "fixed", add notes now where that is appropriate. Never alter old records to hide gaps. Auditors notice, and it harms trust. Record the gap and show how you are fixing it.
Step 4: Run a gap assessment and a mock audit#
A gap assessment compares what you do with what the framework or standard expects. A mock audit tests it in practice. Both are simple:
- List the criteria (ITIL 4 practice guidance, ISO/IEC 20000-1 or your customer's requirements).
- For each item, mark it as met, partly met or not met.
- Note the evidence you found, or the evidence missing.
- Assign an owner and a due date to every gap.
- Ask someone outside the process to interview the team and check a few samples.
The person running the mock audit should not be the process owner. A fresh pair of eyes spots things the team has stopped seeing.
Step 5: Prepare your people#
Auditors talk to the people doing the work, not only the managers. Before the audit:
- Brief the team on the scope and the dates.
- Tell them to answer honestly and describe what they really do.
- Make sure each person can explain their own role in the process.
- Agree who will be the main contact and who handles document requests.
- Remind everyone that it is fine to say "I don't know, but I can find out".
On the day, keep a simple log of every request and finding. Clarify anything you do not understand. If you disagree with a finding, ask what evidence supports it, and calmly provide yours.
Common gaps to look for#
- Emergency changes that bypass the process with no review afterwards.
- Tickets closed without confirmation from the user.
- No link between incidents and problems, so the same fault keeps coming back.
- Service targets that are written but never measured.
- Out-of-date asset or configuration records.
- Improvement ideas that are discussed but never logged or tracked.
- Documents with no owner or review date.
Frequently asked questions#
Can a company be "ITIL certified"?#
At the time of writing, ITIL certifications are for individuals. Companies that want independent certification of their service management system usually look at ISO/IEC 20000-1. Check the current position with PeopleCert and your certification body, as schemes can change.
How long does it take to prepare?#
It depends on your scope, your current documentation and how many gaps you find. A small, well-run team with good records needs far less time than one starting from scratch. A gap assessment early on gives you a realistic estimate.
Do we need to cover all 34 ITIL practices?#
Not usually. Cover the practices in your agreed scope. Most audits concentrate on a core group, such as incident, change, request, problem and service level management. Confirm this with whoever is auditing you.
If you would rather not start from a blank page, the ITIL Toolkit offers editable policies, procedures, checklists, examples and a gap assessment checklist aligned with ITIL 4. If you want to talk through your audit scope, you can contact AdWiser.
Sources#
- ISO/IEC JTC 1/SC 40/WG 2 – published standards, ISO/IEC JTC 1/SC 40/WG 2, 2021

Leave a Comment