Scope creep for freelance web designers: where website projects grow, and the line that stops each one
Website projects rarely grow in random places. They grow where a non-designer can't see the work: the page text that hasn't arrived, the "simple" contact form that now needs to book appointments, the old site that has to come across, the edits someone expects after launch.
That's good news. If scope creep in web design tends to happen in the same few spots, you can write one line for each spot before the project starts. Then most "can you also just..." requests become a quick check against the scope summary instead of a negotiation.
This article covers the main places a website project grows, a fictional project followed from quote to launch, and a block of lines you can paste into your own scope summary.
Not legal advice. The wording below is for a plain-language scope summary or proposal that describes the work. It isn't a contract. Payment terms, ownership, liability and cancellation belong in a contract, ideally one reviewed by a qualified lawyer where you work.
Why website projects are especially easy to stretch
Three things make web design projects easy to stretch:
- The client can't see the work behind a request. "Add a booking button" looks like one button. Behind it there's a tool to choose, an account to set up, settings to test and a page to redesign.
- The project depends on things you don't control. Copy, photos, logins, domain settings and third-party tools all come from somewhere else. When they're late or different from what you expected, the work changes.
- A website doesn't have an obvious finish line. A logo is delivered. A website goes live and then keeps running, so "after launch" requests feel natural to the client.
None of this means the client is being unreasonable. It means the edges of the project have to be written down, because they aren't visible on their own.
The web design scope creep map
Each row is a place website projects often grow, what the request tends to sound like, and the line in your scope summary that answers it in advance.
| Where it grows | What you'll hear | The line that answers it |
|---|---|---|
| Content | "Can you just write something for the About page?" / "The text is nearly ready" | Who supplies text and images, the date they're due, and what happens to the timeline if they're late |
| Page count | "Can we add a page for the new service?" | The exact pages, by name, plus the price or process for extra pages |
| Features | "Can the contact form take bookings?" / "Could we sell gift cards?" | The features included, by name, and that new features are quoted first |
| Third-party tools and fees | "Which booking app should we use? Can you set it up?" | Who chooses, pays for and owns each account; what "connect" includes |
| Old site and migration | "Can you bring over all the old blog posts?" | How many pages or posts move across, and in what form |
| Design direction after sign-off | "We've had a think, can we try a darker look?" | When the design is approved, and that a new direction after approval is a change |
| Devices and browsers | "It looks different on my old tablet" | Which devices and browsers you test on |
| Accessibility and search | "Is it accessible?" / "Will we show up on Google?" | What you do (for example clear headings, alt text fields, page titles) and what you don't promise. If a specific accessibility standard is needed (such as a WCAG level), agree it up front |
| Launch and after | "Can you update the opening hours each week?" | What launch includes, how many days of fixes follow, and how ongoing edits are handled |
| New decision-makers | "My business partner has some thoughts" | Who gives feedback and who has the final say |
You won't need every row in every project. The first five tend to come up on small-business sites. The last few matter more as the client gets bigger or the site gets more complex.
Fictional worked example: a five-page site for a plant nursery
Fictional example. The designer, the client and every request below are invented to show the method. There are no prices in this example on purpose: use your own.
The project. Mara is a solo web designer. A family-run plant nursery asks for "a fresh five-page site, nothing complicated, so people can see what's in stock". Before quoting, Mara asks her intake questions and writes a one-page scope summary. The lines that matter later are these:
- Pages: Home, About, Plants, Visit Us, Contact (5 pages).
- Content: you supply all page text and photos by [DATE]. If they arrive later, the launch date moves back by the same number of working days.
- Features: contact form and a map on the Visit Us page. Stock lists, online sales and bookings aren't included.
- Old site: I'll move the text from your current About and Visit Us pages. Old news posts aren't moved.
- Design: two rounds of changes on the homepage design, then one on the inner pages. Design is approved when you reply "approved" by email.
- Launch: includes 14 days of fixes for anything that doesn't work as agreed. Content updates after that are quoted per request or as a monthly plan.
- Feedback: [OWNER NAME] sends one combined list per round and has the final say.
The client confirms it by email. Here's what happens over the next seven weeks. Where a request is out of scope, the "Type" column uses the four request types from the out-of-scope request email guide: tiny favour, new deliverable, extra revision round, changed goal.
| Week | Request | Type | What the scope line made easy |
|---|---|---|---|
| 2 | "Could you change the green to match our new van?" | In scope (homepage round 1) | Nothing to negotiate: it's part of the included rounds |
| 3 | Photos arrive five working days late | Not a request: a late dependency | Mara replies with the new launch date, pointing to the content line |
| 3 | "Can you add our phone number to the footer too?" | Tiny favour | Mara does it, says so, and logs it |
| 4 | "Customers keep asking about stock. Could the Plants page show what's available each week?" | New deliverable | The features line already says stock lists aren't included, so Mara offers to quote it as a phase two |
| 5 | "My daughter has some ideas for the design" (after approval) | Not a request yet: a feedback-process question | The feedback line names who has the final say; Mara asks the owner which notes, if any, they want to send as a change |
| 7 (after launch) | "Can you update the opening hours for the holidays?" | New deliverable | The 14-day window covers things that don't work as agreed. This is new content, so Mara quotes it or offers the monthly plan |
The week-4 request is the one that would have hurt. A weekly stock list sounds small to the client. In practice it means choosing how the nursery will update it, building a template, and training someone to keep it current. Because the scope summary already said "stock lists aren't included", Mara's reply is short:
Hi [NAME],
That's a good idea, and I can see why customers ask. A weekly stock list isn't part of this build (it's in the "not included" list in the scope summary), and it needs a bit of planning: where the list lives, who updates it, and how.
Two options:
- Phase two: we launch on [DATE] as planned, and I send you a separate quote for the stock list next week.
- Add it now: I quote it this week, and the launch moves to [NEW DATE] if you go ahead.
Which would you prefer?
Best, Mara
No apology, no lecture. The scope line did the arguing in advance, so the email only has to give options.
Two web design moments to pin down early
Most of the map can be handled with a single line. Two moments need slightly more care, because they're where website projects tend to stall.
1. The content deadline
On many small-business sites the client supplies the text and photos. If they arrive late, the designer either waits or starts building with placeholder content and then rebuilds around the real thing. Both cost time.
Put three things in writing:
- What the client supplies (text for each named page, photos, logo files, product details).
- When it's due, as a date, not "before the build".
- What happens if it's late: the launch date moves by the same amount, or you build with placeholder text and treat later layout changes as revisions.
If the client asks you to write the copy instead, that's a new deliverable. Quote it, or recommend a copywriter.
2. Design approval
"Approved" needs to be a moment the client recognises, not something you decide later. Ask for a specific reply, such as the word "approved" by email, and say what it means: after approval, changes to layout or style on the approved pages count as a change, not a revision. The guide to how many revision rounds to include has wording for rounds and feedback windows.
Copy-paste: lines for a web design scope summary
Adapt these to your project. Delete any that don't apply. Not legal advice and not a contract: these sit alongside your contract and should match it.
PAGES: [list each page by name] ([number] pages). Extra pages are
quoted before I start them.
CONTENT: You supply all page text, photos and logo files by [DATE].
If they arrive later, the launch date moves back by the same number
of working days. Copywriting and photography aren't included.
FEATURES: [list: contact form, map, newsletter sign-up, etc.].
New features (bookings, online payments, member areas, stock lists)
are quoted separately before any work starts.
THIRD-PARTY TOOLS: You choose, pay for and own the accounts for
[hosting / domain / booking tool / email marketing]. I'll connect
[tool] to the site as described above. Their fees and support are
between you and the provider.
OLD SITE: I'll move the content from [pages] on your current site.
Other pages and posts aren't moved.
DESIGN APPROVAL: [2] rounds of changes on the homepage design and
[1] on inner pages. The design is approved when you reply "approved"
by email. New layouts or styles after approval are a change.
TESTING: I test on current versions of [browsers] and on [phone /
tablet / desktop] screen sizes.
SEARCH AND ACCESSIBILITY: I set page titles, descriptions, heading
structure and image alt text fields. Search rankings and traffic
aren't promised. [Name any accessibility standard you've agreed.]
LAUNCH AND AFTER: Launch includes [number] days of fixes for anything
that doesn't work as agreed. Content updates and new requests after
that are quoted per request or as a monthly plan.
FEEDBACK: [CLIENT CONTACT] sends one combined list per round and has
the final say on approvals.
For more exclusion wording, the out-of-scope section examples include a web design list and before/after rewrites so the lines don't read as warnings.
Where this fits
These lines work best written before you quote, so the price matches the boundary. A practical order:
- Ask your intake questions. If the brief is vague, the AI hidden-dependency check helps you spot what's missing.
- Write the scope summary using the map above, and get the client to confirm it in writing.
- During the project, check each new request against the summary and reply with options.
The client onboarding checklist shows where each step sits between the first call and kickoff.
The limits
- A scope summary doesn't stop requests. It makes them easier to answer. Clients will still ask, and some requests are worth saying yes to.
- It only covers what you wrote. If something comes up that isn't on the map, treat it as a gap. Clarify it with the client now, and add a line next time.
- It isn't a contract. If the client disputes payment or ownership, the contract is what counts.
Want the full workflow?
The Scope Guard & Client Onboarding Kit turns this into a repeatable process from first brief to change request:
- a client intake brief and a one-page scope-summary template
- an AI prompt pack, including a hidden-dependency audit
- a change-request form and change log
- ten email scripts for the moments where scope usually slips
- an onboarding checklist, plus a fictional worked example that follows a small website project through every stage
The templates come as .docx and .md, with CSV checklists for Google Sheets or Notion. It works with any chat AI assistant. It isn't a contract and it isn't legal advice.
The kit isn't on sale yet. See what's in the kit