--- sourceDocument: Brazil IT Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil IT Service Management ft:clusterId : - itsm bundleId : - itsm workflow : - Technology --- # Schedule types in conflict detection # Schedule types in conflict detection {#ariaid-title1} Release version: Brazil Updated October 14, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read Conflict detection uses maintenance, blackout, and information schedules to evaluate when change requests can be implemented. Each schedule type supports a category and optional ownership fields. All three schedule types extend the Condition Schedule \[cmn_schedule_condition\] table, so they share the same base fields, such as Name, Time zone, Source, and Condition. For information about creating maintenance and blackout schedules, see [Create blackout and maintenance schedules in Change Management](https://www.servicenow.com/docs/ZVVWIn98hUszJFgbY1QDvQ "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."). ## Schedule types {#schedule-types-conflict-detection__schedule-types-conflict-detection-types} {#schedule-types-conflict-detection__table-schedule-types__entry__3} | Schedule type | Table | How conflict detection uses it | |-|-|-| | Maintenance schedule | cmn_schedule_maintenance | Specifies times during which change requests should be scheduled. Conflict detection raises a conflict when a change request is outside a required maintenance window. | | Blackout schedule | cmn_schedule_blackout | Specifies times during which normal change activity should not be scheduled. Conflict detection raises a conflict when a change request is inside a blackout window. | | Information schedule | cmn_schedule_information | Records events that change teams should be aware of, such as holidays or organizational events. Conflict detection doesn't create conflict records for information schedules. | [Table 1. Schedule types used by conflict detection] {#schedule-types-conflict-detection__table-schedule-types} ## Schedule categories {#schedule-types-conflict-detection__schedule-types-conflict-detection-category} Each schedule type has a Category field with its own set of choices. For example, a blackout schedule can be categorized as a hard freeze or a soft freeze. The Category field is empty by default. The category is stored only after you select a value and save the schedule. When conflict detection generates a conflict record for a maintenance or blackout schedule, the conflict record includes the category of that schedule. For the full list of categories, see [Schedule categories](https://www.servicenow.com/docs/ZGJA0rd0DGoFsnBvd4E2rQ "Maintenance, blackout, and information schedules each have their own set of categories that describe the purpose of the schedule."). ## Schedule ownership {#schedule-types-conflict-detection__schedule-types-conflict-detection-ownership} You can assign an owner to any maintenance, blackout, or information schedule by using the Assigned to and Assignment group fields. You can specify a user, a group, or both. The Assigned to field depends on the Assignment group field. Users who can edit schedules can populate these fields. ## Information schedule properties {#schedule-types-conflict-detection__schedule-types-conflict-detection-properties} The following system properties control how conflict detection evaluates information schedules. For other conflict detection properties, see [Conflict detection properties](https://www.servicenow.com/docs/B2HpucwNAJGAFMvbGWRhAQ#conflict-detection-properties "Conflict detection includes properties that determine how the conflict detection capability is executed."). {#schedule-types-conflict-detection__table-information-schedule-properties__entry__3} | Property | Description | Default value | |-|-|-| | change.conflict.information | Includes information windows when checking change request conflicts. | true | | change.conflict.relatedchildinformation | Checks whether the change request falls within the information windows of child CIs. | false | | change.conflict.relatedparentinformation | Checks whether the change request falls within the information windows of parent CIs. | false | [Table 2. Information schedule properties] {#schedule-types-conflict-detection__table-information-schedule-properties} * **[Create an information schedule](https://www.servicenow.com/docs/XAw70FkAL3Z8EyGG6gpKsw)** Create an information schedule to record events such as holidays or organizational events that change teams should be aware of. Conflict detection doesn't create conflict records for information schedules. * **[Schedule categories](https://www.servicenow.com/docs/ZGJA0rd0DGoFsnBvd4E2rQ)** Maintenance, blackout, and information schedules each have their own set of categories that describe the purpose of the schedule. **Related concepts** * [Conflict calendar](https://www.servicenow.com/docs/zhtZjMA1jKN~OHPH9zUmcg "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.") * [Conflict detection](https://www.servicenow.com/docs/~RpnmrozQ9OwPyEP8wCaGg "Conflict detection identifies potential scheduling conflicts for a change request based on the configuration items, and planned start and end date or the change. If a scheduling conflict exists, conflict detection also checks any related blackout or maintenance schedules and other active change requests to determine the scheduling conflict.") **Related tasks** * [Detect change conflicts](https://www.servicenow.com/docs/B2HpucwNAJGAFMvbGWRhAQ#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://www.servicenow.com/docs/ZVVWIn98hUszJFgbY1QDvQ "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.") * [Configure a change request to monitor outside maintenance schedule conflicts](https://www.servicenow.com/docs/us737biPDMUAsNMcFSNrug "Configure a change request to detect conflicts outside the maintenance window. Conflict detection flags planned start and end dates that fall outside the maintenance schedule, so you can modify the change schedule accordingly.") * [Enable automatic change conflict detection](https://www.servicenow.com/docs/4PzHP7bDuWMAJgUkodyBxw "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/CLXg6Qv~xGrV9JUUsilpuw#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.") * [Create an information schedule](https://www.servicenow.com/docs/XAw70FkAL3Z8EyGG6gpKsw "Create an information schedule to record events such as holidays or organizational events that change teams should be aware of. Conflict detection doesn't create conflict records for information schedules.") * [Create blackout and maintenance schedules in Change Management](https://www.servicenow.com/docs/ZVVWIn98hUszJFgbY1QDvQ "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.")