Handle a client asking for work outside the contract
A response to scope creep that protects the relationship while getting extra work paid for or traded off.
The prompt
A client has asked for work that's outside our agreement. Help me respond.
The request: [WHAT THEY ASKED FOR, in their words if possible]
What the contract or statement of work covers: [RELEVANT SCOPE]
Effort the request would take: [HOURS, TEAM, COST ESTIMATE]
Relationship context: [account value, renewal timing, past favors given]
My options: [e.g. quote it as a change order, swap it for something in scope, do it once as goodwill, decline]
Give me:
1. A quick read: is this clearly out of scope, a gray area, or actually covered? Point to the relevant scope wording.
2. Which option fits best given the relationship and effort, and why.
3. A reply that thanks them, confirms we can help, explains plainly that it's outside the current scope, and offers the option(s) with cost or trade-off. Positive and direct, not apologetic.
4. A version for gray areas, proposing how we'll handle similar requests going forward.
5. How to prevent repeat scope creep: a simple change-request process I can propose.
Rules: base the scope judgment only on the contract wording I share; if it's ambiguous, say so. Do not quote prices I haven't provided - use [ADD COST].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Email & Workplace Communication prompts
What to fill in
- WHAT THEY ASKED FOR, in their words if possible
- RELEVANT SCOPE
- HOURS, TEAM, COST ESTIMATE
- account value, renewal timing, past favors given
- ADD COST
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a work apology email that owns the mistake without over-explainingDrafts a professional apology that takes responsibility, states the fix, and rebuilds trust without groveling or excuses.
- Summarize a security incident for executivesTurns technical incident details into a clear leadership briefing on impact, actions, decisions needed, and next update.
- Hold a vendor accountable for a missed project milestoneA firm, factual message to a vendor about a missed milestone that requests a recovery plan and protects your contractual position.
- Write a delay notice that protects my right to a time extensionA timely, factual written notice of delay that meets contract requirements and documents cause, impact, and requested relief.