How to Handle Scope Creep in Client Feedback Rounds
Last updated: November 18, 2026
To handle scope creep, sort every client comment the day it arrives. A fix makes the work match what was agreed; new work changes what was agreed. Do fixes inside the feedback round. For new work, reply in writing with the time and cost it adds, and start only after the client says yes.
This guide is for agency project managers, designers, and freelancers running fixed-scope website projects. In PMI’s 2018 Pulse of the Profession, 52% of projects completed in the previous 12 months had scope creep, up from 43% five years earlier. On client work, most of it does not arrive as a formal request. It arrives inside a feedback round, mixed in with the fixes.
What Scope Creep Is, and What It Is Not
PMI defines scope creep as “the uncontrolled expansion of product or project scope without adjustments to time, cost, and resources.” The key word is uncontrolled. A client asking for something new is normal. Scope creep is new work that gets done without anyone deciding to do it, so the budget and the deadline stay where they were while the work grows.
The UK government’s project delivery guidance says the same thing from the other side: changes are inevitable, but they “should only be implemented through a structured change control process that protects the baseline against scope creep.” The baseline is your signed scope. Change control is the habit of deciding, in writing, before you build.
Fix, Revision, or New Work: A Test for Every Comment
Ask three questions of each comment, in this order. Is something broken? Then it is a bug, and you fix it. Does it change something inside the agreed scope? Then it is a revision, and it uses one of the rounds in your contract. Does it add a page, feature, integration, or deliverable the scope does not list? Then it is new work, and it needs a decision before anyone builds it.
| Client comment | Type | What to do |
|---|---|---|
| “The contact form does not send.” | Bug | Fix it. Do not count your own bugs against the client’s revision rounds. |
| “The heading font does not match the approved design.” | Bug | Fix it to match the design the client signed off. |
| “Can the hero image be a little taller?” | Revision | Do it inside the current round. |
| “We changed our mind on green. Make it navy.” | Revision or new work | A revision while rounds remain. After the last round, a change request. |
| “Can we add a careers page?” | New work | Reply with the time and cost, and wait for a yes. |
| “Can the form also send leads to our CRM?” | New work | Reply with the time and cost, and wait for a yes. |
| “Will this look right on my phone?” | Question | Answer it, and check the page at phone widths before you do. |
Why Scope Creep Hides in Client Feedback
- It arrives in pieces. A request for a new page sits in the same email as six spacing fixes, so it gets done with them.
- Each request is small. One extra button is an hour. Ten extra buttons across three rounds are a week nobody priced.
- Nobody says it out loud. If the team quietly builds the extra item, the client learns that it was included.
- A new reviewer joins late. A stakeholder who missed the brief reopens decisions the client already approved.
- The scope was a sentence. “A new website” cannot be checked against. A list of pages, templates, and rounds can.
PMI found that the projects of its best performers, which it calls champions, had less scope creep: 33%, against 69% for underperformers. Its report ties control to a clear scope, a continuous requirements process, and effective stakeholder and change management.
How to Handle Scope Creep, Step by Step
- Write the scope as a list. Name the pages and templates, the breakpoints you design for, the number of revision rounds, what the client supplies and by when, and what is not included.
- Agree the change process at kickoff. Say how a request outside the scope will be priced and approved, so the first one is not a surprise.
- Collect every comment in one list. When all feedback sits in one place, new work stands out next to the fixes. In an inbox, it blends in.
- Sort each comment the day it arrives. Mark it as a bug, a revision, new work, or a question, using the test above.
- Reply to new work the same day, in the same channel. Confirm the request, name it as outside the scope, give the time and cost, and ask for a yes.
- Record the decision on the item. Approved, deferred, or declined, with the date and who decided.
- Close the round in writing. List what changed, what did not, and why.
Steps 6 and 7 are what keep a project out of arguments at launch. The UK guidance tracks each change request through statuses such as requested, assessed, approved, deferred, implemented, and closed. A small agency does not need a register, but it needs the same record: what was asked, what was decided, and when.
What to Say When a Client Asks for More
The useful answer to new work is yes, at a price. You stay helpful, the client keeps control, and the trade-off is on the record. Four replies cover most cases:
Note: Price it: “Good idea. The careers page is outside the agreed scope: it adds about [hours] and moves launch by [days]. Want me to go ahead?”
Swap it: “We can add the careers page this phase if we drop [not-started item]. Which do you prefer?”
Defer it: “Let’s launch with the agreed pages and put the careers page first in phase two.”
Gift it once, on the record: “Happy to include this one. It is outside the original scope, so I am noting it here. The next request like it will come with a quote.”
The swap comes from Jesse Fewell’s dynamic scope option, quoted in the same PMI report: “You can replace any not-started deliverable with anything of equal or lesser cost.” It works well on a fixed budget, because the client chooses what matters most instead of hearing no.
Scope Creep Examples on Website Projects
| Request | Why it is scope creep | A good response |
|---|---|---|
| “Can we add a blog while you are in there?” | A new section with its own templates and content model | Quote it as a change, or put it in phase two. |
| “The new CEO wants a different homepage.” | It reopens an approved design | Treat it as a change request, and confirm who approves now. |
| “Can it work in Spanish too?” | A second language adds content and testing to every page | Quote it as a change. |
| “We will send the copy next week.” | Late content forces layouts to be redone | Note the delay and its effect on the timeline in writing. |
| “Small thing: can the menu do what this other site does?” | A new interaction, not a fix | Quote it, or offer the swap. |
How to Prevent Scope Creep on the Next Project
- Count the deliverables. “Five page templates at 1440 and 390 pixels wide” can be checked; “a new website” cannot.
- Name the exclusions. Copywriting, photography, a second language, and integrations are the usual surprises.
- State the revision rounds and their price. There is no standard number. Pick one, write it down, and say what an extra round costs.
- Name one approver. One person on the client side settles conflicting feedback and signs off each round. See our guide to review and approval workflows.
- Ask for feedback in a set shape. A round with a deadline, a list of pages, and specific questions produces fewer surprise requests. Our guide on how to ask for client feedback has templates.
Where a Feedback Tool Helps
Scope creep is easier to see when every comment is pinned to the page it is about and lands in one list. In OverlayQA, clients open a review link and comment on the live site with no account or extension. Each comment arrives as an issue with a screenshot, the page address, browser, and screen size, so the team can sort it as a bug, a revision, or new work, add a label such as “change request”, and track it from Open to Resolved. When the client clicks Done reviewing, the team knows the round is finished.
When the round ends, send the recap. NN/g’s followup template fits change requests well: name the feedback, state the decision, give the reason, and say what happens next. For more on running the whole feedback queue, see how to manage client feedback.
Frequently Asked Questions
What is scope creep?
Scope creep is work added to a project without matching changes to its time, cost, or resources. PMI defines it as the uncontrolled expansion of product or project scope. A change that is priced and approved is not scope creep.
How do you handle scope creep without upsetting the client?
Say yes, at a price, and say it early. Reply the day the request arrives, confirm what they asked for, name it as outside the agreed scope, give the time and cost, and ask whether to go ahead. A quote sent the same day reads as service. The same charge on a final invoice reads as a surprise.
Is a revision the same as scope creep?
No. A revision changes work that is already in the scope, and it uses one of the rounds in your contract. Scope creep adds work the scope does not list, or keeps revising after the agreed rounds are used, with no decision about time or cost.
Should bugs count as a revision round?
No. A broken link or a layout that does not match the approved design is the agency’s defect, not a client change. Fix bugs without using up the client’s rounds, and keep them in a separate category so the count stays fair.
How many revision rounds should a website project include?
There is no standard number. What matters is that the number is written in the scope, the client knows it before the first round, and extra rounds have a stated price.
What is a change request?
A change request is a written record of new work: what was asked, what it adds in time and cost, and whether the client approved, deferred, or declined it. It turns an informal favor into a decision both sides can see.
How do you prevent scope creep?
Write the scope as a list, name what is excluded, state the revision rounds, name one approver, agree the change process at kickoff, and keep every client comment in one list so new requests are visible.
Keep every client comment in one list, pinned to the page it is about. With OverlayQA, clients comment with no account, and each comment becomes a tracked issue you can label as a fix or a change request.