Change Control

A change identifies the service, summary, risk, planned start and end, and rollback plan. These details let a change approver consider the operational effect before authorizing work. Draft work can be prepared and moved to review. The approval decision then determines whether the database administrator may begin implementation or whether the change is rejected.

The schedule is a planning record. It should show when work is expected, while the change status says which decision or execution stage has been reached. A change marked approved is ready for the authorized technician to take into implementation. The final verification or rollback state records how that work ended. Treat these as separate decisions so an approval is not mistaken for successful execution.

• Preparation. The change summary, service and risk establish the scope of the proposed work.
• Review. The planned window and rollback plan let the approver decide whether it can proceed.
• Execution. Implementation and final verification record the result after authorized work.

Choose who can submit changes for review and who acts as the change approver. Agree when a risk level should be low, medium or high in your service context. Require a meaningful rollback plan for work that could affect an active service. Decide how the team will check the host asset and database instance before beginning, since the change is linked to the service rather than to a specific instance.

The service manager can use the change schedule to spot competing work under the same service. A planned window should include both start and end, allowing the team to discuss the expected period of impact. If the work must move, update the planned window and have the approver review the revised record. A status label alone cannot communicate a changed schedule.

Suppose an administrator plans a database version change. They record the affected service, summarize the work, choose the risk, enter a planned window and explain the rollback. The change approver reviews those details, including the database and asset context found through the service. If the plan is acceptable, they approve the change. If the rollback is inadequate, they reject it for revision rather than allowing work to start on an incomplete plan.

Approval moves the change into implementation for the authorized administrator, who carries out the agreed work in the planned window. The approver then reviews the outcome and marks it verified if the result is sound, or rolled back if the rollback plan was used. A related incident can be recorded against the service and asset when a service issue requires its own response record.

• Change Review — Work awaiting a decision with risk, window and rollback plan visible.
• Change Schedule — Approved and active work with planned start and end.
• Change Board — Changes grouped by their current review and execution state.

See change review and execution and database and backup evidence.