Incident, problem and change management: how the three practices connect
Lesson
02
UNIVERSITY · LESSON 01
Last reviewed 27 September 2026 · Service Desk Compare reviewers
At the edges. Logging is the easiest stage to automate, because channels such as portals and chat collect structured fields. Resolution of routine requests, such as password resets, is the next most common claim. Closure is the least automated: in our Lifecycle Automation Census only one of nine vendors documents it on its public pages. For the rest, closure depends on an agent or on a rule an admin sets up.
Because it is the only stage that reduces future tickets. A desk that resolves the same issue every week without recording a fix or opening a problem record will keep resolving it. When you look at a service desk, check how it turns resolved tickets into knowledge and whether it can link incidents to a problem. See the ITSM glossary for the terms.
This table counts, for each stage, how many of the nine service desks we rank document automation on the pages we read, and how many describe it only in general terms. It is generated from the same data as the census on the home page.
| Stage | Documented | Partial | Not documented |
|---|---|---|---|
| 01 Logged | 6 | 3 | 0 |
| 02 Categorised | 5 | 2 | 2 |
| 03 Routed | 6 | 2 | 1 |
| 04 Resolved | 8 | 1 | 0 |
| 05 Closed | 1 | 0 | 8 |
| 06 Reviewed | 9 | 0 | 0 |
Use it to set expectations. A stage that few vendors document is a stage to test yourself in a trial rather than take on trust.
Bring three real tickets and ask the vendor to walk each through all six stages, saying at each one whether a person or the tool does the work. Our trial plan turns this into a two-week test.
Next lesson
Lesson
02