What is the purpose of a continual improvement register?
ITIL 4 Foundation, objective 7. Seven ITIL practices in detail medium
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Not correct To record known errors and their workarounds so that incidents can be resolved faster
That is a known error record, owned by problem management. Known errors may generate improvement ideas but the register is not where they live.
Correct To capture, track and manage improvement ideas from identification through to final action
Correct. The register is the structured record that keeps improvement ideas visible, assessable and prioritised rather than lost.
Not correct To hold the authorised list of changes scheduled for the coming period
That describes a change schedule. Some improvements become changes, but the register tracks ideas at every stage, including those never approved.
Not correct To store the agreed service targets so that performance can be reported against them
Agreed service targets live in the service level agreement itself. The register holds improvement opportunities, which are candidate future work rather than current performance commitments.
Why
The continual improvement register is a database or structured document used to track and manage improvement ideas from the moment they are identified to final action. An organization may keep several registers at different levels, and ideas can be reprioritised or moved between them. Its distinguishing feature is that it holds ideas at every stage, including unassessed and rejected ones — unlike a change schedule or a known error record.
Where this comes from
- Cited
- ITIL 4 syllabus clause 7
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 7 and space the ones you get wrong.
More questions on this objective
- Which statement best describes what the incident management practice is intended to achieve? machine-checked
- How is an incident defined in ITIL? machine-checked
- Several incidents are open at once and the support team must decide which to work on first. On what basis should the order be decided? machine-checked
- A difficult incident is worked on by pulling several specialists from different teams into the same session at the same time; once it becomes clear who is best placed to continue, the others step away. What is this technique called? machine-checked
- Why does an organisation define a separate procedure for major incidents rather than handling them exactly like all other incidents? machine-checked
- A support team routinely fixes incidents by phone and updates the incident record only with the word 'fixed'. What is the most significant consequence of this? machine-checked