The steering meeting ends with a seemingly harmless request: “Could the consultants also interview our country teams?” The project sponsor agrees. The consulting partner says the team can fit it in. Nobody checks whether those interviews were included in the statement of work (SOW).
A few weeks later, the additional interviews appear in a revised workplan. The final recommendations move back, and the supplier submits a fee adjustment. Procurement is asked to approve a change that has effectively happened already.
This is how scope creep develops in advisory work. Requests are made through conversations, while contractual authority sits elsewhere. The goal is to make each meaningful change an explicit decision before its costs become difficult to reverse.
Establish the Baseline the Team Can Actually Compare Against
At kickoff, procurement and the business project manager should turn the signed SOW into a usable scope baseline. Keep the signed document authoritative, but extract terms needed in delivery reviews:
- Deliverables, intended audience and acceptance criteria.
- Included activities, interview coverage, workshops and geographic boundaries.
- Client inputs and assumptions on which the supplier's proposal depends.
- Milestones, dependencies, fee basis and any agreed expense or effort limits.
- Exclusions, change-control provisions and the individuals authorized to approve amendments.
A phrase such as “develop a regional operating model” is too broad to settle whether an extra country workshop is included. The agreed proposal and clarification records may help; where documents conflict, contractual precedence matters. Procurement should involve Legal rather than invent a narrower scope after signature.
Store the approved SOW, exhibits and amendments together, alongside dated delivery plans accessible to the sponsor and consulting lead.
Triage the Request Before Calling It a Change
The trigger is any request that could alter a contracted deliverable, activity, assumption, milestone, resource requirement or fee. The business project manager logs it when raised, even if the request originated with the sponsor.
Use four distinctions rather than treating every new conversation as a chargeable variation:
| Request type | Decision test | Next action |
|---|---|---|
| Existing obligation | Is the work already required by the agreed SOW and acceptance criteria? | Assign it within the current plan; do not pay again for delivery or correction of nonconforming work. |
| Clarification | Does the request explain an ambiguous requirement without materially expanding it? | Record the agreed interpretation and check any schedule implications. |
| Scope trade-off | Can an existing activity be removed or reduced in exchange for the new one? | Assess value, quality and schedule effects; document the revised baseline even if fees stay unchanged. |
| Additional scope | Does it add output, coverage, effort or obligations beyond the agreed baseline? | Obtain a priced and scheduled change proposal before authorizing the additional work. |
Illustrative example: An SOW calls for interviews in two markets and a consolidated recommendation report. A sponsor later requests interviews in a third market. That is a candidate for additional scope, not an automatic entitlement to a fee increase. If the supplier also failed to conduct interviews already contracted in the original two markets, completing those interviews is a separate performance obligation.
This avoids double charging without blocking legitimate new needs.
Evaluate the Whole Impact, Not Just the Incremental Fee
For a genuine change request, ask the consulting lead for a short impact assessment tied to the current baseline. It should show what would be added or removed, the revised deliverables, people and effort, incremental fee calculation, expenses, dependencies and effect on existing milestones. Identify research or analysis already paid for.
Procurement tests the commercial basis: Are role rates consistent with the agreement? Is the effort credible for the new activity? Are subcontractors or specialist advisers being introduced? Does the change affect intellectual property, confidentiality or data-access obligations? The project manager tests dependencies; the sponsor judges the business case. Finance confirms funding under internal approval rules.
Always compare three feasible options: add the work, substitute it for lower-value work, or defer it to a separately scoped phase. A fourth answer, decline, is valid when the benefit does not justify the disruption.
For time-and-materials engagements, an unused budget ceiling is not permission to expand scope. For fixed-fee projects, “no extra charge” does not eliminate the need to assess delivery dates and acceptance criteria. Neither pricing model settles what the signed contract actually requires.
Keep Commercial Authority Separate from Project Direction
A senior stakeholder may authorize the business need without having authority to amend the supplier contract. Make that distinction explicit in the project governance plan.
The business sponsor owns the case for the change and accepts any trade-off in business outcomes. The project manager owns the impact log and integrated workplan. Procurement checks the existing commercial terms, challenges the fee proposal and routes the change for approval. Finance and Legal participate when budget, liability, data rights or contractual interpretation require them. Only the parties with delegated authority execute the amendment or other change instrument permitted by the contract.
Agree the decision route early. Project leads may record clarifications if permitted; changes to fees, milestones or obligations follow the authorized signature process. No universal monetary threshold or turnaround time applies to every organization.
The Association for Project Management's change-control guidance describes logging, impact evaluation, a sponsor or governance decision, plan updates and implementation. The CIPS Contract Management Cycle similarly calls for changes in scope to be approved at the appropriate authority level and communicated to stakeholders.
For proposed work not yet authorized, the default instruction should be to hold the affected activity pending the contractual decision, while continuing undisputed in-scope work where practical. If urgent work genuinely cannot wait, use an expressly permitted interim authorization route and document the financial exposure; a meeting comment is not a substitute.
Find the Unapproved Work Before the Invoice Arrives
A change register alone will miss informal scope growth if nobody compares it with delivery. At each agreed project review, the project manager should reconcile three records: requests made in workshops or email, activities appearing in the supplier's latest workplan, and approved scope changes.
Look for new stakeholder groups, country coverage, redesign requests, data collection and workshops without an updated plan. Ask who requested each activity and which approval covers it. A new task is not necessarily a breach, but unexplained work should be classified before it becomes a billing dispute.
Review invoice narratives and effort reports against the approved baseline and authorized changes, particularly under time-and-materials arrangements. This is a check on chargeable work, not an invitation for procurement to direct consultants' daily tasks. If unauthorized work has already happened, preserve the request trail and escalate for contractual assessment; do not assume retrospective approval or automatic nonpayment.
Close a Change Only When the Revised Work Is Accepted
After authorization, update the SOW or approved change instrument, delivery plan, fee forecast and change register. Record who approved it, when it took effect, which original activities it superseded and what evidence will demonstrate completion.
At the revised milestone, the sponsor reviews the deliverable against updated acceptance criteria. Procurement confirms that invoices reflect authorized fees, and the project manager records open defects or unfinished dependencies. A signed amendment shows permission to perform the work; it does not prove the work was delivered well.
The control that prevents consulting scope creep is a traceable decision between a request and a commitment. When that decision includes value, cost, timing and authority, advisory teams can adapt their work without turning every useful idea into an uncontrolled extension.