IT Service Management Training Template and Checklist
A ready-to-run ITSM training program and the adoption checklist to go with it. Teach the practices, then see which teams are actually working to them.
Reviewed by Pradeep Arora, Chief Strategy Officer
- A seven-module ITSM program, covering incident, problem, change, service desk, SLAs and the CMDB
- An adoption checklist mapped to your services and tooling
- A team maturity matrix that shows where the practice is thin
- An operating rhythm calendar from daily triage to change review
What is inside
- A seven-module ITSM program, covering incident, problem and change management, the service desk, SLAs and the CMDB, with audience and coverage for each.
- A 10-point adoption checklist you can map to your own services and tooling, and mark off as the practice takes hold.
- A team maturity matrix that scores each team and shows where the practice is thin.
- An operating rhythm calendar so triage, change review and reporting run to a plan rather than by habit.
Who it is for
Anyone who has to plan what people learn, and answer for whether it landed.
- L&D and training teams
- People managers and team leads
- Heads of function and department
- HR business partners
- Compliance and risk teams
- Onboarding and enablement teams
- Operations and delivery leads
- COOs and HR directors
How to use this template in 4 steps
- Pick your format. Download the PDF to share, the Word file to edit, or the Excel file to work in live. All three are free.
- Make it yours. Adapt the sections, fields and wording to your team, roles and process so it fits how you actually work.
- Put it to work. Fill it in, circulate it to stakeholders for sign-off, or roll it out to your team.
- Track and improve. Review it on a set cadence and refine it as your goals, roles and priorities change.
What is inside
- A seven-module ITSM program, covering incident, problem and change management, the service desk, SLAs and the CMDB, with audience and coverage for each.
- A 10-point adoption checklist you can map to your own services and tooling, and mark off as the practice takes hold.
- A team maturity matrix that scores each team and shows where the practice is thin.
- An operating rhythm calendar so triage, change review and reporting run to a plan rather than by habit.
Adapt the modules and checklist to your own services, tooling and ways of working. This is a starting structure to build from, not a substitute for ITIL guidance or your organisation's agreed process.
The training program template
Seven modules that teach ITSM as a set of connected practices, not a ticketing tool. Run the full set for teams new to service management, then use the role-specific modules for incident, problem and change managers.
| Module | Audience | Duration | What it must cover |
|---|---|---|---|
| 1. ITSM foundations | All IT staff | 30 min | What service management is, the idea of services and value, and how the practices connect. |
| 2. The service desk | Desk agents and leads | 35 min | Single intake, logging and categorising, first-line resolution, and clear communication with users. |
| 3. Incident management | All IT staff | 35 min | Restoring service fast, priority from impact and urgency, escalation, and major incident handling. |
| 4. Problem management | Problem and ops teams | 30 min | Finding root cause, known errors and workarounds, and preventing recurrence. |
| 5. Change enablement | Change and ops teams | 35 min | Assessing, approving and scheduling changes, change types, and reducing change-related incidents. |
| 6. SLAs and service levels | Leads and service owners | 25 min | What an SLA is, agreeing realistic targets, and reporting performance without gaming it. |
| 7. Configuration and the CMDB | Ops and change teams | 30 min | Configuration items, relationships, keeping the CMDB accurate, and using it in incident and change. |
Delivering the modules and a short knowledge check through an LMS gives you dated completion per person and per team, so a service owner can confirm every agent has covered incident priority before a major incident tests it.
The adoption checklist
Ten steps to move IT support from a reactive ticket queue to a working service management practice. Tick items to track your own progress, it stays in this browser. The download has the same list with an owner column.
- Team trained on the incident, problem and change distinctionFoundationsOn start
- A single service desk intake for all requestsService deskOngoing
- Incident priority defined from impact and urgencyIncidentOngoing
- Escalation paths and major incident process agreedIncidentQuarterly
- Recurring incidents raised as problemsProblemOngoing
- Root causes tracked as known errors with workaroundsProblemOngoing
- Change process with assessment and approval in placeChangeOngoing
- SLAs agreed and reported againstService levelsMonthly
- CMDB kept accurate and used in incident and changeConfigurationOngoing
- Maturity tracked by team, not just by ticket volumeGovernanceQuarterly
The most common gap is problem management. A team can close incidents quickly and still let the same root cause generate the same tickets every month, because nothing feeds it into a problem.
Team maturity at a glance
The checklist tells you what a team is missing. This matrix tells you which teams are behind. Score each team on the five practices that most affect how well services are supported. In Excel the readiness and gaps calculate as you type.
| Team | Staff | Incident | Problem | Change | Service desk | SLAs | Ready |
|---|---|---|---|---|---|---|---|
| Service desk | 16 | 2 | 2 | 2 | 2 | 2 | 100% |
| Infrastructure | 10 | 2 | 1 | 2 | 1 | 1 | 70% |
| Applications | 9 | 1 | 0 | 1 | 1 | 1 | 40% |
| Networks | 7 | 2 | 1 | 1 | 1 | 1 | 60% |
| End-user support | 12 | 1 | 1 | 1 | 2 | 0 | 50% |
| Coverage at required | 60% | 20% | 40% | 40% | 20% | 64% |
Applications is the exposure: no problem management and thin on incident handling, so the same application faults keep coming back as fresh tickets.
The operating rhythm calendar
| Timing | Action | Owner |
|---|---|---|
| On joining | ITSM foundations and service desk modules in the first week. | Service desk lead and L&D |
| Daily | Triage new tickets, set priority, and progress open incidents. | Service desk |
| Weekly | Review recurring incidents and raise problems. | Problem manager |
| Per change window | Assess, approve and schedule changes at the change review. | Change manager |
| Monthly | Report SLA performance and review service levels. | Service owner |
| Quarterly | Score maturity by team and coach the weakest practice. | IT manager |
How to run it
- Separate incidents, problems and changes
They need different handling. An incident restores service, a problem removes the cause, a change is planned work. Teach the difference first.
- Give the service desk one front door
A single intake for requests and incidents, so nothing arrives by a side channel and gets lost.
- Define priority, not just severity
Priority combines impact and urgency, so the team works the right ticket first rather than the loudest one.
- Close problems, not just incidents
Feed recurring incidents into problem management so the root cause gets removed, not repeatedly restored.
- Control change deliberately
An assessed, approved and scheduled change process, so improvements do not become the next incident.
- Track maturity by team
Roll it up per team so a group working around the process is visible before it causes an outage.
Frontline teams reach 45 percent-plus completion on Disprz when training is delivered in short, mobile modules, the format this program is built for.
Common mistakes this pack prevents
- Treating every ticket the same, so an incident and a planned change get handled identically.
- Multiple side channels into the team, so requests arrive by chat or email and never get logged.
- Setting priority by who shouts loudest instead of impact and urgency.
- Closing incidents fast but never raising problems, so the same root cause recurs every month.
- Uncontrolled changes that become the next outage, with no assessment or rollback plan.
Which format should you use?
| Format | Best for | What is inside | Editable | Size |
|---|---|---|---|---|
| Sharing and print | The full template, formatted to print or circulate | No | 55 KB | |
| Word | Editing the wording | Every section as editable text you can adapt | Yes | 86 KB |
| Excel | Filling it in live | The grid and fields set up as a working spreadsheet | Yes | 66 KB |
Questions people ask
What is IT service management?
Is this the same as ITIL?
What is the difference between an incident, a problem and a change?
Does the Excel tracker work in Google Sheets?
Do I have to fill the form three times?
ITSM only helps if teams actually work to the practice. That is the part we help embed.
Bring your service desk leads to a 30-minute working session. We will show how Disprz delivers ITSM training in short modules and rolls maturity up by team, so your next service review is based on how support really runs.