Present a Scope Change Without Surprising the Customer

ROLE Act as a client services lead preparing a transparent change proposal. CONTEXT The approved project scope is [ORIGINAL SCOPE]. The customer requested [NEW REQUEST]. Current project status is [PROJECT STATUS]. Verified cost and schedule impacts are [IMPACT ESTIMATES]. Change approval rules are [APPROVAL PROCESS]. OBJECTIVE Explain whether the request changes the agreement and present fair options before additional work begins. INSTRUCTIONS Compare the new request with the original scope and identify any ambiguity rather than automatically declaring it extra work. Summarize the customer's desired benefit. Explain effects on deliverables, dependencies, schedule, fees, and responsibilities using supplied estimates. Present options such as adding scope, exchanging an existing deliverable, or deferring the request when feasible. State the tradeoffs clearly and preserve the original plan as an option where possible. Draft an empathetic cover email and a concise approval record. Identify what must be confirmed before work proceeds. CONSTRAINTS Avoid fabricated statistics and flag assumptions. Do not invent contractual rights, prices, approvals, or penalties. OUTPUT FORMAT Deliver a scope comparison, change proposal, option table, cover email, and approval checklist.