How to stop scope creep in website revisions without losing the client.

Scope creep is the slow growth of a project beyond what was agreed, without the time or budget growing with it. On website projects it usually hides inside revisions: "while you are at it", "just one small thing", "can we also add a page for…". None of these is unreasonable. The problem is that nobody is counting.

Why it happens on website projects

• The client sees the site for the first time and has new ideas. This is normal and often good. A real website is easier to imagine than a sitemap.
• The brief was vague. "A modern website with a blog" can mean almost anything.
• New people join late. A manager who was not in the kickoff sees the site and wants changes.
• Feedback is scattered. When requests come from email, calls and chat, it is hard to see how many there are.
• Nobody wants to be difficult. You say yes to keep the relationship warm, and the client does not know the request was extra.

Prevent it in the proposal

Most scope conversations are easy if the proposal already answers them. Include:

• A list of pages and features, as specific as you can make it. "Up to 8 pages" is better than "a website".
• What is not included, for example copywriting, photography, translations, online booking or an online shop.
• How many revision rounds are included at each stage, and what a round is (see how to run approval rounds).
• What counts as a revision and what counts as new work. A simple rule: a revision changes something already in the scope; new work adds something that is not.
• The price of extra work: an hourly rate, a fixed price per extra round, or a quote before starting.
• Who approves, so that late opinions go through one person.

Tell a revision from a change of scope

When a request arrives, ask three questions:

1. Is the thing being changed already part of the agreed scope?
2. Does it change something that was already approved?
3. Will it take more than a few minutes, or affect other pages?

"Make the headline shorter" on a page in progress is a revision. "Add a page for our new service" is new work. "Change the colour scheme" after the design was approved is a change to an approved decision, and that should be treated as new work, even if it seems small.

Keep a visible record

The best protection against scope creep is a record that both sides can see: every request, where it is, what was said about it and whether it is done. When requests are collected in one place, attached to the page they are about, it becomes obvious when round two has forty notes instead of ten. That is not a confrontation; it is just a fact you can point to.

Approvals belong in the same record. If the Home page was approved on the 3rd, a request to redesign its header on the 20th is clearly a new request.

What to say when a request is out of scope

Most clients do not know where the line is. They will not be upset if you explain it simply, early and without blame. Some phrases that help:

• "Happy to do this. It is outside what we agreed, so it would be [price/time]. Shall I go ahead, or keep it for a second phase?"
• "Good idea. This changes a page you already approved, so I will treat it as a new request. Here is what it involves."
• "We have used the two rounds included for this stage. I can do a third round for [price], or we can collect these points for after launch."
• "Let us put this on a list for phase two, so we can launch on the date we agreed."

Offering a "phase two" list is especially useful. It shows you take the idea seriously, and it protects the launch date.

Say yes sometimes, on purpose

Not every extra request needs a price. Small favours build goodwill, and many studios include some buffer for them. The difference is that you choose them knowingly, and you say so: "This one is on me." The client learns that it was a favour, not the default.

A quick checklist

• Pages, features and exclusions written in the proposal.
• Number of revision rounds and price of extras written down.
• One person on the client side who approves.
• All feedback collected in one place, attached to the page it is about.
• Every page approved in writing before moving on.
• A phase-two list for good ideas that are not in scope.

Where Tweakpin fits

Tweakpin does not set your scope; your proposal does. What it gives you is the visible record. Your client's notes are pinned to the elements on the real page, each with its conversation underneath, so you can see at a glance how many requests a round holds and where they are. Clients mark each page as approved, and the page shows that status to everyone who opens it, so a later request to change an approved page is easy to recognise and talk about.