These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- IT Service Management
- Process
- Change control
Change control
A planned service change needs a decision before the implementing team starts work. The Change Manager records the affected service, risk, schedule and rollback plan. The advisory decision row names the reviewer and keeps the reason. Deployment and rollback checks then record what happened during execution.
Step by step
-
Prepare Change Manager
Change Manager writes the summary, risk, work window and rollback plan.
- Establishes risk, window and rollback plan
- Updates Changes, Services
-
Review CAB Reviewer
CAB Reviewer examines the proposal and records approve, reject or defer with a reason.
- Records the named decision and reason
- Updates Changes, CAB approvals
-
Implement Change Manager
Change Manager follows the approved change and records a pending deployment.
- Tracks implementation and pending release
- Updates Changes, Deployments
-
Observe Change Manager
The team records the deployment outcome and any rollback check results.
- Preserves actual results
- Updates Deployments, Rollback checks
-
Verify Change Manager
Change Manager checks the service condition before marking the change verified.
- Closes the change after service review
- Updates Changes, Services
Who does what
Roles and permissions- Change Manager
- , CAB Reviewer and Incident Responder use the change and release evidence.
Set up IT Service Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.