<aside> 📋 Frequency: Trigger-Based | Time: 30 min | Trigger: When scope changes are identified mid-engagement

</aside>

Scope creep is a fee problem disguised as a relationship problem. When you absorb work outside the original SOW without documenting it, you train clients that scope is negotiable and that you're the one who bends. This SOP creates a fast, professional path from scope change identification to a signed change order — before the work starts, not after it's delivered.

Prerequisites

• The original SOW or engagement letter with the agreed scope clearly defined
• A specific, written description of the work being requested outside that scope
• Your current capacity and rate for additional work — confirm availability before committing
• This SOP is commonly triggered during a Mid-Engagement Review — run it immediately when scope drift is identified rather than letting changes accumulate

Procedure

1. Confirm that the requested work falls outside the current SOW. If there's genuine ambiguity, have a brief clarifying conversation with the client before building the change order — resolve the scope question first, then document the answer.
2. Run the Change Order Builder skill with the original SOW summary, the out-of-scope request, your proposed fee for the additional work, and the revised timeline as input. Review the output for a change order document ready for client review.
3. Review the change order for specificity. The scope description should be precise enough that there's no ambiguity about what's included, what the fee covers, and when the work will be delivered. Vague change orders produce vague boundaries — and the same conversation again in six weeks.
4. If the client has pushed back on scope boundaries before, run the Scope Creep Response skill with the request context and relationship history as input. Use the output to prepare your framing before sending the change order — the tone is professional and routine, not defensive.
5. Send the change order. Do not begin the out-of-scope work until it is signed. Log it in the engagement file and update your billing tracker. If you are seeing repeated scope changes on this engagement, flag it for the next Retainer Renewal Process — the next contract needs tighter boundaries.

Expected Outcome

You'll have a signed change order documenting the additional scope, fee, and timeline before any out-of-scope work begins. The engagement record and billing tracker are updated, and the client's expectations are reset in writing.

<aside> ⚠️ Common mistakes:

— Absorbing the work first and addressing the fee later. Once the work is delivered, the client's motivation to pay for it drops sharply. Change orders go before the work, always.

— Letting small changes accumulate before raising the issue. Three small out-of-scope requests equal one large scope change. Each one you absorb silently makes the next conversation harder. Run this SOP the first time, not the fifth.

</aside>