The discovery call goes well. Forty-five minutes, the client talks freely, you take notes, everyone agrees the problem is important. Two weeks later your proposal mirrors their words back to them: a competency framework, leadership training, a rollout across regions. Three months later you are running a fourth workshop nobody priced, rewriting anchors for a department nobody named, and absorbing it all because the relationship matters.
Here is the claim worth arguing about: that call scoped nothing. It collected symptoms. A discovery conversation that ends without the client making a decision has not bounded the work. It has booked the first instalment of scope creep.
Why the conversation produces a mirror, not a scope
Both sides are rewarded for keeping the call pleasant. The client describes a frustration in the only vocabulary the organisation gives them, which is usually a solution: we need negotiation training, we need a framework, we need AI literacy. You nod, because disagreeing in a sales call feels like losing the work. The proposal then restates the symptom at a price, and the boundary of the work is never drawn, because drawing it means saying no to something the client has not yet asked for.
The project-management literature puts the cost of this politely. PMI’s 2018 Pulse of the Profession found that 52 percent of projects completed in the previous twelve months experienced scope creep or uncontrolled changes to scope, up from 43 percent five years earlier. In PMI’s own analysis of the causes, the first item on the list is an ambiguous or unrefined scope definition, ahead of weak change control and absent sponsors. The boundary was never drawn, so every later request looks like part of the original ask.
One distinction matters before going further. An expansion the client approves and pays for is not creep. Creep is the unapproved addition absorbed silently, the extra cohort, the extra region, the extra analysis. A peer-reviewed guide to writing scopes of work for statistical consulting makes the uncomfortable point that poorly scoped projects often still deliver their answer, but at the expense of overworking the consultant. The failure is invisible in the deliverable and visible only in your margin and your next renewal.
Scoping is consulting work, not administration. It is the step where the business problem is separated from the requested solution, and it is the step the sales calendar quietly removes.
Five questions, in the order the work happens
Each question below forces a decision. A decision has a person, a choice and a date. If the answer has none of those, it is a preference, and preferences do not price.
One: what decision will this work let someone make, who makes it, and by when? Not what problem we will solve. What decision. “Improve leadership capability” scopes nothing. “The plant head decides which eighteen supervisors run the new line’s shift handover, before commissioning on 15 March” scopes everything: population, behaviour, deadline, owner. If no decision can be named, the work is research, and research should be sold as a bounded diagnostic with its own price, not as a transformation with an open tail. The statistical-consulting guide makes exactly this move: when the question is too vague to scope, start with a smaller, separate scope for designing the question itself.
Two: which behaviour, in which role, in which situation, changes first? This forces the population choice the brief avoids. “All managers, better communication” is not a scope; it is an audience. One role, one situation, one observable behaviour is a scope. If the behaviour cannot yet be written as an action a stranger could tick on a recording, the first bounded piece of work is a baseline, not a workshop; an assessments practice that measures before it trains exists for this reason. Turning a course request into a gap statement is a method of its own, and we set it out in a training needs analysis is not a course catalogue. Discovery decides which gap statement this engagement owns. It does not own all of them.
Three: what is explicitly out, and who agrees it is out? The out-list is the scope. PMI’s scope guidance is blunt about this: define both sides of the boundary with the sponsor during planning, not just the inside. Name the three things the client will plausibly ask for in week three and write them down now: the other regions, the competency framework rewrite, the change to the logbook or CRM. An exclusion the client has agreed to in writing is a sentence you can point at later. An exclusion you merely hoped for is a favour you will be asked to repay.
Four: what do you supply, by when, and what happens if it is late? Every training engagement runs on client inputs: data, released people, a named sponsor, access to a room or a system. List them with dates. Then write the consequence of lateness: the timeline moves, or the work pauses, or the scope shrinks. A scope without a pause clause is a promise to absorb someone else’s delay for free. The same guide recommends discussing contingencies before signature, precisely because the alternative is discovering them mid-project.
Five: what counts as done, and what happens if the number does not move? Done is an acceptance criterion tied to a number the business already reads, not a satisfaction score. And the change route is written now: additional requests become a priced appendix to the scope note, re-signed by both parties. That sentence, borrowed from the statistical-consulting guide, converts every future “can you also” from a favour into a decision. It is the cheapest clause in the document and the one that saves the engagement.
| Question | Answer that scopes nothing | Answer that prices work |
|---|---|---|
| Decision | Improve leadership capability | Plant head picks 18 supervisors for the new line by 15 March |
| Behaviour | All managers, better communication | Supervisors name open exceptions at handover, one plant |
| Out list | We will keep it focused | Other plants, framework rewrite and logbook change are out |
| Inputs | Client will support as needed | Two weeks of logs by Friday; two batches of nine released |
| Done and change | Successful rollout | Exceptions named in 36 of 40 notes; extras priced as appendix |
The artefact: one page, signed before work starts
Write the answers as a one-page scope note: the decision and its owner, the behaviour and population, the out-list, the inputs with dates and the pause clause, the acceptance number and the change clause. Send it the same day as a summary of the call, and ask for a reply confirming it. The statistical-consulting guide is explicit that the scope is signed before the project formally begins, and that a follow-up email reviewing the takeaways is part of the scoping, not a courtesy after it.
If questions one and two cannot be answered in the call, do not write the proposal. Price a two-week diagnostic instead: a bounded piece of work whose deliverable is the decision and the gap statement. That is an honest product. A transformation priced on top of an undecided question is not.
A worked example
Illustrative example. A manufacturing group asks for “a competency framework and leadership training for 52 managers across four regions”. The implied budget is about Rs 22 lakh and the implied scope is everything.
One discovery call with the plant head and the HR head runs the five questions. The decision: which twelve key-account managers carry the new consultative pitch into the Q1 launch, chosen by the regional head before the launch briefing. The behaviour: two diagnostic questions before any discount is offered, in twelve managers, one region. The out-list: the other forty reps, the framework rewrite, the CRM change, the other three regions. The inputs: twenty recorded calls by Friday, twelve managers released for two half-days, the regional head chairing the Monday pipeline review. Done: discount-free first proposals rise from a baseline of 4 in 16 sampled calls to 12 in 16, read in the pipeline meeting; if the number has not moved by week six, one priced revision cycle, not an open tail.
The bounded engagement prices at Rs 6.5 lakh over six weeks. The framework rewrite and the other regions remain available as priced appendices. These figures are constructed for illustration, not a client result or a benchmark. What generalises is the shape: one decision, one behaviour, one region, an out-list the client agreed to, and a change route that keeps every later request a decision instead of a favour.
The honest limit
The five questions surface an undecided client; they cannot force one. Sometimes the ambiguity is deliberate: a sponsor who will not name the decision is protecting a political option, and no scope note fixes that. What the note gives you is an early, cheap exit: price the diagnostic, or decline, before the margin is committed.
Two further limits. The 52 percent figure comes from PMI’s global project survey, not from Indian training engagements; it tells you the failure is common and structural, not that your next programme has a 52 percent chance of creeping. And a signed scope note bounds the work, not the outcome. A behaviour that is scoped, priced and rehearsed can still fade once the reinforcement stops, for the reasons we set out in why behavioural training fades. Scope discipline and transfer discipline are separate jobs, and the note only does the first.
What to do on Monday
Take the proposal you are about to send, or the brief you are about to answer. Book forty-five minutes with the person who owns the decision, not only the person who wrote the brief. Ask the five questions in order and write the answers as one page. Send it back the same day and ask for confirmation before you price anything.
If question one has no answer, stop and price a two-week diagnostic instead. That single substitution, a bounded diagnostic in place of an open transformation, is the difference between a scope note and a mirror. The mirror flatters everyone in the call. The note is what you can defend in week three.
Sources
- PMI, Scope Patrol (2018), reporting the 2018 Pulse of the Profession: 52 percent of projects experienced scope creep, up from 43 percent five years earlier: https://www.pmi.org/learning/library/scope-creep-rising-11308
- PMI, Top Five Causes of Scope Creep: ambiguous scope definition first; approved expansion is not creep; define both sides of the boundary: https://www.pmi.org/learning/library/top-five-causes-scope-creep-6675
- Peterson et al. (2022), Reaping what you SOW, Stat 11(1):e496: scope signed before work begins, contingencies discussed, expansion as a re-signed appendix, smaller design-only scope when the question is vague: https://pmc.ncbi.nlm.nih.gov/articles/PMC12302940
