{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":31942,"path":"it-service-management/configure-schedules-for-simplified-change-management.md","title":"Configure schedules for Simplified Change Management","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure schedules for Simplified Change Management\n\nCreate and manage blackout and maintenance schedules for Change Management to control when changes are permitted or blocked across your organization.\n\n## Before you begin\n\nRole required: sn\\_itsm\\_chg\\_admin.change\\_schedules\\_config and sn\\_ia\\_config.ia\\_user\n\n**Note:** The sn\\_itsm\\_chg\\_admin.change\\_schedules\\_config role no longer automatically inherits the sn\\_ia\\_config.ia\\_user role. Users who need to configure the console must now be assigned both the appropriate Change Management role \\(for example, sn\\_itsm\\_chg\\_admin.change\\_schedules\\_config\\) and the sn\\_ia\\_config.ia\\_user role explicitly. Existing roles aren't modified during upgrade, allowing you to maintain full control over assignment of elevated privileges. After upgrading, if you have previously relied on inherited access, you won't be able to configure the console until the sn\\_ia\\_config.ia\\_user role is assigned explicitly.\n\n## About this task\n\nUse the Blackout and Maintenance windows to schedule a change. Blackout schedules block changes during critical periods such as financial year-end or major platform releases. Maintenance windows designate periods when changes are actively expected, such as recurring patching cycles. Both schedule types serve as the authoritative source for downstream enforcement logic including conflict detection and approval routing.\n\n## Procedure\n\n1.  From the header of your ServiceNow instance, navigate to **All** > **Admin Home**.\n\n2.  From the **Manage your products** section, select **View product overview** for IT Service Management.\n\n3.  On the Product Hub page for IT Service Management, from the Configure your product section, select **Configure**.\n\n4.  On the Configuration Console, from the left navigation panel, select **ITSM fulfiller experience > Change Management > Change schedules**. \\[Omitted image \"simplified-change-schedules.png\"\\] Alt text: Change schedules configuration page\n\n    The **Schedules** list displays the pre-configured schedules, organized under the **Blackouts** and **Maintenance** tabs.\n\n5.  To create a new schedule, select **Add New**.\n\n    **Note:** To edit an existing schedule, select it from the **Schedules** list and make the necessary updates.\n\n6.  In the Name your schedule section, enter a descriptive name in the **Schedule name** field.\n\n    For example, you can include the type, scope, or timeframe, like APAC Holiday Blackout or Monthly Patching Window US East. The name appears in the change calendar, conflict notifications, and audit reports.\n\n7.  In the What type of schedule are you creating? section, select a schedule type.\n\n    |Option|Description|\n    |------|-----------|\n    |**Blackout schedule**|Changes are blocked during this time.|\n    |**Maintenance window**|Changes are allowed only during this time.|\n\n8.  In the Which items does this schedule apply to? section, select a source to define the scope of the schedule.\n\n    |Option|Description|\n    |------|-----------|\n    |**All CIs**|The schedule applies to all configuration items in the database across the organization.|\n    |**CI class**|The schedule applies to a specific class of configuration items, such as all Windows servers.|\n    |**Change request**|The schedule applies based on change request attributes such as assignment group, change model, or change type.|\n\n9.  In the When does this schedule run? section, configure the schedule timing.\n\n    1.  Enter the **Start date/time** and **End date/time**, or select **All day** to apply the schedule for the full calendar day.\n\n    2.  In the **Select the correct timezone for your schedule** field, select the applicable timezone.\n\n    3.  Under **Schedule repeat**, select a recurrence pattern.\n\n        |Pattern|Behavior|\n        |-------|--------|\n        |**One time**|The schedule runs once between the specified dates.|\n        |**Weekly**|The schedule repeats every week.|\n        |**Monthly**|The schedule repeats every month.|\n        |**Yearly**|The schedule repeats every year.|\n        |**Specific**|Define a custom recurrence rule.|\n\n    4.  Enter the interval in the **Repeat every** field.\n\n        Runs once from 12:00:00 to 12:00:00 \\(US/Pacific\\) starting 10 May 2026 and ending 13 May 2026.\n\n10. Select **Save**.\n\n11. When you have finished configuring, select **Mark as configured** to save your settings and mark this step as complete.\n\n    To revert changes made in the current session before saving, select **Undo**.\n\n    As an alternative to the form-based wizard, you can also complete this configuration through the **Configure with AI** conversational flow, accessible from the banner at the top of the page.\n\n\n## Result\n\nThe new schedule is created and appears in the **Schedules** list under the **Blackouts** or **Maintenance** tab, depending on the type you selected. The schedule is active immediately and is used by Change Management for conflict detection and change enforcement.\n\n**Parent Topic:**[Configuring Simplified Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/configuring-change-management-experience-in-it-service-management.md)\n\n**Related topics**  \n\n\n[Create blackout and maintenance schedules in Change Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/change-management/t_CreateBlkoutMaintSched.md)\n\n"}}