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.
- Server Monitoring
- Process
- Change review
Change review
Put a recorded human decision before implementation and keep the release outcome visible.
Step by step
-
Draft change Release Operator
The Release Operator names the service, summarizes the work, selects risk and records a rollback plan.
- Establish risk and rollback plan
- Updates Changes, Services
-
Schedule review Release Operator
The operator records planned start and end times so the reviewer can consider the service effect.
- Put the proposed window in context
- Updates Changes, Maintenance windows
-
Decide Change Reviewer
The Change Reviewer enters a review decision, reviewer and reason. An approved decision permits the change to proceed; a rejected decision leaves the reason visible.
- Record approval or rejection
- Updates Change reviews, Changes
ApprovalA person approves before the work moves on. -
Implement Release Operator
The Release Operator records a pending deployment for the service, then records its environment, version and outcome.
- Preserve the release outcome
- Updates Deployments, Changes
-
Verify Release Operator
The operator records rollback checkpoint results and reviews new health observations with the Service Owner.
- Compare expected and actual result
- Updates Rollback checks, Availability checks
Who does what
Roles and permissions- Release Operator
- Prepares and implements; Change Reviewer decides; Service Owner checks the service effect.
Set up Server Monitoring your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.