Scope Creep Handler

Scope creep isn't malicious. It happens because the SOW was vague, the deliverables were fuzzy, or the freelancer said "sure, I can do that quickly" three times in a row and now it's an expectation. Every uncounted addition erodes margin until the profitable project costs you money. The fix isn't to become rigid — it's to have a system that treats scope changes as normal business practice (because they are) and removes the awkwardness.

The skill sorts requests into four categories before drafting a response. Genuine quick win — under 30 minutes, no precedent risk, builds goodwill — just do it, mention it was a favour, move on. Grey area — a few hours, arguably related but not explicitly in scope — acknowledge, clarify, offer options. Clear addition — unambiguously outside scope — change order, no apology, this is how business works. Moving goalpost — the project has drifted so far that the original agreement no longer reflects reality — reset conversation, re-scope, potentially re-price the whole engagement. Sending a formal change order for a 15-minute favour wastes goodwill. Sending a "sure, no problem" for 8 hours of new work bleeds margin. The severity calculator stops both errors.

A few principles the skill is opinionated about. Never apologise for having boundaries — "sorry, but that's out of scope" undermines you, while "that's outside our current scope, here's how we can handle it" is professional. Never blame the client even when they're pushing — frame it as logistics, not character. Always offer a path forward, because "no" without an alternative feels like a wall. And never reduce price without reducing scope — discounting teaches clients your prices are inflatable.

You get the response written, matched to the category, with the original scope referenced specifically. A change order template with cost, timeline impact, and approval block. Five templates covering gentle redirect, professional boundary, strategic no, full reset conversation, and the post-fact embedded feedback for when you already did the extra work and need to prevent it next time. Plus the prevention layer — specific SOW patterns, explicit exclusion lists, revision limits, and a change control clause — so this becomes a one-off instead of a monthly recurrence.