Changes

A planned service change has a risk level, a scheduled start and end, and a rollback plan. Service Operator moves the record into Review so the window and recovery path can be checked before approval. An approved change remains distinct from one being implemented or verified.

The service link lets the operator check the scope of the window. Keep the risk and rollback plan beside the schedule when handing work to the implementer. If the provider rejects related work or the implementation fails, record the outcome as a rollback instead of marking verification complete.

• Ownership. Service Operator prepares the change and makes the review decision.
• Evidence. Check risk, the start and end of the window, and the rollback plan.
• Follow-through. Verify observed work before changing the final status.

Agree which service owns the change, who reviews the risk and window, and what counts as provider acknowledgment. The scheduled period gives the team a shared reference when an incident begins during implementation. Rollback details must be usable before the work starts.

Rehearse an ordinary record and an exception with the people who will use this area. Check the linked owner or service before changing a status. If the outside information changes, compare it with the original request before the next handoff.

Use a change for a service that supports a domain. Check the planned window against the service context and read the rollback plan. Approve the change only after the review, then compare the provider response with the expected work before marking it Verified.

Have the receiving operator repeat the check using the linked records. Review a mismatched owner, value or date with the decision owner before applying the same handling to more work.

For an exception, schedule a change during a service incident. The Service Operator should compare the planned start and end with the incident chronology and decide whether to proceed or defer. A risk label alone does not explain how the service will recover. Read the rollback plan aloud to the person expected to use it. If the outside work fails, record the observed outcome and keep the change in the appropriate state. A scheduled end is only a plan; verification depends on the acknowledged result. Make the service owner aware of that result before closing the handoff.

• Change review inbox — Changes awaiting a decision on risk, window and rollback plan.
• Change window schedule — Approved or implementing changes with their planned start and end.

Follow the change planning handoff and review the data model before migrating records.