Most consulting engagements go wrong at the scoping stage, not the delivery stage. The scope document is signed quickly, often under time pressure, and the assumptions embedded in it are not examined until they become problems. This article covers the questions worth asking before any contract is agreed.
What Is the Scope Document Actually For? ¶
A scope document is not a project plan. It is an agreement about what the engagement will and will not address. The distinction matters because most organisations treat the scope as a formality, something to be agreed quickly so the work can begin. In practice, the scope is the most important document in the engagement. It defines the boundaries of the work, the criteria for completion, and the basis on which any disputes about additional work will be resolved. Time spent on it at the start is not time lost.
The Three Questions Most Scopes Do Not Answer ¶
First: what would a successful outcome look like, in specific and measurable terms? Not 'improved operational efficiency' but 'a ranked set of recommendations with implementation sequencing, delivered by week ten'. Second: what is explicitly out of scope, and why? Naming what the engagement will not address is as important as naming what it will. Third: what are the conditions under which the engagement should be paused or stopped? This question is almost never asked. It should be.
How to Handle Scope Creep Before It Happens ¶
Scope creep is not usually the result of bad faith. It is the result of a scope that was not specific enough to make the boundary visible when it was crossed. The practical fix is to include a change control clause in the engagement agreement: any material change to scope is agreed in writing before additional work begins, and the fee is adjusted accordingly. This protects both parties. It also forces a useful conversation about what 'material' means before there is any disagreement about it.
When to Walk Away From a Scope ¶
If the scope cannot be agreed in specific terms, that is information. It usually means the organisation does not yet have enough internal clarity about what it needs. Proceeding with a vague scope produces a vague engagement. The more useful step is to commission a short diagnostic phase, with its own narrow scope, before the main engagement begins. This is slower at the start. It is faster overall.
Scoping is not a bureaucratic step. It is the first piece of analytical work in the engagement, and it tells you a great deal about whether the conditions for a successful outcome exist.