--- title: Review and close an improvement description: Once all tasks in each phase of the improvement have been completed, the Improvement Coordinator sets the improvement to review for the Improvement Manager to close. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/continual-improvement-management/review-close-cim-initiative.html release: australia product: Continual Improvement Management classification: continual-improvement-management topic_type: task last_updated: "2026-03-12" reading_time_minutes: 3 breadcrumb: [Managing improvements, Continual Improvement Management, IT Service Management] --- # Review and close an improvement Once all tasks in each phase of the improvement have been completed, the Improvement Coordinator sets the improvement to review for the Improvement Manager to close. ## Before you begin - Incident manager created an improvement request. - Improvement Manager accepted and assigned the improvement request. - Approver group member approved the improvement. - Improvement Manager and Improvement Coordinator implemented the improvement. Role required: sn\_cim.improvement\_manager, sn\_cim.improvement\_coordinator ## Procedure 1. Review the improvement for closure. 1. Navigate to **Continual Improvement** > **Under Review**. 2. In the Improvement Register list, open the improvement in the **Monitor/Review** state. 3. On the Improvement Initiative form, verify that all phases in the CIM Phases related list are 100% complete. 2. Verify the improvement has met the improvement goal. 3. Close the improvement. 1. In the Closure Notes tab, set the closure code, achieved outcome category, and close notes. 2. Click **Close** in the header bar to close the improvement. The improvement is no longer shown in the Open Improvement Register list. \[Omitted image "cim-closed.png"\] Alt text: Closed process flow ## Close improvement In the process of reviewing KPI performance in the Performance Analytics application, the Incident Manager noticed the **Average time to resolve an incident** KPI scorecard was too long \(24 hours\). As part of the review process for **Improve average time to resolve an incident by 25%** improvement, the Improvement Manager verified the work for the improvement is complete \(Improvement Initiative form and CIM Phases related list shows 100% complete\). The Improvement Manager also verified the improvement in two places before closing the improvement. - Performance Analytics now shows that the **Average time to resolve an incident** KPI has a value of 16 hours, which is more improvement than the target value of 18 hours \(18 hours is 25% faster than the previous average of 24 hours\). - Benchmarks application now shows that the company result for the **Average time to resolve an incident** KPI has a value of 16 hours, which is 2 hours better than the global industry average.
| Field | Value |
|---|---|
| Number | CIMT0000116 \(assigned internally\) |
| Percent complete | \*100 |
| Actual end date | \*2018-03-14 |
| Short description | Resolved incident and reassigned count improvements |
| CIM Task 1 | |
| Number | CIMT0000118 \(assigned internally\) |
| Active | \*\(Not selected\) |
| State | \*Closed Complete |
| Short description | Improve % of incidents resolved by first assigned group by using self service and more automation |
| Work notes | \*Self service and automation implemented to improve % of incidents resolved by first assigned group |
| CIM Task 2 | |
| Number | CIMT0000119 \(assigned internally\) |
| Active | \*\(Not selected\) |
| State | \*Closed Complete |
| Short description | Reduce the reassigned count by using ServiceNow Auto Categorization and Auto Assignment models |
| Work notes | \*Auto Categorization and Auto Assignment implemented to reduce reassigned count |