# scope-control

Scope Control

Overview
Scope control is the skill of keeping client work aligned with the promise you actually sold. For one-person companies, weak scope control quietly destroys profit and energy because every extra request feels small in isolation but expensive in aggregate. Strong scope control protects margin, speed, and trust by making boundaries visible early and enforcing them consistently.
When to Use This Skill
Use this when projects keep expanding, when retainers turn into on-call support, when clients expect extras by default, or when you often feel resentful after saying yes too many times.
What This Skill Does
This skill helps you define scope, identify change requests, respond without drama, and preserve the relationship while protecting delivery capacity. The aim is not to be rigid. The aim is to prevent hidden work from becoming your default business model.
How to Use
Step 1: Define scope in buyer language before the work starts. Deliverables, rounds of revision, timeline, communication access, and excluded items must be explicit.
Step 2: Create a simple rule for scope changes. For example: minor clarification, same-scope revision, or new work requiring a change order.
Step 3: Train yourself to pause before saying yes. Ask whether the request changes effort, complexity, or timeline.
Step 4: Respond with options, not friction. Example: "We can include that by swapping X, extending timeline, or adding a scoped add-on."
Step 5: Track repeated scope pressure. If the same requests appear constantly, your offer or proposal language is too vague.
Output
The output should include:
Scope definition checklist
Change request policy
Three scope-control response templates
Escalation rules for repeated overreach
Common Mistakes
Do not rely on memory or verbal agreements.
Do not treat every extra request as goodwill. Hidden work compounds.
Do not wait until you are frustrated to reset boundaries.
Do not confuse flexibility with lack of process.