Reset a Client Relationship After Repeated Scope Creep Without Blame

Get a calm client email with a table comparing what was agreed to what has been asked, plus a simple change-request path and a pre-send checklist.

You getSubject line, email body containing a table with these columns and "How to add work"

Prompt

Prompt
Act as an account manager who writes calm, firm client emails for agencies, consultants and freelancers.

Right after this prompt I will paste two things: a summary of what my contract or statement of work covers, and a list of recent client requests. Write an email that resets the relationship by restating what we agreed and giving a clear path for anything extra.

Rules:
1. No blame language: never use "scope creep," "again," "as previously stated" or "unfortunately." Describe the requests, not the client's behavior.
2. Every table row must closely paraphrase my contract summary and the actual request. Do not invent terms, prices or dates. If something is unclear, mark it "Needs confirming."
3. For each out-of-scope item, offer two options: add it through a change request, or swap it for an equal in-scope item.
4. Open with one sentence about real progress on the project. Close with one specific next step, such as a 20-minute call this week.
5. Keep the email body under 250 words, not counting the table.

Output format:
- Subject line: 2 options
- Email body containing a table with these columns: Item | What we agreed | What's been asked | Where it stands
- "How to add work": 3 numbered steps
- Note to me: items to check against the contract before sending

End by listing any assumptions you made about pricing, timelines or contract terms.

Example output

At a glanceAgreed scope vs. new client requestsBrightwell dental site: 4 extra requests against the plan
ItemWhat we agreedWhat's been asked
Site pages8 pages in SOW9th Invisalign page
Revisions2 rounds per page3rd round on About
BlogNot listedSetup + 3 starter posts
Check-insFortnightly 30-min callWeekly calls
Launch support2 weeks of fixesBug fixes after launch

Example for: a small web studio building an 8-page site for a dental clinic. The contract includes 2 revision rounds, and the client has made 4 extra requests.

Subject line options

  1. Brightwell site: where we are and next steps
  2. Quick alignment on the Brightwell website plan

Email

Hi Lena,

The homepage and services pages are approved, and the new booking flow tested well with your front-desk team last week. That's a strong position to finish from.

We've had several new ideas come in, so I'd like to line them up against our original plan. That way we both know what's included and what would need a separate quote.

ItemWhat we agreedWhat's been askedWhere it stands
Site pages8 pages, listed in the SOWA 9th landing page for InvisalignOutside current plan
Revisions2 rounds per pageA third round on the About pageOutside current plan
BlogNot listedBlog setup with 3 starter postsOutside current plan
Check-insFortnightly 30-min callWeekly callsNeeds confirming
Launch support2 weeks post-launch fixesBug fixes after launchIncluded

For each item outside the plan, there are two easy options. We can add it with a short change request, and I'll send a quote within 2 business days. Or we can swap it for something already in scope. For example, we could drop the Team page and build the Invisalign page in its place.

Could we do a 20-minute call Thursday or Friday to choose? Once we agree, I'll confirm the timeline in writing.

Best,
Marcus
Harbor & Pine Studio

How to add work

  1. Reply with the items you'd like to add or swap.
  2. We send a one-page change request with cost and timeline impact.
  3. Work starts once you approve it by email.

Note to you before sending

  • Confirm the SOW lists exactly 8 pages and names them.
  • Check whether "fortnightly calls" is written in the contract or was only agreed verbally.
  • Make sure your 2-day quote turnaround is realistic.

Assumptions: I did not include prices or a launch date because none were provided. I treated the call frequency as unclear because your summary didn't specify it.

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

Tips and common edits

Why this works

  • Banning blame words like "again" and "scope creep" keeps the email factual, so the client doesn't get defensive.
  • The agreed-vs-asked table turns a tense conversation into a neutral comparison the client can check against the contract.
  • Offering a choice between adding and swapping gives the client control and protects your margin.

Use this in ChatGPT, Claude or Gemini when extra requests keep piling up. Have your SOW or contract summary ready, plus a plain list of what the client has asked for recently.

Common edits

  • Add your hourly or day rate so the email can include price ranges for each extra item.
  • Ask for a shorter version to send over Slack or Teams before the full email.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Email