Scope Change Playbook

Knowing how to handle scope creep requests from clients is the difference between a profitable project and one you finish at a loss. The request usually arrives as a casual email or a Slack message that starts with 'quick question' — and by the time you've read it, you're already doing math in your head, trying to figure out whether you can absorb it or whether you're about to have an uncomfortable conversation. Most solo operators either say yes to avoid conflict and eat the margin, or they freeze and say nothing while the project keeps moving. Neither works.

This kit gives you four tools to handle it: the Scope Change Playbook (guide PDF) that walks you through the full response process from the moment the request lands; the Scope Change Decision Tree (checklist PDF) that classifies any request into one of three outcomes — Absorb It, Propose Add-On Fee, or Escalate to Formal Change Order — using three decision criteria evaluated in sequence; the Change Order and Scope Change Email Templates (script pack PDF) with copy-paste language for every scenario including retainer boundary violations, fixed-price add-ons, and last-minute feature requests before launch; and the Change Order Template (editable DOCX) that formalizes the scope change with all five required sections and gets you a signed approval.

Here's how you actually use it. A client emails asking to add a deliverable. You open the Decision Tree, run the request through Time Impact, Complexity, and Relationship Stage in sequence. The tree tells you which of the three outcomes applies. If it's a formal change order, you open the email template, drop in the six template variables — client name, change description, additional fee, timeline impact, original scope summary, approval deadline — send the initial response within 30 minutes, then follow it with the completed Change Order Template for signature. The whole process from request to documented approval runs on a defined track instead of an improvised conversation.

This kit was built because the 'quick question' problem kept showing up the same way: a reasonable-sounding request, no clear process for evaluating it, and a solo operator who either said yes too fast or handled it awkwardly and damaged the relationship. The 2-hour threshold in the Decision Tree — the dividing line between an absorbable small add-on and a scope change requiring a formal change order — came from working through enough of these situations to see where the margin actually disappears.