You Cannot Control a Scope You Never Wrote Down.

Written and narrated by Serguei Poppeleer.

Scope creep is rarely dramatic. It is a sequence of reasonable requests, each one small, each one hard to refuse, none of them written down — until the project you are delivering is no longer the project you priced.

Scope does not creep because people are careless. It creeps because nobody wrote down where the line was.

The most common failure at the very start of a project is the absence of a written scope at kickoff. Everyone is keen, the relationship is warm, the work begins on a shared sense of what is included. Then the requirements shift mid-stream, finance asks why the cost moved, and the credibility lost in that conversation is hard to win back.

CONTAIN is the discipline of fixing the line in writing before work starts — so the line does not have to be defended from memory later.

The belief to drop

The belief is that a tight scope at kickoff signals distrust — that naming exclusions is unfriendly, and a warm start matters more than a precise one. So scope stays vague, and the firm pays for the vagueness in every later argument.

A clear boundary is not hostile. It is the kindest thing you can do for the relationship, because it removes the conversation that actually sours it: the surprise invoice, the mid-project dispute about what was meant.

Vague scope is not generous. It is a future argument you have agreed to have.


What CONTAIN looks like

A contained scope has four written parts, settled before work starts: what is explicitly in, what is explicitly out, the assumptions the price and programme depend on, and the mechanism by which scope can change. With those in place, scope cannot move quietly — and when it does move, it moves on the record.

In
Itemised inclusions

A specific list of what is being delivered, precise enough that anyone can answer “is this included?” without a meeting.

Out
Explicit exclusions

The adjacent work, the favours, the “while you are here” requests — named out loud, so holding the line is policy, not awkwardness.

Assume
A written assumptions ledger

Every assumption the price rests on. When one proves false, it is a documented change — not a debate about intent.

Change
A defined change mechanism

How a change is raised, priced and approved. Without a mechanism, scope moves silently; with one, every move is visible and costed.


How to install it

1
Refuse to start without the four parts

In, out, assumptions, change — on the page before mobilisation. The discipline is in making this non-negotiable, not in its complexity.

2
Build a standing exclusions list

The creep items you keep meeting go on a default exclusions list every project starts from, so hard-won lessons are not relearned each time.

3
Make raising a change easy

If using the change mechanism is harder than absorbing the work, people absorb it. Make it a one-page routine so the right behaviour is the easy one.


The objections

“A long exclusions list will put the client off.”

Clients are put off by surprise costs and mid-project arguments, not by clarity. A firm that knows exactly what it is and is not doing reads as competent. The boundary protects the relationship; the vagueness is what damages it.

“We can sort the details once we are moving.”

Details sorted under delivery pressure are sorted badly and expensively. The cheapest moment to contain scope is before anyone has mobilised against an assumption. After that, every clarification is a negotiation.

AI Reality Check

AI can build a scope standard from your own history — reading past contracts, change orders and disputes to surface the inclusions, exclusions and assumptions you tend to rely on, far faster than from a blank page. It can also flag, in flight, when a request looks like it falls outside the written scope.

But it is flagging against the boundary you defined. It does not know where your line should be, or which exclusions matter on this client. The judgement about the line is yours; AI accelerates writing it down and watching it.

AI can draft the scope. You still decide where the line is.


What it protects

A camp build in Equatorial Guinea — the line held by the document

In a setting where every condition pushed toward creep and claims, the protection was a scope contained in writing before work began — inclusions, exclusions and assumptions explicit, so the line did not depend on anyone being present to defend it.

The result was a build delivered in 28 months against a 36-month standard, at a fraction of typical cost, with no claims. The contained scope is what turned a hostile environment into a predictable one.

You cannot control a scope you never wrote down.

Contain it first — in, out, assumptions, change — and every later conversation about the work happens on the record, where it can be managed, instead of from memory, where it cannot.

Where does your delivery system actually stand?

The Delivery Score measures your governance architecture across the five dimensions of The 5Cs Framework™. Fifteen Yes/No questions. About four minutes. Instant result.

Get my Delivery Score — free → Back to the library →