Scope discipline and change orders

Scope creep does not arrive as a demand. It arrives as a friendly question: "while you are in there, could you also..." Say yes without a system and you train the client that scope is a suggestion. Say no badly and you sour the relationship. Scope discipline is the middle path, and it is mostly prepared sentences.

The rule

Everything is in scope or out of scope, and the scope sheet decides, not the mood of the conversation. Because you sell productized packages (previous lessons), you always have the sheet to point to. That is the quiet superpower of productizing: the document does the confrontation for you.

The three responses you need

• In scope: "Yes, that is included. I will have it in the next review round."
• Small and out of scope: "That is outside the package, but it is small. I will add it as a request on your care plan once we launch." This is how care plans sell themselves.
• Big and out of scope: "Great idea, and bigger than this project. Let me price it as an add-on so we can do it properly." Then send a one-line change order with a price.

Protect the timeline too

Scope has a twin: schedule. Client-side delays (content not sent, feedback not given) move the launch date, and your agreement says so (Module 2). When a delay happens, do not absorb it silently. One friendly sentence: "No rush on my end, just flagging that the launch moves out a week for every week the photos are pending." Calm, factual, on the record.

Revisions without the spiral

Your packages include a set number of revision rounds, and a round is a batch: the client sends all feedback at once, you deliver it at once. Drip-fed feedback ("one more thing" seventeen times) is what turns a two-week build into a two-month one. Teach the batching at kickoff (Module 8) and revisions stay a process instead of a leak.