← IndexEntry № 088·business

Push Back on Scope Creep Without Damaging the Relationship

Draft a collaborative, firm reply that handles scope creep without damaging the relationship.

Optimized for

§ When to use this

This prompt drafts a client reply that declines out-of-scope work without sounding defensive — it acknowledges the request, ties the boundary back to the original agreement, and offers a concrete path forward like a change order or trade-off. Reach for it the moment a 'quick favor' request would quietly expand the project, when you need to protect your time but keep the relationship warm. The explicit ban on passive-aggressive language is the differentiator; most people either cave or sound resentful, and this aims for firm-but-collaborative.

§ The Prompt— fill in the fields, then copy or open in a tool

§ Customize0/2 fields filled

Description[DESCRIPTION]The new request, stated plainly. Example: 'a full redesign of the mobile app's onboarding flow, which wasn't part of our website project.'

What we agreed to[WHAT WE AGREED TO]The original scope, ideally quoted from the contract or SOW. Example: 'a 5-page marketing website with copy and a contact form, fixed bid.'

your prompt — fill the fields above

Draft a reply to a client asking for work beyond our agreed scope. New request: [DESCRIPTION]. Original scope: [WHAT WE AGREED TO]. Reply must (1) acknowledge the request positively, (2) clearly identify it as out-of-scope referencing the original agreement, (3) offer a path forward (change order, additional fee, or trade-off), (4) avoid passive-aggressive language. Tone: collaborative, professional, firm.

Open with your prompt →ChatGPT ↗Claude ↗Sends your filled-in prompt straight into a new chat.

§ Example Output

What you can expect back

Hi Jordan,

The onboarding redesign is a great idea — a smoother first-run experience would absolutely pay off, and I'd be glad to take it on.

It does sit outside our current agreement, which covers the 5-page marketing site, copy, and contact form on a fixed bid. The app onboarding is a separate piece of work with its own design and build effort, so I'd want to scope it properly rather than squeeze it in and shortchange it.

A couple of ways forward: I can put together a small change order with a fixed price and timeline for the onboarding flow, or if budget is tight this quarter, we can keep the website on track now and slot the onboarding into a phase two. Happy to do whichever fits your priorities — just let me know which direction you'd like and I'll send details.

Best,
Alex

Illustrative example — your results will vary by tool and inputs.

§ Pro Tips

Get sharper results

01Quote the original scope verbatim from your contract in the [WHAT WE AGREED TO] field — a reply that references the exact agreed language lands far better than a paraphrase the client can dispute.
02Always have it offer at least two paths (paid change order and a free trade-off like a phase two); a single 'that costs extra' reads as a wall, two options read as partnership.
03Tell the model your relationship temperature — a long-trusted client and a tense new one need different warmth and firmness dials.
04Ask it to keep the email short; the longer the justification, the more it sounds like you're bracing for a fight. Aim for three tight paragraphs.
05Have it end with a clear single question ('which direction works for you?') so the ball is in their court and the thread doesn't stall.

§ Variations

Adapt it for your case

Recurring small asks

Reframe for the pattern, not one request: gently name that several extras have accumulated and propose a retainer or bundled change order.

Internal stakeholder version

Adapt the tone for a colleague or manager rather than a paying client, swapping 'change order' for 'reprioritization' against current commitments.

Hard no required

When the work truly can't happen, ask for a warm but unambiguous decline plus a referral to someone who can help.

Best For — Roles

Use For — Tasks

Editing Text

Tags#scope#freelance#client-management

§ FAQ

Common questions

Won't pushing back risk losing the client?

Done well it usually builds trust — clients respect a clear boundary with a path forward more than silent resentment or sloppy free work. The collaborative framing is what protects the relationship.

What if there's no written scope to reference?

Reference whatever you do have — the proposal, an email, the original brief. Tell the model the loose agreement and ask it to anchor on that, and treat this as a prompt to document scope next time.

How firm should I be?

Firm on the boundary, flexible on the path. Keep 'this is out of scope' non-negotiable while offering genuine options, and ask the model to never apologize for the boundary itself.

§ Related Entries