Structure · Proposals & SOWs

Build a Scope-Creep Prevention Clause

Write a scope-creep prevention clause that turns 'just one more thing' requests into billable change orders.

foundermanagerAdvancedRecovers 5-15 hours/month of unbilled work
When to use
Use this when you've been burned by clients drip-feeding 'small asks' that quietly burn 10 hours a month. This produces the clause you can drop into any existing SOW or retainer to convert ad-hoc requests into scoped change orders. Best for retainer engagements over 3 months long.
The prompt
You are a seasoned agency account director who has watched dozens of profitable retainers turn unprofitable through unchecked scope creep, and has the legal language to prevent it.
Engagement type: [ENGAGEMENT_TYPE] | Service line: [SERVICE_LINE] | Monthly fee: [PRICE] | Hours included per month: [HOURS_PER_MONTH] | Hourly rate for overages: [HOURLY_RATE] | How clients typically try to expand scope: [SCOPE_CREEP_PATTERNS]
Write a scope-creep prevention clause for inclusion in the SOW. It must define: what counts as 'in scope' work, what counts as a change request, the change-order process (who submits, who approves, turnaround time), pricing for ad-hoc requests, an optional pre-purchased hour bank, and a monthly hours-reconciliation policy.

- Tone: collaborative, not defensive — frame it as protecting both sides' time
- Be concrete: name the request channels (email, Slack), the approver, the turnaround commitment
- Specify the hourly rate AND a discounted block-of-hours rate
- Include language that small (
Markdown clause with H3 subsections: 'In-Scope vs. Change Requests', 'Change-Order Process', 'Ad-Hoc Hourly Rate', 'Hour Bank (Optional)', 'Monthly Reconciliation'.
Variables
  • [ENGAGEMENT_TYPE] — Retainer, ongoing services, hybrid
  • [SERVICE_LINE] — Service category
  • [PRICE] — Monthly retainer fee
  • [HOURS_PER_MONTH] — Hours included in the monthly fee
  • [HOURLY_RATE] — Your ad-hoc hourly rate
  • [SCOPE_CREEP_PATTERNS] — How this client (or clients like them) typically expand scope — Slack DMs, last-minute campaign asks, etc.
Example input
Engagement: SEO retainer | Service line: SEO | Fee: $4,500/mo | Hours: 30/mo | Hourly rate: $185 | Scope creep patterns: last-minute landing page copy requests via Slack, ad-hoc 'can you look at this competitor' analyses, weekly 'quick question' calls that run 45 minutes
Example output
## Scope-Creep Prevention

### In-Scope vs. Change Requests
In-scope work is defined in the Deliverables section above (30 hours/month, SEO services). Anything not listed there — including ad-hoc landing page copy, competitor deep-dives, additional strategy calls beyond the monthly review, or net-new initiatives — is a change request.

Requests under 15 minutes (a quick question in Slack, a one-line answer) are absorbed at no charge. Anything larger triggers the change-order process below.

### Change-Order Process
1. Client submits the request to [ACCOUNT_LEAD] via email (Slack 'quick asks' do not count as submitted).
2. We scope the request within 2 business days: hours estimate, deliverable, timeline.
3. Client approves in writing before work begins.

### Ad-Hoc Hourly Rate
$185 per hour, billed in 15-minute increments on the next invoice.

### Hour Bank (Optional)
Pre-purchase a 10-hour block for $1,650 (10% discount). Hours expire 90 days after purchase.

### Monthly Reconciliation
If included hours are exceeded, overages appear on the next invoice with a line-item log. If included hours are unused, up to 5 hours roll into the following month (no further rollover).
Pro tips
  • The '15-minute absorption' rule is what stops clients feeling nickel-and-dimed — it earns trust to enforce the bigger stuff
  • Insisting requests come via email (not Slack) kills 70% of scope creep before it starts
  • Offer the hour bank as a discount — clients feel they got a deal and you get cash up front
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts