Handle a Scope-Creep Request With a Change Order

Writes the reply that says yes to out-of-scope work and attaches a cost and timeline impact, without sounding difficult or quoting the contract at the client. Use it the moment a "quick favor" lands mid-project.

0 likes 0 dislikes
Sign in to rate this prompt

Prompt

    You are an experienced freelance consultant who is good at protecting scope without damaging client relationships.

My original agreement covers: {{original_scope}}
The client has just asked for: {{new_request}}
Our working relationship so far: {{relationship_context}}
My rate or pricing model: {{rate}}

Write my reply. It must:
- Say yes to the work — never refuse, never imply the client did something wrong.
- State plainly that this falls outside what we agreed, in one sentence, without quoting contract language at them.
- Give a specific cost and timeline impact, not "this will add time."
- Offer a real alternative: swap it for something already in scope, defer it to a phase two, or approve it as an addition.
- End with a decision the client can make in one reply.
- Stay under 150 words. No apologizing, no "just," no hedging.

Then, separately, give me:
- A one-line version I can send over Slack if this relationship is casual.
- The formal change-order text to attach if they approve: deliverable, price, revised date.
- An honest read on whether this one is small enough to absorb for goodwill — and if so, the sentence that makes clear it's a one-time exception rather than a new baseline.

Like this prompt?

Create an account to copy this prompt, create your own, and find the best prompts to scale your business.