A scope change request records what someone wants to add, remove or revise after work has been agreed. To write one, compare the original commitment with the proposed change, show its effect on time, cost and responsibilities, and ask the authorized decision-maker to approve, reject or defer it before treating the new work as committed.
This guide gives you a one-page template, a completed illustrative example and four emails for different relationships. It focuses on the decision record rather than general advice about spotting scope creep.
When do you need a scope change request?
Use a written request when a new instruction materially changes an approved deliverable, acceptance criterion, deadline, cost or resource commitment. A typo correction within an agreed review round might be routine; adding a second audience, new data source or approval round may change the baseline. Compare the request against the signed brief, statement of work, project plan or latest documented agreement rather than memory.
The Association for Project Management describes change control as capturing, evaluating and deciding requests to alter an approved baseline. A request is not itself approval. The relevant approver and procedure depend on your organization and contract. See APM’s change-control explanation and PMI’s discussion of baseline control and change logs.
Practical tip: Attach the original brief version and quote the exact affected line. “Add regional breakdown” is ambiguous until you show that the approved report specified a single consolidated table.
One-page scope change request template
Copy these fields into a document, shared form or change log. The purpose is to enable a decision, not reproduce the whole project history.
| Field | What to enter |
|---|---|
| Change ID and date | CR-014; 11 November 2026 |
| Project and requester | Quarterly supplier report; Operations |
| Original approved scope | One consolidated supplier scorecard, approved brief v2 |
| Requested change and reason | Add regional breakdown for three markets to support regional review |
| Impact on time | Three additional working days proposed; dependency on regional data |
| Impact on cost and people | Eight analyst hours estimated; budget decision required |
| Options | A: extend delivery; B: replace existing appendix; C: defer breakdown |
| Approval authority and decision due | Project sponsor; decision requested by 13 November |
| Decision and record | Pending; approver, timestamp, conditions and baseline version after decision |
Replace every sample value with your actual records. Keep the decision field pending until an authorized person replies; a requester’s enthusiasm does not change approval authority.
Small tip: Use a stable ID such as CR-014 in the email subject, request file and decision log. Name the attachment CR-014_supplier-report_regional-breakdown_v1.docx. If reviewers reply in separate threads, the ID keeps the decision and the supporting estimate together.
Worked example: from vague addition to an approvable decision
Illustrative scenario: A team is due to deliver a consolidated supplier scorecard on 20 November. On 11 November, a regional manager asks for separate views for Hong Kong, Singapore and Malaysia. The approved brief contains only a combined scorecard, and the source files use different regional codes.
Before: “Please add three regional tabs to the report. It should be quick.” This leaves the analyst to guess whether the tabs replace existing work, whether regional data can be compared and who can move the delivery date.
After: The analyst creates CR-014, identifies the approved scope as “one consolidated scorecard,” and lists the additional regional breakdown as a new deliverable. The analyst estimates eight hours for code mapping and review, notes the need for regional data confirmation, and proposes either extending delivery to 25 November or removing the optional commentary appendix while keeping the original date.
The project sponsor reviews the alternatives with the regional manager. In this example, the sponsor approves replacing the appendix, with regional data owners confirming their mappings by 13 November. The analyst records the approver, date, condition and revised deliverable list in the decision log, then updates the project brief to v3. The original 20 November deadline remains only because the approved trade-off removes other work.
Easy-to-miss detail: Separate the requested decision date from the proposed delivery date. If regional owners miss their data checkpoint, the team needs a fresh decision; a conditional approval should not be presented as an unconditional deadline promise.
How to assess time, cost and approval before sending
Start with the actual baseline and write the delta, not a new project plan. Ask what additional work is required, which tasks can be removed, which dependencies must respond, and whether the original acceptance criteria still apply. Estimate effort and elapsed time separately: eight hours of analysis may span three days if the team must wait for external data.
For cost, specify the estimate basis. “Eight analyst hours” is more useful than “small extra cost,” even when no hourly rate is appropriate to disclose. If procurement, legal review or a vendor quote is involved, state that dependency rather than inventing a price. Note the person who can authorize budget or contract changes.
Offer at least two credible choices. An extension may preserve the full original deliverable; a substitution may protect the date; deferral may protect the approved baseline. Do not suggest that every project can simply add staff or skip required reviews. For more on the initial conversation, read how to handle scope creep.
Practical tip: Put “decision required” beside each assumption that only a manager or client can authorize. For example, “Replace appendix: sponsor approval required” prevents an analyst from treating a proposed trade-off as a personal scheduling choice.
Four copy-ready scope change request email examples
1. To your manager: ask for a priority decision
Subject: CR-014 — decision needed on regional report breakdown
Hi [Name], the approved supplier report covers one consolidated scorecard. The new request adds three regional views and requires data mapping and review. I estimate eight additional analyst hours. We can move delivery to 25 November or replace the optional appendix to retain 20 November, subject to regional data confirmation. Which option would you approve by 13 November? I will update the brief after your decision.
2. To a peer: request impact information, not authorization
Subject: CR-014 — regional data dependencies for proposed change
Hi [Name], we are assessing a proposed regional breakdown for the supplier report. Could you confirm which market files are available, who owns the regional code mapping and when the data can be checked? Please flag any known gaps by 12 November. This is an impact assessment; the project sponsor will decide whether the change proceeds.
3. To a client: present a formal choice
Subject: Scope change request CR-014 — regional reporting option
Hello [Name], following your request for separate regional views, we have documented the change against the agreed consolidated report. The additional work affects data preparation and review. Attached is CR-014 with the proposed schedule and deliverable options. Please confirm your preferred option and the authorized approver by 13 November. We will confirm the revised scope and schedule after the change is formally approved.
For contracted work, use the contractual notice and variation process where required. A friendly email is not a substitute for the agreed authorization mechanism.
4. To a third party: hold the dependency without promising delivery
Subject: Regional data availability check — CR-014
Hello [Name], we are evaluating a possible addition to the supplier report. Can you confirm whether the three regional extracts and code definitions can be provided by 13 November, and whether any access approval is needed? Please send availability and constraints only for now. We will confirm any formal work request after our internal scope decision.
Record the decision and hand off the revised baseline
After the approver responds, record the change ID, outcome, decision date, decision-maker, conditions, impacted deliverables and revised baseline version. A status such as Approved with conditions is different from Approved. If the request is rejected or deferred, retain the record so the same request does not quietly reappear as an assumed commitment.
Send a short confirmation to the people who execute and review the work: what changed, what stayed the same, who owns the next step and which document is now authoritative. If there are several requests, keep a separate decision log rather than burying outcomes in inbox threads. For follow-up structure, see the decision-log guide and deadline pushback guidance.
Frequently asked questions
Can I submit a change request without knowing the cost?
Yes. Record the requested outcome and mark cost assessment as an assigned action. Do not insert a fabricated zero; the approver needs to know what remains to be evaluated before commitment.
Who approves a scope change request?
The authorized person or body identified by the project governance, delegation or contract. The requester, analyst and project manager may have different roles. Record the actual decision authority.
What if someone says the change is urgent?
Use the organization’s expedited approval route where available, identify the minimum necessary work and document the decision afterward according to policy. Urgency does not by itself establish authority to change budget or contractual commitments.
Make the next decision easy
A good scope change request is short because it isolates the decision: baseline, proposed difference, impact, alternatives and approval. Keep the record with the project documents, and update the baseline only when the decision is authorized.
For more wording around difficult approvals, deadlines and scope changes, explore our Difficult Work Emails & Pushback Vault (US$4.99), with 100 editable Word scripts and a searchable PDF. It is a one-time digital purchase through Gumroad; applicable taxes are shown at checkout.