--- sourceDocument: Australia IT Service Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Service Management ft:clusterId : - itsm bundleId : - itsm workflow : - Technology --- # Configure the Emergency change model # Configure the Emergency change model {#ariaid-title1} Release version: Australia Updated May 18, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Configure the Emergency change model to define who can submit emergency changes, set up stakeholder notifications, configure approvals, and control automatic change task creation. ## Before you begin Role required: sn_itsm_chg_admin.change_models_config, sn_itsm_chg_admin.admin, or admin ## Procedure 1. Open the Emergency change model in the Configuration Console. For navigation steps, see [Configure change models for Simplified Change Management](https://servicenow-prod.fluidtopics.net/_DN83l70k9md9vD7QNGXvg "Configure the change models that control how Normal, Standard, Emergency, and Change Registration changes are processed in Simplified Change Management."). 2. Configure the availability, templates, authorized submitters, risk-based approvals for the states, and control automatic change task creation. {#configure-emergency-change-model-scm__table_bfl_l23_hjc__entry__2} | Section | Description | |-|-| | Availability | The Availability setting controls whether the model is available to select while creating new change requests. Set the Available for new change requests toggle. Turn on to expose the model in the change type picker while creating new change requests. When you enable the model by selecting the Availability check box, the corresponding global model is set to inactive and ITIL changes process is set to the simplified change model. | | New | The New state defines who can submit emergency change, who get notified, and templates for the change model. In the Who can submit emergency changes? field, select users or user groups authorized to submit emergency changes. Only members of the selected groups can choose the Emergency model when creating a change. Emergency changes bypass normal schedules, so limit this to authorized teams. Note: Only users with the sn_change_write role are available for selection. Under Who should be informed about emergency changes, configure notifications. An email is sent each time an emergency change is created. 1. In the Select users or groups field, add the notification recipients. 2. In the Select the email template field, select the notification template. {#configure-emergency-change-model-scm__ol_lkf_fpj_hjc} The templates have pre-filled common fields that follow the change model's workflow and approval requirements. Review the template that use this change model. To add a template, select New template. For steps to configure a template, see [Create and propose a change template](https://servicenow-prod.fluidtopics.net/kp~dpiwKPH2o8r5cKIH4cw "Create, customize, and then propose for publication a change template aligned to a change model to make change creation faster, and promote data quality and consistency."). | | Authorize | The Authorize state is the business approval gate. It verifies the change is approved to proceed to implementation. Configure approvers separately for Low risk, Moderate risk, and High risk. Select one or more approver. The available approvers are: * Member of assignment group: Any member of the assignment group can approve. One approval is sufficient. * Manager of assignment group: The manager of the assignment group must approve. * Change manager: Any member of the change management group can approve. * CAB member: At least one CAB member must approve. * Other group: A specific group that you select must approve. Select an assignment group from the list on the modal window. {#configure-emergency-change-model-scm__ul_jj3_hht_ljc} Default approvers for each risk level are: * Low risk: Member of assignment group * Moderate risk: CAB member * High risk: CAB member {#configure-emergency-change-model-scm__ul_w53_zht_ljc} | | Scheduled | The Scheduled state controls auto-creation of a task to verify planning and resources required for the change. Select Yes to generate the change tasks automatically when the change enters this state. This task helps confirm the change is properly planned and resources are in place before implementation. | | Implement | The Implement state controls auto-creation of a task to implement the change. Select Yes to generate the change tasks automatically when the change enters this state. This task helps the change through execution, verification, and documentation. | | Review | The Review state controls auto-creation of a task to review the change implementation. Select Yes to generate the change tasks automatically when the change enters this state. This task helps to verify the change was successful and record lessons learned. | [Table 1. Emergency change model settings] {#configure-emergency-change-model-scm__table_bfl_l23_hjc} 3. Select Save. To discard unsaved changes, select Cancel. {#configure-emergency-change-model-scm__steps_emrg_mdl} ## Result The Emergency change model configuration is saved. Only members of the designated submitter groups can create emergency changes, and the configured recipients receive email notifications on each creation. ## What to do next To configure additional change models, return to [Configure change models for Simplified Change Management](https://servicenow-prod.fluidtopics.net/_DN83l70k9md9vD7QNGXvg "Configure the change models that control how Normal, Standard, Emergency, and Change Registration changes are processed in Simplified Change Management.").