Scope of Work Template for Web Design Projects

A web design project without a scope of work is a project waiting to go wrong. The client imagines one thing, you build another, and the gap between those two visions gets filled with awkward emails, unpaid revisions, and damaged relationships.

A solid scope of work eliminates that gap. It spells out exactly what you are building, how many pages, what functionality, how many revision rounds, and when payment is due. Both sides sign it. Both sides are protected.

This guide walks you through every section your web design SOW needs, explains why each one matters, and gives you a complete template you can copy and customise for your next project.

Why Web Designers Need a Scope of Work

Freelance web designers and small agencies lose more money to scope creep than almost any other profession. The reasons are predictable:

• Clients do not understand what goes into building a website
• “Can you just add one more page?” sounds small but takes hours
• Design is subjective, so revision requests are never-ending without a cap
• Technical requirements often surface mid-project when someone says “oh, we also need e-commerce”

A scope of work prevents all of this. It transforms a handshake agreement into a documented project plan that both parties have reviewed and approved.

Beyond protection, a good SOW also makes you look professional. Clients trust designers who present structured documents over those who say “yeah, I’ll sort it.”

What Your Web Design SOW Must Include

Every web design scope of work needs these sections. Skip one and you leave a gap that the client will fill with their own assumptions.

1. Project Overview

Start with a plain-English summary of the project. This is not the place for technical jargon. Write it so the client’s business partner — who was not in the initial meeting — can read it and understand what is being built.

Include:

• The client’s business name and primary contact
• Your business name and primary contact
• A one-paragraph project description
• The project start date and estimated completion date
• The total project fee

2. Sitemap and Page List

This is where most web design SOWs fail. Listing “a website” is meaningless. You need to list every single page that will be designed and developed.

For a typical small business website, this might look like:

• Homepage
• About Us
• Services (hub page)
• Service 1: Web Design
• Service 2: SEO
• Service 3: Content Marketing
• Portfolio (with 6 project entries)
• Blog (listing page + 3 initial posts)
• Contact
• Privacy Policy
• Terms of Service

Count those pages. The number matters because it directly affects your timeline and pricing. If the client later asks for three more service pages, you can point to this list and say those were not included.

3. Design Phase Deliverables

Break the design phase into clear steps with specific outputs:

Wireframes

• Number of unique page layouts to be wireframed (e.g., 5 unique templates)
• Wireframe tool (Figma, Adobe XD, pen and paper)
• Number of revision rounds (recommend 2)
• Approval process (written sign-off before moving to visual design)

Visual Design Mockups

• Number of homepage concepts (typically 2-3)
• Number of inner page designs (typically 3-4 unique layouts)
• Desktop and mobile versions (specify both)
• Number of revision rounds (recommend 2-3)
• What constitutes a “revision” vs. a “new direction”

This last point is critical. A revision is changing the button colour from blue to green. A new direction is scrapping the entire layout and starting again. Your SOW should define this boundary.

Brand Assets

• Will you create a logo? If so, how many concepts and revision rounds?
• Colour palette selection
• Typography selection
• Icon set or illustration style
• Image sourcing (stock photos, client-provided, custom photography)

4. Development Phase

Specify the technical scope clearly:

Technology Stack

• CMS or framework (WordPress, Webflow, custom HTML/CSS, Next.js, etc.)
• Whether the client will be able to edit content themselves
• Any plugins, themes, or third-party integrations

Functionality List every functional element:

• Contact form (number of forms, fields, where submissions go)
• Newsletter signup (integration with Mailchimp, ConvertKit, etc.)
• Social media feeds or links
• Google Maps embed
• Analytics setup (Google Analytics 4, Search Console)
• Cookie consent banner
• Blog functionality (categories, tags, author pages)
• E-commerce (if applicable — number of products, payment gateway, shipping)

Responsive Design

• Which screen sizes will be tested (desktop, tablet, mobile)
• Minimum browser support (Chrome, Firefox, Safari, Edge — specify versions if needed)
• Whether you will support Internet Explorer (hopefully not)

5. Content Responsibility

State clearly who is providing:

• Page copy (headlines, body text, calls to action)
• Images and photography
• Videos
• Testimonials and case studies
• Legal pages (privacy policy, terms)

If the client is providing content, set a deadline. Something like: “All page content must be delivered by [date]. Development cannot begin until content is received. Delays in content delivery will push the project timeline accordingly.”

If you are writing the content, specify word counts per page and include it as a separate line item. Link this to your copywriter scope of work if applicable.

6. Timeline and Milestones

Break the project into phases with dates:

Include a note that timelines assume prompt client feedback. A common clause: “Each phase requires written client approval before the next phase begins. Delays in client feedback will extend the project timeline by an equivalent duration.”

7. Revision Policy

This section saves more arguments than any other. Be specific:

• Number of revision rounds per phase (e.g., 2 rounds for wireframes, 3 rounds for design, 2 rounds for development)
• What counts as one round (all feedback collected and submitted at once, not drip-fed over a week)
• Cost of additional revisions beyond the included rounds (e.g., £75/hour)
• Turnaround time for revisions (e.g., 3 business days)
• Definition of revision vs. new scope (changing copy is a revision; adding a new page is new scope)

8. Browser and Device Testing

Specify exactly what you will test:

• Browsers: Chrome (latest), Firefox (latest), Safari (latest), Edge (latest)
• Devices: Desktop (1920px, 1440px), Tablet (768px), Mobile (375px)
• Operating systems: Windows, macOS, iOS, Android

State what is excluded: “Testing on legacy browsers (Internet Explorer, older mobile devices) is not included. If legacy browser support is required, this will be quoted separately.”

9. Hosting, Domain, and Post-Launch

Specify who is responsible for:

• Domain registration and renewal (client-owned recommended)
• Hosting account and costs (client-owned recommended)
• SSL certificate
• Email hosting
• DNS configuration
• Post-launch support period (e.g., 30 days of bug fixes included)
• Ongoing maintenance (quoted separately, or offered as a monthly retainer)

10. Payment Terms

Be explicit:

• Total project fee
• Payment schedule (e.g., 50% deposit, 25% on design approval, 25% on launch)
• Payment method (bank transfer, Stripe, PayPal)
• Payment terms (due within 14 days of invoice)
• Late payment fees (e.g., 2% per month on overdue amounts)
• Kill fee (if the client cancels mid-project, what do they owe?)

Link to your freelance invoice template for the actual billing documents.

11. Ownership and Licensing

Clarify intellectual property:

• The client owns the final website and its content upon full payment
• You retain the right to display the project in your portfolio
• Third-party assets (stock photos, fonts, plugins) are licensed, not owned
• If the project is cancelled or payment is not received, you retain ownership of all work

12. Change Request Process

Define how changes beyond the original scope are handled:

1. Client submits a change request in writing (email is fine)
2. You provide a quote for the additional work within 2 business days
3. Client approves the quote in writing
4. Work begins on the change request
5. Change requests are billed separately or added to the final invoice

This process prevents the “can you just…” problem that plagues web design projects.

Full Web Design Scope of Work Template

Below is a complete template you can copy and adapt. Replace the bracketed text with your specific project details.

SCOPE OF WORK — WEB DESIGN PROJECT

Date: [Date]

Client: [Client Business Name] Client Contact: [Name, Email, Phone]

Designer: [Your Business Name] Designer Contact: [Name, Email, Phone]

1. Project Summary

[Your Business Name] will design and develop a [number]-page website for [Client Business Name] using [CMS/platform]. The website will [one-sentence description of purpose — e.g., “showcase the client’s property portfolio and generate enquiries through a contact form”].

Project Start Date: [Date] Estimated Completion Date: [Date] Total Project Fee: [Amount]

2. Pages and Sitemap

The following pages are included in this project:

1. Homepage
2. About
3. [Service/Product Page 1]
4. [Service/Product Page 2]
5. [Service/Product Page 3]
6. [Portfolio/Gallery]
7. Blog (listing page)
8. Contact
9. Privacy Policy
10. Terms & Conditions

Total pages: [Number]

Any additional pages requested after signing this SOW will be quoted separately at [rate] per page.

3. Design Deliverables

Wireframes:

• [Number] unique page layouts wireframed in [Figma/tool]
• 2 rounds of revisions included
• Client sign-off required before visual design begins

Visual Design:

• [Number] homepage concepts
• [Number] unique inner page layouts (desktop + mobile)
• 3 rounds of revisions included
• Client sign-off required before development begins

Brand Assets Included:

• [Logo design / not included]
• Colour palette
• Typography selection
• [Number] stock images sourced and licensed

4. Development

Platform: [WordPress / Webflow / Custom / etc.]

Functionality included:

• Responsive design (desktop, tablet, mobile)
• Contact form with email notifications to [email]
• [Newsletter integration with [platform]]
• Google Analytics 4 setup
• Google Search Console verification
• Cookie consent banner
• [Blog with categories]
• [Any other functionality]

Not included:

• E-commerce functionality
• Custom web applications
• Ongoing content writing
• [Anything else excluded]

5. Content

Client is responsible for providing:

• All page copy (headlines, body text, CTAs)
• Business photographs
• Testimonials
• Logo files (if existing)

Content deadline: All content must be received by [date]. Delays in content delivery will delay the project timeline accordingly.

[Designer] is responsible for:

• [Number] stock images
• Content formatting and placement
• SEO meta titles and descriptions for all pages

6. Timeline

7. Revisions

• Wireframes: 2 rounds included
• Visual Design: 3 rounds included
• Development: 2 rounds included
• One revision round = all feedback submitted at once (not individual requests over time)
• Additional revisions beyond included rounds: [rate] per hour
• A revision is a modification to existing elements. Adding new pages, features, or sections constitutes new scope and will be quoted separately

8. Browser and Device Support

Supported browsers: Chrome, Firefox, Safari, Edge (latest versions) Supported devices: Desktop (1440px+), Tablet (768px), Mobile (375px) Not supported: Internet Explorer, browsers more than 2 versions old

9. Hosting and Domain

• Domain: [Client-owned / to be registered by designer]
• Hosting: [Provider] at [cost/year], [client-owned / managed by designer]
• SSL: Included with hosting
• Email: [Included / not included / client to arrange separately]

10. Post-Launch Support

• 30-day support period included after launch (bug fixes only)
• Bug = something that does not work as specified in this SOW
• Feature requests and content changes are not bugs
• Ongoing maintenance available at [rate/month] — quoted separately

11. Payment

Payment method: Bank transfer to [account details] / [Stripe/PayPal link] Payment terms: Due within 14 days of invoice date Late payment: 2% monthly interest on overdue balances Cancellation: If the project is cancelled by the client, all completed work is billed at [rate/hour] or the deposit is retained, whichever is greater

12. Ownership

• Upon full payment, the client owns the completed website, its design, and all custom code
• [Designer] retains the right to feature this project in their portfolio
• Third-party assets (stock images, fonts, plugins) remain subject to their respective licences
• Until full payment is received, all work remains the property of [Designer]

13. Change Requests

Any work not described in this SOW requires a written change request:

1. Client emails the change request
2. [Designer] provides a quote within 2 business days
3. Client approves the quote in writing
4. Work proceeds and is billed as agreed

Signatures

Client: _________________________ Date: _____________

Designer: _________________________ Date: _____________

Common Mistakes in Web Design SOWs

Not listing every page. “A website” is not a scope. List every page by name. If you wrote “approximately 10 pages,” the client will expect 15.

Skipping the content deadline. Clients delay content for weeks, then blame you for the project running late. A documented content deadline with a timeline-delay clause solves this.

Unlimited revisions. Offering unlimited revisions sounds generous. In practice, it means the client never has to make a decision because they can always change their mind. Cap revisions. Charge for extras.

Not defining browser support. A client will test the site on their ancient iPad and find something that looks odd. If you have documented browser support, you can explain why that device is not included.

Vague functionality. “The website will have a contact form” — how many forms? How many fields? Where do submissions go? Does it need a CAPTCHA? Specificity prevents arguments.

No kill fee. Clients cancel projects. If you have spent 40 hours on wireframes and design and the client cancels, you should be compensated. A kill fee clause ensures you are.

How This SOW Connects to Your Invoice

Once the project is underway, you will need to invoice based on the milestones in your SOW. Your web design invoice should reference the SOW directly — matching the milestone names, amounts, and dates.

This creates a paper trail: the SOW defines the work, the invoice bills for it, and the payment receipt confirms it was paid. Three documents, fully linked.

For a broader look at creating effective scopes of work across any industry, see our complete scope of work guide or browse scope of work examples across 10 different industries.

Final Thoughts

A web design SOW takes 30 minutes to write properly. That half hour will save you from hours of unpaid revisions, uncomfortable conversations about what was and was not included, and the slow resentment that builds when both parties feel the other is being unreasonable.

Write the SOW. Be specific. Get it signed. Then build the website knowing exactly what you owe and exactly what you are owed.