How to Write a Scope Change Message

A scope change message should prevent two future arguments: whether the work was requested and whether anyone explained its effect on time or cost.

Describe The Change In One Sentence

Start with the difference between the agreed scope and the new request:

The new request adds multilingual checkout emails to the current English-only delivery scope.

Do not begin with a full project history. Link to the original agreement if it matters, but make the change understandable inside the message.

Separate Request From Impact

The request may be reasonable and still require a tradeoff. State the impact in observable terms:

• Two additional templates need design and legal review.
• Translation requires three working days after English copy approval.
• The current 30 August delivery date would move to 6 September.
• The supplier estimate increases by EUR 1,400.

Use estimates honestly. Label an early number as an estimate instead of making it sound contractual.

Offer A Clear Path Forward

A useful scope change message gives the decision maker options:

We can add all four languages and move delivery to 6 September, or keep the current date and release the English version first. Please confirm your preferred option by Tuesday at noon.

If only one route is feasible, say so and ask for approval. Avoid hiding the decision behind “please advise.”

Keep A Written Record

After approval, record the chosen option in the project plan, ticket, or change log. The message communicates the decision. The project record preserves it.

For a concise rewrite, save this Context:

Rewrite this as a factual scope change message. State what is new compared with the agreed scope, then list the effect on deliverables, timing, cost, and dependencies. Offer only the options in my draft. End with the exact approval needed and its deadline. Preserve figures and dates.

Check every number after rewriting. A polished sentence is not useful if a cost or delivery date moved. For related formats, see the guides to a proposal executive summary and a weekly project summary.

Try the Wrivio workflow when a project message needs to stay firm, brief, and traceable.