Write a change request that gets through the change board
Drafts a complete change request with risk, testing, rollback, and communication so approvers can say yes quickly.
The prompt
Write a change request for our change advisory board (CAB).
Change: [WHAT I am changing - e.g. "upgrade the VPN appliance firmware"]
Why: [business or security reason, ticket or vulnerability reference]
Systems and users affected: [SCOPE]
Proposed window: [DATE, TIME, DURATION]
Implementation steps I plan: [ROUGH STEPS]
Testing done so far: [lab, pilot, vendor notes - or "none yet"]
Change type: [standard / normal / emergency]
Write the request with these sections:
1. Summary (two sentences a non-technical approver understands).
2. Business justification and the risk of not doing it.
3. Scope and impact: services, users, and dependencies, including expected downtime.
4. Risk assessment: likelihood and impact rating with reasons; what could go wrong.
5. Implementation plan: numbered steps with expected duration and who does each.
6. Test and verification plan: how we will know it worked.
7. Rollback plan: trigger conditions, steps, and time to roll back. If rollback is not possible, say so and explain the mitigation.
8. Communication plan: who is told, when, and how.
9. Approvals needed.
Rules: flag missing information as [ADD: ...] instead of guessing. Point out any weakness an approver will likely question (no tested rollback, window during business hours, missing backup). Keep it under two pages.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- SCOPE
- DATE, TIME, DURATION
- ROUGH STEPS
- lab, pilot, vendor notes - or "none yet"
- standard / normal / emergency
- ADD: ...
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a project closure reportFormally closes a project: results vs. objectives, handover, open items, and lessons.
- Write a banquet event order for a wedding or functionA complete BEO that tells kitchen, banquet, AV, and setup teams exactly what to deliver and when.
- Investigate a truck crash and write the internal incident reportA structured crash investigation covering evidence, timeline, root cause, preventability, and corrective actions, written factually.
- Write a corrective action plan for a recurring quality problemA CAPA plan that contains the problem, finds the root cause, fixes it, and proves the fix worked.