Assess the impact of a change request
Evaluates a scope change's impact on time, cost, quality, and risk.
The prompt
Role: Act as a delivery lead assessing a change request for the change control board.
Context: The change requested and who raised it: [CHANGE_REQUEST]. Reason / driver: [DRIVER]. Current baselines (scope, schedule, cost, quality): [BASELINES]. Current status and critical path: [STATUS_CP]. Dependencies and other in-flight changes: [DEPENDENCIES]. Benefits case it affects: [BENEFITS_CASE].
Task: Produce: a clear statement of the change and its rationale; the impact on scope, schedule (including critical path), cost, resources, risk, and the benefits case if accepted; the impact of NOT making the change; 2-3 options (accept as-is / accept modified / defer / reject) with pros, cons and cost; a recommendation with the reasoning; and the approvals needed.
Format: Sections: Change & rationale | Impact analysis (scope / schedule / cost / risk / benefits) | Do-nothing impact | Options | Recommendation | Approvals. ~450 words.
Verification: Quantify schedule and cost impact against the baselines and show the assumption; flag any impact you cannot size without more input.
Validation: Challenge as a sponsor watching the budget: is the recommendation driven by benefit and risk, or by avoiding a hard conversation? Re-justify if needed.
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
- CHANGE_REQUEST
- DRIVER
- BASELINES
- STATUS_CP
- DEPENDENCIES
- BENEFITS_CASE
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Build a RAID log (risks, assumptions, issues, dependencies)Captures and tracks the risks, assumptions, issues, and dependencies on a project.
- Create a risk register with mitigationsIdentifies, scores, and plans responses to project or business risks.
- Capture lessons learned from a projectA blameless lessons-learned write-up with actions for next time.
- Turn business insights into an action plan with owners and deadlinesConverts findings from an analysis, review, or workshop into a prioritized action plan with owners, deadlines, and success measures.