---
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


---

# Enable automatic change conflict detection

# Enable automatic change conflict detection {#ariaid-title1}

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

## Before you begin

Prior to running conflict detection, consider the following scenarios:

CMDB list size and relationship complexities
:   If you have a large organization with a large CMDB, conflict detection can take longer to complete.

Inactive changes are not evaluated
:   Conflict detection does not evaluate inactive changes when determining conflicting changes.

Advanced mode conflict checking is disabled by default
:   When you upgrade the application, advanced mode conflict checking is disabled by default and affected CIs are not considered during conflict detection. To evaluate all CIs, set the mode to
    Advanced.

Role required: change_manager or admin

## Procedure

1. Navigate to AllChangeAdministrationConflict Properties.
2. Select one of the following options.

   | Option | Description |
   | Run conflict detection automatically after changes to Configuration item, Planned start date, Planned end date, or State when a change request is updated | When selected, runs conflict detection automatically when a change to one or more of the following fields on the change request record is saved. * Configuration item * Planned start date * Planned end date * State {#t_RunAutomatedConflictDetection__ul_kk3_p3d_3t} |
   | Enable the scheduled change conflict checker | When selected, runs the following conflict detection scheduled jobs at these intervals: Change Conflict Detection \< 1 Week Away is scheduled every day. Change Conflict Detection \< 1 Month Away is scheduled every two days. Change Conflict Detection \>=1 Month Away is scheduled every seven days. |
   |-|-|

   {#t_RunAutomatedConflictDetection__choicetable_kz3_j3d_3t}
3. Click Save.  
   You can view the conflicts on the Conflicts tab on the change request record.
**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")
* [Configure a change request to monitor outside maintenance schedule conflicts](https://servicenow-prod.fluidtopics.net/4qha2Y2yPoZUitLS4JxHtg "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.")
* [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