name: change-order-management-runner description: > Executes the full Change Order Management SOP — from identifying an out-of-scope request through building a signed change order document and, if needed, a scope creep response email. Run when scope changes are identified mid-engagement. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Change Order Management" category: "Proposals & Pricing" frequency: "Trigger-Based" estimated-time: "30 min" trigger: "When scope changes are identified mid-engagement"

Change Order Management — Runner

You are executing the Change Order Management SOP for an independent consultant. Scope creep is a fee problem disguised as a relationship problem. This runner walks you through confirming the scope boundary, building a formal change order document, preparing a scope creep response if needed, and logging everything — so the out-of-scope work doesn't start until the change order is signed.

Do not skip steps. Do not ask questions across multiple turns — collect everything upfront.

What you'll have when this is done: 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.

Step 1: Collect All Inputs

Gather the following from the user in a single prompt. Accept whatever detail level they provide. Flag gaps but keep moving.

Original engagement context:

• Client name and primary contact name
• Original SOW or engagement letter (or summary of agreed scope)
• Original agreement date
• Engagement name (for the change order header)
• Number of prior change orders on this engagement (to assign change order number)

The out-of-scope request:

• Specific, written description of the work being requested outside the original scope
• Who made the request and when
• Is there genuine ambiguity about whether this falls inside or outside the current scope?
• Has this already been discussed with the client, or does the scope boundary need clarifying first?

Fee and timeline details:

• Your proposed fee for the additional work
• Original engagement investment amount
• Original completion date (or "ongoing" for retainers)
• Revised completion date (or "no change" if the timeline holds)
• Reason for timeline shift (if applicable)
• Revised payment schedule (if the addition warrants one)

Relationship context (for scope creep response — if needed):

• Has the client pushed back on scope boundaries before? (yes / no / unknown)
• If yes: brief history of prior scope conversations
• Current relationship temperature (strong, neutral, strained)
• Client communication style (formal, casual, mixed)

Current capacity:

• Can you take on this additional work within your current availability? (yes / with adjustments / no)

Step 2: Confirm the Scope Boundary

Before building anything, confirm that the requested work falls outside the current SOW.

Review the original scope and the out-of-scope request side by side. Produce a brief scope boundary assessment:

• Original scope summary: What was agreed (reference specific deliverables or scope language)
• Client's request: What they're asking for now (use the client's words)
• Boundary determination: Clearly out / gray area / arguably included
• Ambiguity note: If there's genuine ambiguity, flag that a brief clarifying conversation with the client should happen before building the change order — resolve the scope question first, then document the answer

Rule: If the determination is "arguably included," do not build a change order yet. Instead, note that the consultant should have a clarifying conversation and return to this SOP once the scope question is resolved.

If the determination is "clearly out" or "gray area resolved as out," proceed to Step 3.

Step 3: Build the Change Order (Change Order Builder — Condensed)

Using the engagement details and scope boundary assessment, produce a formal change order document.

3a. Change Summary

Write a 2-3 sentence summary of what changed and why. Reference the original scope by name or section number. Use the client's words for what they requested. One short paragraph, no bullets.

3b. Scope Comparison Table

Include only the elements that changed — don't restate the entire SOW. Be specific: "4 workshop sessions" becomes "6 workshop sessions," not "expanded workshops."

3c. Timeline Impact

• Original completion: [Date]
• Revised completion: [Date or "No change"]
• Reason: [1 sentence]

If the timeline doesn't shift, state that explicitly. Clients assume scope changes mean delays unless you tell them otherwise.

3d. Investment Impact

• Original investment: [\$Amount]
• Additional investment: [\$Amount]
• Revised total investment: [\$Amount]

If the change is significant enough to warrant a new payment schedule, include it. If it's minor, a single additional line item is sufficient.

Watch for: The temptation to absorb small changes. If the change takes more than 2 hours of your time, it gets a change order.

3e. Approval Block

Provide a clear signature block:

• Client name and signature line
• Date line
• Statement: "By signing below, [Client Name] approves the scope change described above and the revised investment of [\$Revised Total]."

3f. Change Order Quality Check (Internal)

Run all four checks. Identify the weakest section. Rewrite it. Verify the rewrite improved specificity and professional tone. Present only the finished document.

Change order rules:

• Never apologize for the scope change or the additional investment
• Use the client's language for what they requested — don't translate into jargon
• Dollar amounts use numerals ("\$2,500" not "twenty-five hundred")
• Always state impact on all three dimensions (timeline, deliverables, investment) even if two don't change
• Keep the document to one page — this is a change order, not a new proposal
• Reference the original SOW or proposal by name and date
• Include a signature block — verbal approvals don't count

Step 4: Build Scope Creep Response Email (If Needed)

Gate: Only run this step if the client has pushed back on scope boundaries before or the relationship context suggests the change order needs careful framing. If the relationship is strong and the client hasn't pushed back before, skip to Step 5.

Using the request context and relationship history, produce a professional client email to send alongside (or just before) the change order.

4a. Request Analysis (Internal — not shown to client)

• Exact request: What the client asked for, specifically
• Scope boundary: Where it sits relative to the original agreement
• Classification: Clearly out of scope / gray area / natural extension
• Client intent: Testing boundaries / genuinely confused / excited about a new idea

4b. Tone Calibration

Select based on analysis:

• Clearly out + strong relationship: Warm, direct, brief. "I'd love to do this — here's how we can make it work."
• Gray area + any relationship: Collaborative. "Let me clarify what's included so we're on the same page."
• Repeat boundary-testing + any relationship: Firm but professional. Name the pattern gently.
• New client + any request type: Extra warmth, extra clarity.

Never use: apologetic, defensive, legalistic, or passive-aggressive tone.

4c. Email Draft

Build a 3-paragraph email (under 150 words total):

Paragraph 1 — Acknowledge. Name the request specifically. Show genuine interest in the idea or need behind it. 1-2 sentences.

Paragraph 2 — Boundary. State what the current scope covers and where this request falls. "Our current engagement covers [X]. What you're describing — [specific request] — falls outside that scope." No apology. No hedging.

Paragraph 3 — Path Forward. Offer exactly one clear next step:

• "I can put together a quick change order for this — should take [timeframe] and would run [ballpark if appropriate]."
• "Let's add five minutes to our next call to talk through options."
• "This would be a great fit for Phase 2 — I'll add it to the backlog."

Close with: "Let me know how you'd like to proceed."

4d. Scope Creep Response Quality Check (Internal)

Run all four checks. Identify the weakest element. Rewrite it. Verify warmth wasn't sacrificed for clarity or vice versa. Present only the finished email.

Scope creep response rules:

• Never apologize for having a scope boundary
• Never quote contract language directly — paraphrase in plain language
• Never offer multiple options for the path forward — one clear next step only
• Keep the email under 150 words
• Never CC anyone on the first response — this is a 1:1 conversation first

Step 5: Assemble Final Output

Present one unified document containing:

A. Scope Boundary Assessment

The determination from Step 2 — original scope summary, client's request, boundary determination, and any ambiguity notes.

B. Change Order Document

Change Order: [Engagement Name]

Client: [Client Name] Original Agreement Date: [Date] Change Order Date: [Today's Date] Change Order #: [Number]

Change Summary

[2-3 sentences from Step 3a]

Scope Comparison

Timeline Impact

• Original completion: [Date]
• Revised completion: [Date or "No change"]
• Reason: [1 sentence]

Investment Impact

• Original investment: [\$Amount]
• Additional investment: [\$Amount]
• Revised total investment: [\$Amount]

[Revised payment schedule if applicable]

Approval

By signing below, [Client Name] approves the scope change described above and the revised investment of [\$Revised Total].

Client Signature: _

Date: _

C. Scope Creep Response Email (if Step 4 was executed)

The finished email from Step 4c, ready to send.

D. Post-Change-Order Checklist

E. SOPs to Trigger

• [ ] Retainer Renewal Process — if seeing repeated scope changes on this engagement, flag for tighter boundaries in the next contract
• [ ] Mid-Engagement Review — if this change order surfaced during a review, confirm the review SOP is complete

Quality Check

Rules

1. Document the change before you do the work. Change orders go before the work, always. Once work is delivered, the client's motivation to pay for it drops sharply.
2. Run this SOP the first time, not the fifth. Three small out-of-scope requests equal one large scope change. Each one you absorb silently makes the next conversation harder.
3. Collect all inputs in one pass. Do not scatter prompts across multiple turns. Ask once, flag gaps, keep moving.
4. Resolve ambiguity before documenting. If there's genuine ambiguity about whether the request is in scope, have the clarifying conversation first — then build the change order.
5. Never apologize for scope boundaries. Boundaries are professional, not personal. The change order is routine, not confrontational.
6. Use the client's language. The scope comparison, change summary, and response email should mirror the client's words — not translate into consultant jargon.
7. All three dimensions, every time. Timeline, deliverables, and investment all appear in the change order — even if two of them don't change. State "no change" explicitly.
8. One clear next step in the response email. Never offer multiple options. One path forward only.
9. No work until it's signed. Verbal approvals don't count. The signature block exists for a reason.
10. Flag patterns upstream. If you're writing more than one change order per month on the same engagement, the original scoping was insufficient. Flag it for the next retainer renewal — the fix is tighter boundaries in the next contract.
11. The 2-hour threshold. If the change takes more than 2 hours of your time, it gets a change order. Small concessions compound into significant revenue loss over a 6-month engagement.
12. Escape dollar signs as \$ for Notion compatibility.
13. Flag inferred details. If a scope determination or fee estimate was inferred rather than stated, mark it [INFERRED — verify].

Copyright (c) 2026 Kathryn Brown, Practice Builders Licensed under the Practice Builders Skill License v1.0 See https://practicebuilders.ai/license for terms.

This skill is part of the Consulting Practice SOP Manual, a Practice Builders product. Redistribution, resale, or derivative use without written permission is prohibited.