Every scope statement is a positive list. Its authors read it as complete. Everyone else reads it as a sample.
A retailer replaces its merchandising and point-of-sale platform. Eighteen months, board-approved, a scope document circulated to every function and signed off without dissent. It goes live on time and close to budget.
Within a quarter, three parts of the business report that the programme failed. Store operations expected mobile stocktake. The buying team expected the supplier portal to be integrated. Finance expected the old promotional pricing engine to be switched off. None of those three things was in the scope document. None of them was excluded from it either.
Nobody lied and nobody changed their mind. The document said what the programme would produce and said nothing about these three, and three groups of experienced people read that silence in the only way silence can be read when a large investment is being made on your behalf: as not yet detailed.
The Strategic Context
The purpose of a scope statement, in the standard form of the document, is a shared understanding. The wording in one widely taught version is exact: it should provide "a sufficiently detailed description of what will be produced by the project so that all stakeholders have a shared understanding of what the project will produce."
Shared understanding is a two-party condition. It is not achieved by one party writing an accurate description; it is achieved when the second party's expectation matches it. A positive list cannot get there alone, because a positive list is half of a boundary.
The discipline has known this for a long time. The same material carries exclusions as a named component of the initiating document, alongside objectives, scope, assumptions, constraints and risks, and states its purpose plainly: exclusions "clearly defines those things which are to be excluded from the project", because "formally stating those things which are not project deliverables clarifies stakeholders understanding of the scope of the project."
The instrument exists and its rationale is on the record. The executive question is not whether your documents have an exclusions field. It is whether that field addresses what people in your organisation actually believe they are getting.
What Leaders Commonly Misread
The first misreading is that a scope statement is a description. It is a boundary claim, and a boundary has two sides. Describing the inside with great care does not locate the outside.
The second misreading is that silence is neutral. The author knows which candidate items were considered and declined; the reader cannot distinguish considered and declined from not thought about yet, because the document looks identical in both cases. Faced with that ambiguity, a reader with a live expectation resolves it in the direction of their own interest, in good faith. An unstated negative is not read as a negative. It is read as a positive that has not been elaborated.
The third misreading is that an exclusion is a constraint, or an assumption. Three different objects, which the same material separates precisely. An assumption is a factor "considered true, real, or certain" for planning purposes, which "generally involve a degree of risk" — a belief that may prove false, and testing beliefs belongs to [Related article: What Must Be True: The Assumptions Register as a Strategy Instrument]. A constraint is a limit on how the work may be done, expected to have "a 100% chance of occurring" and beyond the delivery leader's capacity to remove; reading a constraint set is a separate skill with its own method in [Related article: Read the Constraints, Not the Deliverables]. An exclusion is neither a belief nor a limit. It is a decision, already taken, that something will not be produced. Filing it under either of the others loses it: a register of beliefs invites testing and a register of limits invites negotiation, and an exclusion needs neither.
The fourth misreading is that the omission is somebody's fault. Treating it as a documentation failure guarantees the wrong remedy. Nothing can enumerate the complement of a scope statement; the list of things a programme will not produce is unbounded. The skill is not completeness but knowing which absences are load-bearing — which few unstated items somebody is currently planning around.
Reframing the Issue
The reframing is to treat the scope statement as two lists written together: what will be produced, and what will not.
The second list is not the complement of the first. It is short, it is targeted, and — this is the part that changes how it is produced — it is harvested rather than invented. A delivery team cannot generate it by imagination, because the team does not hold the expectations. The people who do are in operations, in finance, in the functions that will inherit the result, each quietly planning against a belief nobody has written down.
That makes the exclusion list the output of a question rather than a drafting exercise. The question is: what do you currently believe this programme is going to give you? An hour per function, producing three kinds of answer — in scope and poorly communicated, genuinely out and never said, and not yet decided.
Note what this is not. It is not a claim about who may change the programme's purpose, a decision-rights question with its own logic in [Related article: Drivers, Supporters and Observers: Who Is Allowed to Change What Your Programme Is For]. An exclusion list confers authority on nobody. It records a decision already taken and makes it legible to people who would otherwise infer it.
Strategic Analysis
State what remains, not only what goes
A closure brief in a teaching case makes the negative concrete. The project is to clear a site of all buildings and structures — and the brief then names what stays: one heritage-listed administration building, and a number of specifically identified trees.
The second sentence does more work than the first. "Clear the site" is a positive instruction with an unbounded reading; "everything goes except these" converts an infinite negative into a finite residue a reader can check against their own expectation in seconds. Anyone who believed a particular structure was being retained knows at once that it is not.
The generalisable move is to express the exclusion as a residue wherever the work is subtractive. Decommissioning, consolidation, rationalisation and divestment all have this shape, and all are naturally scoped in the positive — we will close eleven sites — when the sentence people need is these three are staying and nothing else is.
The expectation that is never contradicted is never renegotiated
A port terminal operator upgrades its container handling systems. The scope is quay-side: cranes, yard planning, the terminal operating system. Landside access — the gate booking system used by the haulage companies — is not in scope, and is not stated as excluded.
The hauliers do not read the scope document. Their expectation forms second-hand, from a briefing that says the terminal is being modernised, and they plan a two-year fleet investment around a gate system about to become the slowest part of the operation. Nobody negotiates with them, because nobody knows there is anything to negotiate.
That is the mechanism, and it matters because of what it is not. This is not a change arriving late and being priced at a premium through a change-control process — the economics of late change are a separate matter with their own logic in [Related article: The Front End Owns the Outcome]. Nor is it a benefit that failed to materialise and was misattributed between the delivery team and the receiving function, which is the argument in [Related article: The Hidden Cost of Putting Work Into Project Form], nor a question about who was seated to notice, which belongs to [Related article: Who Sits on the Board for the Benefits?]. It is something narrower and earlier: an expectation that was never contradicted was therefore never renegotiated, and by the time it surfaces the conversation is about what was agreed rather than about what should happen next. Those are different conversations, and the second one is much cheaper.
Why the template will not save you
There is a temptation to solve this by amending a template, and it is worth seeing how weak an instrument that is.
Two documents from the same teaching source, describing the same artefact, disagree with each other. One gives seven minimum components with risk as a section of its own; the other gives eight numbered sections in which risk survives as a clause and a single bullet inside a planning summary, while two optional sections become mandatory. They also disagree about what the first section means: in one, objectives "represent the requirements of the Client, the organisation and other important stakeholders"; in the other, objectives are expressed "in terms of business benefits and the process for measuring the business benefit."
Those are not trivial differences. One asks the author to write down what people need; the other asks what the enterprise will gain and how it will be counted. An author following one and a reader trained on the other are not reading the same document.
If a single institution cannot hold one version of a foundational form, an enterprise with forty years of accumulated templates certainly cannot. The remedy is not a better field. It is a step in the process — a conversation with the people who hold the expectations — whose output happens to be recorded in a field.
Decision Framework
Five steps, applicable to any initiative before commitment and worth repeating at each major replan.
1. Write the positive list, then stop. Do not proceed to approval. The positive list is an input to the next step, not an output of the process.
2. Ask each receiving function what they believe is coming. Not do you agree with this scope? — that gets agreement. The question is what do you currently expect this programme to give you?, put to the person planning around the answer.
3. Sort every answer into three bins. In scope and badly communicated — fix the wording. Out of scope — write it into the exclusions, in the words the person used. Not decided — the valuable bin; each entry needs a named owner and a date, because an undecided item behaves exactly like an unstated one.
4. Publish the exclusions with the scope, in the same document, at the same time. Separated, they are read separately and the second one is not read at all. Approving that combined document is an act of the office that owns the decision, and where that office is unfilled or ceremonial the approval means nothing, for reasons set out in [Related article: Sponsorship Is an Office, Not an Endorsement].
5. Record who was told, and when. An exclusion sitting in a document nobody outside the programme has read is not an exclusion. It is a defence prepared in advance, and it will be recognised as one.
The mirror image: a statement the document does make, which the person named in it never undertook — a different failure with a different remedy, in [Related article: Most of Your Plan Is Somebody Else's Promise].
A supporting convention: every exclusion needs a destination. "Not in this programme" is half an answer. The other half is whether the thing is somewhere else, scheduled later, or not happening at all. Those three produce entirely different behaviour in the person receiving the news, and a list that does not distinguish them is read as the most optimistic of the three.
From Strategy to Execution
Immediate. Take the initiative closest to commitment and run steps two and three with three receiving functions. Half a day, producing perhaps five to eight items — of which one or two will surprise the delivery team and one will be a decision the executive did not know was outstanding.
Medium term. Change what an approval paper must contain. A scope section with no corresponding exclusions section is incomplete and should be returned, as a business case with no cost section would be. That is a one-line amendment to a template and a much larger change to what proposers investigate before they write, which is where the value is created.
Long term. Build the habit of harvesting expectations rather than announcing decisions. An organisation that communicates scope outward and never collects belief inward accumulates a standing gap between what is built and what is planned around — invisible by construction, because it consists entirely of things nobody has said.
Signals to Monitor
- Disputes that open with "we always understood that…" The signature of an unstated exclusion. Three in a year on one programme is a scoping problem, not a communication problem.
- Functions committing budget on the strength of a briefing rather than a scope document. An expectation exists that you have not seen.
- Exclusions lists containing only trivia. Where the exclusions read as training materials, hardware refresh, data archiving, the list was drafted by the delivery team from its own imagination rather than harvested from anyone else's.
- Undecided items with no owner or date. The most reliable predictor of a late dispute in the document, because they behave exactly like unstated ones until somebody closes them.
- Late requests framed as clarifications rather than changes. People do not ask for a change to something they believed was already included. The vocabulary tells you which they think it is.
- Second-hand expectation. Where affected people learned the scope from a town hall, a newsletter or a colleague, the boundary they hold is not the one you wrote.
Questions for the Leadership Team
- On our largest current initiative, what does each receiving function believe it is getting — and has anyone asked them in those words?
- Which items are genuinely undecided, and does each one have a name and a date against it?
- When we last had a dispute about scope, was the disputed item excluded in writing, or merely absent?
- Do our exclusions have destinations — somewhere else, later, or never — or do they simply say what we are not doing?
- Who outside the programme has actually read the boundary we think we set?
- If a colleague planned a two-year investment on the strength of our published scope, what would they get wrong?
Closing Perspective
Scope is treated as a description of work and behaves as a set of promises, most of which nobody made. They accumulate quietly, in the space between what a document says and what its readers needed it to address, and they come due where the enterprise has least room to respond.
The correction is not more documentation or a stricter template. It is one conversation, held before commitment, with the people who will plan around the answer — and the discipline to write down what they say in their own words, including the parts they will not want to hear.
An initiative that states clearly what it will not produce gives up nothing. It converts unexamined expectations into known positions, and the difference between those two states is where a great deal of avoidable disappointment lives.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.