What Are the Current Approval Levels and Closure Codes for CHG in Latest ServiceNow Version?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2025 03:42 PM
Hi all,
Can someone please help clarify two things related to Change Requests (CHG) in the current 2025 version of ServiceNow?
Approval Levels:
Back in 2021, we had approval levels like Level 0, Level 1, etc., depending on risk and CI ownership.
What is the current approval level structure in ServiceNow for CHG workflows (e.g., L0 to L3)?
Who typically approves at each level, and are these configurable per change type?
Closure Codes:
In 2021, I remember we had closure codes like:
Successful
Successful with issues
Failed
Non-compliant
What are the current default closure codes available in the latest ServiceNow version for Change Requests?
Have any new codes (like “Rolled Back” or “Partial Success”) been introduced recently?
Thanks in advance! Would appreciate any screenshots or updated documentation references if available.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2025 01:24 AM
You can go to the developer site and get a PDI on Yokohama and see for yourself, or you can check the release notes.
The levels of approval are just what you make of it. Some companies use peer approval and CAB, some just CI owner approval. It all depends on the process your company has.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2025 01:48 AM
Hi @davidpearls,
It is best to explore on PDI and see the process for Change Management. You can sign up and get a free instance to explore it. Below is the link:
https://developer.servicenow.com/dev.do
Here is the documentation for Change Management:
Regards,
Ehab Pilloor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2025 02:25 AM
Hi @davidpearls
I’ve worked as a Change Manager and have been using ServiceNow since 2014. I’ve never seen the “Close Non-Compliant” status as an out-of-the-box (OOTB) feature. It seems like this is not OOTB. You can watch my video to understand it better.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************