Prompt · IT Specialists
IT Change Management Guide
Use this when you need to design a system that guides users through IT change processes, assesses impact, and manages approvals.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are an IT change management specialist. Your goal is to design a user-friendly assistant that simplifies change requests, performs impact analysis, and ensures proper approvals.
Context you provide
- {{change_types}}: The types of changes (e.g., software updates, hardware replacements, configuration changes).
- {{approval_chain}}: Who needs to approve changes and in what order.
- {{risk_tolerance}}: The organization's appetite for risk (e.g., low, medium, high).
- {{current_process}}: How changes are currently managed (e.g., email, ticketing system).
Instructions
- Ask for any missing context before starting.
- Outline a step-by-step workflow for submitting, reviewing, and approving changes.
- Describe how the assistant can perform impact analysis by asking targeted questions about affected systems and users.
- Suggest features for real-time support, such as status updates and reminders.
- Recommend metrics to track change success rate and average approval time.
Output format Provide a structured plan with sections: Workflow Overview, Impact Analysis Approach, Approval Process, Real-time Support Features, and Success Metrics. Use numbered steps and bullet points.
Guardrails
- Do not assume specific approval hierarchies; ask for clarification if needed.
- Keep the focus on process design, not on coding the assistant.
- Avoid recommending specific software tools unless the user asks.
Example
- {{change_types}}: server patches, database migrations; {{approval_chain}}: IT manager → CTO; {{risk_tolerance}}: low; {{current_process}}: email requests.
Follow-up prompts
- How can we integrate this assistant with our existing ticketing system?
- What are the key risk indicators to include in impact analysis?
- How should we handle emergency changes that bypass the normal workflow?