--- title: Basic OT Change Model playbook description: Learn about the Basic Operational Technology \(OT\) Change Model playbook stages that an OT change without approvals must go through until it’s completed. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/operational-technology/operational-technology-change-management/basic-ot-change-model.html release: australia product: Operational Technology Change Management classification: operational-technology-change-management topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Select a change model to fulfill change requests, Configure, Operational Technology Change Management, Operational Technology] --- # Basic OT Change Model playbook Learn about the Basic Operational Technology \(OT\) Change Model playbook stages that an OT change without approvals must go through until it’s completed. ## Initiate The Initiate stage of an OT change request lets you capture the details of the requested change and assign the change as necessary. This stage has three tasks. |Field|Description| |-----|-----------| |Short description|Brief description of the change.| |Description|Details of the change.| |Category|Type of change.| |Site|Site where the change takes place.| |Watch list|Users who receive notifications about this change when comments are added.| |Work notes list|Users who receive notifications about this change when work notes are added.| |Field|Description| |-----|-----------| |Priority|Impact and urgency to identify how quickly the change should be addressed.| |Risk|Amount of risk that the change poses.| |Impact|Measure of the effect that a change has on your industrial processes.| |Field|Description| |-----|-----------| |Requested by|User who requests the change.| |Assignment group|Assigned group that works on the change. The assignment group can be any group with the type OT.| |Assigned to|User who works on this change. If the assignment group changes, the **Assigned to** field is cleared.| ## Plan The Plan stage of an OT Change request lets you add a justification for the change, an implementation plan, a risk and impact plan, a backout plan, a test plan, and a time to schedule the change. This stage has six tasks. |Field|Description| |-----|-----------| |Justification|Reason why the change must take place.| |Field|Description| |-----|-----------| |Implementation plan|Details of how to implement the requested change.| |Field|Description| |-----|-----------| |Risk and impact analysis|Details of any risk and impact factors that are related to this change.| |Field|Description| |-----|-----------| |Backout plan|Details of how to reverse the change in place if necessary.| |Field|Description| |-----|-----------| |Test plan|Details of how to test the implemented change.|
| Field | Description |
|---|---|
| Planned start date | Date that the change takes place.**Note:** You can also choose an available downtime slot on the calendar by selecting the **Scheduling Assistant** button to fill in the planned start date field automatically. |
| Planned end date | Date that the change ends.**Note:** You can also choose an available downtime slot on the calendar by selecting the **Scheduling Assistant** button to fill in the planned end date field automatically. |