---
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 change request to monitor conflicts

# Configure a change request to monitor outside maintenance schedule conflicts {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
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.

## Before you begin

Role required: personalize_ui or admin

## About this task

The Outside maintenance schedule check box is informational and the instance sets this value and disregards any changes that you make to this check box. The check box is selected by default if either of the following actions occur.

* The planned start and end dates in the change request with an associated configuration item (CI) are compared to the maintenance schedule and are determined to be outside the schedule.
* Affected CIs associated with the change request are checked against their assigned maintenance schedules, if any.

{#monitor-maintenance-schedule__ul_enn_4fy_3fb}  
Note:  
Only the maintenance window for the primary CI or affected CIs is checked; the upstream and downstream items are not checked.

## Procedure

1. Navigate to AllChangeOpen and select an existing change request.
2. If the Outside maintenance schedule field does not appear, add the field to the form.
   1. Click the context menu icon and then click Additional actionsConfigureForm Layout.
   2. Move Outside maintenance schedule to the Selected list.
   3. Click Save.
   {#monitor-maintenance-schedule__substeps_nfy_fgz_3fb}

## Result

When you save a change request that is outside the maintenance schedule, a warning appears for each item (primary or affected). This warning also displays the planned dates that fall outside the maintenance window.
**Related concepts**   

* [Conflict calendar](https://servicenow-prod.fluidtopics.net/I7dfJU_iBpGgC_duVHTFBg "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**   

* [Detect change conflicts](https://servicenow-prod.fluidtopics.net/HQtY4pGQb30K3L5cH7hUYg#configure-conflict-properties "Detect change conflicts by setting Change Management conflict analysis properties. Use the resulting information to calculate conflicts for change requests and review and modify the change to eliminate conflicts.")
* [Create blackout and maintenance schedules in Change Management](https://servicenow-prod.fluidtopics.net/Gyeat1enp08Zj9DzXEzZrA "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")
* [Enable automatic change conflict detection](https://servicenow-prod.fluidtopics.net/WhxTMacVOFwKSVhGIs9how "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://servicenow-prod.fluidtopics.net/uWeywcJWCXG8NmbgNukTaw#t_RunManualConflictDetection "Run conflict detection manually for a change request. Review the conflicts detected either automatically or manually and resolve them by changing the schedules.")

*[\>]: and then