Turning a scope change into a clear stakeholder communication
A mid-project scope change is a communication problem as much as a planning one: the sponsor needs to understand what is changing, what it costs in time and money, the options, and the decision you need from them. Written under pressure, these notes come out defensive or vague. AI shapes your assessed impact into a clear, neutral change request — provided it uses only the numbers you have actually worked out.
You are a project communications assistant. Draft a clear, neutral scope-change communication for a stakeholder, based only on the impact assessment I provide. Do not invent cost, schedule, or scope figures. What is changing and why (the request): {{change_description}} Impact I have assessed (schedule, cost, scope, quality, risk): {{impact_assessment}} Options I want to present: {{options}} Recipient and the decision I need from them: {{recipient_decision}} Produce: 1. A one-line summary of the change and who requested it. 2. Why it has come up now. 3. Impact — using only my figures — on schedule, cost, scope, and risk. 4. Options with the trade-off of each, and my recommendation. 5. The specific decision and by-when I need from the recipient. Rules: - Use only the impact figures I provided. Do not estimate or invent a cost or a number of days — mark anything I left blank as [VERIFY] rather than filling it. - Neutral and factual, not defensive or persuasive. Present the trade-offs honestly. - Make clear the decision belongs to the sponsor/change board, not to me and not to any tool. - Keep it to something a busy stakeholder will actually read.
Fill in your details and the prompt updates live — then copy.
Change summary: The client has requested multi-currency support for the portal, which was not in the original scope. Why now: Raised during UAT as a launch blocker for their EU customers. Impact (from our assessment): +15 development days, +$18k, and a 2-week shift to go-live. Adds a dependency on a live FX-rate feed. Options: - A) Add now — meets the client need but moves go-live two weeks. - B) Ship v1 without it, fast-follow in v1.1 — protects the date; leaves EU customers waiting. Recommendation: Option B, if the date is the priority. Decision needed: Your approval of an option and any budget by July 18.
The full workflow
- Assess the real schedule, cost, and scope impact yourself before drafting
- Run the prompt with only your assessed figures and resolve every [VERIFY]
- Have finance or your PMO confirm cost and contract implications
- Send through your change-control process and record the decision in the change log
Watch out for
Never let AI generate the cost or schedule numbers — a fabricated impact figure in a change request can commit real budget and mislead the sponsor. Provide the figures yourself and verify them; the AI only shapes the wording.
The scope and budget decision belongs to the sponsor or change control board, not to the AI and not to you unilaterally. Present options and a recommendation; let the accountable stakeholder decide.
Change requests often carry commercial and contract detail. Keep client names, pricing, and contract terms out of consumer AI tools; use an approved enterprise account or generic placeholders.
Where this comes from
Every use case on this site is grounded in real reports from working project managers — not invented by us.