SCOPE & CLIENT CHANGES / RUNBOOK BUREAU
How to Stop Scope Creep
Make a change visible before you accept the work. Write down what the project includes, compare new requests against that baseline and agree any effect on the fee and schedule before starting. The aim is to make room for sensible changes without silently expanding your commitment.
Recognize the point where a request becomes extra work
Scope creep is the gradual expansion of work beyond what was agreed, without a corresponding decision about the time, fee or delivery expectations. A new request is not automatically a problem. It becomes one when it slips into production without anyone deciding what changes.
A correction needed to meet the agreed brief is different from a new deliverable. If you missed an agreed requirement, put it right. If the client wants a different outcome, an additional version or another review round, compare that request with the written scope before treating it as included.
Make the starting scope specific enough to check
- List the deliverables, quantities and formats, including anything the client must supply.
- Define the number of review rounds and what each round covers. Ask for consolidated feedback from a named approver.
- Record meetings, research, handover and reporting that are included. These take time even when they do not produce a separate file.
- Write down exclusions, milestones and dependencies, plus how proposed changes will be discussed.
For example, “one five-page website with one consolidated revision round” is easier to check than “website support.” Keep the agreed brief and later decisions together so you and the client can refer to the same version.
Watch for small changes that add up
- Feedback arrives in several batches after the agreed review round.
- A second stakeholder introduces a different objective after work is approved.
- “One quick version” becomes a regular request for extra formats or audiences.
- More calls, research or reporting appear without anything leaving the original workload.
- The deadline moves forward while the amount of work stays the same.
These are reasons to check the scope, not reasons to accuse the client. Clients may not see the production effort behind a small-looking request. Flag the impact when it first becomes clear rather than saving a list of frustrations for the final invoice.
Use Request → Impact → Approval → Fee → Record
- Request: capture the proposed change in a shared note or email, with the outcome the client needs.
- Impact: compare it with the baseline. Estimate additional effort, direct costs, dependencies and any effect on the delivery date. Include a proposed fee or a no-cost scope swap here.
- Approval: ask the agreed decision-maker to accept the revised work, fee and timing in writing before work starts.
- Fee: carry the approved amount into the project budget and agreed billing schedule. This is recording an agreed fee, not adding a surprise charge after approval.
- Record: save the decision with the updated scope and tell affected people which version now applies.
If the request is too unclear to estimate, clarify it first. If the client has a fixed budget, offer a smaller change or a swap with something of comparable effort. A scope swap still needs a written record of what is removed.
A small change caught early
You are producing one presentation with one review round. During review, the client asks for a shorter investor version as well. That is a second deliverable, not simply a correction to the first.
Confirm the intended audience, estimate the adaptation and review time, and show whether it affects the original deadline. The client can approve an additional fee, replace part of the original work or defer the new version. Until a decision is made, keep working only on the unaffected agreed scope.
Avoid prevention habits that backfire
- A vague “reasonable changes included” promise leaves both sides guessing. Describe the review allowance instead.
- Approving a request verbally and recording it weeks later makes the decision harder to reconstruct. Send a short written recap promptly.
- Charging for every clarification damages trust. Check whether the work already belongs in the brief.
- Absorbing an extra once without saying so can create an expectation. Record a deliberate no-charge exception and its limits.
- A change log is useful only if decisions happen before delivery. Do not let it become a diary of unpaid work already completed.
Give the next request a clear decision
Check your current brief for deliverables, review limits and an approver. The Scope Control System gives you working records for agreed scope, change requests, approvals and commercial impact when you need a consistent place to manage them.
Paid products are purchased on Etsy.