scope creep

The client asks for one more page. Then a second revision becomes a new design direction. Someone adds a reporting dashboard to a project that covered a basic website. Each request seems manageable in isolation, until the team realizes the original budget and deadline no longer describe the work.

Scope creep happens when project work expands without a corresponding decision about resources, timing, or commercial terms. To handle client requests outside the agreement, clarify the request, compare it with the approved scope, assess its impact, and obtain the appropriate agreement before starting the additional work.

A client can have a legitimate new need. Your team can also need a revised plan to meet it. The aim is to make that trade-off clear while preserving a constructive working relationship.

1. Check whether the request is actually outside scope

Start with the statement of work, accepted proposal, approved specifications, and documented decisions. Compare the requested outcome with the deliverables and acceptance criteria. Avoid judging the request only by how long someone thinks it will take.

A correction that brings work up to the agreed standard is different from an added feature. If a contact form was supposed to submit successfully and does not, fixing it addresses an existing commitment. Adding a second approval workflow may introduce new requirements. Revisions within an agreed allowance should also follow that allowance.

Where the agreement is ambiguous, investigate before declaring an extra charge. Review the relevant correspondence together and identify what each party understood. A weak brief needs clarification; it should not become an opportunity to surprise the customer with an invoice.

A PMI paper on scope change control emphasizes the importance of defined requirements and a structured process for changes affecting expectations. Apply that principle by establishing an agreed reference point before deciding how to handle the new request. [1]

2. Understand the business need before discussing the boundary

Ask what the request should accomplish, who needs it, and when the result becomes important. A request for another dashboard may really be a need to answer one question already covered by an existing report. Understanding the purpose helps you offer a proportionate solution.

Acknowledge the request without committing the team. “Thanks for explaining the need. We will review how it fits the approved work and come back with the options” keeps the conversation moving. Avoid “no problem” if the client could reasonably interpret it as approval to proceed.

Bring requests from email, calls, and messaging into one shared record. Record the requester and desired outcome, then identify the people authorized to approve changes. A helpful conversation with a project participant should not silently become a commercial commitment.

For the discipline behind that pause, read Why Your Mindset Is Your Advantage. The connection here is the discipline to listen, examine the facts, and respond without treating a new request as a personal challenge.

3. Assess the impact across the whole project

Estimate more than the visible production task. A new page can require copy, design, development, testing, analytics, accessibility checks, and final review. A small interface change can affect integrations or previously approved work.

Identify dependencies on the client and your team. If the request needs new content or access, show how those inputs affect the schedule. If it interrupts work already underway, include the effect on sequencing rather than assuming every task can run in parallel.

A PMI paper on fixed-price projects recommends evaluating, pricing, and agreeing changes before promising or acting on them. That is especially useful when the original fee depends on a bounded deliverable. [2]

Separate an estimate from a commitment. Where a request needs investigation, propose a defined assessment first. Do not invent a fixed price to end an uncomfortable conversation, or promise the original deadline before the people delivering the work have reviewed it.

4. Offer a clear choice and a written change summary

Give the client options that reflect the actual constraints. You might add the work with a revised fee and delivery date, exchange it for a specified unfinished item, or defer it to a later phase. A trade of deliverables still needs impact review; two features are not equivalent simply because each occupies one line in a list.

If you choose to absorb a small addition as a goodwill gesture, document what you are including and confirm the remaining boundaries. A deliberate exception can serve the relationship. An invisible exception leaves the next person guessing about what the fee covers.

Use a short change summary that includes:

  • The new request and its business purpose.
  • The added, removed, or revised deliverables and acceptance checks.
  • The additional fee or explicit confirmation of no additional fee.
  • The effect on milestones, dependencies, and customer inputs.
  • The person authorized to approve and the required approval method.
  • The point at which the team may begin the changed work.

Follow the change process in the actual arrangement. For disputed or significant contract questions, involve the appropriate commercial or legal reviewer. The summary is a practical communication tool, not a replacement for resolving those questions.

Tel’s article The CEO as Chief Cultural Engineer offers a useful connection: standards need to live in everyday decisions. Clear approval roles help the team respond consistently, rather than making the account manager enforce a boundary that nobody else follows.

5. Respond with specific options rather than a defensive refusal

Consider a hypothetical website project that includes five pages and two design revision rounds. The client requests a separate campaign landing page and a CRM integration. The request may be useful, but it needs assessment against the agreed work.

A reply could read:

“Thanks for outlining the campaign landing page and CRM connection. The current project covers the five agreed website pages and contact form. These additions introduce a separate page and integration workflow, so we will assess the design, testing, and delivery impact before starting them.

“We can prepare a change proposal with the additional fee and revised schedule, or consider the work as a second phase after the agreed website launch. If your priority is to keep the current budget, we can also review whether there is unfinished work you would prefer to remove; we would confirm the impact before treating it as an exchange.

“Which route would you like us to assess? We will document the scope, cost, and timing for your authorized approval before beginning the additions.”

The reply acknowledges the need, refers to the existing commitment, and offers a next step. It does not claim that a fee or delivery date has already been accepted. Keep the original project moving where the new request does not block it, and explain any genuine dependency promptly.

6. Prevent repeat surprises through delivery habits

At kickoff, review deliverables, exclusions, revision allowances, client inputs, and approval roles in plain language. Explain how the team will assess new requests. A customer should understand the process before encountering a change proposal.

Include a short scope update in regular project reviews: what is approved, what is complete, what is pending a decision, and what new requests need assessment. Update the delivery plan after approval so design, production, account management, and billing work from the same version.

In an iterative engagement, expect priorities to evolve. Clarify whether the commercial arrangement buys a fixed outcome, a defined capacity, or another model. Reprioritizing a backlog does not automatically create more capacity or preserve every original delivery commitment.

Look internally for causes of repeated expansion. Vague sales promises, incomplete discovery, unclear acceptance criteria, or team members independently agreeing changes can all create confusion. Track the cause and improve the process instead of treating every extra request as a customer problem.

Protect trust by making commitments visible

Tel K. Ganesan’s work across technology services and entrepreneurship provides a relevant setting for this leadership lesson. The Leadership OS emphasis on execution and systems applies to client delivery: define responsibilities and make commercial promises match the work the team can perform. [3]

Choose one active project and review its pending requests. For each, identify whether it is an included correction, an agreed revision, an unresolved ambiguity, or a proposed addition. Then put the next decision in front of the person authorized to make it.

A healthy client relationship can accommodate change. It becomes easier to sustain when everyone understands what the team has agreed to deliver, what needs a new decision, and what happens next.

Explore more of Tel K. Ganesan’s leadership and entrepreneurship insights as you build client delivery systems your team can sustain.

Frequently asked questions

Q1. Is every additional client request scope creep

No. A request may be an included revision, a correction, or an approved change. Scope creep concerns expansion without an appropriate decision about its effect on the work and commitments.

Q2. How do you explain that work is outside scope

Acknowledge the business need and refer to the relevant agreed deliverables. Explain that you will assess the additional work and offer options for scope, timing, and price before proceeding.

Q3. What belongs in a change request summary

Record the request, affected deliverables, acceptance checks, cost, schedule, dependencies, and approval process. Update the team’s working plan after the authorized decision.

Share this article