---
title: Create a change lockdown
description: Create a change lockdown to pause in-flight change requests during major unplanned IT, critical, or financial events.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/it-service-management/change-management/create-change-lockdown.html
release: brazil
product: Change Management
classification: change-management
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 2
keywords: [change lockdown, create lockdown, schedule entry]
breadcrumb: [Change lockdown, Configure, Change Management, IT Service Management]
---

# Create a change lockdown

Create a change lockdown to pause in-flight change requests during major unplanned IT, critical, or financial events.

## Before you begin

Role required: change\_manager

## Procedure

1.  Navigate to **All** > **Change** > **Administration** > **Change Lockdown**.

    The list shows the existing lockdown records with their name, type, time zone, and the date on which each record was updated.

2.  Select **New**.

3.  On the Change Lockdown form, fill in the fields.

    **Note:** The **CI Condition** tab appears only when you select the **Filter by CI** check box. If you clear the check box, the lockdown applies to all change requests that match the **Change Request Condition** field.

    |Field|Description|
    |-----|-----------|
    |Name|Name of the change lockdown.|
    |Description|Purpose of the change lockdown.|
    |Time zone|Time zone that the lockdown schedule uses. The default value is **-- Floating --**.|
    |Filter by CI|Option that limits the lockdown to specific configuration items \(CIs\). The **CI Condition** tab appears when this check box is selected.|
    |Source|Method that identifies the CIs, such as **CI Class**.|
    |Applies to \(**CI Condition** tab\)|Table that the **Condition** field filters. The default value is Configuration Item \[cmdb\_ci\]. This field is available only when the **Filter by CI** check box is selected.|
    |Condition \(**CI Condition** tab\)|Conditions that filter the records in the table selected in the **Applies to** field. This field is available only when the **Filter by CI** check box is selected.|
    |Change Request Condition \(**Change Condition** tab\)|Conditions that select the change requests to place on hold.|
    |Assignment group|Group that receives the lockdown approval.|
    |Assigned to|User who receives the lockdown approval.|
    |State|State of the change lockdown. A new change lockdown starts in the **Draft** state. This field is read-only.|

4.  Select **Submit**.

    The record indicates that the schedule has no schedule entry. A change lockdown takes effect only after you add a schedule entry.

5.  On the **Schedule Entries** tab, select **New** and then define the period that the lockdown covers.

    A schedule entry sets values such as **All day**, **Repeat on**, and **End date time**.


## What to do next

After the schedule entry is saved, **Preview** becomes available. Preview the affected change requests before you request approval. For more information, see [Manage a change lockdown](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/manage-change-lockdown.md).

**Parent Topic:**[Change lockdown](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/change-lockdown.md)

**Related topics**  


[Change lockdown](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/change-lockdown.md)

[Manage a change lockdown](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/change-management/manage-change-lockdown.md)