- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2025 08:20 AM
Hi,
I'm new to ServiceNow and currently exploring Change Management. I’d like to understand the differences between Normal, Standard, and Emergency changes.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2025 08:23 AM
Hi @Richa2712
1. Normal Change:
Definition:A change that follows the full change management process, including risk assessment, approvals, testing, and CAB (Change Advisory Board) review.
Use Case: Scheduled upgrade of a server, deploying a new feature to production.
2. Standard Change
Definition: A pre-approved, low-risk, and frequently repeated change with well-documented steps.
Use Case: Adding a user to a group, rebooting a printer server, or applying a non-impactful patch.
3. Emergency Change
Definition: A change that must be implemented immediately due to an unplanned event like an outage or security breach.
Use Case: Patching a vulnerability under active exploitation, restoring a critical service outage.
Also read this article:
https://www.servicenow.com/docs/bundle/yokohama-it-service-management/page/product/change-management...
If my response solves your query, please marked helpful by selecting Accept as Solution and Helpful.
Thanks,
Prerna
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2025 08:22 AM
Hi @Richa2712
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]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2025 08:22 AM
Normal Change
-
Definition: A change that goes through the complete Change Management process — including risk assessment, approvals, and CAB (Change Advisory Board) review.
-
Example: Upgrading a server, deploying a new feature to production.
-
Approval: Required
-
Planning: Fully planned
-
CAB Involvement: Yes
🔸 Standard Change
-
Definition: A pre-approved, low-risk, and repetitive change that follows a defined process.
-
Example: Password reset process, updating a user profile, routine patching.
-
Approval: Not required every time (pre-approved)
-
Planning: Pre-defined
-
CAB Involvement: No
🔴 Emergency Change
-
Definition: A change that must be implemented immediately to fix a critical issue, prevent a major incident, or address an urgent security risk.
-
Example: Fixing a system outage, applying a critical security patch.
-
Approval: Fast-tracked (can be post-implementation in some cases)
-
Planning: Minimal, due to urgency
-
CAB Involvement: Emergency CAB (ECAB) may review
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]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2025 08:23 AM
Hi @Richa2712
1. Normal Change:
Definition:A change that follows the full change management process, including risk assessment, approvals, testing, and CAB (Change Advisory Board) review.
Use Case: Scheduled upgrade of a server, deploying a new feature to production.
2. Standard Change
Definition: A pre-approved, low-risk, and frequently repeated change with well-documented steps.
Use Case: Adding a user to a group, rebooting a printer server, or applying a non-impactful patch.
3. Emergency Change
Definition: A change that must be implemented immediately due to an unplanned event like an outage or security breach.
Use Case: Patching a vulnerability under active exploitation, restoring a critical service outage.
Also read this article:
https://www.servicenow.com/docs/bundle/yokohama-it-service-management/page/product/change-management...
If my response solves your query, please marked helpful by selecting Accept as Solution and Helpful.
Thanks,
Prerna
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2025 08:43 AM
@prerna_sh do you feel satisfied accepting your owns solutions from random one use profiles? 😆
with this attributes you are probably the best respondent in the whole ServiceNow world. When you want to cheat, please do it less obvious this is ridiculous and you devaluate the commitment of the Community. 🙃
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */