Fill in your details optional The prompt below updates as you type. What you type stays in this browser and is never sent to us.
You are a project manager handling change control, working with engineering leads, developers and IT buyers at a software company that ships a SaaS product.
## Goal
Assess a requested change and give a clear recommendation on whether to accept it.
## What matters in IT & Software
- People involved: product managers; engineering leads; DevOps and SRE engineers; the security team; customer success; IT buyers and procurement.
- Common risks to plan for: outages; data breaches and security holes; vendor lock-in; scope creep; knowledge held by one person; churn after a bad release.
- Documents people already work with: PRDs; technical design docs; runbooks; incident postmortems; release notes; security questionnaires.
- Timing and seasons: quarterly planning; release trains; annual renewal dates; end-of-quarter and fiscal-year-end deals.
## What I will give you
- The change requested: [DESCRIBE THE CHANGE]
- Who asked and why: [REQUESTER AND REASON]
- Current plan: [DEADLINE, BUDGET, SCOPE SUMMARY]
## What to do
1. Describe the change and the problem it solves.
2. Estimate the impact on scope, schedule, cost, quality and risk.
3. List the options: accept, reject, defer or accept with trade-offs.
4. Recommend one and explain why.
5. Draft the decision record and the message to the requester.
## What to deliver
- A change impact table
- A recommendation with reasoning
- A change log entry
- A reply to the requester
## Rules
- Keep uptime, security and data-protection requirements in mind throughout, and point out anything in my plan that would break them.
- Where it fits, connect your recommendations to deployment frequency and uptime.
- Use plain language and short sentences. Use headings and tables where they make the answer easier to scan.
- Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.
## Before you answer
Check your draft against this list and fix anything that fails:
- Every task, risk and action has an owner role and a date or trigger.
- It is written for a software company that ships a SaaS product; nothing in it would read the same for any other business.
- Every item under "What to deliver" is included.
How to use this prompt
- Copy the prompt. Press Copy prompt and the full text goes to your clipboard.
- Fill the brackets. Use the form above, or replace [DESCRIBE THE CHANGE], [REQUESTER AND REASON], [DEADLINE, BUDGET, SCOPE SUMMARY] with your own details.
- Paste and send. Paste it into ChatGPT, Claude, Gemini and Microsoft Copilot and send. Ask follow-up questions to refine the answer.
Why use this Run a change request assessment prompt?
This run a change request assessment prompt is written for a software company that ships a SaaS product. It tells the assistant who the answer is for (engineering leads, developers and IT buyers) and the limits it must respect: uptime, security and data-protection requirements. That context is what turns a generic reply into one an IT & Software team can use straight away.
Most people type a single line and get a generic answer back. This prompt gives the assistant the role, the context and the structure it needs, so the first answer is already close to what you would hand to your team. Because it is written for IT & Software, it keeps the focus on what that industry measures: deployment frequency and uptime.
How to get the best answer
- Be specific in the brackets: real names, numbers and dates give a far better answer than placeholders.
- Paste real material: where the prompt asks for notes, data or text, paste the actual content rather than a summary.
- Refine in the same chat: ask "make it shorter", "turn it into a table" or "add more detail on step 2".
- Check the result: review it against what you know about deployment frequency and uptime before you share it.
Other industries
Same prompt for other industries
The same run a change request assessment prompt, rewritten for each industry.
FAQ
Frequently asked questions
Which AI assistant works best with this Run a change request assessment prompt?
It works in any chat assistant. It suits ChatGPT, Claude, Gemini and Microsoft Copilot best. Paste it in, send it, and ask follow-up questions in the same chat.
What do I need to replace before sending it?
Replace the 3 highlighted brackets – [DESCRIBE THE CHANGE], [REQUESTER AND REASON], [DEADLINE, BUDGET, SCOPE SUMMARY] – with your own details. The more specific you are, the better the answer.
Is this prompt only for IT & Software?
This version is written for a software company that ships a SaaS product. The same prompt is also available for 15 other industries, listed on this page.
Is it free to use?
Yes. Copy it as often as you like and use it in your own work. No sign-up is needed.
Can I trust the answer?
Treat it as a strong first draft. Check facts and figures yourself, especially anything with legal, financial, medical or safety consequences.
Keep exploring