Operations
5 min read· Updated 2026-10-05

Stop scope creep with a clear change-request process

Scope creep is not simply a demanding client. It is additional work entering a project without a shared decision about time, cost or priorities. A good change process protects the relationship by making those trade-offs explicit instead of turning every request into an argument.

Write the boundary before work begins

Describe the deliverables, acceptance conditions, included revisions and assumptions in plain language. State what the customer must provide and what happens if that input changes. 'Website refresh' is less useful than a specific page list and content responsibility. Have a qualified adviser review contract terms when legal enforceability matters; an operational checklist is not legal advice.

Separate a correction from a change

If work does not meet the agreed requirement, fixing it is not automatically chargeable extra scope. If the client asks for a new requirement, assess the impact against the accepted baseline. Keep that baseline available to both parties. The purpose is to identify a difference clearly, not to use technical wording to avoid responsibility.

Worked example: adding a booking flow

A hypothetical client approves a five-page information site, then requests online booking during production. The team records the additional integration, testing and policy questions. It offers a revised delivery date, a reduced original scope or a separate later phase. The client chooses before anyone silently starts a sixth deliverable.

  • Requested change and business reason.
  • Effect on deliverables, dependencies, price and dates.
  • Alternative that keeps the original commitment.
  • Named approver and written decision.

Pause only the affected work

A change request does not always require stopping the whole project. Identify the work that can continue safely and the decisions that must wait. Give the customer a clear response window if timing matters. Keep the discussion separate from the original task list so an unapproved idea is not mistaken for an assigned deliverable.

Update the plan after approval

Save the accepted change, adjust dates and budget assumptions, and tell everyone whose work is affected. At project close, compare planned and actual effort, including changes. Repeated requests for the same excluded item may indicate that your standard offer is poorly defined or that the package should include it from the beginning.

Related guides