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

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 Blocks

Example output

Example for: adding single sign-on authentication mid-project

Change Request Summary
FieldDetails
Change Request IDCR-2024-014
TitleAdd Azure AD Single Sign-On (SSO) Support
RequesterSecurity Operations (Mark Vance)
Date SubmittedOctober 12, 2024
Description and Justification

Implement SAML 2.0 single sign-on integration via Azure AD for enterprise customers. This change addresses updated corporate compliance requirements mandated for enterprise contracts starting in Q1.

Impact Matrix
DimensionBaselineRevisedVarianceRisk Level
ScopeEmail/password login onlyAzure AD SSO + existing auth+1 integration moduleLow
ScheduleLaunch Nov 15Launch Nov 29+2 weeksMedium
Budget$85,000$94,500+$9,500Low
Resources2 Fullstack Devs2 Fullstack Devs + 1 SecOps Lead40 additional hoursMedium
RiskNo external identity dependencyRelies on corporate Azure AD tenantNew external dependencyMedium
Implementation Plan
  1. Provision staging Azure AD tenant credentials by October 20.
  2. Develop and test authentication handshake by November 5.
  3. Conduct penetration test and role mapping audit by November 12.
  4. Deploy to production alongside the November 29 release.
Decision Recommendation and Sign-off Blocks

Recommendation: Approve. Compliance requires this integration before enterprise onboarding can proceed.

Approved by Project Sponsor: __________________ Date: _______
Approved by PMO Lead: ________________________ Date: _______

Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Project Management
Project Management

Draft a formal project charter

Create a clear, authoritative project charter defining scope boundaries, measurable success metrics, and sponsor decision rights.

Project Management

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.