Teams starting an ITIL implementation often ask for a definitive list of mandatory documents. The honest answer is that ITIL does not give one. It is a framework of guidance, not a certifiable standard with "shall" requirements. Even so, you cannot run incident, change or service request management consistently without writing down how it works.
This article sets out the documents most organisations end up needing, why each one exists, and how to avoid producing paperwork nobody reads.
ITIL guides you; it does not dictate documents#
ITIL 4 describes a service value system, guiding principles, four dimensions of service management and a set of management practices. It encourages you to adopt and adapt what suits your context. It also encourages you to keep things simple and to focus on value.
So the question is not "what does ITIL force me to write?" but "what must we document so people work consistently, and so we can show how services are managed?" Three things usually drive the answer:
- Customer and contract commitments, such as service levels and reporting.
- External requirements, such as an audit against ISO/IEC 20000-1, which is the certifiable service management standard. If certification is your goal, that standard sets what you must document. ITIL practices are a common way of meeting it.
- Operational risk. The more damage a mistake can cause, the more a clear written procedure is worth.
The core governance documents#
These set direction and ownership. Keep them short; most are a page or two.
- Service management scope and objectives. Which services, teams, locations and technologies are covered, and what you want to achieve.
- Service management policy. Management's intent for how services are planned, delivered and improved.
- Roles and responsibilities. Who owns each practice, who owns each service, and who approves what. A simple RACI table is usually enough.
- Service catalogue. A clear description of the services you offer, what each includes and how customers request it.
- Service level agreements and related targets. What you have agreed with customers or internal business units, and how you measure it.
- Continual improvement register. A running list of improvement ideas, owners, priorities and status.
Practice-level documents#
You do not need to document all of ITIL's practices on day one. Start with the ones that create the most daily friction, typically incident management, service request management, change enablement, problem management and service desk. The table below shows the typical documents for each.
| Practice | Typical documents | Purpose |
|---|---|---|
| Incident management | Procedure, priority and categorisation matrix, escalation rules | Restore service quickly and consistently |
| Service request management | Request fulfilment procedure, standard request models | Handle routine requests predictably |
| Change enablement | Change policy, change types and approval rules, change template, emergency change procedure | Balance speed with risk control |
| Problem management | Problem procedure, known error record format | Find and reduce root causes |
| Service configuration management | Configuration management approach, CMDB or asset record structure | Know what you run and how it connects |
| Release and deployment management | Release procedure, deployment checklist, rollback plan | Move changes into live use safely |
| Service level management | SLA template, reporting and review procedure | Agree, measure and review service levels |
| Supplier management | Supplier register, contract and performance review approach | Control third parties that support your services |
| Availability, capacity and continuity | Availability and capacity plans, service continuity plan | Keep services running under load and disruption |
If service continuity is a priority, it helps to align with business continuity work. Our guide on what documents you need for ISO 22301 implementation covers that side in more detail.
Records: the evidence that practices actually run#
Procedures say what should happen. Records show what did happen. Most records are generated by your service management tool, not written by hand, so the job is to make sure the tool captures them properly.
- Incident, request, problem and change records with timestamps, owners, priorities and outcomes.
- Change approvals showing who authorised what and when.
- Post-incident reviews for major incidents, with actions assigned.
- Service performance reports against agreed targets.
- Customer feedback and satisfaction results, and what you did with them.
- Training and competence records for service desk and technical staff.
- Review minutes from service review meetings and management reviews.
If an auditor, customer or manager asks "how do you know this works?", these are the records you point to.
How to build your document set without overdoing it#
- Map what already exists. Most IT teams have scattered runbooks, wiki pages and email rules. Collect them before writing anything new.
- Decide your scope and drivers. Are you improving internally, meeting customer contracts, or preparing for ISO/IEC 20000-1? The answer sets how formal the documents need to be.
- Prioritise by pain and risk. Begin with the practices where inconsistency causes outages, delays or complaints.
- Use a consistent template. Purpose, scope, owner, inputs, steps, outputs, records and review date. One format makes documents easier to write, read and audit.
- Write for the person doing the work. Use short steps, clear decision points and links to forms. Put the longer rationale in a separate policy.
- Put the tool and the documents in step. If the procedure says one thing and the ticketing workflow does another, people will follow the workflow.
- Control versions and review dates. Assign an owner to each document and review it on a schedule or after significant incidents and changes.
- Test with real people. Ask someone who did not write the procedure to follow it. Fix whatever confuses them.
Common mistakes include copying generic procedures without adapting them, documenting every practice before any are running, and writing documents that describe an ideal process nobody follows.
Frequently asked questions#
Is there a mandatory document list for ITIL?#
No. ITIL is guidance, so it does not mandate documents. What you need depends on your services, your customers and any standard you are working towards. If you plan to certify against ISO/IEC 20000-1, that standard defines the documented information it expects.
Can an organisation be certified in ITIL?#
Individuals can take ITIL training and examinations. Organisations are not certified against ITIL itself; they can be certified against ISO/IEC 20000-1. Many organisations use ITIL practices to meet that standard.
How much documentation is too much?#
It is too much when people cannot find it, do not follow it, or when it costs more to maintain than the risk it reduces. Document what supports consistent delivery and gives you evidence, and leave the rest to tooling and training.
If you would rather start from a structured base than a blank page, the ITIL Toolkit is a ready-to-use documentation toolkit you can adapt to your own services. You can also contact AdWiser to discuss how it fits your situation.
