How to Fix Weak Change Control Language in Your SOW

In Part 1, we looked at why verbal approvals are a bigger problem than most delivery teams realize — and how a casual Slack message can create a legally binding obligation with no price attached.

So now you know the problem. Here's what to do about it.

Why the Problem Keeps Happening

This isn't a discipline problem. It's a cultural one.

Most professional services organizations coach their people to never give a flat no. The guidance sounds reasonable: don't say no, say not yet — find a way to say yes with conditions. It's good client relationship advice. But when it becomes the default response to every scope request, it quietly removes the friction that protects your team.

The PM who says "let me check if that's in scope" and then never circles back isn't being careless. They're navigating a culture that treats "no" as a relationship risk — and a process that makes issuing a formal Change Order (CO) feel like more trouble than it's worth.

And it's not just PMs. Sales is a significant and underappreciated source of undocumented scope commitments — often with the best of intentions. A rep closes a deal by verbally agreeing to include something that wasn't in the Statement of Work (SOW). The client heard a promise. The delivery team inherited a scope gap nobody told them about. The SOW says one thing; the relationship expectation says another. That gap is where margin goes to die.

What Good Change Control Language Actually Looks Like

A well-drafted SOW change control clause does three specific things. Most SOWs only do one.

1. Define the approval mechanism explicitly

Not "written approval" — but "a Change Order (CO) executed by both parties via [DocuSign / email from authorized signatory / formal CO form]." Name the method. Remove ambiguity. If your SOW says "in writing" without specifying what that means, you've already lost the argument before it starts.

2. Specify who has authority to approve

Your client's project manager does not have authority to authorize scope changes on behalf of their organization unless your SOW explicitly says so. Define the authorized signatories on both sides. Otherwise anyone with a Slack account — or a quota to hit — can approve scope on behalf of their company. You won't know it's a problem until you try to invoice for it.

3. State what happens to work performed without approval

This is the clause most SOWs skip entirely. Add language like:

"Work performed outside the agreed scope without a fully executed Change Order shall be at Vendor's discretion and may be billed as additional services."

It's not aggressive. It's honest. And it gives you a contractual foundation for the conversation instead of relying on goodwill.

The Real Cost of Getting This Wrong

Let's put a number on it.

If your average engagement is $500K and you absorb 8–12% in undocumented scope — a conservative estimate across most IT consulting engagements — that's $40,000 to $60,000 in margin erosion you never invoiced per project.

In just 5 projects a year, that's a quarter of a million dollars walking out the door. Not because your team failed to deliver. Because nobody documented the ask.

Three Things You Can Do Right Now

You can't retrofit a good change control process onto a signed SOW. But you can start here:

1. Audit every active SOW for the change control clause

Does it define the approval method? Does it name authorized signatories on both sides? Does it address what happens to work performed without a CO? If not, you know where you're exposed.

2. Align your sales and delivery teams on what verbal commitments mean

Not as a policy document nobody reads — as a standing team norm. Sales can't commit scope the SOW doesn't cover. PMs can't approve scope changes verbally. Everyone needs to understand this before the project starts, not after the invoice dispute.

3. Make the Change Order conversation easy

The harder it is to issue a CO, the more likely your team skips it. Have a template. Have a process. When the Slack message comes in, your PM should be able to respond professionally in minutes — not spend an hour drafting something from scratch or, worse, just say yes to keep the peace.

The Bottom Line

Verbal approvals feel like progress. The relationship stays warm, the client is happy, and the team moves forward. But undocumented scope is debt — and like all debt, it compounds.

The conversation you avoid at week one costs ten times more at week eight. The Change Order your PM didn't issue is ten times harder to recover when the invoice is disputed.

Good change control isn't about being difficult. It's not about slowing down delivery or souring a client relationship. It's about making sure the work your team does gets paid for — and making sure everyone, on both sides, knows exactly what was agreed.

That's not a legal problem. That's a delivery leadership problem. And it starts with the SOW.