🚀 Get PingPaid — Automate your invoice collection Try Free →
PingPaid

Scope Creep Defence Kit

SOW template, change request form, and 5 defence scripts. Stop scope creep before it starts.

📄 Statement of Work (SOW) Template

Use this as the foundation of every project. Define the scope before work begins.

STATEMENT OF WORK

Project: [Project Name]
Client: [Client Name]
Date: [Date]
Effective: [Start Date] – [End Date]

1. PROJECT OVERVIEW
Brief description of what this project covers.

2. SCOPE OF WORK
This agreement includes the following deliverables:
  • [Deliverable 1]
  • [Deliverable 2]
  • [Deliverable 3]

3. EXCLUSIONS (NOT INCLUDED)
The following are explicitly NOT included in this scope:
  • [Exclusion 1]
  • [Exclusion 2]
  • [Exclusion 3]

4. TIMELINE
  • Milestone 1: [Date] — [Deliverable]
  • Milestone 2: [Date] — [Deliverable]
  • Final Delivery: [Date]

5. REVISIONS
This agreement includes [2] rounds of revisions. Additional revisions will be billed at [Rate] per round.

6. RATES & FEES
  • Total Project Fee: [Amount]
  • Hourly Rate (for out-of-scope work): [Rate]
  • Rush Fee: [Rate or %]

7. PAYMENT TERMS
  • Deposit: [%] due upon signing
  • Milestone payments: [Details]
  • Final payment: Due upon final delivery
  • Late fee: [1.5%] per month after due date

8. CHANGE REQUESTS
Any work outside the scope of this SOW requires a written change request. Both parties must sign a change order before additional work begins.

9. TERMINATION
Either party may terminate with [14] days' written notice. Client shall pay for all work completed to date.

10. SIGNATURES

_________________________          _________________________
[Contractor Name]                  [Client Name]
Date: _______________              Date: _______________

Click to copy

📝 Change Request Form

When a client asks for something outside scope, send them this form. It forces them to think about the real cost.

CHANGE REQUEST FORM

Project: [Project Name]
Date: [Date]
Requested by: [Client Name]

1. CHANGE DESCRIPTION
Describe the change request in detail:
[________________________________________________________________]

2. REASON FOR CHANGE
Why is this change needed?
[________________________________________________________________]

3. IMPACT ASSESSMENT
  • Additional time required: [____] hours
  • Additional cost: [________]
  • Timeline impact: [____] days delay
  • Other deliverables affected: [________________]

4. NEW TOTAL PROJECT COST
Original: [________]  +  Additional: [________]  =  New Total: [________]

5. APPROVAL

I approve this change request and the additional cost of [________].

_________________________          _________________________
[Client Name]                      [Contractor Name]
Date: _______________              Date: _______________

Click to copy

🛡️ 5 Scope Creep Defence Scripts

1. The "Not in Scope" Script

Best for: When a client asks for something clearly outside the agreement.

Hi [Client Name],

Thanks for the suggestion! That sounds like a great addition, but it's outside the scope we agreed on in the SOW.

I can absolutely add it. Here's what it would take:
  • Additional time: [X] hours
  • Additional cost: [Amount]
  • Timeline impact: [X] days

I'll send over a change request form for your approval. Once signed, I can get started right away.

[Your Name]

Click to copy

2. The "Happy to Help, But..." Script

Best for: When you want to stay helpful but protect your boundaries.

Hi [Client Name],

I'm happy to help with this! Since it's outside our original scope, I'll need to add it as a change request.

Quick estimate:
  • Time: [X] hours
  • Cost: [Amount]

If you want to proceed, just reply and I'll send the formal change order. If not, no worries — we can save it for a future phase.

[Your Name]

Click to copy

3. The "This Deserves Its Own Project" Script

Best for: When the request is so large it should be a separate engagement.

Hi [Client Name],

This is a great idea, but it's substantial enough that it deserves its own project scope and timeline rather than being added to the current one.

I'd love to put together a separate proposal for this. It would include:
  • Full scope definition
  • Separate timeline
  • Dedicated budget

Would you like me to draft that up? We can keep the current project on track and tackle this as Phase 2.

[Your Name]

Click to copy

4. The "Refer to the SOW" Script

Best for: When a client repeatedly asks for out-of-scope work and you need to be direct.

Hi [Client Name],

I want to make sure we're both aligned on what's included in this project.

Per our signed SOW (Section 2), the agreed deliverables are:
  • [Deliverable 1]
  • [Deliverable 2]
  • [Deliverable 3]

The recent request for [new thing] falls outside this scope. I'm absolutely open to adding it, but per our agreement (Section 8), it requires a written change request.

I've attached the change request form for your review. Let me know if you'd like to proceed!

[Your Name]

Click to copy

5. The "Trade-Off" Script

Best for: When a client wants something added but can't increase budget.

Hi [Client Name],

I understand the budget is fixed, and I'm happy to accommodate [new request] within the existing budget.

Here's what that would mean:
  • We add [new request]
  • We reduce [existing deliverable] to [smaller version]
  • Timeline stays the same

Alternatively, if [existing deliverable] is critical, we could phase the project:
  • Phase 1 (current scope): [Date]
  • Phase 2 ([new request]): [Date + 2 weeks]

Which approach works better for you?

[Your Name]

Click to copy

📧 Want the complete Scope Creep Defence Kit as a PDF? Enter your email and get it instantly.