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


---

# Change lockdown

# Change lockdown {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Change lockdown allows change managers to pause all or a subset of in-flight change requests. Use it during major unplanned IT, critical, or financial events.

Change lockdown is available in the base system. After installation, the Change Lockdowns module appears in the Change application menu. To view or create a new change lockdown, see [Create a change lockdown](https://www.servicenow.com/docs/Usv9dxokLC4YW4iNmFPhow "Create a change lockdown to pause in-flight change requests during major unplanned IT, critical, or financial events.").

A lockdown moves through an approval cycle before it takes effect. You can preview the affected change requests and refine the criteria while the lockdown is in draft. You can also cancel the lockdown when the situation that
prompted it is resolved. For the full list of states, see [Change lockdown states](https://www.servicenow.com/docs/9AQ8mO_Kr_rrwoCxmGk1Yw "These states describe where a change lockdown sits in its approval cycle, which actions are available, and whether the lockdown holds any change requests.").

When a lockdown is approved and it reaches the Enforced state, the system writes the previewed change requests to the Schedule Lockdown Changes related list and sets their
On hold field to `true`. Cancelling an enforced lockdown releases those change requests.  
For steps on previewing, approval, and cancellation, see [Manage a change lockdown](https://www.servicenow.com/docs/XoNDL7HWJesryNg5cAgbIA "Manage a change lockdown by previewing affected change requests, submitting for approval, reverting to draft, or canceling it.").  
Note:  
If a change request was already on hold before the lockdown was created, it remains on hold after the lockdown is cancelled.

## Lockdowns and conflict detection {#change-lockdown__section_lockdown_conflicts}

A new conflict type is introduced, Inside Change Lockdown conflict type which identifies change requests that overlap with an active lockdown period.

Conflict detection checks change requests against active lockdown records. If you create or reschedule a change request inside a lockdown period, the system places it on hold automatically.  
For more information, see [Change lockdown conflict detection](https://www.servicenow.com/docs/_t6mLdu9nC8reB5lPdjF~Q "Conflict detection checks change requests against active lockdown records in the same run that checks maintenance windows and blackout windows. A change request that falls inside a lockdown period is reported as a conflict and automatically placed on hold.").  
Note:  
* Whether conflict detection runs against a lockdown depends on the change model state configuration.
* The scheduling assistant excludes enforced lockdown periods when suggesting maintenance windows.
{#change-lockdown__ul_r2p_qd4_jkc}
* **[Create a change lockdown](https://www.servicenow.com/docs/Usv9dxokLC4YW4iNmFPhow)**   
  Create a change lockdown to pause in-flight change requests during major unplanned IT, critical, or financial events.
* **[Manage a change lockdown](https://www.servicenow.com/docs/XoNDL7HWJesryNg5cAgbIA)**   
  Manage a change lockdown by previewing affected change requests, submitting for approval, reverting to draft, or canceling it.
* **[Set the lockdown preview maximum](https://www.servicenow.com/docs/Zx~o9gWs0QckDnXl_clD~g)**   
  Change the maximum number of records that a change lockdown preview displays. This keeps the preview readable on instances with a large volume of change requests.
* **[Change lockdown states](https://www.servicenow.com/docs/9AQ8mO_Kr_rrwoCxmGk1Yw)**   
  These states describe where a change lockdown sits in its approval cycle, which actions are available, and whether the lockdown holds any change requests.
* **[Change lockdown conflict detection](https://www.servicenow.com/docs/_t6mLdu9nC8reB5lPdjF~Q)**   
  Conflict detection checks change requests against active lockdown records in the same run that checks maintenance windows and blackout windows. A change request that falls inside a lockdown period is reported as a conflict and automatically placed on hold.

**Related concepts**   

* [Change lockdown conflict detection](https://www.servicenow.com/docs/_t6mLdu9nC8reB5lPdjF~Q "Conflict detection checks change requests against active lockdown records in the same run that checks maintenance windows and blackout windows. A change request that falls inside a lockdown period is reported as a conflict and automatically placed on hold.")  
**Related tasks**   

* [Create a change lockdown](https://www.servicenow.com/docs/Usv9dxokLC4YW4iNmFPhow "Create a change lockdown to pause in-flight change requests during major unplanned IT, critical, or financial events.")
* [Manage a change lockdown](https://www.servicenow.com/docs/XoNDL7HWJesryNg5cAgbIA "Manage a change lockdown by previewing affected change requests, submitting for approval, reverting to draft, or canceling it.")
* [Limit conflict detection to a change model state](https://www.servicenow.com/docs/ICGjn4l0pKUxpvH0BgWeIQ "Use the Allow Conflict Detection attribute to limit conflict detection to a specific change model state. Conflict detection then runs only when a change request reaches that state.")  
**Related reference**   

* [Change lockdown states](https://www.servicenow.com/docs/9AQ8mO_Kr_rrwoCxmGk1Yw "These states describe where a change lockdown sits in its approval cycle, which actions are available, and whether the lockdown holds any change requests.")