---
sourceDocument: Xanadu IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/it-service-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Create blackout and maintenance schedules in Change Management

# Create blackout and maintenance schedules in Change Management {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Use the Blackout and Maintenance windows to schedule a change. Blackout windows
specify times during which normal change activity should not be scheduled. Maintenance
windows specify times during which change requests should be scheduled. For example, create
a blackout schedule for code freezes at the end of the year.
blackout-maintenance-schedule

## Before you begin

Role required: itil_admin or admin

Ensure that the [Change Management - Collision Detector](https://www.servicenow.com/docs/XJmMgHEf7SkcmSgW5ifCyw "You can activate the Change Management - Collision Detector plugin (com.snc.change.collision) if you have the admin role. This plugin includes demo data and activates related plugins if they are not already active.")
(com.snc.change.collision) plugin is activated.

## About this task

Conflict detection uses blackout and maintenance schedules to find potential scheduling conflicts for the configuration items (CIs) associated with a change request. When conflict detection runs, either automatically or by manual request, conflict detection determines if either type of defined schedule applies to the change request. If a potential conflict is identified, a warning message appears and conflicts are listed within the Conflict form section. View conflicts in the [Conflict calendar](https://www.servicenow.com/docs/hlXOmpDhQ~o9REfCWorw8Q "The conflict calendar graphically represents the potential scheduling conflicts for a change request. Conflicts are identified as active change requests, blackout schedules, and changes scheduled outside maintenance schedules. Use the Scheduling Assistant to resolve any schedule conflicts.").  
Note:  
To use the business service as the source for a blackout or maintenance schedule, the business service must be converted to an application service. For instructions, see [Convert business services to
application services](https://www.servicenow.com/docs/access?context=convert-bus-to-app-svc-intro&version=xanadu&pubname=xanadu-servicenow-platform&ft:locale=en-US). For information about application services, see [Application services](https://www.servicenow.com/docs/access?context=application-services&version=xanadu&pubname=xanadu-servicenow-platform&ft:locale=en-US).

## Procedure

1. Create a blackout or maintenance schedule.

   | Option | Description |
   | Create a blackout schedule | 1. Navigate to ChangeSchedulesBlackout Schedules. 2. Click New. {#t_CreateBlkoutMaintSched__ol_jcb_j2d_3t} |
   | Create a maintenance schedule | 1. Navigate to ChangeSchedulesMaintenance Schedules. 2. Click New. {#t_CreateBlkoutMaintSched__ol_ftf_k2d_3t} |
   |-|-|

   {#t_CreateBlkoutMaintSched__choicetable_p11_g2d_3t}
2. On the form, fill in the fields.  
   {#t_CreateBlkoutMaintSched__table_avy_xxk_xs__entry__2}

   | Field | Description |
   |-|-|
   | Name | Unique name for the schedule. |
   | Description | Short description about the schedule. |
   | Time zone | Time zone for the schedule. Select Floating to evaluate planned start and end dates on the Change Request form for the logged-in user. |
   | Source | Source of the blackout or maintenance schedule. The available options are Service, Change Request, and CI Class. Note: When you select Service or Change Request from the Source list, the Applies to field does not appear. The Applies to field appears if you select CI Class as the Source, which in turn enables the selection of a CI Class. |
   | Applies to | The class of CI that this schedule applies to. Specifying CI \[cmdb_ci\] indicates that this schedule is applicable to all CIs in this class and any children of this class. Conflict detection evaluates whether the schedule applies to a given change request, service, or CI, and the condition defined on the schedule. |
   | Condition | Conditions to specify the CIs that the schedule applies to. This field does not appear when the Applies to field is set to None. Note: Related fields used in conditions are not evaluated for blackout or maintenance schedules. Condition on the schedule can only apply to one table at a time. |
   [Table 1. Blackout and Maintenance schedule form]

   {#t_CreateBlkoutMaintSched__table_avy_xxk_xs}
3. Open the form context menu and click Save.  
   A blackout or maintenance schedule is created and the Schedule Entries, Child Schedules, and Referenced By related lists appear in the change.  
   Note:  
   The Blackout Schedule \[cmn_schedule_blackout\] table extends the Condition
   Schedule \[cmn_schedule_condition\] table, which in turn extends the
   Schedule \[cmn_schedule\] table. The Blackout Schedule table inherits the
   domain properties from the Schedule table which has the Domain and
   Domain path columns.

   Because the Blackout schedule table uses the same Child Schedule and Schedule Entry tables as the Schedule table uses, the domain support is identical. The domain_master attribute is used to derive the domain from a parent record. For more information, see [Domain support for schedules](https://www.servicenow.com/docs/access?context=domain-support-for-schedules&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US).
4. Create one or more schedule entries by completing the following steps:
   1. In the Schedule Entries related list of the new maintenance schedule, click New.
   2. Enter a unique name and define the time during which you want to schedule the maintenance.  
      For more information about the schedule entries field, see [Schedule entry
      fields](https://www.servicenow.com/docs/access?context=r_ScheduleEntryFields&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US).

## Result

A blackout or maintenance schedule is created.

## What to do next

Associate the configuration item with the maintenance schedule that is used in the
change request.
* **[Assign a maintenance schedule to configuration items](https://www.servicenow.com/docs/7ta8~8w9wuOmkomkJYm9AQ)**   
  You can review and determine the conflicts in a change schedule by assigning the maintenance schedules to configuration items (CI). After you assign a maintenance schedules to the CI, add the CI to the change request.

**Related concepts**   

* [Conflict calendar](https://www.servicenow.com/docs/hlXOmpDhQ~o9REfCWorw8Q "The conflict calendar graphically represents the potential scheduling conflicts for a change request. Conflicts are identified as active change requests, blackout schedules, and changes scheduled outside maintenance schedules. Use the Scheduling Assistant to resolve any schedule conflicts.")  
**Related tasks**   

* [Configure conflict analysis properties](https://www.servicenow.com/docs/xScMryGihLvbgit7uY7oQQ#configure-conflict-properties "Configure Change Management conflict analysis properties to detect change conflicts. Use the relevant information to calculate conflicts for change requests and review and modify the change to eliminate conflicts.")
* [Configure a change request to monitor outside maintenance schedule conflicts](https://www.servicenow.com/docs/eeZPBylHdw8Il6z2Y4c2kw "When a change request is configured to display the conflicts that are outside the maintenance schedule, conflict detection indicates whether the planned start and end dates occur outside the maintenance window or not. By reviewing the conflicts that are detected, you can modify the change schedule.")
* [Enable automatic change conflict detection](https://www.servicenow.com/docs/H7vcta8QyV21fBfY~efymA "Automate conflict detection to run at specific intervals or when a change request is updated to immediately review the conflicts when the schedule dates are updated.")
* [Detect conflicts manually and review conflict details](https://www.servicenow.com/docs/iVNknameZKYY9AOOalfRew#t_RunManualConflictDetection "Run conflict detection manually for a change request and cancel conflict detection before it completes. Review the conflicts detected either automatically or manually and resolve them by changing the schedules.")  
**Related topics**   

* [Define a schedule](https://www.servicenow.com/docs/access?context=t_DefineASchedule&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US)
* [Schedule entry fields](https://www.servicenow.com/docs/access?context=r_ScheduleEntryFields&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US)
* [Parent and child schedules](https://www.servicenow.com/docs/access?context=c_ParentAndChildSchedules&version=xanadu&pubname=xanadu-platform-administration&ft:locale=en-US)

*[\>]: and then