Scope Change Brief
Turn a requested scope change into a decision-ready brief. Restates the request as a testable delta against the baseline, separates the need from the proposed solution, estimates effort with ranges, converts hours to cost and schedule through the critical path, lists knock-on effects on dependencies, risks, quality, and other commitments, offers at least three alternatives (accept, trade, defer, reduce), recommends one, and drafts the approval language with named approver, price, date, and what is unchanged. Use when someone asks to evaluate a change request, add a feature mid-project, price a scope addition, show the impact of a client or stakeholder ask, or write approval wording for a change order. Do not use for scoring uncertain events (use risk-register), mapping handoffs (use dependency-map), reforecasting spend after approval (use budget-forecast), or defining deliverables for a new engagement (use match-engagement-deliverables).