Plan a change to a managed service
Agree the outcome, approval, timing, and validation before implementation.
Define the intended result
Explain the current behavior, requested change, and business reason. Include the service, business owner, desired deadline, and preferred maintenance window. Describe constraints such as working hours, customer impact, or integrations that must continue to function.
Provide a reviewable request
- Identify the systems and users in scope.
- Supply the proposed settings, content, or requirements.
- Name the authorized approver.
- Explain dependencies and timing constraints.
- Define how you will recognize a successful result.
A precise outcome helps the team determine whether the request fits the existing engagement or needs additional work to be agreed.
Confirm implementation details
Depending on impact, the team may need a documented sequence, backup or recovery approach, communication plan, and validation steps. Submitting a ticket begins that discussion. It does not automatically authorize disruptive changes or changes outside the stated scope.
Close the loop
After implementation, test the agreed business workflow and record the result. Report remaining differences on the original ticket so they can be compared with the approved request. If the deadline, scope, or approver changes before execution, update the conversation promptly rather than assuming the original plan still applies.
Include this guide and what you tried in your ticket so we can pick up from there.
Contact support