PermitANY
ConfigurationPrompt

Network Change Request Writer

Describe a network change and get a complete change request document: scope, risk assessment, rollback plan, step-by-step implementation, and verification commands.

35 copies
ChatGPTClaudeGemini

Customize variables

Describe the change in plain language

Devices, OS versions, and impact scope

When the change will be executed

Tips for better results

  • ·Be specific about the devices and IOS versions — the AI generates exact CLI commands for your platform
  • ·Mention any dependencies (HSRP, STP root, routing protocols) that could be affected
  • ·The rollback plan is the most important section — review it carefully before the change window
  • ·Copy the output to your ticketing system (ServiceNow, Jira) and share with your team for approval

Prompt preview

○ CHANGE_DESCRIPTION○ ENVIRONMENT○ MAINTENANCE_WINDOW
You are a senior network engineer writing a formal change request document.

Change: [What are you changing?]
Environment: [Environment / devices involved]
Maintenance window: [Maintenance window]

Write a complete change request document with these sections:

## 1. Change Summary
One paragraph description of the change and business justification.

## 2. Scope & Impact
- Devices affected
- Services/users impacted during the change
- Expected downtime (if any)

## 3. Risk Assessment
- Risk level: LOW / MEDIUM / HIGH with justification
- What could go wrong
- Dependencies and prerequisites

## 4. Pre-Change Checklist
Verification steps before starting (backups, confirmations, baseline captures).

## 5. Implementation Steps
Numbered step-by-step with exact CLI commands for each step.

## 6. Verification
Commands to confirm the change worked correctly with expected output.

## 7. Rollback Plan
Step-by-step rollback procedure with exact CLI commands if the change needs to be reversed.

## 8. Post-Change Monitoring
What to watch for in the 24 hours after the change.

Tags

change-managementdocumentationitilrollbackmaintenance