Scoping a website project means turning a client’s goals into a written list of exact pages, features, integrations, and responsibilities, plus what’s excluded, before any design or development starts. Do it through a short set of discovery questions, write the answers down as a scope of work, and get it signed before the proposal or contract locks in a price.
Most scope creep doesn’t start with a pushy client. It starts with a scope nobody wrote down. Someone says “a modern marketing site with a blog” in a kickoff call, everyone nods, and six weeks later you’re arguing about whether a resource library was ever part of the deal. It wasn’t written anywhere, so there’s nothing to point to.
I’ve scoped more WordPress builds than I can count over 15+ years of doing this work, a lot of it for agencies. The projects that stay profitable all have one thing in common: a scope of work that names the pages, the integrations, and the exclusions before a single line of code gets written. Here’s the method, plus a copy-paste template and a filled example.
What questions do you ask to scope a website project?
Scoping starts with discovery, not a template. You need answers to a short set of questions that surface the real scope, not the one-line pitch the client gave you.
- What does this site need to do? Not “look modern.” Book consultations, sell products, generate leads. The goal decides which pages and features matter.
- Who is it for? A B2B buyer researching vendors needs different pages than a homeowner comparing local contractors.
- What exists today? Branding, existing copy, a domain, an old site’s URLs you need to preserve for SEO. This decides how much you’re building from scratch.
- What has to connect to what? CRM, email platform, payment processor, booking tool. Integrations are where scope quietly balloons if you don’t ask up front.
- Who’s providing the content? Copy, photography, video. If the client is writing their own pages, your timeline depends on them, and that needs to be in writing.
- What’s the real deadline, and why? A trade show or a rebrand launch changes what you can promise; a soft deadline gives you room to negotiate scope if things shift.
We built a longer version of this into a full web design questionnaire you can send clients before the kickoff call. The answers are the raw material for the scope of work below.
What goes in the deliverables list?
The deliverables list is the part of the scope that gets built, and it needs to be specific enough that two different developers would build the same thing from it.
- Pages, named individually. Not “a handful of pages.” Home, About, each Service page, Contact, every landing or resource page. If the count matters to your price, the list matters more.
- Templates, not just pages. A blog needs an index and a single-post template. Say how many unique templates you’re building, since that’s real design and dev work.
- Integrations. Every third-party connection: CRM, email marketing, booking, payment, live chat, analytics. Name the tool, not just “integrations.”
- Content responsibilities. Who writes the copy, who supplies images, who owns the SEO metadata. The most common gap in a rushed scope, and the one that stalls timelines longest.
- Functionality beyond static pages. Forms and where they send, search, filtering, e-commerce, gated content, a client login. Each is its own line, not a footnote under “custom features.”
Write the list like you’d hand it to a developer who’s never talked to the client. If it’s specific enough for that, it holds up when someone asks for “just one more small thing.”
What should you explicitly leave out of scope?
The exclusions section is the most valuable part of a scope of work, and the part most agencies skip because it feels negative to write. It isn’t. It’s what protects the price you quoted.
List, by name, what a reasonable client might assume is included but isn’t: copywriting, photography, stock image licensing, logo or brand design, ongoing maintenance and hosting, a second design concept, more revision rounds than you’ve allotted, and anything mentioned in conversation that never made the deliverables list. If it wasn’t written down as in, write it down as out.
It doesn’t need to read like a legal document. One plain sentence per item is enough: “Copywriting is not included; the client provides final page text.” The point isn’t to sound formal, it’s to leave no room for “I thought that was included.”
How do you structure milestones, assumptions, and approvals?
A scope without milestones is a wish list with a deadline attached. Break the project into stages the client formally approves before you move to the next one, and write down the assumptions and client responsibilities each stage depends on: content due dates, who’s providing hosting and account access, and how many business days the client has to review before a milestone counts as accepted.
- Discovery and content collection. Questionnaire answers and client-supplied assets gathered and confirmed.
- Design approval. Wireframes or visual design signed off before development starts, so you’re not building against a moving target.
- Development and staging review. The built site reviewed on a staging URL, not the live domain.
- Client review and revisions. The agreed number of rounds, with a clear line between a revision and a new request.
- Launch. Site goes live, redirects verified, a short post-launch check confirms nothing broke.
Each milestone needs a written approval, even a one-line email that says “approved.” That’s what marks a stage as done, so a client can’t reopen design decisions during development and call it a revision.
How do you handle work that falls outside the scope?
Scope creep isn’t a personality problem with certain clients. It’s a process gap. The fix isn’t a firmer tone, it’s a documented change process everyone agreed to before the project started.
| Metric | Figure |
|---|---|
| Projects that experienced scope creep or uncontrolled change in the past 12 months | 52% |
| Same figure five years earlier | 43% |
Source: Project Management Institute, Pulse of the Profession, 2018.
That’s the default outcome of a project without a clear scope and a clear process for changing it, not a difficult-client problem. When a request isn’t on your deliverables list, the fix is the same every time: write down what’s being asked, quote the added time or cost, and get a yes before anyone touches it. We laid out the exact steps in our change request process, and if scope creep has already been costing you margin, our guide on taking control of scope creep covers the patterns that let it happen in the first place.
- A real scope names every page, template, and integration individually. “A modern site with a blog” isn’t a scope, it’s a pitch.
- The exclusions list protects your price more than any other section. If it wasn’t written as in-scope, write it as out.
- More than half of projects run into scope creep, per PMI, so a documented change process isn’t optional overhead, it’s the default fix.
- A written scope feeds two other documents: the proposal that wins the project and the contract that makes it binding. Write it before either one.
A copy-paste website scope of work template
Fill in the brackets and this covers most marketing-site projects.
WEBSITE SCOPE OF WORK Project: [Project or site name] Prepared by: [Your agency] Date: [Date] 1. PROJECT GOAL [One or two sentences on what this site needs to accomplish.] 2. DELIVERABLES - Platform: [WordPress / other] - Pages: [list every page by name] - Templates: [home, single post, service page, landing page, etc.] - Integrations: [CRM, email platform, booking tool, payment processor, etc.] - Functionality: [forms, search, filtering, e-commerce, gated content, login, etc.] - Content responsibility: [who provides copy, images, and SEO metadata] - Responsive on mobile, tablet, and desktop 3. OUT OF SCOPE - [Copywriting] - [Photography or stock image licensing] - [Logo or brand design] - [Ongoing maintenance and hosting] - [Pages or features not listed in Section 2] - [Revisions beyond the number listed in Section 5] 4. ASSUMPTIONS AND CLIENT RESPONSIBILITIES - Content due by: [date] - Access needed from client: [hosting, domain, existing accounts] - Approval turnaround: [number] business days per milestone 5. MILESTONES AND APPROVAL - Discovery and content collection: [date] - Design approval: [date] - Development and staging review: [date] - Client review and revisions ([number] rounds included): [date] - Launch: [date] Each milestone requires written client approval before work begins on the next stage. 6. CHANGE PROCESS Any request outside Sections 2-4 is handled as a change request: documented in writing, quoted for added time or cost, and approved before work starts. See our [change request process] for the exact steps. Prepared by: ____________________ Date: __________ Approved by: ____________________ Date: __________
A filled example: a 10-page marketing site
Here’s the same skeleton filled for a hypothetical 10-page marketing site. The details are invented; the structure is exactly what we’d use on a real project.
WEBSITE SCOPE OF WORK Project: Marketing site redesign Prepared by: Example Design Agency Date: September 2026 1. PROJECT GOAL A redesigned marketing site that clearly explains the client's services and turns search and referral traffic into booked consultations. 2. DELIVERABLES - Platform: WordPress - Pages: Home, About, Services (3 individual pages), Case Studies (index + template for 4 initial entries), Blog (index), Contact, Careers - Templates: home, service page, case study, blog index, single post - Integrations: HubSpot form submissions, Calendly for consultation booking, Google Analytics - Functionality: consultation booking widget on Contact and each Service page, blog search, footer newsletter signup - Content responsibility: client provides final page copy and case studies; agency provides on-page SEO titles and meta descriptions - Responsive on mobile, tablet, and desktop 3. OUT OF SCOPE - Copywriting (client-provided) - Photography (client-provided or stock licensed) - Logo and brand guideline development (existing assets used) - Ongoing maintenance and hosting after launch - Any page or feature not listed in Section 2 - Revisions beyond the two rounds listed in Section 5 4. ASSUMPTIONS AND CLIENT RESPONSIBILITIES - Content due by: two weeks after design approval - Access needed from client: hosting login, domain registrar access, existing HubSpot and Calendly accounts - Approval turnaround: three business days per milestone - Other: current site's top 10 URLs preserved or redirected to protect rankings 5. MILESTONES AND APPROVAL - Discovery and content collection: complete before design begins - Design approval: homepage and one interior template approved before build starts - Development and staging review: full site reviewed on staging URL - Client review and revisions (two rounds included): staging build only - Launch: DNS cutover, redirects verified, post-launch check within 48 hours Each milestone requires written client approval before work begins on the next stage. 6. CHANGE PROCESS Any request outside Sections 2-4, including a new page, a new integration, or added functionality, is handled as a change request: documented in writing, quoted for added time, and approved before work starts. Prepared by: Example Design Agency Date: September 2026 Approved by: ________________________________________ Date: __________
Notice what makes this usable: the page count is exact, the integrations are named tools instead of “integrations,” and the redirect assumption is written down instead of assumed. That’s the difference between a scope that prevents an argument in week four and one that starts it.
Once the scope is written, the fastest way to turn it into a signed project is a proposal and a contract that reference it directly. We covered both in our guides to a web design proposal and a web design contract, and if you want a fast, itemized starting range before you price the work, our website cost calculator gives you a working number in seconds.
When yours is written, send it to us. We’ll come back with a fixed quote you can mark up, usually within two business hours, and build the site under your brand while you keep the client and the relationship. Send us the scope and we’ll take it from there.
Scoping is stage two of the seven-stage website project workflow.
Once the scope is fixed and you have a partner quote, run the numbers through our white-label margin calculator to see what the project actually leaves you after your team’s time.
A tight scope is what makes a fixed price safe; the trade-offs are in fixed price vs hourly vs retainer.
Write the handoff into the scope too; here is what to hand the client at launch.
However tight the scope, changes still arrive, so it helps to have a routine for handling client change requests when they do.
When a request does change the scope, price or date, it needs a change order rather than a verbal yes.
Frequently asked questions
What is website scope of work?
A written document listing exactly what a project includes: the pages, templates, integrations, and functionality being built, who’s responsible for content, and what’s excluded. It’s the reference document a proposal and contract both point back to when a question comes up mid-project.
How detailed should a website scope of work be?
Detailed enough that a developer who never spoke to the client could build the right thing from it. Name every page individually, name integrations by tool, and write down who provides the content. Vague language like “a handful of pages” is where disputes come from later.
What’s the difference between a scope of work and a proposal?
The scope of work is the detailed build list: pages, features, exclusions, assumptions, and milestones. The proposal is the client-facing document built from that scope, written to win the project rather than to run it day to day.
Who writes the scope of work, the agency or the client?
The agency writes it, built from the client’s answers during discovery. A questionnaire is the fastest way to gather what you need before drafting the scope, so the document reflects what the client actually asked for instead of what you assumed they meant.
What happens if a client asks for something outside the scope of work?
It gets handled as a change request, not a favor. Document what’s being asked, quote the added time or cost, and get approval before any work starts. A scope with a written change process built in makes this a routine step instead of an argument.
Get a free consultation and a fixed quote, usually within one business day, delivered under your agency's brand.