Create a formal scope change request
Turn an informal change request into an audit-ready scope change form complete with a multi-factor impact assessment.
Prompt
Act as an enterprise project manager. Your job is to produce a structured Scope Change Request document with an impact matrix.
First, ask me 3 numbered questions in one message and wait for my response:
1. What is the requested change, and who requested it?
2. What is the original baseline schedule and budget for this work?
3. Which teams or external vendors are directly involved?
Once I answer, produce the document under these rules:
- State the business justification and problem solved.
- Break down impacts across scope, schedule, budget, resources, and operational risk.
- Provide an explicit recommendation on whether to approve, defer, or reject.
Output format:
Change Request Summary (metadata table)
Description and Justification
Impact Matrix (markdown table: Dimension, Baseline, Revised, Variance, Risk Level)
Implementation Plan (3-4 numbered steps)
Decision Recommendation and Sign-off BlocksExample output
Paste the prompt into Claude, ChatGPT, or Gemini. The model will ask you 3 questions; reply with your details to receive the completed document. You can follow up by asking to convert the matrix into bullet points for an executive memo.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Draft a formal project charter
Create a clear, authoritative project charter defining scope boundaries, measurable success metrics, and sponsor decision rights.
Audit a RACI chart for split accountability
Identify dangerous governance flaws, duplicate owners, and delivery bottlenecks in an existing RACI matrix. Use this before launching high-stakes projects.
Identify silent stakeholders before locking requirements
Uncover hidden reviewers across security, compliance, legal, and IT before scope freezes. Use this during early discovery to prevent late launch blocks.
Synthesize past project lessons into kickoff safeguards
Turn historic post-mortem archives into practical governance rules, charter additions, and pre-mortems for upcoming projects.
Build a project intake scoring rubric for requests
Establish an objective scoring matrix to evaluate incoming project requests and prevent urgent ad-hoc demands from crowding out strategic priorities.
Design a change control board review agenda and rubric
Establish a fast, repeatable 30-minute Change Control Board agenda paired with an objective scoring rubric to approve or reject changes.