Scope creep: how to stop it with one clause and a change order

Scope creep rarely arrives as one large request. It arrives as small ones ("can you just", "while you're in there", "one more page"), each too small to argue about, and together enough to turn a profitable project into a loss. Two documents stop it: a scope of work that says where the project ends, and a change order for everything past that line.

What is scope creep?

Scope creep is the continuous or uncontrolled growth of a project's scope after the project has started. On client work it usually means extra work delivered for the same fee and against the same deadline, which costs the person doing the work in time, money or both. On a website project it usually looks like one of these:

• A five-page site becomes eight because "the services page needs splitting up".
• A third and fourth round of design changes, when two were included.
• Copy the client was going to write ends up written by you.
• "Can you also set up the newsletter?", a week before launch.
• A new person joins at the review stage and reopens decisions that were already approved.

Each request is reasonable on its own, and the client is rarely trying to take advantage. They ask because nothing in the agreement shows them where the line is. Growth in scope can also make the result better; the damage comes from the part nobody priced or scheduled.

Why does scope creep happen?

Scope creep happens when the scope was never defined or documented precisely enough to tell a new request apart from the agreed work, and when there is no agreed way to handle that request. The common causes on client projects:

• The scope is vague. "Website design" does not say how many pages, how many rounds of changes or who writes the copy, so almost any request can be argued to be included.
• There is no change process. Without one, the options are to do the work for free or to start an awkward conversation, and most people pick the first.
• The first free favour sets the price of the next. Once one addition was free, the client reasonably expects the next one to be.
• Nobody owns the decisions. Feedback from several people contradicts itself, and each round of it becomes new work.

How do you prevent scope creep in the scope of work?

You prevent most scope creep with three parts of the scope of work: countable deliverables with an out-of-scope list, a defined number of revision rounds, and a clause that says how changes are handled.

1. 1Deliverables you can count ("up to 8 page templates") and a list of what is excluded ("copywriting is not included") answer requests before they are made. The full list of sections is in how to write a scope of work.
2. 2Revisions counted and defined: two rounds per deliverable, a round being one consolidated list of changes.
3. 3A change clause: one paragraph, agreed before anyone needs it, that says how extra work is priced and approved.

Any work not described in this Statement of Work is outside its scope. We will describe requested work, its cost and its effect on the timeline in a written change order. Work on a change starts only after the client approves the change order in writing. Approved change orders form part of this agreement.

When a request comes in later, you are following a process the client already signed, which is an easier conversation than proposing a new charge.

What is a change order and what goes in it?

A change order is a short document that adds work to, removes work from, or replaces work in an agreed scope, and records whether the price and the completion date change. It is usually one page, and it needs:

• A reference to the original agreement: its number and date.
• What is changing, described as specifically as a deliverable.
• Who asked for it and when.
• The cost, as a fixed amount or as hours at your rate, and when it is invoiced.
• The new date for every milestone that moves.
• A line saying everything else in the original agreement stays as it was.
• Approval from both sides, with a date.

What are your options when a client asks for more?

When a request falls outside the scope, you can price it as a change order, swap it for something already in scope, or move it to a later phase. Each option treats the price and the deadline differently:

How do you raise a change order without an argument?

Raise it the day the request arrives, in writing, by pointing to the agreed scope and offering options. The steps:

1. 1Confirm what is being asked for, so you are both describing the same thing.
2. 2Say that it is outside the current scope, and point to the section that shows it.
3. 3Offer the options from the table above.
4. 4Send the change order the same day, while the client still wants the change.

Happy to add the newsletter sign-up. It isn't part of the current scope (section 3 lists the integrations we agreed), so I've attached a change order: it adds 6 hours, $540, and moves launch by two days. If you'd rather keep the launch date, we can do it in the week after launch instead. Which do you prefer?

Should small changes get a change order too?

Yes. Even when you decide to do a change for free, send a change order with the amount set to zero. The client sees that the work was extra and that you chose not to charge for it, and the next request starts from that record.

Most people skip it because writing a document from scratch for a two-hour change feels like more work than the change itself. A change order you can produce in a couple of minutes gets sent.

What do you do when scope creep has already happened?

List everything delivered beyond the scope, put it in one change order with a price, and agree it with the client before any more extra work starts.

Build the list from the scope of work, section by section: what was agreed, what was delivered, and the difference. Price the difference at your rate, then decide what to ask for. Charging all of it, part of it or none of it can each be the right call for the relationship, as long as the change order shows the full amount, so the client sees what the extra work was worth.

From then on, every new request goes through the change process. If the scope of work has no change clause, add the one above to the change order, so the client approves the process along with the price.

This is practical guidance from client work, not legal advice. Have a lawyer review the change and acceptance terms you rely on.