Change preparation

When to use

Use this guide when you need to prepare evidence, dependencies, validation steps, and rollback considerations for a proposed change.

What you need

Replace these bracketed values before you copy the prompt.

• change requestRequired

  Change ticket identifier or proposed change description.

• maintenance windowOptional

  Optional proposed maintenance window.

Information used

Stackyapper uses only the Apps and permissions available to the current user.

• Service ticketsRequired
• Ticket historyIf available
• Managed devicesIf available
• Device policiesIf available
• Identity configurationIf available
• Asset inventoryIf available
• DocumentationIf available

Expected output

• Change scope
• Dependencies and affected parties
• Risk and approval gaps
• Validation plan
• Rollback considerations

Steps

1. Resolve the objective, scope, approvals, affected parties, and timing.
2. Collect relevant history, device, policy, configuration, asset, and runbook context.
3. Produce a pre-change plan with risks, validation, rollback, and approval gaps; execute nothing.